Constant BSOD increasing each day

[scsuperman2000]

windows 7 was the original install, ultimate x64 retail
constructed system last year
probably past 10 bsod a day now, only problem before was update the lan driver on the asus crosshair IV extreme was fine for a while and then the bsod more and more

 

[zigzag3143]

windows 7 was the original install, ultimate x64 retail
constructed system last year
probably past 10 bsod a day now, only problem before was update the lan driver on the asus crosshair IV extreme was fine for a while and then the bsod more and more

Most of these point directly to your e1q62x64.sys driver. That is your Intel Ethernet driver. A re-install should helo the problem and can be found here. http://downloadcenter.intel.com/

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\041911-25708-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03256000 PsLoadedModuleList = 0xfffff800`03493e50
Debug session time: Tue Apr 19 13:18:36.918 2011 (GMT-4)
System Uptime: 0 days 11:02:41.276
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, fffff88012bb1990}

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+1b990 )

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

4: 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: fffff88012bb1990, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fe0e0
 0000000000000068 

CURRENT_IRQL:  2

FAULTING_IP: 
e1q62x64+1b990
fffff880`12bb1990 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:  fffff8800b4207e0 -- (.trap 0xfffff8800b4207e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009b3b810 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88012bb1990 rsp=fffff8800b420970 rbp=00000000000000b9
 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
e1q62x64+0x1b990:
fffff880`12bb1990 f00fc14168      lock xadd dword ptr [rcx+68h],eax ds:00000000`00000068=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032c5ca9 to fffff800032c6740

STACK_TEXT:  
fffff880`0b420698 fffff800`032c5ca9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b4206a0 fffff800`032c4920 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0b4207e0 fffff880`12bb1990 : fffffa80`09cf9250 fffffa80`09d39640 00000000`00000000 00000000`00000009 : nt!KiPageFault+0x260
fffff880`0b420970 fffffa80`09cf9250 : fffffa80`09d39640 00000000`00000000 00000000`00000009 00000000`00000000 : e1q62x64+0x1b990
fffff880`0b420978 fffffa80`09d39640 : 00000000`00000000 00000000`00000009 00000000`00000000 fffff880`12bb9b84 : 0xfffffa80`09cf9250
fffff880`0b420980 00000000`00000000 : 00000000`00000009 00000000`00000000 fffff880`12bb9b84 fffffa80`00000000 : 0xfffffa80`09d39640


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1q62x64+1b990
fffff880`12bb1990 f00fc14168      lock xadd dword ptr [rcx+68h],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1q62x64+1b990

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1q62x64

IMAGE_NAME:  e1q62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c364c04

FAILURE_BUCKET_ID:  X64_0xD1_e1q62x64+1b990

BUCKET_ID:  X64_0xD1_e1q62x64+1b990

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