BSOD DRIVER_POWER_STATE_FAILURE, sometimes really long boot times and keyboard not working on boot

[matetoes]

Hi all!

I've been getting DRIVER_POWER_STATE_FAILURE (I got it once as I was plugging in a keyboard, so it might be related to that) and often, keyboards did not work on boot.

I also have extremely long boot times sometimes (especially after the BSoD) lasting up to 20 or 30 minutes on the Windows boot logo and the spinning circle (yet I am using an SSD).

Specs:

· Windows 10 Enterprise LTSC (build 17763)
· x64
· Windows 10 Insider Preview
· Retail
· 3 years
· My OS is a few weeks old - I have just reinstalled it once

· AMD FX-6350 (3.90 GHz)
· AMD Radeon R7 200 Series
· BIOSTAR TA970
· Raidmax RX-730SS (730 watts)

· System Manufacturer: N/A
· Exact model number: N/A

· Desktop


I have attached the Sysnative zip file.

Thanks!

 

[MrPepka]

Update:
BIOS (Best motherboard manufacturers. Biostar provides various high quality motherboard gaming series, including am4 motherboa)
Windows 10 to version 1903 (https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant)
And test your disks with SeaTools (Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test)

 

[matetoes]

OK, thanks for the quick reply. I will update my BIOS and Windows version. I'll also test my disk, but I just bought it a few weeks ago, so that might not be the problem.

 

[Patrick]

Not sure what the BIOS has to do with an 0x3 9F bugcheck as mentioned earlier above. It's a driver problem, and we will need you to enable Driver Verifier in order to pinpoint which driver is blocking the IRP.

5: kd> !irp ffffcc0e06037250
Irp is active with 5 stacks 2 is current (= 0xffffcc0e06037368)
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
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffcc0e070bd060 00000000 fffff8071beb90f0-ffffcc0e0764f840 Success Error Cancel pending
           \Driver\atapi    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffcc0e0764f300 00000000 fffff8071b0e45c0-00000000 Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffcc0e071f9980 00000000 fffff80716f6bd30-ffffcc0e063fad00 Success Error Cancel pending
           \Driver\partmgr    nt!PopRequestCompletion

Looks to be a driver that is working closely with storage, so we'll see after the system crashes with verifier enabled - Driver Verifier - Windows drivers

 

[matetoes]

Alright. I enabled Driver Verifier, so I just have to wait for it to BSoD again and give you a new SysnativeFileCollectionApp.zip file, right?

BTW, I have already updated the BIOS in accordance to @MrPepka. Of course, I cannot update to 1903 since I am running LTSC, so I didn't try that.

 

[x BlueRobot]

Alright. I enabled Driver Verifier, so I just have to wait for it to BSoD again and give you a new SysnativeFileCollectionApp.zip file, right?

[...]

Yes, that's right, hopefully Driver Verifier will be able to pinpoint the issue.

 

[MrPepka]

@Patrick I meant that the BIOS may have had some error that resulted in power problems (which, according to the error code, led to blue screens)

 

[x BlueRobot]

IRPs are managed by the I/O manager, in particular, Stop 0x9F is related to power IRPs which are used to manage device power states during shutdowns and reboots for instance. I would be doubtful that the BIOS would be the issue here.