BSOD, New Build with Windows Ultimate 64x Bit

[Deathz Shadow]

Just build a new computer not even a week ago and 4 times now i have been BSOD I looked around and I cant find the problem. It seems it happens mainly when im doing a ton of stuff.



System Info
OS: Windows 7 Ultimate 64x Bit
CPU:AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz 6 x 512KB
MotherBoard:ASUS Crosshair IV Extreme AM3 AMD 890FX
Memory:G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
HardDrive:Western Digital Caviar Black WD1001FALS 1TB 7200 RPM 32MB
Graphics: SAPPHIRE 100283L Radeon HD 5770 (Juniper XT) 1GB 128-bit GDDR5
PSU:RAIDMAX HYBRID 2 RX-730SS 730W ATX12V V2.2/ EPS12V
Tower:NZXT LEXA S LEXS

 

[wish]

Hi,
Your single dmp point to e1q62x64.sys as the cause. It's your Intel[R] Gigabit Ethernet driver, so I recommend you to update that driver.

For troubleshooting purpose, uninstall Zone Alarm because ZA is well known as BSOD maker on windows 7, so I suggest you to uninstall it completely.
Windows 7 built-in firewall is good enough to use, Win7 firewall have improved better than in XP or Vista.
Use this tools if you have problem uninstalling ZA -> http://download.zonealarm.com/bin/free/support/cpes_clean.exe

Also uninstall Alcohol/Daemon software and remove its driver (sptd.sys) with this tools --> DuplexSecure - Downloads
Because sptd.sys have some issue with Windows 7 and for alternative software you may use MagicISO.

These drivers need to be updated:

e1q62x64.sys Thu Nov 05 10:23:03 2009 -> [URL="http://downloadcenter.intel.com/"]Intel[R] Gigabit Ethernet[/URL]
sptd.sys     Sun Oct 11 13:55:14 2009 -> [COLOR=Red]Uninstall [/COLOR]it with [URL="http://www.duplexsecure.com/en/downloads"]SPTDinst[/URL]

Then we'll see how it goes.

Log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {68, 2, 1, fffff88004e18e60}

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
---------

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

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001eb40e0
 0000000000000068 

CURRENT_IRQL:  2

FAULTING_IP: 
e1q62x64+18e60
fffff880`04e18e60 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:  fffff8800bf4a7e0 -- (.trap 0xfffff8800bf4a7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004119cd1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004e18e60 rsp=fffff8800bf4a970 rbp=000000000000019e
 r8=fffffa8004119cd0  r9=0000000000000000 r10=fffffa8005c208c0
r11=000000000000fffb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
e1q62x64+0x18e60:
fffff880`04e18e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c7bca9 to fffff80001c7c740

STACK_TEXT:  
fffff880`0bf4a698 fffff800`01c7bca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0bf4a6a0 fffff800`01c7a920 : fffffa80`05c53500 00000000`00000000 fffffa80`0964c470 fffffa80`0964c470 : nt!KiBugCheckDispatch+0x69
fffff880`0bf4a7e0 fffff880`04e18e60 : fffffa80`05d2a730 fffffa80`05c88198 00000000`00000000 00000000`00000008 : nt!KiPageFault+0x260
fffff880`0bf4a970 fffffa80`05d2a730 : fffffa80`05c88198 00000000`00000000 00000000`00000008 00000000`00000000 : e1q62x64+0x18e60
fffff880`0bf4a978 fffffa80`05c88198 : 00000000`00000000 00000000`00000008 00000000`00000000 fffff880`04e213b4 : 0xfffffa80`05d2a730
fffff880`0bf4a980 00000000`00000000 : 00000000`00000008 00000000`00000000 fffff880`04e213b4 00000000`00000000 : 0xfffffa80`05c88198


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1q62x64+18e60
fffff880`04e18e60 f00fc14168      lock xadd dword ptr [rcx+68h],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1q62x64+18e60

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME:  e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4af31807

FAILURE_BUCKET_ID:  X64_0xD1_e1q62x64+18e60

BUCKET_ID:  X64_0xD1_e1q62x64+18e60

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