BSOD on shut down

[ArchaicWarrior]

ok, occassionally I get a BSOD when shutting down my computer. It reboots ok. It happened today after i backed up on a 3.5" hot-swap drive.

Here is the dump details.

W7 64 bit -

Any help thanks.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\windows\GDSymbols\*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`03695670
Debug session time: Sat Mar 3 09:19:59.289 2012 (UTC + 11:00)
System Uptime: 0 days 2:30:36.148
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 0, fffff8000525a3d0}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: 0000000000000000, The thread currently holding on to the Pnp lock.
Arg4: fffff8000525a3d0

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


DRVPOWERSTATE_SUBCODE: 4

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003558ca6 to fffff800034ccc40

STACK_TEXT:
fffff800`0525a398 fffff800`03558ca6 : 00000000`0000009f 00000000`00000004 00000000`00000258 00000000`00000000 : nt!KeBugCheckEx
fffff800`0525a3a0 fffff800`0370a2fc : fffff800`00000000 fffff800`00000000 00000000`00000000 fffff800`034d55fa : nt!PnpBugcheckPowerTimeout+0x76
fffff800`0525a400 fffff800`034d85fc : fffffa80`06a00000 fffff880`00000000 fffffa80`40c30089 fffff880`0feb5416 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff800`0525a430 fffff800`034d8496 : fffff880`03f549c0 00000000`0008d6a4 00000000`00000000 fffff880`0feb5416 : nt!KiProcessTimerDpcTable+0x6c
fffff800`0525a4a0 fffff800`034d837e : 00000015`09f6c689 fffff800`0525ab18 00000000`0008d6a4 fffff800`03646708 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0525aaf0 fffff800`034d8167 : 00000006`f851e5c2 00000006`0008d6a4 00000006`f851e557 00000000`000000a4 : nt!KiTimerExpiration+0x1be
fffff800`0525ab90 fffff800`034c496a : fffff800`03642e80 fffff800`03650cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`0525ac40 00000000`00000000 : fffff800`0525b000 fffff800`05255000 fffff800`0525ac00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+76
fffff800`03558ca6 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+76

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

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

 

[JMH]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[ArchaicWarrior]

Here's the minidump file, it seems exactly like the other?

BTW, thanks for the quick reply!

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


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

Symbol search path is: srv*c:\windows\GDSymbols\*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`03695670
Debug session time: Sat Mar 3 09:19:59.289 2012 (UTC + 11:00)
System Uptime: 0 days 2:30:36.148
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 0, fffff8000525a3d0}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: 0000000000000000, The thread currently holding on to the Pnp lock.
Arg4: fffff8000525a3d0

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


DRVPOWERSTATE_SUBCODE: 4

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003558ca6 to fffff800034ccc40

STACK_TEXT:
fffff800`0525a398 fffff800`03558ca6 : 00000000`0000009f 00000000`00000004 00000000`00000258 00000000`00000000 : nt!KeBugCheckEx
fffff800`0525a3a0 fffff800`0370a2fc : fffff800`00000000 fffff800`00000000 00000000`00000000 fffff800`034d55fa : nt!PnpBugcheckPowerTimeout+0x76
fffff800`0525a400 fffff800`034d85fc : fffffa80`06a00000 fffff880`00000000 fffffa80`40c30089 fffff880`0feb5416 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff800`0525a430 fffff800`034d8496 : fffff880`03f549c0 00000000`0008d6a4 00000000`00000000 fffff880`0feb5416 : nt!KiProcessTimerDpcTable+0x6c
fffff800`0525a4a0 fffff800`034d837e : 00000015`09f6c689 fffff800`0525ab18 00000000`0008d6a4 fffff800`03646708 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0525aaf0 fffff800`034d8167 : 00000006`f851e5c2 00000006`0008d6a4 00000006`f851e557 00000000`000000a4 : nt!KiTimerExpiration+0x1be
fffff800`0525ab90 fffff800`034c496a : fffff800`03642e80 fffff800`03650cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`0525ac40 00000000`00000000 : fffff800`0525b000 fffff800`05255000 fffff800`0525ac00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+76
fffff800`03558ca6 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+76

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+76

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

 

[JMH]

Refer my Post 2.
To analyse your crash we do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

Please re read & follow those directions.
What you have supplied twice is not what was asked for.

 

[ArchaicWarrior]

ok, i've done the changes you asked for, now i'll have to wait for the system to crash again .. probably about 2 weeks.

thanks again.

AW.

 

[JMH]

We await the next DMP's.

 

[ArchaicWarrior]

ok, system just crashed again. I've noted it only crashes on a Saturday, just after I've connect my backup hotswap drive, backedup, removed drive then try to reboot.

BTW, it's not a blue screen of death but a black screen, i says alot of text and "DRIVER_POWER_STATE_FAILURE"


Minidump file

=====================================

Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: srv*c:\windows\GDSymbols\*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`03666000 PsLoadedModuleList = 0xfffff800`038aa670
Debug session time: Sat May 12 10:11:56.503 2012 (UTC + 10:00)
System Uptime: 0 days 1:34:57.362
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 0, fffff80004f333d0}

Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )

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

 

[writhziden]

Please provide the actual .dmp files by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html. Thank you.