Firstly Hi All,
I have a BSOD issue that i would like help resolving.
O/S: Windows 7 x64 Enterprise (KMS licence)
Age of hardware: New < 1 month - DELL E6410 laptop.
Age of O/S: New < 1 month
Attached are the BSOD dump files and Perfmon HTML in zip file.
Thank You for your help.
Two problems
1-Old drivers These need updating
Code:
PBADRV.sys 1/7/2008 14:12:13 0x4782798d fffff880`017ec000 fffff880`017f8000 0x0000c000
dne64x.sys 11/10/2008 20:01:24 0x4918d964 fffff880`04352000 fffff880`0437e000 0x0002c000
iaStorV.sys 4/8/2009 11:57:17 0x49dcd76d fffff880`010c8000 fffff880`011e6000 0x0011e000
2-Your e1k62x64.sys driver. This driver is the cause of all 5 of the crashes. It is your Intel network driver and needs to be re-installed using the most current version
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\Windows_NT6_BSOD_jcgriff2\022211-24460-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`0323fe50
Debug session time: Mon Feb 21 18:11:11.184 2011 (GMT-5)
System Uptime: 0 days 0:38:24.042
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {68, 2, 1, fffff8800441b2e0}
Unable to load image \SystemRoot\system32\DRIVERS\e1k62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1k62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
Probably caused by : e1k62x64.sys ( e1k62x64+1b2e0 )
Followup: MachineOwner
---------
2: 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: 0000000000000068, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800441b2e0, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032aa0e0
0000000000000068
CURRENT_IRQL: 2
FAULTING_IP:
e1k62x64+1b2e0
fffff880`0441b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800ab1e850 -- (.trap 0xfffff8800ab1e850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004066780 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800441b2e0 rsp=fffff8800ab1e9e0 rbp=00000000000001ed
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
e1k62x64+0x1b2e0:
fffff880`0441b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003071ca9 to fffff80003072740
STACK_TEXT:
fffff880`0ab1e708 fffff800`03071ca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ab1e710 fffff800`03070920 : fffffa80`03b8d0b0 00000000`00000000 fffffa80`03b8d6f0 fffffa80`03b8d3d0 : nt!KiBugCheckDispatch+0x69
fffff880`0ab1e850 fffff880`0441b2e0 : fffffa80`05e88520 fffffa80`05b7a6a0 00000000`00000000 00000000`00000007 : nt!KiPageFault+0x260
fffff880`0ab1e9e0 fffffa80`05e88520 : fffffa80`05b7a6a0 00000000`00000000 00000000`00000007 00000000`00000000 : e1k62x64+0x1b2e0
fffff880`0ab1e9e8 fffffa80`05b7a6a0 : 00000000`00000000 00000000`00000007 00000000`00000000 fffff880`044234f4 : 0xfffffa80`05e88520
fffff880`0ab1e9f0 00000000`00000000 : 00000000`00000007 00000000`00000000 fffff880`044234f4 00000000`00000000 : 0xfffffa80`05b7a6a0
STACK_COMMAND: kb
FOLLOWUP_IP:
e1k62x64+1b2e0
fffff880`0441b2e0 f00fc14168 lock xadd dword ptr [rcx+68h],eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: e1k62x64+1b2e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: e1k62x64
IMAGE_NAME: e1k62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bbae4c3
FAILURE_BUCKET_ID: X64_0xD1_e1k62x64+1b2e0
BUCKET_ID: X64_0xD1_e1k62x64+1b2e0
Followup: MachineOwner
---------
2: kd> lmvm e1k62x64
start end module name
fffff880`04400000 fffff880`0444c000 e1k62x64 T (no symbols)
Loaded symbol image file: e1k62x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1k62x64.sys
Image name: e1k62x64.sys
Timestamp: Tue Apr 06 03:37:39 2010 (4BBAE4C3)
CheckSum: 0004DF61
ImageSize: 0004C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4