BSODing after second reformat

Hi there;

I recently bought a new machine:

Microsoft Windows 7 Home Premium Edition 64BIT DVD OEM
Western Digital WD20EARS Caviar Green 2TB SATA2 3Gbps 64MB Cache 3.5IN Hard Drive OEM
Corsair CMT8GX3M4A1866C9 Dominator GT 8GB 4X2GB DDR3-1866 CL9-9-9-24 Memory Kit
Antec Dark Fleet DF-85 Full Tower Gaming Case ATX 12 Drive Bay No PS Top USB3.0 USB Audio
ASUS Crosshair IV Extreme AM3 DDR3 EATX AMD 890FX 5PCI-E16 1PCI CrossFireX SATA3 USB3.0 Motherboard
AMD Phenom II X6 1100T Black Edition Thuban 6 Core Processor 3.3GHZ Socket AM3 Retail Box
ASUS GeForce 570 GTX DirectCU II Fermi 742MHZ 1280MB 3.8 GHz GDDR5 2XDVI HDMI PCI-E Video Card
Antec CP-1000 1000W Cpx Dual PCB Power Supply Modular ATX12V V2.3 80PLUS Active PFC S
OCZ Sata3 120G drive

Anyhoo, I put it together and games always seemed to run very slow. I reformatted and this solved the issue, however I started receiving BSODs. Also, I couldn't do Windows Updates for whatever reason, SP1 wouldn't install. I reformatted again and did all my updates so I'm completely up to date, installed a few games, everything seemed to be OK.

I then installed Microsoft Visual C++ 2008 Redistributable x64 (may be coincidental, not sure) and now I'm BSODing again. It can happen at any time it seems.

Any input is appreciated.

e1q62x64.sys is the cause its your Intel Network adapter driver
Update it using the Intel update utility
Intel® Driver Update Utility
Or at http://downloadcenter.intel.com/

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff880043cde60, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c5100
 0000000000000068 

CURRENT_IRQL:  2

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

LAST_CONTROL_TRANSFER:  from fffff80002e952a9 to fffff80002e95d00

STACK_TEXT:  
fffff880`08603698 fffff800`02e952a9 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`086036a0 fffff800`02e93f20 : fffffa80`09a722d0 fffff880`01724200 fffffa80`091ec1d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`086037e0 fffff880`043cde60 : fffffa80`07aea460 fffffa80`07a4a3c0 00000000`00000000 00000000`00000002 : nt!KiPageFault+0x260
fffff880`08603970 fffffa80`07aea460 : fffffa80`07a4a3c0 00000000`00000000 00000000`00000002 00000000`00000000 : e1q62x64+0x18e60
fffff880`08603978 fffffa80`07a4a3c0 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff880`043d63b4 : 0xfffffa80`07aea460
fffff880`08603980 00000000`00000000 : 00000000`00000002 00000000`00000000 fffff880`043d63b4 00000000`00000000 : 0xfffffa80`07a4a3c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1q62x64+18e60
fffff880`043cde60 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
---------

Thank-you for the response. After updating the network adaptor via the Intel website as suggested, the BSODing continues. Should I re-run the BSOD utility?

BSODBlues said:

Thank-you for the response. After updating the network adaptor via the Intel website as suggested, the BSODing continues. Should I re-run the BSOD utility?

Revert back to an older version of the driver if possible until Intel addresses the issue