Question DEVICE_POWER_FAILURE BOSD on new build

[mikejs78]

Have a brand new build, been getting a periodic BSOD with the stop error DRIVER_POWER_STATE_FAILURE. Fresh install of Windows 11, so no upgrade considerations. Anyone see this before/have suggestions?

Build specs:

CPU: AMD Ryzen 7 7700X 4.5 GHz 8-Core Processor
CPU Cooler: Thermalright Phantom Spirit 66.17 CFM CPU Cooler
Motherboard: Asus ROG STRIX X670E-F GAMING WIFI ATX AM5 Motherboard
Memory: G.Skill Trident Z5 Neo 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory
Storage: Samsung 990 Pro w/Heatsink 1 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Storage: Samsung 990 Pro w/Heatsink 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Storage: Western Digital Blue 2 TB 3.5" 7200 RPM Internal Hard Drive
Video Card: Sapphire NITRO+ Radeon RX 7900 XTX 24 GB Video Card
Case: be quiet! Pure Base 500DX ATX Mid Tower Case
Power Supply: be quiet! Dark Power 13 1000 W 80+ Titanium Certified Fully Modular ATX Power Supply
Case Fan: be quiet! Silent Wings Pro 4 97.41 CFM 140 mm Fan
Case Fan: be quiet! Silent Wings Pro 4 97.41 CFM 140 mm Fan
Case Fan: be quiet! Silent Wings Pro 4 97.41 CFM 140 mm Fan
O/S: Windows 11 Pro

Minidump analyze -v


************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


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

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff804`57400000 PsLoadedModuleList = 0xfffff804`580134a0
Debug session time: Thu Dec 14 08:45:31.016 2023 (UTC - 5:00)
System Uptime: 0 days 0:06:54.357
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000029`35e53018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`57816b00 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff989`c4a3fb20=000000000000009f
1: 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: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffe08be6de6060, Physical Device Object of the stack
Arg3: fffff989c4a3fb68, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe08bee33c420, The blocked IRP

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1125

Key : Analysis.Elapsed.mSec
Value: 3583

Key : Analysis.IO.Other.Mb
Value: 16

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 33

Key : Analysis.Init.CPU.mSec
Value: 125

Key : Analysis.Init.Elapsed.mSec
Value: 25293

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Failure.Bucket
Value: 0x9F_3_AML!_SB.PCI0.GPP0.SWUS.SWDS.HDAU._STA_ACPI_IMAGE_pci.sys

Key : Failure.Hash
Value: {f81fa676-c506-d045-02e8-ba0ed753c0ad}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe08be6de6060

BUGCHECK_P3: fffff989c4a3fb68

BUGCHECK_P4: ffffe08bee33c420

FILE_IN_CAB: 121423-6187-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8045c480000 pci

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MsMpEng.exe

DPC_STACK_BASE: FFFFF989C4A3FFB0

STACK_TEXT:
fffff989`c4a3fb18 fffff804`57981166 : 00000000`0000009f 00000000`00000003 ffffe08b`e6de6060 fffff989`c4a3fb68 : nt!KeBugCheckEx
fffff989`c4a3fb20 fffff804`5798103c : 00000000`00000002 ffffae00`f3b40180 ffffe08b`ee342280 fffff989`c4a3fc99 : nt!PopIrpWatchdogBugcheck+0x122
fffff989`c4a3fba0 fffff804`576763ab : ffffe08b`00000001 00000000`00000001 fffff989`00000000 00000000`00000002 : nt!PopIrpWatchdog+0xc
fffff989`c4a3fbd0 fffff804`57673084 : 00000000`00000024 fffda2f0`358d4898 fffff780`00000014 fffff804`551c6a48 : nt!KiProcessExpiredTimerList+0x1eb
fffff989`c4a3fd00 fffff804`57820135 : cccc0000`36fae8c0 00000000`00000000 ffffae00`f3b40180 00000000`00000000 : nt!KiRetireDpcList+0xaf4
fffff989`c4a3ffb0 fffff804`578200df : fffff989`c6fdf3c9 fffff804`576609d5 00000000`00000004 00000000`00000004 : nt!KxSwapStacksAndRetireDpcList+0x5
fffff989`c6fdf330 fffff804`576609d5 : 00000000`00000004 00000000`00000004 00000000`c6fdf448 00000029`36efe7c0 : nt!KiPlatformSwapStacksAndCallReturn
fffff989`c6fdf340 fffff804`5781f89b : 00000000`00000004 00000000`00000000 000001f0`ddc22e50 00000000`00000000 : nt!KiDispatchInterrupt+0xd5
fffff989`c6fdf430 fffff804`578195e1 : fffff989`c6fdf4e0 00000029`36efe628 000001f0`e5bef650 00000000`00000000 : nt!KiDpcInterruptBypass+0x1b
fffff989`c6fdf460 00007ff8`1e0c5bdb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
00000029`36efe360 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`1e0c5bdb


IMAGE_VERSION: 10.0.22621.1254

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.GPP0.SWUS.SWDS.HDAU._STA_ACPI_IMAGE_pci.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f81fa676-c506-d045-02e8-ba0ed753c0ad}

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

 

[Ralston18]

I suggest going back a step or two.

First, look in Reliabiity History/Monitor and Event Viewer for specific error codes being captured just before or at the time of the BSODs.

Second, power down, unplug, open the case.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place.

No one wants to force anything especially with a new build. So what seems to be fully in place is not.

Carefully plug and unplug each a few times. You may discover that suddenly something simply goes back into place much more easily and smoothly.

 

[ubuysa]

These are fairly easy to diagnose if you upload the dump file. Dump analysis is way more involved than just analyze -v....