BSOD on e1c62x64.sys

[Mr Bob]

I'm getting a pretty regular blue screen lately, seems like it happens either during a file transfer (I believe over the network) or during an install of some sort.

Computer specs are:

Win 7 x64
Core i7 3770K
Asus P8Z68-V Pro Gen3 (upgraded to latest bios in order to run the new Core i7)
Coresair 2x8GB PC3-10700 (667mhz)
NVIDIA GeForce 8600 GTS x2
Intel 520 SSD

1: 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: 0000000000000090, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004623713, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c5100
GetUlongFromAddress: unable to read from fffff800036c51c0
0000000000000090 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
e1c62x64+23713
fffff880`04623713 48899090000000 mov qword ptr [rax+90h],rdx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff8800b6c76a0 -- (.trap 0xfffff8800b6c76a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8012af0030
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004623713 rsp=fffff8800b6c7830 rbp=0000000000000127
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
e1c62x64+0x23713:
fffff880`04623713 48899090000000 mov qword ptr [rax+90h],rdx ds:00000000`00000090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003495769 to fffff800034961c0

STACK_TEXT:
fffff880`0b6c7558 fffff800`03495769 : 00000000`0000000a 00000000`00000090 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b6c7560 fffff800`034943e0 : fffffa80`1290dac0 fffffa80`1290d4f0 fffffa80`1290d110 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0b6c76a0 fffff880`04623713 : fffffa80`00000801 fffffa80`0e8479d0 00000000`00000000 fffff880`04625cc0 : nt!KiPageFault+0x260
fffff880`0b6c7830 fffffa80`00000801 : fffffa80`0e8479d0 00000000`00000000 fffff880`04625cc0 00000000`00000000 : e1c62x64+0x23713
fffff880`0b6c7838 fffffa80`0e8479d0 : 00000000`00000000 fffff880`04625cc0 00000000`00000000 fffffa80`0e1aee20 : 0xfffffa80`00000801
fffff880`0b6c7840 00000000`00000000 : fffff880`04625cc0 00000000`00000000 fffffa80`0e1aee20 fffffa80`00000000 : 0xfffffa80`0e8479d0


STACK_COMMAND: kb

FOLLOWUP_IP:
e1c62x64+23713
fffff880`04623713 48899090000000 mov qword ptr [rax+90h],rdx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: e1c62x64+23713

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1c62x64

IMAGE_NAME: e1c62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c9924d7

FAILURE_BUCKET_ID: X64_0xD1_e1c62x64+23713

BUCKET_ID: X64_0xD1_e1c62x64+23713

Followup: MachineOwner

 

[Dahak]

from what it looks like, it is related to the network driver
you can try the latest intel drivers from here

 

[Mr Bob]

So far everything is looking good!