Thread: BSOD on Wakeup
View Single Post
26 May 2011  
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by pikalax View Post
Is Windows 7 . . .
- x86 (32-bit) or x64 ?
- the original installed OS on the system? NO
- an OEM or full retail version?
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 2 YEARS
- What is the age of OS installation (have you re-installed the OS?) 1 YEAR SINCE REINSTALL

HP Pavilion dv3-1075us came with Vista, uploaded to 7 using HP's disks.

Hardware changes: Purchased HP KS523AA USB TV Tuner and followed instructions in package to install device. Purchased USB Highspeed 7 Port Hub w/ AC Adapter, plug & go.

Computer went to sleep according to the current power plan. I woke it up and unlocked it, then tried to refresh a Google Chrome page, but before I could, the system bluescreened.
These were Related to Rt64win7.sys 8101E/8168/8169 NDIS 6.20 64-bit Driver from Realtek Corporation.

I would re-install it



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\Windows_NT6_BSOD_jcgriff2\041611-29140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03261e90
Debug session time: Fri Apr 15 20:55:07.921 2011 (GMT-4)
System Uptime: 0 days 11:11:56.966
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
..................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800468e060, fffff80000ba2748, fffffa8005d99b50}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800468e060, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa8005d99b50, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8005d99b50

DEVICE_OBJECT: fffffa80051b5050

DRIVER_OBJECT: fffffa8005211d10

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3936e8

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88004b77000 Rt64win7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  SmartMenu.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003108b52 to fffff8000309c640

STACK_TEXT:  
fffff800`00ba26f8 fffff800`03108b52 : 00000000`0000009f 00000000`00000003 fffffa80`0468e060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`030a8062 : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00ba27a0 fffff800`030a7f06 : fffffa80`068e7168 fffffa80`068e7168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`030a7dee : 0000005d`dec8d2e5 fffff800`00ba2e88 00000000`00276f54 fffff800`03211d08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`030a7bd7 : fffffa80`05804bc4 00000000`00276f54 00000000`00000000 00000000`00000054 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`0309f165 : 00000000`00000000 fffffa80`04d92650 00000000`00000000 fffff880`014a2a00 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`0309ef7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`09998300 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec