BSOD while entering sleep mode

[yowanvista]

PC just BSOD while entering sleep mode

 

[ttran]

Hi yowanvista

-The bugcheck code is 9F, this usually indicate device drivers.
The dump indicated that the problem was caused by the system driver for the PCI slots.\
-To fix this file, start an elevated command prompt (hit start, cmd, right click, run as admin) and type sfc /scannow. What happens?
-PCI.sys was a common issue with XP. Did your Upgrade form XP to Windows 7 ?? Or was it a clean install ?? If its an upgrade it might wanna consider clean install

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.536\062810-20014-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04b3a500?
Symbol search path is: 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`02e63000 PsLoadedModuleList = 0xfffff800`030a0e50
Debug session time: Mon Jun 28 18:01:55.165 2010 (UTC + 7:00)
System Uptime: 0 days 4:05:11.866
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8005c7aa20, fffff80004b3a518, fffffa8006bef3b0}

Probably caused by : pci.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: fffffa8005c7aa20, Physical Device Object of the stack
Arg3: fffff80004b3a518, Functional Device Object of the stack
Arg4: fffffa8006bef3b0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f5a000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`04b3a4c8 fffff800`02f421b3 : 00000000`0000009f 00000000`00000003 fffffa80`05c7aa20 fffff800`04b3a518 : nt!KeBugCheckEx
fffff800`04b3a4d0 fffff800`02edf6a6 : fffff800`04b3a600 fffff800`04b3a600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`04b3a570 fffff800`02edea26 : fffff800`03075290 00000000`000e63d6 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`04b3a5e0 fffff800`02edf57e : 00000022`40f4a4a1 fffff800`04b3ac58 00000000`000e63d6 fffff800`03051d48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04b3ac30 fffff800`02eded97 : 00000009`5dbe92c2 00000009`000e63d6 00000009`5dbe9280 00000000`000000d6 : nt!KiTimerExpiration+0x1be
fffff800`04b3acd0 fffff800`02edbdfa : fffff800`0304de80 fffff800`0305bc40 00000000`00000000 fffff880`104492dc : nt!KiRetireDpcList+0x277
fffff800`04b3ad80 00000000`00000000 : fffff800`04b3b000 fffff800`04b35000 fffff800`04b3ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_yk62x64_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_yk62x64_IMAGE_pci.sys

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

 

[richc46]

It may be that the driver in question comes from this company Marvel

I would try to update the driver that was mentioned in the prior post
Marvell: Support
** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys

 

[yowanvista]

This is a clean installation, the system file checker finds no errors

 

[yowanvista]

It may be that the driver in question comes from this company Marvel

I would try to update the driver that was mentioned in the prior post
Marvell: Support
** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys

Its my onboard network adapter, already have its latest drivers from windows update

 

[ttran]

Have you ever tried to do repair install my friend? I have seen this person, who Lordbob and I were trying to help. He finally did a http://www.sevenforums.com/tutorials/3413-repair-install.html (upgrade), then his issue was solved.
http://www.sevenforums.com/crashes-debugging/76340-pci-sys-driver-powerstate-blue-screens.html

If it doesn't work, you may have to turn on driver verifier to know what exact drivers are bad

~Tuan

 

[yowanvista]

Problem fixed: updated the network drivers from safe mode

 

[quantumgravity]

I came along a year later with exactly the same problem. My minidump files implicated the Marvell yk62x64.sys driver for months, and I kept updating it, thinking the problem had gone away. But I was only deluding myself; it never went away.

Soooo, I did reluctantly do the Repair/Install following the great instructions referenced above. This is essentially upgrading Windows 7 on top of itself, so that programs and files are maintained. It took 19 hours to run on a reasonably fast PC, probably due to some registry-heavy programs like Adobe CS5, etc. When it finished, I had contracted a new problem: Roxio Burn from Roxio Creator Premiere 2010 in Startup caused my Power Plans in Power Options in the Control Panel to be inaccessible. A small price to pay, I removed Roxio Burn from Startup.

The result? Sleep and Hibernate work fine now. Apparently it wasn't the Marvell driver at all, but that driver perhaps interacted with some detritus from two years of operation that had built up. The machine, even when it did manage to go to sleep, struggled for minutes to do so. Now it's instantaneous.

Moral: ttran is right above. Don't always assume the object of your dump results is the ultimate cause of a problem. Thanks, guys.