BSOD crash by e1k6232.sys

webnoob

New member
Local time
4:52 PM
Messages
20
Location
Bogense
I need help analyzing some dump files, I simply cannot see what is causing the crash.

All dump files point to e1k6232.sys but why? Is it a memory error or a system file?
 

My Computer My Computer

At a glance

Windows 7 Ultimate x64 SP1Intel Core Due 1.6 Ghz5 Gb DDR3
Computer Manufacturer/Model Number
Dell E4200
OS
Windows 7 Ultimate x64 SP1
CPU
Intel Core Due 1.6 Ghz
Memory
5 Gb DDR3
Screen Resolution
1280x800
Hard Drives
256 Gb Samsung SSD

My Computer My Computer

At a glance

Windows 10 Pro x64, Arch LinuxIntel Core 2 Quad Q8200 OC'd 3.08GHz8GB DDR2 900MhzMSI GT730 2GB GDDR5 (Kepler)
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 10 Pro x64, Arch Linux
CPU
Intel Core 2 Quad Q8200 OC'd 3.08GHz
Motherboard
Asus Rampage formula LGA775
Memory
8GB DDR2 900Mhz
Graphics Card(s)
MSI GT730 2GB GDDR5 (Kepler)
Sound Card
Supreme FX2
Monitor(s) Displays
Samsung LS22F350 LED
Screen Resolution
1080P
Hard Drives
Kingston SSDNow UV400 120GB, 500GB Hitachi, 2TB Samsung, 500GB Seagate FreeAgent, 640GB Samsung, 160GB Toshiba (Arch)
PSU
AeroCool 500W Bronze
Cooling
Cooler Master V6 + 3X fans
Keyboard
Prolink keyboard
Mouse
Logitech M705
Internet Speed
1MiB/s
Browser
Chrome Beta
I need help analyzing some dump files, I simply cannot see what is causing the crash.

All dump files point to e1k6232.sys but why? Is it a memory error or a system file?

These are virtually identical and caused by your gigabit driver ( e1k6232.sys). Re-installing with the newest version should help.

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\020811-18517-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e0c000 PsLoadedModuleList = 0x82f54810
Debug session time: Tue Feb  8 03:52:10.902 2011 (GMT-5)
System Uptime: 0 days 1:16:43.432
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {34, 2, 1, 91f7b171}

Unable to load image \SystemRoot\system32\DRIVERS\e1k6232.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1k6232.sys
*** ERROR: Module load completed but symbols could not be loaded for e1k6232.sys
Probably caused by : e1k6232.sys ( e1k6232+16171 )

Followup: MachineOwner
---------

3: 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: 00000034, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 91f7b171, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f74718
Unable to read MiSystemVaType memory at 82f54160
 00000034 

CURRENT_IRQL:  2

FAULTING_IP: 
e1k6232+16171
91f7b171 f00fc111        lock xadd dword ptr [ecx],edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  b18f1b28 -- (.trap 0xffffffffb18f1b28)
ErrCode = 00000002
eax=0000fffb ebx=88bdc280 ecx=00000034 edx=ffffffff esi=88bf2040 edi=00000000
eip=91f7b171 esp=b18f1b9c ebp=b18f1be8 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
e1k6232+0x16171:
91f7b171 f00fc111        lock xadd dword ptr [ecx],edx ds:0023:00000034=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 91f7b171 to 82e5282b

STACK_TEXT:  
b18f1b28 91f7b171 badb0d00 ffffffff 00000000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
b18f1be8 91f77a0e 88bd3000 88bdc280 0000000a e1k6232+0x16171
b18f1c58 91f76093 88bd3000 00000000 b18f1ca0 e1k6232+0x12a0e
b18f1c74 8c27c309 88bd3000 00000000 b18f1ca0 e1k6232+0x11093
b18f1cb0 8c25d6b2 886e3acc 006e3ab8 00000000 ndis!ndisMiniportDpc+0xe2
b18f1d10 8c244976 886e3c50 00000000 8b41c5d0 ndis!ndisQueuedMiniportDpcWorkItem+0xd0
b18f1d50 8301a6d3 00000003 9587fc2c 00000000 ndis!ndisReceiveWorkerThread+0xeb
b18f1d90 82ecc0f9 8c24488b 00000003 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1k6232+16171
91f7b171 f00fc111        lock xadd dword ptr [ecx],edx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  e1k6232+16171

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1k6232

IMAGE_NAME:  e1k6232.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bbae470

FAILURE_BUCKET_ID:  0xD1_e1k6232+16171

BUCKET_ID:  0xD1_e1k6232+16171

Followup: MachineOwner
---------
 

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
I got the same results as postet, but it dosen't add up with the system behavior that the end user explained to me. But I will removed the device from device manager install the newest driver for the device after a reboot.
 

My Computer My Computer

At a glance

Windows 7 Ultimate x64 SP1Intel Core Due 1.6 Ghz5 Gb DDR3
Computer Manufacturer/Model Number
Dell E4200
OS
Windows 7 Ultimate x64 SP1
CPU
Intel Core Due 1.6 Ghz
Memory
5 Gb DDR3
Screen Resolution
1280x800
Hard Drives
256 Gb Samsung SSD
Back
Top