- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
My Environment is:
2012 R2 Cluster
Teamed 82599
Hyper-V
I am seeing this issue, intermittently, unload load - but only on a single host.
BugCheck 1E, {ffffffffc0000005, fffff801685c700e, 0, ffffffffffffffff}
Probably caused by : ixn64x64.sys ( ixn64x64+2e00e )
KMODE_EXCEPTION_NOT_HANDLED (1e)
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801685c700e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
ixn64x64+2e00e
STACK_TEXT:
ffffd000`218fc438 fffff800`e27f560a : 00000000`0000001e ffffffff`c0000005 fffff801`685c700e 00000000`00000000 : nt!KeBugCheckEx
ffffd000`218fc440 fffff800`e276aeed : ffffd000`218fcbb0 00000000`00000000 ffffd000`218fd3a8 ffffd000`218fc5b0 : nt!KiFatalExceptionHandler+0x22
ffffd000`218fc480 fffff800`e26d1b25 : 00000000`00000001 fffff800`e2613000 ffffd000`218fd300 ffffe000`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd000`218fc4b0 fffff800`e26d5ede : ffffd000`218fd3a8 ffffd000`218fd0b0 ffffd000`218fd3a8 ffffe000`aaca9000 : nt!RtlDispatchException+0x1a5
ffffd000`218fcb80 fffff800`e276f5c2 : ffffe801`b5e6e1a0 fffff801`66edda53 00000000`00000000 ffffe801`bb0e6cf0 : nt!KiDispatchException+0x646
ffffd000`218fd270 fffff800`e276dafe : 00000200`00000001 ffffe000`00000400 00000000`00000002 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd000`218fd450 fffff801`685c700e : ffffe801`00000801 ffffe000`aaca9000 ffffe801`bb0e6cf0 ffffe000`aaca9000 : nt!KiGeneralProtectionFault+0xfe
ffffd000`218fd5e0 fffff801`685a5650 : ffffe000`aa85a110 ffffe000`aaca9000 ffffe000`aacb6740 ffffe000`0000000b : ixn64x64+0x2e00e
ffffd000`218fd690 fffff801`685a5a01 : ffffe000`a9f91ae0 00000001`0000000b 00000001`0000000b ffffe000`aac65000 : ixn64x64+0xc650
ffffd000`218fd700 fffff801`685a4ec8 : ffffd000`218fd829 00000001`0000000b 00000000`00000000 00000000`00000000 : ixn64x64+0xca01
ffffd000`218fd770 fffff801`66edfe12 : ffffe801`c3e65a80 fffff801`68175222 00000000`00000003 ffffe801`c3e656c0 : ixn64x64+0xbec8
ffffd000`218fd7b0 fffff800`e26c7d50 : 00000000`00000000 ffffe000`a9cd5240 ffffd000`218d3180 ffffd000`218d3180 : NDIS!ndisInterruptDpc+0x1a3
ffffd000`218fd890 fffff800`e26c7007 : 00000000`00000014 00000000`002cb415 ffffe000`ade5f1f0 ffffd000`218d3180 : nt!KiExecuteAllDpcs+0x1b0
ffffd000`218fd9e0 fffff800`e27674ea : ffffd000`218d3180 ffffd000`218d3180 ffffd000`218dfbc0 ffffe801`d1d11880 : nt!KiRetireDpcList+0xd7
ffffd000`218fdc60 00000000`00000000 : ffffd000`218fe000 ffffd000`218f8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
Is this a known issue? I am running the very latest drivers.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello mrrorschach,
We are moving your question to the/community/wired Wired Ethernet Forums so you can get assistance about this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mrrorschach,
Thank you for contacting Intel.
Please provide the information below so we can further check on the issue:
1. Network Adapter's Model -
2. Driver version:
3. PROSet version:
We'll wait for your reply.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
As mentioned:
82599 10 GbE ControllerDriver version version 20.0.
I am running whatever PROSet is bundled with version 20.0.
Is this enough?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mrrorschach,
Thanks for providing the details.
I'll further check on this and will get back to you if I find anything.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mrrorschach,
Good day.
In order to further understand your environment better, we would like to request the information below:
1. When and where do you encounter the issue, any specific place?
2. Your clustering set up
3. Do you encounter this error prior to installing Driver version 20.0?
Looking forward to your response.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
1. Under load, no specific conditions trigger the crash.
2. Clustering set-up, 4 node fail-over cluster, only virtual machine roles, all iSCSI.
3. I have only ever seen this issue under driver 2.0.
Thank you,
Nick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mrrorschach,
Thanks for providing the additional details. This is helpful for us to study your case.
In relation to item # 3, I understand you are only seeing the issue using the latest driver ver 20.0.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi mrrorschach,
I'm sorry we weren't able to find anything from logs.
We would like to further understand your configuration and what would you like to achieve from the configuration. Kindly provide your system information:
1. System Configuration:
a. Software Details:
b. OS: Windows 2012 R2 Cluster Hyper-V
c. Proset version: 20.0
2. Hardware Configuration:
a. Server brand/model:
b. Teamed 82599
- how many adapters are in the team?
- total number of adapters in the server? (teamed and individual)
c. Driver versions of the adapters:
d. Teaming mode:
3. Steps to replicate:
4. Expected result:
5. Actual result:
We look forward to your reply.
Sincerely,
Sandy

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page