I read the other blue screen threads, but none seemed to help me out. I did not want to interfere with the other person's problem so I started this thread and I will attach the zip file of the most recent blue screen.
This Blue screen is happening when My computer is barley running anything. I basically turned off all start up programs so that I could get to this forum and start this thread. Any help would be useful thanks.
STW
this one was caused by your netw5v64.sys realtek driver suggest you re-install it
Everything else looks ok
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\101109-19359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\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`02a16000 PsLoadedModuleList = 0xfffff800`02c53e50
Debug session time: Sun Oct 11 16:03:30.034 2009 (GMT-4)
System Uptime: 0 days 0:05:29.016
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, fffff8800a0d5bbe}
Unable to load image \SystemRoot\system32\DRIVERS\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
---------
1: 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: fffff8800a0d5bbe, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e0
0000000000000064
CURRENT_IRQL: 2
FAULTING_IP:
netw5v64+aabbe
fffff880`0a0d5bbe 807f6400 cmp byte ptr [rdi+64h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: OEM02Mon.exe
STACK_COMMAND: kb
FOLLOWUP_IP:
netw5v64+aabbe
fffff880`0a0d5bbe 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
---------
Ken
