Blue screen crash?? AHHHHHH

[Majesticks]

Hi,

So im having BSOD issues only when i log in or restart,

ive run windows debuging and its telling me my intel wireless is the problem(netw5v64
.sys),if i do a clean install (windows 7 ultimate x64) and do not install/load/or even do anything i still get the blue screen,tho the BSOD will happen quicker if i install something/nearly anything,my wireless is working fine but could the wireless card still b an issue? ive got a few spare cards to try.or is there a way to reset them? changing drivers dosent help because installing any thing usually makes it BSOD upon restart and why would a driver be fine for two years and then blue screen,my laptop was fine untill 2 weeks ago,i have clean installed it 5 times since then trying to fix this,theres heaps of same problems in google with this exact thing.


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\102310-33243-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02864000 PsLoadedModuleList = 0xfffff800`02aa1e50
Debug session time: Fri Oct 22 23:59:34.787 2010 (UTC + 13:00)
System Uptime: 0 days 0:00:36.660
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {64, 2, 0, fffff88004b21bbe}
Unable to load image netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+aabbe )
Followup: MachineOwner
---------
0: 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: 0000000000000064, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004b21bbe, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0c0e0
0000000000000064
CURRENT_IRQL: 2
FAULTING_IP:
netw5v64+aabbe
fffff880`04b21bbe 807f6400 cmp byte ptr [rdi+64h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9be10 -- (.trap 0xfffff80000b9be10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80051a2000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b21bbe rsp=fffff80000b9bfa0 rbp=fffffa80051a2000
r8=fffff80000b9c080 r9=fffff80000b9c148 r10=0000000080e14b2a
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
netw5v64+0xaabbe:
fffff880`04b21bbe 807f6400 cmp byte ptr [rdi+64h],0 ds:8ad8:00000000`00000064=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028d5469 to fffff800028d5f00
STACK_TEXT:
fffff800`00b9bcc8 fffff800`028d5469 : 00000000`0000000a 00000000`00000064 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9bcd0 fffff800`028d40e0 : 00000000`00000000 fffffa80`04722df0 00000000`00000002 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9be10 fffff880`04b21bbe : 00000000`00000001 00000000`00000001 fffff800`00b9c148 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9bfa0 00000000`00000001 : 00000000`00000001 fffff800`00b9c148 00000000`00000000 fffff800`00b9c090 : netw5v64+0xaabbe
fffff800`00b9bfa8 00000000`00000001 : fffff800`00b9c148 00000000`00000000 fffff800`00b9c090 fffff880`04a8e092 : 0x1
fffff800`00b9bfb0 fffff800`00b9c148 : 00000000`00000000 fffff800`00b9c090 fffff880`04a8e092 00000000`00000000 : 0x1
fffff800`00b9bfb8 00000000`00000000 : fffff800`00b9c090 fffff880`04a8e092 00000000`00000000 fffffa80`042a4420 : 0xfffff800`00b9c148

STACK_COMMAND: kb
FOLLOWUP_IP:
netw5v64+aabbe
fffff880`04b21bbe 807f6400 cmp byte ptr [rdi+64h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: netw5v64+aabbe
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netw5v64
IMAGE_NAME: netw5v64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49cbab84
FAILURE_BUCKET_ID: X64_0xD1_netw5v64+aabbe
BUCKET_ID: X64_0xD1_netw5v64+aabbe
Followup: MachineOwner
---------
0: kd> lmvm netw5v64
start end module name
fffff880`04a77000 fffff880`04fb2000 netw5v64 T (no symbols)
Loaded symbol image file: netw5v64.sys
Image path: netw5v64.sys
Image name: netw5v64.sys
Timestamp: Fri Mar 27 05:21:24 2009 (49CBAB84)
CheckSum: 00533DE3
ImageSize: 0053B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> .trap 0xfffff80000b9be10
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80051a2000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b21bbe rsp=fffff80000b9bfa0 rbp=fffffa80051a2000
r8=fffff80000b9c080 r9=fffff80000b9c148 r10=0000000080e14b2a
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
netw5v64+0xaabbe:
fffff880`04b21bbe 807f6400 cmp byte ptr [rdi+64h],0 ds:8ad8:00000000`00000064=??
0: kd> lmvm netw5v64
start end module name
fffff880`04a77000 fffff880`04fb2000 netw5v64 T (no symbols)
Loaded symbol image file: netw5v64.sys
Image path: netw5v64.sys
Image name: netw5v64.sys
Timestamp: Fri Mar 27 05:21:24 2009 (49CBAB84)
CheckSum: 00533DE3
ImageSize: 0053B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[cybercore]

Caused by your Intel® Wireless WiFi Link Adapter, March 2009 <- update it.

Follow BSOD posting instructions please.

 

[Lemur]

Good morning.

First, please do the following:

[FONT=&quot]BSOD Posting Instructions[/FONT]
[FONT=&quot]http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html[/FONT]

Then ...

Probably caused by : netw5v64.sys ( netw5v64+aabbe )

Update the Intel Wireless driver:

http://downloadcenter.intel.com/Sea...roducts&ProdId=3062&LineId=1784&FamilyId=1783

 

[cybercore]

OOps, Lemur - just saw you around viewing this thread (thought it was the OP), sorry, please go ahead. : )

 

[Lemur]

No, good job cybercore! +1