Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Slow shutdown-restart, ends with BSOD - power driver state failure


  • Please log in to reply
21 replies to this topic

#1 thostby

thostby

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 07:38 PM

Hello!

 

I have a problem with shutting down when I restart or hibernate. Pc use up to 5-10 min staying on "restarting" screen and Hibernating ends with shutdown - Bsod in both instances.

 

BSOD say "power driver state failure" and bluescreenview say it's caused by drivers: 'mssmbios.sys' and 'mbae64.sys'.

 

Earlier BSOD: 'memory managment'(ntoskrnl.exe), 'system service exception'(ntoskrnl.exe), 'driver verifier detected violation'(nvlddmkm.sys).

 

 

pnp= plug and play? tried removing 'usb card reader', nothing..

 

 

Posting two minidumps from osronline.com:

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff802`c5a76000 PsLoadedModuleList = 0xfffff802`c5d4f250
Debug session time: Sat Jan 24 14:51:17.048 2015 (UTC - 5:00)
System Uptime: 0 days 0:49:30.858
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe001b5452880, The thread currently holding on to the Pnp lock.
Arg4: fffff802c73d1ac0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now ffffe001`b5452880
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: ffffe001b5452880

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff802c5c54446 to fffff802c5bc6aa0

STACK_TEXT:
fffff802`c73d1a88 fffff802`c5c54446 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe001`b5452880 : nt!KeBugCheckEx
fffff802`c73d1a90 fffff802`c5e022c6 : ffffe001`00000000 fffff802`00000000 ffffe001`b4e94900 fffff802`00000000 : nt!PnpBugcheckPowerTimeout+0x6a
fffff802`c73d1af0 fffff802`c5b22c58 : 00000000`00000010 00000000`002cb2c9 fffff802`c5d79180 00001f80`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff802`c73d1b20 fffff802`c5bca5ea : fffff802`c5d79180 fffff802`c5d79180 fffff802`c5dd2a00 ffffe001`b43f7080 : nt!KiRetireDpcList+0x4f8
fffff802`c73d1da0 00000000`00000000 : fffff802`c73d2000 fffff802`c73cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: .thread 0xffffe001b5452880 ; kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+6a
fffff802`c5c54446 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 545167e0

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

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

 

___________________________________________________________________________________________________

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff803`15c16000 PsLoadedModuleList = 0xfffff803`15eef250
Debug session time: Sat Jan 24 18:18:52.061 2015 (UTC - 5:00)
System Uptime: 0 days 2:21:09.101
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe0009e1c7880, The thread currently holding on to the Pnp lock.
Arg4: fffff803175d1ac0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now ffffe000`9e1c7880
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: ffffe0009e1c7880

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80315df4446 to fffff80315d66aa0

STACK_TEXT:
fffff803`175d1a88 fffff803`15df4446 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe000`9e1c7880 : nt!KeBugCheckEx
fffff803`175d1a90 fffff803`15fa22c6 : ffffe000`00000000 fffff803`00000000 ffffe000`9e907b00 fffff803`00000000 : nt!PnpBugcheckPowerTimeout+0x6a
fffff803`175d1af0 fffff803`15cc2c58 : 00000000`0000001e 00000000`002cb2c9 fffff803`15f19180 fffff803`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff803`175d1b20 fffff803`15d6a5ea : fffff803`15f19180 fffff803`15f19180 fffff803`15f72a00 ffffe000`9dd95080 : nt!KiRetireDpcList+0x4f8
fffff803`175d1da0 00000000`00000000 : fffff803`175d2000 fffff803`175cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: .thread 0xffffe0009e1c7880 ; kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+6a
fffff803`15df4446 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 545167e0

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

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



BC AdBot (Login to Remove)

 


#2 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 08:00 PM

nvlddmkm.sys is an nVidia display driver. Try updating to the latest version.


Have you tried turning it off and on again?


#3 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 08:12 PM

nvlddmkm.sys is an nVidia display driver. Try updating to the latest version.

 

Actually I did update that driver back when I had that bsod. I can't remember having those anymore. Just for safe, checked if there were any new updates, but no..

 

thank you, for your suggestion :)



#4 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 08:18 PM

Ok, try uninstalling Malwarebytes Anti Exploit.

After rebooting, see if you still have the problem.


Have you tried turning it off and on again?


#5 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 09:38 PM

Uninstalled Malwarebytes with Revo Uninstaller. Same problem..



#6 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 09:46 PM

What does Bluescreenview say now?


Have you tried turning it off and on again?


#7 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 10:04 PM

012515-7421-01.dmp 25.01.2015 02:40:58 DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000`00000004 00000000`0000012c ffffe001`078fe880 fffff801`969d1ac0 ntoskrnl.exe ntoskrnl.exe+150aa0 NT Kernel & System Microsoft® Windows® Operating System

 

 

BTW: I'm having a problem with the website loading, is it just me?

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff801`95018000 PsLoadedModuleList = 0xfffff801`952f1250
Debug session time: Sat Jan 24 20:40:58.583 2015 (UTC - 5:00)
System Uptime: 0 days 2:19:35.752
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe001078fe880, The thread currently holding on to the Pnp lock.
Arg4: fffff801969d1ac0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now ffffe001`078fe880
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: ffffe001078fe880

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff801951f6446 to fffff80195168aa0

STACK_TEXT:
fffff801`969d1a88 fffff801`951f6446 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe001`078fe880 : nt!KeBugCheckEx
fffff801`969d1a90 fffff801`953a42c6 : ffffe001`00000000 fffff801`00000000 ffffe001`0418db00 fffff801`00000000 : nt!PnpBugcheckPowerTimeout+0x6a
fffff801`969d1af0 fffff801`950c4c58 : 00000000`00000016 00000000`002cb2ca fffff801`9531b180 fffff801`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff801`969d1b20 fffff801`9516c5ea : fffff801`9531b180 fffff801`9531b180 fffff801`95374a00 ffffe001`04449880 : nt!KiRetireDpcList+0x4f8
fffff801`969d1da0 00000000`00000000 : fffff801`969d2000 fffff801`969cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: .thread 0xffffe001078fe880 ; kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+6a
fffff801`951f6446 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 545167e0

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

Followup: MachineOwner


Edited by thostby, 24 January 2015 - 10:12 PM.


#8 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 10:11 PM

What is the make and model of your computer? Usually for things like this it is something like a wireless driver (bluetooth, wlan, wwan, etc).


Have you tried turning it off and on again?


#9 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 10:30 PM

I have built my own som years ago:

Core2 Duo 3ghz

motherboard: Gigabyte X48-DQ6

new SSD hdd

8 gb ram

 

my wireless usb-stick is: Gigabyte GN-W801GS (this is pretty old).

 

Edit: I do have a relative old logitech wireless usb-plug for my keyboard an mouse..


Edited by thostby, 24 January 2015 - 10:36 PM.


#10 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 10:36 PM

Shut down the computer and unplug the Gigabyte USB Wireless Adapter. Start the computer back up and see if you still have the issue.

I'll check for other drivers for your motherboard's chipset etc. in the meantime.


Have you tried turning it off and on again?


#11 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 10:58 PM

Try updating these drivers:

Intel Chipset Driver

Realtek 8111C Drivers Page - Choose the Windows 8 / Server 2012 automatic installer

Realtek Audio Drivers Page - Choose the Windows 8 executable file


Have you tried turning it off and on again?


#12 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 11:09 PM

Unplugged and restarted, gave bsod.

 

Restarted (frozen bsod) and restarted again from windows (still unplugged), which went great (fast and no bsod).

 

I then tried to put it to sleep, and I got the long restarting blank screen and bsod at the end.

 

Will try updating the three and come back with result again.


Edited by thostby, 24 January 2015 - 11:10 PM.


#13 zcomputerwiz

zcomputerwiz

  • Members
  • 312 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:27 PM

Posted 24 January 2015 - 11:17 PM

For troubleshooting, lets turn Windows 8 Fast Boot off.

Follow these instructions to turn off fast startup in windows 8


Have you tried turning it off and on again?


#14 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 24 January 2015 - 11:48 PM

updated. restart is normal. Tried sleep and trouble again. 

 

Plugged in wireless gigabyte and restart gives bsod. unplugg again and no bsod on restart. 

 

This now seems consistent, but the sleep mode doesn't want to join the party.

 

I have a wallplugged wired atm.

 

will try turning off fast boot now.


Edited by thostby, 24 January 2015 - 11:49 PM.


#15 thostby

thostby
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:07:27 PM

Posted 25 January 2015 - 12:19 AM

Shut down is normal (with wireless gigabyte). Have not tried sleep though.

 

I'm posting a couple of the bsod's I've had in the last hours.

 

Bluescreenview say the first bsod post is "caused by driver": SSport.sys. - The other three are ntoskrnl.exe.

 

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff802`08a0f000 PsLoadedModuleList = 0xfffff802`08ce8250
Debug session time: Sat Jan 24 22:47:06.572 2015 (UTC - 5:00)
System Uptime: 0 days 1:14:20.157
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe00070be6040, The thread currently holding on to the Pnp lock.
Arg4: fffff8020a3d1ac0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now ffffe000`70be6040
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: ffffe00070be6040

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80208bed446 to fffff80208b5faa0

STACK_TEXT:
fffff802`0a3d1a88 fffff802`08bed446 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe000`70be6040 : nt!KeBugCheckEx
fffff802`0a3d1a90 fffff802`08d9b2c6 : ffffe000`00000000 fffff802`00000000 ffffe000`7197eb00 fffff802`00000000 : nt!PnpBugcheckPowerTimeout+0x6a
fffff802`0a3d1af0 fffff802`08abbc58 : 00000000`00000018 00000000`002cb2ca fffff802`08d12180 fffff802`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff802`0a3d1b20 fffff802`08b635ea : fffff802`08d12180 fffff802`08d12180 fffff802`08d6ba00 ffffe000`71ed1080 : nt!KiRetireDpcList+0x4f8
fffff802`0a3d1da0 00000000`00000000 : fffff802`0a3d2000 fffff802`0a3cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: .thread 0xffffe00070be6040 ; kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+6a
fffff802`08bed446 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 545167e0

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

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

___________________________________________________________________________________________________________________________

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff803`e3a8e000 PsLoadedModuleList = 0xfffff803`e3d67250
Debug session time: Sat Jan 24 22:57:41.075 2015 (UTC - 5:00)
System Uptime: 0 days 0:05:46.846
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000158a3e50, Physical Device Object of the stack
Arg3: fffff803e53d1aa0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe000171ed8c0, The blocked IRP

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: fffff800111a3000 tap0901

DEVICE_OBJECT: ffffe000161cc050

DRIVER_OBJECT: ffffe0001622d190

IRP_ADDRESS: ffffe000171ed8c0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff803`e53d1a68 fffff803`e3c96f2e : 00000000`0000009f 00000000`00000003 ffffe000`158a3e50 fffff803`e53d1aa0 : nt!KeBugCheckEx
fffff803`e53d1a70 fffff803`e3c96e4e : ffffe000`16ff3bb0 00000000`00000000 ffffe000`16ff3be8 fffff803`e3b3e2f1 : nt!PopIrpWatchdogBugcheck+0xde
fffff803`e53d1ad0 fffff803`e3b3ac58 : 00000000`00000000 fffff803`e53d1c20 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
fffff803`e53d1b20 fffff803`e3be25ea : fffff803`e3d91180 fffff803`e3d91180 fffff803`e3deaa00 ffffe000`17d8d080 : nt!KiRetireDpcList+0x4f8
fffff803`e53d1da0 00000000`00000000 : fffff803`e53d2000 fffff803`e53cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ntkrnlmp

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp

BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp

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

___________________________________________________________________________________________________________________________

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff801`cda8b000 PsLoadedModuleList = 0xfffff801`cdd64250
Debug session time: Sat Jan 24 23:22:41.332 2015 (UTC - 5:00)
System Uptime: 0 days 0:05:52.203
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000659aa590, Physical Device Object of the stack
Arg3: fffff801cf3d1aa0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe000681d9860, The blocked IRP

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff801e9ae2000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff801`cf3d1a68 fffff801`cdc93f2e : 00000000`0000009f 00000000`00000003 ffffe000`659aa590 fffff801`cf3d1aa0 : nt!KeBugCheckEx
fffff801`cf3d1a70 fffff801`cdc93e4e : ffffe000`6808d400 00000000`00000000 00000000`00003536 fffff801`cdb3b2f1 : nt!PopIrpWatchdogBugcheck+0xde
fffff801`cf3d1ad0 fffff801`cdb37c58 : 00000000`00000000 fffff801`cf3d1c20 00000000`00000001 00000000`00000001 : nt!PopIrpWatchdog+0x32
fffff801`cf3d1b20 fffff801`cdbdf5ea : fffff801`cdd8e180 fffff801`cdd8e180 fffff801`cdde7a00 ffffe000`6772f880 : nt!KiRetireDpcList+0x4f8
fffff801`cf3d1da0 00000000`00000000 : fffff801`cf3d2000 fffff801`cf3cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_Rt630x64_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_Rt630x64_IMAGE_pci.sys

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

___________________________________________________________________________________________________________________________
 
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
Machine Name:
Kernel base = 0xfffff800`e9a1d000 PsLoadedModuleList = 0xfffff800`e9cf6250
Debug session time: Sat Jan 24 23:34:43.188 2015 (UTC - 5:00)
System Uptime: 0 days 0:06:50.957
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe0002ee27880, The thread currently holding on to the Pnp lock.
Arg4: fffff800eb3d1ac0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now ffffe000`2ee27880
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: ffffe0002ee27880

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800e9bfb446 to fffff800e9b6daa0

STACK_TEXT:
fffff800`eb3d1a88 fffff800`e9bfb446 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe000`2ee27880 : nt!KeBugCheckEx
fffff800`eb3d1a90 fffff800`e9da92c6 : ffffe000`00000000 fffff800`00000000 ffffe000`2e784700 fffff800`00000000 : nt!PnpBugcheckPowerTimeout+0x6a
fffff800`eb3d1af0 fffff800`e9ac9c58 : 00000000`00000002 00000000`002cb2ca fffff800`e9d20180 fffff800`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff800`eb3d1b20 fffff800`e9b715ea : fffff800`e9d20180 fffff800`e9d20180 fffff800`e9d79a00 ffffe000`2f3c3080 : nt!KiRetireDpcList+0x4f8
fffff800`eb3d1da0 00000000`00000000 : fffff800`eb3d2000 fffff800`eb3cc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: .thread 0xffffe0002ee27880 ; kb

FOLLOWUP_IP:
nt!PnpBugcheckPowerTimeout+6a
fffff800`e9bfb446 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!PnpBugcheckPowerTimeout+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 545167e0

FAILURE_BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

BUCKET_ID: X64_0x9F_4_nt!PnpBugcheckPowerTimeout+6a

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

Edited by thostby, 25 January 2015 - 12:20 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users