Blue screen with i350 and X520 Adapters

[DKarm]

Hi!

I've just had the same issue with 19.5.303.0 drivers on Windows 2012 R2 (but it's not Hyper-V).

Three are two i350 network connections (teamed) and two X520 adapters (not teamed).

Crash dump analysis:

KMODE_EXCEPTION_NOT_HANDLED (1e)

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff8004dae617a, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception

ADDITIONAL_DEBUG_TEXT:

You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff8021e60f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 53bdbd2d

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:

ixn64x64+b17afffff800`4dae617a 41ff5210 call qword ptr [r10+10h]

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff8021e7f16fa to fffff8021e75faa0

STACK_TEXT:

ffffd000`924ab478 fffff802`1e7f16fa : 00000000`0000001e ffffffff`c0000005 fffff800`4dae617a 00000000`00000000 : nt!KeBugCheckExffffd000`924ab480 fffff802`1e766fed : ffffd000`924abbf0 00000000`00000000 ffffd000`924ac3e8 ffffd000`924ab5f0 : nt!KeRegisterNmiCallback+0x17effffd000`924ab4c0 fffff802`1e6e9d35 : 00000000`00000001 fffff802`1e60f000 ffffd000`924ac300 00000001`00000000 : nt!_chkstk+0x5dffffd000`924ab4f0 fffff802`1e6ee0ee : ffffd000`924ac3e8 ffffd000`924ac0f0 ffffd000`924ac3e8 ffffe000`63a02000 : nt!RtlWalkFrameChain+0x33dffffd000`924abbc0 fffff802`1e76b6c2 : ffffd000`924ac302 ffffe800`9dda1030 ffffd000`924ac400 00000000`00000000 : nt!RtlVirtualUnwind+0xedeffffd000`924ac2b0 fffff802`1e769bfe : ffffd000`00000000 fffff800`4c494ee8 ffffe000`63a001a0 ffffe800`9a11ddf0 : nt!setjmpex+0x38b2ffffd000`924ac490 fffff800`4dae617a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!setjmpex+0x1deeffffd000`924ac620 fffff800`4dae76df : ffffe000`5dbeb540 00000000`00000005 ffffe000`63810e00 00000000`00000005 : ixn64x64+0xb17affffd000`924ac690 fffff800`4dae7a01 : ffffe000`63810e00 00000001`00000005 00000001`00000005 00000001`00000005 : ixn64x64+0xc6dfffffd000`924ac700 fffff800`4dae6ec8 : ffffd000`924ac829 00000001`00000005 ffffd000`924ac7e8 00000000`00000000 : ixn64x64+0xca01ffffd000`924ac770 fffff800`4c429e02 : 00000000`00000000 ffffe000`5cdeb268 00000000`00000000 fffff780`00000320 : ixn64x64+0xbec8ffffd000`924ac7b0 fffff802`1e6bc580 : 00000000`00000000 fffff802`1e6af3ee 00000000`000025dc ffffd000`924875c0 : NDIS!NdisGetThreadObjectCompartmentId+0x472ffffd000`924ac890 fffff802`1e6bb837 : 00000000`00000000 fffff800`4dabb6d7 ffffe800`9b6d51f0 ffffd000`92482180 : nt!ExUnblockOnAddressPushLockEx+0x12f4ffffd000`924ac9e0 fffff802`1e7635ea : ffffd000`92482180 ffffd000`92482180 ffffd000`9248e3c0 ffffe800`9ff6a040 : nt!ExUnblockOnAddressPushLockEx+0x5abffffd000`924acc60 00000000`00000000 : ffffd000`924ad000 ffffd000`924a7000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efaSTACK_COMMAND: kb

FOLLOWUP_IP:

ixn64x64+b17afffff800`4dae617a 41ff5210 call qword ptr [r10+10h]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: ixn64x64+b17a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ixn64x64

IMAGE_NAME: ixn64x64.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

---------

[SYeo3]

Hi Dmitry_Karmazin,

Thank you for posting.

We'll check on your issue and will get back to you on our findings.

Sincerely,

Sandy

[SYeo3]

Hi Dmitry_Karmazin,

We would like to request for your system configuration:

1. System Configuration:

a. Software Details:

b. OS: Windows 2012 R2 (but it's not Hyper-V).

c. Proset version: 19.5.303.0

2. Hardware Details:

a. Server brand/model:

b. 2x i350 network connections (teamed)

c. 2x X520 adapters (not teamed)

d. total number of adapters in the server? (teamed and not teamed)

e. Network Adapter driver versions: i350 and X520

f. Teaming mode:

3. Steps to replicate:

4. Expected result:

5. Actual result:

6. Have you tried using Software version 20.0?

We'll wait for your reply.

Sincerely,

Sandy

[DKarm]

Hi, Sandy_Intel!

This server is one of 3 nodes in cluster, hosting MS Scale-Out File Server.

Server is Supermicro's X9DRD-EF platform.

2x i350 are teamed in Switch Independent mode with dynamic balancing mode (Win2012R2 native teaming). This is for server management.

2x X520 are not teamed, each adapter configured to use it's own tagged VLAN (VLAN created by means of Intel's driver). These adapters are used for SMB 3.0 traffic.

No other adapters in server.

Drivers:

i350 - e1r64x64.sys - version 12.11.97.1

x520 - ixn64x64.sys - version 3.9.58.9101

I was rebuilding virtual disks on storage spaces pool, when server crashed. But that happened only one time and never repated since then. Although I run rebuild multiple times on multiple virtual disks (because I need to replace 12 hard drives). And I hadn't installed 20.0 software yet.

[st4]

Hi Dmitry_Karmazin,

Thanks for the info. we will check on this.

rgds,

wb

[Richmond_S_Intel]

Hi Dmitry,

Can you provide the exact model of the i350 and x520 adapters that you are using? Are these onboard NICs or add-in adapters? Just to make sure that I get the specifics.

E.g I350-T1, I350-T4, I350-AT2 controller, X520-T2, X520-DA2

Thanks,

Rich

[DKarm]

Hi, Rich!

i350 is an integrated chip (Supermicro X9DRD-7LN4F platform)

X520 is an also supermicro's AOC-STGN-i2S network card (dual SFP+ connectors + E10GSFPSR modules)

[SYeo3]

Thanks for the info, Dmitry_Karmazin.

Sincerely,

Sandy

[SYeo3]

Hi Dmitry_Karmazin,

Thank you for contacting Intel. We regret to inform you that we weren't able to find anything on the dump file and failed to reproduce the issue. However, if this poses risk to you, we suggest to contact your system manufacturer (Supermicro*) for further assistance. This way, they can try to reproduce the issue and possibly on the same server system model.

Thank you for your patience and understanding.

Sincerely,

Sandy