View Single Post
05 Nov 2010  

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by spolugar View Post
I keep getting BSODs on my new system. This is quite literally a brand new, clean system, built from the ground up. The screens come at seemingly random times (even when the computer is sitting idle) as there is nothing we are doing the same each time. We have gone through and updated every last driver on the system (if there was an updated version). The memory test came back clean as well. This is driving us up the wall as it has happened too many times to count in the last 3 days (how old the system is). The .dmp files and perfmon report are attached as described. Please help!

Windows 7 Professional 64-bit
AMD Phenom II X6 1090T
Asus Crosshair IV Extreme
8gb (2gb x 4) OCZ DDR3 1333
Sapphire Radeon HD5870 2GB DDR5
Silverstone ST1500W PS

12 of 19 crashes were caused by your e1q62x64.sys Intel ethernet driver. While not exceptionally old It should be updated.

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\110510-43134-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e8aeb0
Debug session time: Fri Nov  5 05:06:28.740 2010 (GMT-4)
System Uptime: 0 days 6:47:14.067
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, fffff88002c18e60}

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

Followup: MachineOwner

5: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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

Debugging Details:

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef50e0


fffff880`02c18e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax





TRAP_FRAME:  fffff8800946b7e0 -- (.trap 0xfffff8800946b7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800a208011 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002c18e60 rsp=fffff8800946b970 rbp=0000000000000195
 r8=fffffa800a208010  r9=0000000000000000 r10=fffffa80081fa6b0
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff880`02c18e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cbbae9 to fffff80002cbc580

fffff880`0946b698 fffff800`02cbbae9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0946b6a0 fffff800`02cba760 : 00000000`00000001 00000000`00000068 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0946b7e0 fffff880`02c18e60 : fffffa80`080ac010 fffffa80`08452d60 00000000`00000000 00000000`00000004 : nt!KiPageFault+0x260
fffff880`0946b970 fffffa80`080ac010 : fffffa80`08452d60 00000000`00000000 00000000`00000004 00000000`00000000 : e1q62x64+0x18e60
fffff880`0946b978 fffffa80`08452d60 : 00000000`00000000 00000000`00000004 00000000`00000000 fffff880`02c213b4 : 0xfffffa80`080ac010
fffff880`0946b980 00000000`00000000 : 00000000`00000004 00000000`00000000 fffff880`02c213b4 00000000`00000000 : 0xfffffa80`08452d60


fffff880`02c18e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax


SYMBOL_NAME:  e1q62x64+18e60

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME:  e1q62x64.sys


FAILURE_BUCKET_ID:  X64_0xD1_e1q62x64+18e60

BUCKET_ID:  X64_0xD1_e1q62x64+18e60

Followup: MachineOwner
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 manufacturer links are on this page: Drivers and Downloads

Other drivers needing update
wanatw64.sys        fffff880`0517b000    0x0000c000    4/11/2005 18:07:10            0x425af50e    fffff880`0516f000                
ALSysIO64.sys        fffff880`07762000    0x00008000    4/19/2009 15:41:04            0x49eb7e50    fffff880`0775a000
My System SpecsSystem Spec