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.


BSOD on Hibernate - BCCode x1000009f [Windows 7]

  • Please log in to reply
1 reply to this topic

#1 melisende


  • Members
  • 1 posts
  • Local time:11:56 PM

Posted 05 June 2018 - 10:44 AM

Please help! I tried to set my computer to sleep and got the BSOD message:


Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.
  Locale ID: 1033

Additional information about the problem:
  BCCode: 1000009f
  BCP1: 0000000000000004
  BCP2: 0000000000000258
  BCP3: FFFFFA800D1CD660
  BCP4: FFFFF80005CBF420
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1

Files that help describe the problem:

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:




I have the minidump file but I don't have a program that can open it nor attach it. I searched for the WER-19562-0.sysdata.xml file but it's not in Temp, strangely. I see another WER file instead: WER-14024-0.sysdata which I cannot open. I am the admin but it says access is denied.





Attached Files

BC AdBot (Login to Remove)


#2 jcgriff2


  • BSOD Kernel Dump Expert
  • 1,109 posts
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:01:56 AM

Posted 07 June 2018 - 03:42 PM

Hi. . .

Two BSODs in the attached zip file - about 30 days apart.

The bugcheck on both BSODs was 0x9f - driver power state failure

BugCheck 9F, {3, fffffa801132acc0, fffff80000b9a3d8, fffffa8012c39c60}
BugCheck 1000009F, {4, 258, fffffa800d1cd660, fffff80005cbf420}

The bugcheck parms differed slightly. Parm 1 (the first number inside the parenthesis) was 0x3 on one dump and 0x4 on the other.

0x4 - driver failed to complete a power IRP within a given time. No 3rd party driver was mentioned. Windbg list the NT Kernel as the probable cause. This is simply a default -- the NT Kernel is just fine.

0x3 - a device object has been blocking an IRP for too long a time. Parm 4 is the actual IRP being blocked (0xa8012c39c60, so we can look it up within the mini kernel memory dump and see if any 3rd party driver is associated with it.

[font=verdana]0: kd> !irp fffffa80`12c39c60
Irp is active with 6 stacks 5 is current (= 0xfffffa8012c39e50)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
            0 e1 fffffa8011658890 00000000 00000000-00000000    pending
	      *** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
			Args: 00000000 00000001 00000004 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa801145c880    

			Args: 00000000 00000000 00000000 00000000
This one did list a 3rd party driver - asmthub3.sys - ASMedia USB 3.0 Hub driver

See if you can find a driver update for it - https://www.sysnative.com/drivers/driver.php?id=asmthub3.sys

The timestamp of your current driver -

asmthub3.sys Thu Feb 12 01:57:05 2015 (54DC4EC1)
So, you obviously want to find a driver with a timestamp greater (newer) than February 2015.

Regards. . .


Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users