BSOD after exiting sleep mode

usasma · 24 Dec 2009

Use this link to perform an analysis yourself: WinDbg Analysis Report
The post the results here for us to have a look at.

Destroyer1990 · 08 Jan 2010

Finally figured out the problem with the whole zipping. Here's the mini dump files, any analysis information would be great.

**Pauly** · 09 Jan 2010

Both dumps report BC 0x116 VIDEO_TDR_FAILURE
This is an error between the gfx card and the gfx driver, things to check are the gfx card is seated properly and has adequate cooling, gpu-z can help you there, and IMO remove all gfx software/drivers and re-install latest drivers from manufacturers website without full software package they normally give you to see if you can regain stability.

Hope this helps
Post back your results

Destroyer1990 · 09 Jan 2010

I'll have to do the latter, as I don't trust myself to open up a laptop to check for card seating. I'll reinstall the driver software and see if it works. Thanks for the help!

usasma · 10 Jan 2010

Because it's a laptop, the steps are a bit different due to it's construction.
Please blow out all the vents with a can of compressed air in both directions (and ensure that the fan is working) DON'T use a vacuum cleaner or an air compressor - they can damage the computer.

Then you can easily follow the rest of Pauly's excellent advice.

Maverick1 · 07 May 2010

I have a similar problem. Here is a link to the memory dmp file.

MEGAUPLOAD - The leading online storage and file delivery service

zigzag3143 · 07 May 2010

Maverick1 said:

I have a similar problem. Here is a link to the memory dmp file.

MEGAUPLOAD - The leading online storage and file delivery service

)\
A driver is causing an inconsistent power state. That driver is Rt64win7.sys your Realtek Ethernet driver Rt64win7.sys. I would download and install a fresh copy

let us know if you need help

Ken

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\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Thu Apr 29 15:49:38.519 2010 (GMT-4)
System Uptime: 0 days 5:52:10.220
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols

Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004888a20, fffff80000b9c518, fffffa8006771b10}

*** 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: fffffa8004888a20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8006771b10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8006771b10

DEVICE_OBJECT: fffffa8005b55050

DRIVER_OBJECT: fffffa8005b542b0

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a16bc2e

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88004434000 Rt64win7

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002afe1b3 to fffff80002a8f600

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02afe1b3 : 00000000`0000009f 00000000`00000003 fffffa80`04888a20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02a9b6a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`02a9aa26 : fffffa80`05c607b0 fffffa80`05c607b0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02a9b57e : 00000031`3297cb5e fffff800`00b9cc58 00000000`0014aafc fffff800`02c0e208 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a9ad97 : 0000000f`5fdc17c5 0000000f`0014aafc 0000000f`5fdc170e 00000000`000000fc : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a97dfa : fffff800`02c09e80 fffff800`02c17c40 00000000`00000000 fffff880`010fe4c0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

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