I recently began having intermittent issues with BSOD appearing. Using bluescreenviewer, the problem was caused by netw5v3.sys. I updated my driver for my wifi card in an attempt to fix it but wanted to post my log so that other more knowledgeable people could figure out if there was more to the problem. As I said, I had no issues up until yesterday, when it began crashing randomly. I rolled back the system in an attempt to fix it, so the logs up until this latest one were lost.
Specs: windows 7 professional 32bit. HP pavillion dv6700t laptop. Upgraded from vista without problems over 5 months ago.
Still blamed on the netw5v3.sys driver. and it is 16 months old. Try re-installing it and the other drivers listed below.
Then run a system file check
SFC /SCANNOW Command - System File Checker
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\110910-22869-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a09000 PsLoadedModuleList = 0x82b51810
Debug session time: Tue Nov 9 17:34:42.255 2010 (GMT-5)
System Uptime: 0 days 6:45:41.221
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, 924a2d54}
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
Probably caused by : netw5v32.sys ( netw5v32+6bd54 )
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: 00000064, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 924a2d54, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b71718
Unable to read MiSystemVaType memory at 82b51160
00000064
CURRENT_IRQL: 2
FAULTING_IP:
netw5v32+6bd54
924a2d54 80786400 cmp byte ptr [eax+64h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: javaw.exe
TRAP_FRAME: 8078a8b4 -- (.trap 0xffffffff8078a8b4)
ErrCode = 00000000
eax=00000000 ebx=86fcc000 ecx=00000001 edx=8078a934 esi=8078a9f0 edi=00000000
eip=924a2d54 esp=8078a928 ebp=8078a97c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
netw5v32+0x6bd54:
924a2d54 80786400 cmp byte ptr [eax+64h],0 ds:0023:00000064=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 924a2d54 to 82a4f82b
STACK_TEXT:
8078a8b4 924a2d54 badb0d00 8078a934 8934cd02 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8078a97c 924a67c3 86fcc000 00000000 8078a9ac netw5v32+0x6bd54
8078a9c8 924a786a 86fcc000 8078a9e8 8078a9ec netw5v32+0x6f7c3
8078a9f4 924a7f13 86fcc000 00000003 8078aa64 netw5v32+0x7086a
8078aa6c 924a8290 86fcc001 8a31e018 87189fb8 netw5v32+0x70f13
8078aa88 9244338e 86fcc000 8a31e018 87189fb8 netw5v32+0x71290
8078aab4 924436d3 87189fb8 87189fd8 8a31e018 netw5v32+0xc38e
8078aacc 92442b35 8a31e018 87189fb8 00000000 netw5v32+0xc6d3
8078aae8 92459e96 895d10d8 00000157 00000001 netw5v32+0xbb35
8078ab34 9255519f 895d1098 ff000808 8078abb0 netw5v32+0x22e96
8078ab54 9257ec57 8a342aa0 ff000808 8078abb0 netw5v32+0x11e19f
8078abb4 9257f6b6 858c4000 00000001 00000007 netw5v32+0x147c57
8078ac1c 9257e55f 858c4000 0000009f 877ba6f4 netw5v32+0x1486b6
8078ac84 92572c4e 00000001 0000000e 899940c0 netw5v32+0x14755f
8078ace0 9244338e 858c4000 899940c0 00000000 netw5v32+0x13bc4e
8078ad0c 924436d3 86e5ffa8 86e5fff0 899940c0 netw5v32+0xc38e
8078ad24 92442b35 899940c0 86e5ffd0 00000008 netw5v32+0xc6d3
8078ad40 92555007 8a342ae0 000000ba 00000000 netw5v32+0xbb35
8078ad84 92459d57 8a342aa0 20030011 8078adb8 netw5v32+0x11e007
8078ad9c 92464298 895d1098 20030011 8078adb8 netw5v32+0x22d57
8078adc0 92452cb8 8530c7f8 86137004 8555f650 netw5v32+0x2d298
8078ade8 92453bd4 86137004 00000000 86137004 netw5v32+0x1bcb8
8078adfc 924570c9 85606490 86137004 00000000 netw5v32+0x1cbd4
8078ae38 924572a7 87df5008 8529b008 86137040 netw5v32+0x200c9
8078ae88 9244ee6f 00000001 8529b008 000000ff netw5v32+0x202a7
8078aec4 9244b31c 852e1001 8529b008 8078aee0 netw5v32+0x17e6f
8078aed4 924387a5 8529b008 8078af20 8b18b301 netw5v32+0x1431c
8078aee0 8b18b301 8571a970 00000000 00000000 netw5v32+0x17a5
8078af20 8b1369f4 8671811c 00718008 00000000 ndis!ndisMiniportDpc+0xda
8078af48 82a713b5 8671811c 86718008 00000000 ndis!ndisInterruptDpc+0xaf
8078afa4 82a71218 82b32d20 8527fa10 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82a709dc 9a95cce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 9a95cce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82a709dc 00000000 0000001a 00d6850f bb830000 0x9a95cce4
STACK_COMMAND: kb
FOLLOWUP_IP:
netw5v32+6bd54
924a2d54 80786400 cmp byte ptr [eax+64h],0
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: netw5v32+6bd54
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netw5v32
IMAGE_NAME: netw5v32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49cba8fd
FAILURE_BUCKET_ID: 0xD1_netw5v32+6bd54
BUCKET_ID: 0xD1_netw5v32+6bd54
Followup: MachineOwner
---------
Old drivers
Code:
rixdptsk.sys 0x92905000 0x00051000 11/14/2006 20:35:19 0x455a6ed7 0x928b4000
HpqRemHid.sys 0x92906c00 0x00001c00 7/11/2007 10:30:21 0x4694f78d 0x92905000
RTKVHDA.sys 0x921fb940 0x001f2940 1/15/2008 06:18:36 0x478c968c 0x92009000
hamachi.sys 0x9ec09c00 0x00004c00 2/19/2009 05:36:27 0x499d362b 0x9ec05000
Rt86win7.sys 0x9286f000 0x00025000 2/26/2009 04:04:22 0x49a65b16 0x9284a000
netw5v32.sys netw5v32.sys+6bd54 0x9284a000 0x00413000 3/26/2009 11:10:37 0x49cba8fd 0x92437000
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Quote