Windows 7 BSOD when putting laptop (Thinkpad t410i) to sleep

[oobioobi]

I have a Thinkpad T410i with Windows 7 Pro 64bit. Whenever I close the lid and the laptop tries to go to sleep, it hangs for a few minutes then I get the Blue Screen of Death. The Sleep light does not turn on so I know it crashed.

I've used the Windows Debugger to look at the MiniDump files and it gives me the following that i've copied below. I know it's a driver going into a unknown state when trying to sleep, but I can't tell which driver it is. It's being caused by the pci.sys/PCI Express. If anyone has any idea what could be causing the consistent BSOD, it would be greatly appreciated. I can't seem to figure it out. Do i just need to update a particular driver? I've updated all drivers to the latest ones available and flashed the BIOS.

Thanks.

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


Loading Dump File [C:\Windows\Minidump\052010-40685-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: symsrv*symsrv.dll*f:\localsymbols*Symbol information
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`02c65000 PsLoadedModuleList = 0xfffff800`02ea2e50
Debug session time: Thu May 20 20:52:22.384 2010 (UTC - 7:00)
System Uptime: 0 days 2:09:12.976
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80048eba20, fffff80000b9c518, fffffa80047f1830}

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

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f43000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c4c8 fffff800`02d441b3 : 00000000`0000009f 00000000`00000003 fffffa80`048eba20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ce16a6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`02ce0a26 : fffffa80`0718c168 fffffa80`0718c168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ce157e : 00000012`0d225628 fffff800`00b9cc58 00000000`00079556 fffff800`02e52d48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02ce0d97 : 00000003`c05eaac6 00000003`00079556 00000003`c05eaa98 00000000`00000056 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cdddfa : fffff800`02e4fe80 fffff800`02e5dc40 00000000`00000002 fffff880`00000000 : 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_3_NETw5s64_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_NETw5s64_IMAGE_pci.sys

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

0: kd> lmvm pci
start end module name
fffff880`00f43000 fffff880`00f76000 pci (pdb symbols) C:\WinDDK\7600.16385.1\Debuggers\sym\pci.pdb\F98D68109228430DADC2FD033EBF5C471\pci.pdb
Loaded symbol image file: pci.sys
Mapped memory image file: C:\WinDDK\7600.16385.1\Debuggers\sym\pci.sys\4A5BC11733000\pci.sys
Image path: \SystemRoot\system32\DRIVERS\pci.sys
Image name: pci.sys
Timestamp: Mon Jul 13 16:19:51 2009 (4A5BC117)
CheckSum: 0002E579
ImageSize: 00033000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: pci.sys
OriginalFilename: pci.sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: NT Plug and Play PCI Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.

 

[webscaper]

There is nothing specific in the dump.

Sleep is a function of power management in the bios. You say you have the current bios.

Have you updated to the most current power management drivers from this site: Link Removed.

Uninstall the old driver then install the new driver rather than just updating the driver in place.

 

[Saltgrass]

Have you tried opening a command prompt and using the powercfg commands to check your system?

powercfg -energy will check your system. When you run it, close all open programs you can and make note of where the resulting report is kept.

And the help switch will give more options you might want to check.

You might also go through device management and see if any of your devices, such as a network adapter, has a power management tab in properties and what options it shows.

 

[Mitchell_A]

There is one driver reference in the dump - pci.sys
PCI.. Graphics Card? Do you have an external PCI one? Could you use an integrated one to see if the problem persists?