UNSOLVED

amandosoftware

updated

13 years ago

0

29675

January 21st, 2014 06:00

Problems with Teaming and Win2012R2

Have someone Problems with Boradcom Teaming with Windows 2012R2 Server, too?

My Dell R620 has shutdowns wit a Bugcheck failure. Can be that the newest Broadcom driver didn't support 2012r2?

How can i use the broadcom BASP Timing, need co configure Link Aggregation, or is it an other Problem?

See Memory Dump:

MODULE_NAME: basp

 

FAULTING_MODULE: fffff800e8a8d000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP:  5240bbd2

 

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

BUGCHECK_STR:  0x133

 

CURRENT_IRQL:  0

 

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

 

LAST_CONTROL_TRANSFER:  from fffff800e8bfef7c to fffff800e8bdaca0

 

STACK_TEXT: 

ffffd000`218a9e38 fffff800`e8bfef7c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffd000`218a9e40 fffff800`e8ae181b : 00000000`00000000 ffffd000`217f1180 ffffe000`02ea0000 00000000`00000000 : nt!CcTestControl+0x17144

ffffd000`218a9ed0 fffff800`e8c603a3 : ffffe000`01200300 ffffd000`217f1180 ffffd000`00000000 ffffe000`03b64fc0 : nt!KeAreAllApcsDisabled+0x8b

ffffd000`218a9f10 fffff800`e8a24f85 : ffffe000`00fe2940 ffffe000`02173080 ffffd000`217f78c0 fffff800`e8a8d000 : nt!KeClockInterruptNotify+0xe3

ffffd000`218a9f40 fffff800`e8b23343 : ffffd000`2189bb50 fffff800`e8b8fcd3 ffffd000`00000000 00000000`00000000 : hal!HalPerformEndOfInterrupt+0x195

ffffd000`218a9f70 fffff800`e8bdc12a : ffffe000`01200300 ffffe000`03b64fc0 00000000`00000002 ffffe000`07b4f3c8 : nt!ExAcquireRundownProtection+0xcb

ffffd000`218a9fb0 fffff800`e8bdc50f : ffffe000`07ca95f0 00000000`00000002 00000000`00000000 00001f80`00000200 : nt!KeSynchronizeExecution+0x83a

ffffd000`2189a5f0 fffff800`e8b21e00 : ffffe000`f2650002 00000000`00010008 ffffe000`033fc1a0 ffffd000`2189a8b0 : nt!KeSynchronizeExecution+0xc1f

ffffd000`2189a780 fffff800`e8b21dc2 : 00000000`00000002 ffffe000`029ee540 00000000`00000000 fffff800`006bd8c0 : nt!KeAcquireSpinLockRaiseToDpc+0x70

ffffd000`2189a7b0 fffff800`02d5f9b2 : 00000000`00000282 00000000`00000000 ffffe000`03024000 ffffe000`0aa4f690 : nt!KeAcquireSpinLockRaiseToDpc+0x32

ffffd000`2189a7e0 fffff800`02d60f9f : ffffe000`03ad4000 ffffe000`03ad4000 ffffd000`2189a8c9 00000000`00000000 : basp+0xd9b2

ffffd000`2189a830 fffff800`02d6a237 : ffffe000`03ad4000 ffffe000`03ad4000 ffffe000`07b4f078 00000000`ffffffff : basp+0xef9f

ffffd000`2189a860 fffff800`02d6b676 : ffffe000`04435010 ffffe000`07b4f030 ffffe000`07b4f030 ffffe000`03ae1d78 : basp+0x18237

ffffd000`2189a930 fffff800`006bd9b4 : ffffe000`03ae1d78 ffffe000`07b4f030 00000000`00000000 00000000`00000000 : basp+0x19676

ffffd000`2189aa30 fffff800`006dbe33 : 00000000`00000000 ffffe000`05744920 00000000`00000000 00000000`00000001 : NDIS!NdisSetThreadObjectCompartmentId+0xd74

ffffd000`2189aae0 fffff800`0182532f : ffffe000`041da5a0 ffffe000`07b4f030 ffffd000`00000000 ffffe000`07b4f030 : NDIS!NdisCmRegisterAddressFamilyEx+0x1a9b

ffffd000`2189acc0 fffff800`01823ecc : ffffe000`04055000 ffffe000`07b40000 ffffd000`2189ae90 ffffe000`00000000 : vmswitch+0x632f

ffffd000`2189ae20 fffff800`01823baa : ffffe000`f3f00000 ffffe000`f3f07000 ffffe000`07b4f001 fffff800`01821c01 : vmswitch+0x4ecc

ffffd000`2189af10 fffff800`006b1cde : 00000000`00000000 00000000`00000000 ffffd000`2189afd1 00000000`0000c001 : vmswitch+0x4baa

ffffd000`2189af70 fffff800`006c0892 : ffffd000`2101ff02 fffff800`01834747 ffffe000`00000000 ffffe000`00000001 : NDIS!NdisFreeCloneNetBufferList+0x87e

ffffd000`2189b030 fffff800`006b2cd5 : ffffe000`029491a0 00000000`00000001 00000000`00000000 fffff800`00000001 : NDIS!NdisAllocateNetBufferMdlAndData+0x592

ffffd000`2189b0c0 fffff800`018228d9 : ffffe000`f3f07000 ffffe000`f27de000 ffffe000`07b4f030 ffffe000`07b4f030 : NDIS!NdisMIndicateReceiveNetBufferLists+0xba5

ffffd000`2189b2b0 fffff800`006b4b14 : ffffe000`0290c000 fffff800`008ad701 00000000`00000000 ffffe000`00000021 : vmswitch+0x38d9

ffffd000`2189b440 fffff800`01828b17 : ffffe000`03ff8010 ffffe000`07b4f030 ffffe000`00000000 00000000`00000000 : NDIS!NdisSendNetBufferLists+0x554

ffffd000`2189b620 fffff800`01827be7 : ffffe000`07b4f000 ffffe000`07b4f030 ffffe000`f3f07000 ffffe000`f3f07000 : vmswitch+0x9b17

ffffd000`2189b6f0 fffff800`01827920 : ffffe000`f3771b00 ffffd000`2189b8a0 ffffe000`068e0000 00000000`0000ff02 : vmswitch+0x8be7

ffffd000`2189b7a0 fffff800`00a7e1e0 : 00000000`00000003 ffffe000`068e0102 00000000`00000034 ffffbbeb`000000ca : vmswitch+0x8920

ffffd000`2189b8d0 fffff800`00803e3d : 00000000`00000001 ffffe000`f275c6c0 001bc32d`356990f7 00000000`00000000 : vmbkmclr+0x21e0

ffffd000`2189b950 fffff800`e8ae7d10 : ffffd000`2189baa0 ffffe000`01c8c240 ffffd000`217f1180 ffffe000`026af430 : vmbusr+0x3e3d

ffffd000`2189b9a0 fffff800`e8ae79f0 : ffffe000`00000000 00001f80`00000001 00000000`000000e6 00000000`00000002 : nt!NtTraceEvent+0x1430

ffffd000`2189baf0 fffff800`e8bde7ea : ffffd000`217f1180 ffffd000`217f1180 00000000`00000000 ffffd000`217fd940 : nt!NtTraceEvent+0x1110

ffffd000`2189bc60 00000000`00000000 : ffffd000`2189c000 ffffd000`21896000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efa

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP:

basp+d9b2

fffff800`02d5f9b2 4533c0          xor     r8d,r8d

 

SYMBOL_STACK_INDEX:  a

 

SYMBOL_NAME:  basp+d9b2

 

FOLLOWUP_NAME:  MachineOwner

 

IMAGE_NAME:  basp.sys

 

BUCKET_ID:  WRONG_SYMBOLS

 

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:wrong_symbols

 

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

 

Followup: MachineOwner

  • MTN1206

    5 Posts

    1332

    0

    Posted February 21st, 2014 07:00

    I just upgraded a T710 to Server 2012 R2 a couple of weeks ago, and it developed the same problem. I'm using the Broadcom driver from Nov 2013, which claims 2012 R2 compatibility.  Were you ever able to solve the issue? 

    I'm going to look around for other drivers, but I'm considering trying the builtin Windows NIC teaming feature that was released with Server 2012 instead. We'll see.

  • MTN1206

    5 Posts

    1332

    0

    Posted February 21st, 2014 07:00

    Actually, I just noticed that Broadcom has a newer version of the Windows Management Applications (from Feb 11 2014), which, according to the release notes, includes a newer basp.sys teaming driver (1.6.14) that causes the BSOD. Here's the link if anyone is interested: http://www.broadcom.com/support/ethernet_nic/netxtremeii.php.

    I will try installing this afterhours and see what happens.

  • dlacroix

    4 Posts

    1332

    0

    Posted March 19th, 2014 15:00

    Hi , i'm happy to see im not alone with this grrrrr bug i try so many thing but crash happen ... but i see this afternoon this patch .... i hope that fix the bsod i have ramdomly on 3 of my r620 server .... the crash dump tell its the basp crashing .... so i keep myy finger crossed .... i continu to get you informed on this ... i updated bios updated anything ... put bios maximum performance disable c1 and c1e state etc... all this money for new server and crashing like <ADMIN NOTE: Substitute character removed as per TOU>

  • MTN1206

    5 Posts

    1332

    1

    Posted March 19th, 2014 15:00

    I totally forgot to update this thread after installing the February patch - sorry about that! I can confirm that it completely stabilized the PE T610 we were having trouble with.

  • dlacroix

    4 Posts

    1332

    1

    Posted March 19th, 2014 16:00

    yeah finally somes good news ... i keep my finger crossed ty for you're update
  • 1332

    0

    Posted March 20th, 2014 01:00

    at the moment i use the mircosoft timing, but the performance is not so good.... i'm wasted if the new driver works.