Question BSOD Driver_power_state_failure

jdelapp

Commendable
Jul 26, 2018
6
0
1,510
0
Ryzen 5 3600
MSI Radeon RX 570 DirectX 12 RX 570 8GT OC 8GB 256-Bit GDDR5 PCI Express x16 (Uses x8) HDCP Ready ATX Video Card
MSI PERFORMANCE GAMING X470 GAMING PLUS MAX
Intel 660p Series M.2 2280 1TB PCIe NVMe
CORSAIR Vengeance RGB Pro 16GB (2 x 8GB) DDR4 3200 Model CMW16GX4M2C3200C16

EVGA SuperNOVA 650 G3, 80 Plus Gold 650W, Fully Mo
Fractal Design Meshify C

The system is about 4 months old now and all was fine in the beginning. I experienced crashing when playing Unreal Tournament GOTY edition about a week or two after building it. This still exitst and haven't found a fix for it yet. At this time they system will not go to sleep. It will turn off the monitors but not go into sleep mode and in order to get the monitors back on it requires a hard reboot. 90% of the time when it restarts it gets a Driver_Power_state_Failure error and then restarts. It can take up to 5 or 7 minutes for it to go through the process. 50% of the time when I try to hsut it down the monitors will turn off but the system will not shut down and a hard reboot is required. I have tried everything I know to do and have researched on. Updating all drivers, BIOS, Windows 10 with no success. I have restored from backups with not success. I have even reinstalled a fresh Windows using the media creation tool.

Below is the complete minidump file, I don't know how to read this and can't find anything relevant to 2020 when I search. Anyone know whats going on here and how to fix it?? I just a stable system back.

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

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

* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80742c00000 PsLoadedModuleList = 0xfffff8074382a330
Debug session time: Tue Aug 11 18:48:12.133 2020 (UTC - 5:00)
System Uptime: 0 days 1:49:04.767
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80742fddf40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffba0337a37850=000000000000009f
2: kd> !analyze -v
***
* Bugcheck Analysis *
***

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

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

Implicit thread is now ffff80077f57a040
Unable to load image \SystemRoot\System32\drivers\amd_xata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_xata.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3296

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-S5R5EN0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 5021

Key : Analysis.Memory.CommitPeak.Mb
Value: 85

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 9f

BUGCHECK_P1: 4

BUGCHECK_P2: 12c

BUGCHECK_P3: ffff80077f57a040

BUGCHECK_P4: ffffba0337a37880

DRVPOWERSTATE_SUBCODE: 4

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff807474a0000 pci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

BAD_STACK_POINTER: ffffba0337a37848

STACK_TEXT:
ffffba03
37a37848 fffff80743113f06 : 000000000000009f 0000000000000004 000000000000012c ffff80077f57a040 : nt!KeBugCheckEx
ffffba03
37a37850 fffff807435bead6 : 0000000000000000 0000000000000005 000000000003cf57 ffffba0337a37b10 : nt!PnpBugcheckPowerTimeout+0x76
ffffba03
37a378b0 fffff80742e368f2 : ffffba0337baf520 ffffbc81742a5180 ffffbc81742a5180 0000000000000002 : nt!PopBuildDeviceNotifyListWatchdog+0x16
ffffba03
37a378e0 fffff80742e39d8d : 0000000000000000 0000000000000000 0000000000140001 000000000003cf57 : nt!KiProcessExpiredTimerList+0x172
ffffba03
37a379d0 fffff80742fe1aae : ffffffff00000000 ffffbc81742a5180 ffffbc81742b0340 ffff800775c73080 : nt!KiRetireDpcList+0x5dd
ffffba03
37a37c60 0000000000000000 : ffffba0337a38000 ffffba0337a32000 0000000000000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION: 10.0.19041.423

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_4_amd_sata_IMAGE_pci.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {95c7d19c-c084-e356-ffb8-0e9c09668a9d}

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

 
Aug 10, 2020
67
3
35
0
Win32k.sys checksum error in your dump: https://file-intelligence.comodo.com/windows-process-virus-malware/SYS/WIN32K
Several messages of amd disk driver failure.
You say system box doesn't turn off. However it is not on because "hard reboot" (hard like hitting the switch with a hammer? Disconnect power at the wall outlet?) is required. If legacy usb support is enabled in BIOS then ctrl-alt-del should work. Dump indicates windows asked the motherboard bios to shut down power but it never responded so windows exits anyway. Also the thread to communicate with the motherboards plug and play system was locked by another application, unrecognized by windows. The SATA driver errors may mean something else is using the disk. You didn't mention the drives spinning down as monitors went off. Something is taking priority access of your disk away from windows. Perhaps you are running windows inside another shell or virtual environment, or a boot sector virus loadind before windows. Another error says the image of hardware drivers for your plug and play motherboard can't be loaded from the drive. Motherboard flash BIOS does deteriorate over time. Disconnect the hard drive and see if boots from CD (I keep Knoppix around) or write protected USB, then try shutdown. If you installed Win10 into the same directory, no fixes are made. Some virus files will be on the root of C because (stupid) Windows first checks root and then windows directory then c:\windows\system32 directory where the file should be. A boot sector virus will not be removed by Windows setup.
 
Aug 10, 2020
67
3
35
0
There is an answer "DRIVER_POWER_STATE_FAILURE (9f)"
But it is a failure in an intel storage driver. Your error is in pci.sys or the hardware model of a modern plug and play BIOS system in Windows. Perhaps motherboard drivers that were in Win7 are not in clean Win 10. You don't mention storage type and several errors like: "FAILURE_BUCKET_ID: 0x9F_4_amd_sata_IMAGE_pci.sys"
point to AMD SATA issue. Used to be common for mfgs to install as "emulated ide" in BIOS but plug and play detects "native sata" which is totally incompatible with prebuilt driver stack.
 

ASK THE COMMUNITY

TRENDING THREADS