Hi
I need help with a BSOD problem. I've only had windows 7 for about 3-4 weeks or less, after having windows xp, I upgraded to windows 7. It installed without any problems but in the last week or so, every so often I get the blue screen error which states it is shutting down to prevent damage, I've done virus scans, tried updating my drivers which won't anyway because they are up to date.
So I have attached the contents from \windows\minidump and hope I get it solved.
Hi and welcome
this one was caused by your intel wifi driver ( netw5v32.sys).
I would download and install a fresh copy.
I would also run a system file chektype cmd in search>right click and run as admin>
sfc /scannow
Since there is also some memory issue I would
doenload memtestx86 and run it for 5 passes
Ken J+
Code:
011710-45349-01.dmp 1/17/2010 2:08:50 AM PFN_LIST_CORRUPT 0x0000004e 0x00000099 0x00064301 0x00000002 0x0001e180 halmacpi.dll halmacpi.dll+5b48 32-bit C:\Users\K\Desktop\BSOD\011710-45349-01.dmp 1 15 7600
011610-41699-01.dmp 1/16/2010 11:49:36 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0x80000003 0x90c8885c 0x80d8ac04 0x00000000 netw5v32.sys netw5v32.sys+5985d 32-bit C:\Users\K\Desktop\BSOD\011610-41699-01.dmp 1 15 7600
011110-43087-01.dmp 1/11/2010 9:56:44 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0xffffffec 0x00000002 0x00000001 0x925f110b netw5v32.sys netw5v32.sys+1e610b 32-bit C:\Users\K\Desktop\BSOD\011110-43087-01.dmp 1 15 7600
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\BSOD\011610-41699-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8281d000 PsLoadedModuleList = 0x8295c570
Debug session time: Sat Jan 16 18:48:01.651 2010 (GMT-5)
System Uptime: 0 days 2:52:33.758
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
........
Unable to load image \SystemRoot\system32\DRIVERS\netw5v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000003, 90c8885c, 80d8ac04, 0}
Probably caused by : netw5v32.sys ( netw5v32+5985c )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 90c8885c, The address that the exception occurred at
Arg3: 80d8ac04, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP:
netw5v32+5985c
90c8885c 50 push eax
TRAP_FRAME: 80d8ac04 -- (.trap 0xffffffff80d8ac04)
ErrCode = 00000000
eax=80d8acbc ebx=86b5c060 ecx=80d8aca0 edx=00000062 esi=86b5c000 edi=84d9efd8
eip=90c8885d esp=80d8ac78 ebp=80d8acc8 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000292
netw5v32+0x5985d:
90c8885d c645ff00 mov byte ptr [ebp-1],0 ss:0010:80d8acc7=85
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: avgcsrvx.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 90c3b38e to 90c8885d
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80d8acc8 90c3b38e 00000000 84990c20 84d9efb8 netw5v32+0x5985d
80d8acf4 90c3b6d3 84d9efb8 84d9efd8 84990c20 netw5v32+0xc38e
80d8ad0c 90c3ab35 84990c20 84d9efb8 80d8ad50 netw5v32+0xc6d3
80d8ad28 90c7f874 859ad0c8 000000d1 00000000 netw5v32+0xbb35
80d8adc0 90c4acb8 86b5c000 86514004 867d7bf8 netw5v32+0x50874
80d8ade8 90c4bbd4 86514004 00000000 86514004 netw5v32+0x1bcb8
80d8adfc 90c4f0c9 859b14d0 86514004 00000000 netw5v32+0x1cbd4
80d8ae38 90c4f2a7 859b18b0 86333c10 86514000 netw5v32+0x200c9
80d8ae88 90c46e6f 00000001 86333c10 000000ff netw5v32+0x202a7
80d8aec4 90c4331c 859b1e01 86333c10 80d8aee0 netw5v32+0x17e6f
80d8aed4 90c307a5 86333c10 80d8af20 8925d301 netw5v32+0x1431c
80d8aee0 8925d301 85646b28 00000000 00000000 netw5v32+0x17a5
80d8af20 892089f4 859b31ac 009b30d8 00000000 ndis!ndisMiniportDpc+0xda
80d8af48 82872815 859b31ac 859b30d8 00000000 ndis!ndisInterruptDpc+0xaf
80d8afa4 82872678 8293ed20 87083d48 00000000 nt!KiExecuteAllDpcs+0xf9
80d8aff4 82871e3c 80da5bd4 00000000 00000000 nt!KiRetireDpcList+0xd5
80d8aff8 80da5bd4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82871e3c 00000000 0000001a 00d6850f bb830000 0x80da5bd4
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
netw5v32+5985c
90c8885c 50 push eax
SYMBOL_NAME: netw5v32+5985c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netw5v32
IMAGE_NAME: netw5v32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49cba8fd
FAILURE_BUCKET_ID: 0x8E_netw5v32+5985c
BUCKET_ID: 0x8E_netw5v32+5985c
Followup: MachineOwner
---------
Quote
