e1i65x64.sys BSOD

kzhud · ‎06-01-2020

0: kd> .trap 0xfffff8015d87a200

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=00000000f322e07f

rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8015d07eb5a rsp=fffff8015d87a390 rbp=fffff8015d87a490

r8=0000000000000000 r9=ffff94879d026eb0 r10=ffff94879d026de0

r11=0000000000000010 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

tcpip!TcpBeginTcbSend+0x103a:

fffff801`5d07eb5a f0ff403c lock inc dword ptr [rax+3Ch] ds:00000000`0000003c=????????

0: kd> lmvm e1i65x64

Browse full module list

start end module name

fffff80e`0b360000 fffff80e`0b3ee000 e1i65x64 (pdb symbols) c:\symbols\e1i65x64.pdb\9865451D8CA14D539528165E96E0B9F61\e1i65x64.pdb

Loaded symbol image file: e1i65x64.sys

Image path: e1i65x64.sys

Image name: e1i65x64.sys

Browse all global symbols functions data

Timestamp: Tue Jun 12 02:01:06 2018 (5B1EB8E2)

CheckSum: 0008A03D

ImageSize: 0008E000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Information from resource tables:

0: kd> kv

*** Stack trace for last set context - .thread/.cxr resets it

# Child-SP RetAddr : Args to Child : Call Site

00 fffff801`5d87a390 fffff801`5d07cf5c : 00000000`0000000a 00000000`00000113 00000000`00000002 00000000`00000000 : tcpip!TcpBeginTcbSend+0x103a

01 fffff801`5d87a610 fffff801`5d06b12d : ffff9487`a0bf3790 00000000`00989680 00000000`00000000 00000000`00000000 : tcpip!TcpTcbSend+0x32c

02 fffff801`5d87a9b0 fffff801`5d04b80d : ffff9487`97bf06ec 00000000`0000bb01 00000000`00000000 00000000`00000000 : tcpip!TcpReceive+0x87d

03 fffff801`5d87aab0 fffff801`5d03a46a : 00000000`00000000 00000000`00000000 fffff801`5d21e2e0 00000000`00000000 : tcpip!TcpNlClientReceivePreValidatedDatagrams+0x2d

04 fffff801`5d87aaf0 fffff801`5d051a3a : ffff9487`9b913a00 ffff9487`993ea8a0 ffff9487`00000006 00000000`00000101 : tcpip!IpFlcReceivePreValidatedPackets+0xc4a

05 fffff801`5d87ad60 fffff801`5ad720e8 : fffff801`5d87b040 00000000`00000002 fffff801`5b243400 fffff801`5d87afc8 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x16a

06 fffff801`5d87ae90 fffff801`5ad7205d : fffff801`5d0518d0 fffff801`5d87afc8 ffff9487`97cb95a0 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78

07 fffff801`5d87af00 fffff801`5d04173c : ffff9487`9bb7add0 fffff801`5d87b040 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d

08 fffff801`5d87af40 fffff801`5cdcb531 : ffff9487`00000010 00000000`00000020 ffff9487`9cbc8fb1 ffff9487`9cb5afb3 : tcpip!FlReceiveNetBufferListChain+0x30c

09 fffff801`5d87b1e0 fffff801`5cdcb027 : ffff9487`9cad8c40 00000000`00000001 ffff9487`00000000 ffff9487`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x141

0a fffff801`5d87b2c0 fffff801`5cdd0eb1 : ffff9487`9b80b1a0 fffff80e`00000000 ffff9487`9b80b1a0 00000000`00000372 : ndis!ndisMTopReceiveNetBufferLists+0x227

0b fffff801`5d87b3c0 fffff801`5ce01716 : ffff9487`9bb7add0 fffff801`5d87b491 00000000`00000000 ffff9487`9bb7add0 : ndis!ndisCallReceiveHandler+0x61

0c fffff801`5d87b410 fffff801`5cdce874 : 00000000`00012c50 00000000`00000801 ffff9487`9b80b1a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x20766

0d fffff801`5d87b4e0 fffff80e`0b3783b3 : 00000000`00000000 00000000`00000801 00000000`00000001 ffff9487`9bb7add0 : ndis!NdisMIndicateReceiveNetBufferLists+0x104

0e fffff801`5d87b570 fffff80e`0b37947a : ffff9487`9bb7ad00 ffff9487`9b853000 ffff9487`9b854080 00000000`00000000 : e1i65x64!RECEIVE::RxIndicateNBLs+0x12f

0f fffff801`5d87b5d0 fffff80e`0b380c14 : ffff9487`99920ff0 ffff9487`9b853000 ffff9487`9b853001 fffff801`00000000 : e1i65x64!RECEIVE::RxProcessInterrupts+0x20a

10 fffff801`5d87b650 fffff80e`0b38108f : ffff9487`99914ff0 ffff0001`00000000 ffff0001`00000000 00000000`00000000 : e1i65x64!INTERRUPT::MsgIntDpcTxRxProcessing+0x124

11 fffff801`5d87b6c0 fffff80e`0b380668 : ffff9487`99914ff0 00000000`fffffffe fffff801`00000000 00000000`00000000 : e1i65x64!INTERRUPT::MsgIntMessageInterruptDPC+0x1ff

12 fffff801`5d87b780 fffff801`5cdcf2cd : fffff801`59cec180 00000000`00000000 00000000`00000000 fffff801`5ad6d9d6 : e1i65x64!INTERRUPT::MiniportMessageInterruptDPC+0x28

13 fffff801`5d87b7c0 fffff801`5ad7315a : 00000000`00000000 ffff9487`00000002 fffff801`5d87b968 fffff801`5d87b988 : ndis!ndisInterruptDpc+0x19d

14 fffff801`5d87b8f0 fffff801`5ad727af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x30a

15 fffff801`5d87ba30 fffff801`5ae77ebe : 00000000`00000000 fffff801`59cec180 fffff801`5b243400 ffff9487`959ef140 : nt!KiRetireDpcList+0x1ef

16 fffff801`5d87bc60 00000000`00000000 : fffff801`5d87c000 fffff801`5d876000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e

kzhud · ‎06-01-2020

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 000000000000003c, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

Arg4: fffff8015d07eb5a, address which referenced memory

Debugging Details:

------------------

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: VMware, Inc.

VIRTUAL_MACHINE: VMware

SYSTEM_PRODUCT_NAME: VMware7,1

SYSTEM_VERSION: None

BIOS_VENDOR: VMware, Inc.

BIOS_VERSION: VMW71.00V.14410784.B64.1908150010

BIOS_DATE: 08/15/2019

BASEBOARD_MANUFACTURER: Intel Corporation

BASEBOARD_PRODUCT: 440BX Desktop Reference Platform

BASEBOARD_VERSION: None

DUMP_TYPE: 1

BUGCHECK_P1: 3c

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8015d07eb5a

WRITE_ADDRESS: 000000000000003c

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!TcpBeginTcbSend+103a

fffff801`5d07eb5a f0ff403c lock inc dword ptr [rax+3Ch]

CPU_COUNT: 6

CPU_MHZ: c78

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: B4'00000000 (cache) B4'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: CORREY

ANALYSIS_SESSION_TIME: 06-01-2020 14:12:43.0958

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME: fffff8015d87a200 -- (.trap 0xfffff8015d87a200)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=00000000f322e07f

rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8015d07eb5a rsp=fffff8015d87a390 rbp=fffff8015d87a490

r8=0000000000000000 r9=ffff94879d026eb0 r10=ffff94879d026de0

r11=0000000000000010 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

tcpip!TcpBeginTcbSend+0x103a:

fffff801`5d07eb5a f0ff403c lock inc dword ptr [rax+3Ch] ds:00000000`0000003c=????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8015ae861e9 to fffff8015ae74390

Caguicla_Intel · ‎06-02-2020

Hello kzhud,

Thank you for posting in Intel Ethernet Communities.

Please provide the following information for us to check on your query.

1.) Model of your Ethernet Controller

2.) Brand and model of your system

3.) What is the exact Operating System used?

4.) Where was the driver downloaded from? Please share the link with us.

5.) When was the issue first encountered?

6.) Is there any software or hardware changes prior to the issue, like driver or OS update?

Hoping to hear from you soon.

Should there be no response, we will follow up after 3 business days.

Best regards,

Crisselle C

Intel® Customer Support

Caguicla_Intel · ‎06-05-2020

Hello kzhud,

Good day!

We'd like to follow up the requested information for us to proceed in checking your request.

Awaiting to your reply.

Should there be no response, we will follow up after 3 business days.

Best regards,

Crisselle C

Intel® Customer Support

Caguicla_Intel · ‎06-10-2020

Hello kzhud,

How are you today?

Please be informed that we will now close this request since we haven't received any response from our previous follow ups. Just feel free to post a new question if you may have any other inquiry in the future.

May you have an amazing day ahead!

Best regards,

Crisselle C

Intel® Customer Support