[FW13][W11] BSOD when IDLE a few minits and screen off

danibash · October 17, 2025, 8:37am

Hello community,
I am experiencing a highly specific and consistently reproducible BSOD on my new Framework Laptop 13 (AMD). I would appreciate any insight or assistance.

System Details:

Laptop: Framework Laptop 13
CPU: AMD AI 370
OS: Fresh installation of Windows 11 Pro
BIOS Version: 3.04
Drivers: The official Framework Driver Bundle for the AMD model, installed immediately after the OS. Also tried latest AMD drivers

Problem Description:

The system crashes with a DRIVER_POWER_STATE_FAILURE (9f) blue screen. This BSOD only occurs under the following very specific conditions:

The laptop is left idle, running on AC power (dont tried with battery)
The crash happens after several minutes that the screen powers off on IDLE status, also happens with music playing in background.

The crash does not occur if:

The laptop is being used actively.

Troubleshooting Steps Performed:

Clean OS Install: The issue was present on a fresh installation of Windows 11.
Official Drivers: The first thing I installed was the official Framework Driver Bundle. The issue persists.
Memory Dump Analysis: I analyzed the full MEMORY.DMP file using WinDbg. The analysis points directly to a timeout in the DirectX Graphics Kernel Subsystem (dxgkrnl) during a power IRP request.

WinDbg Analysis Summary:

The !analyze -v output provided the following key information, clearly indicating a graphics driver power state issue:

.......................................
*******************************************************************************
*                                                                             *
*                        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: ffffd28e6ff11060, Physical Device Object of the stack
Arg3: ffffa30a794e79f0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd28e76eb9790, The blocked IRP

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

Implicit thread is now ffffd28e`6b723080

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3656

    Key  : Analysis.Elapsed.mSec
    Value: 24264

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27920.1001

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x9f

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 0x21800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_ACPI.sys

    Key  : Failure.Hash
    Value: {647b8107-c400-6fbe-5ce8-dc5911f35388}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x6493cfd4

    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: 1

    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: 38670575

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24e10ef

    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: 0x3f7

    Key  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : Stack.Pointer
    Value: NMI

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 3.4.0.0


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd28e6ff11060

BUGCHECK_P3: ffffa30a794e79f0

BUGCHECK_P4: ffffd28e76eb9790

FILE_IN_CAB:  MEMORY.DMP

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


DUMP_FILE_ATTRIBUTES: 0x21800

FAULTING_THREAD:  ffffd28e6b723080

DRVPOWERSTATE_SUBCODE:  3

ADDITIONAL_DEBUG_TEXT:  DXG Power IRP timeout.

IRP_ADDRESS: ffffd28e76eb9790

DEVICE_OBJECT: ffffd28e6ff3cbd0

DRIVER_OBJECT: ffffd28e6b6aac90

IMAGE_NAME:  ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff8070b340000 ACPI

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFA30A794E7FB0

STACK_TEXT:  
ffffa30a`7941ef60 fffff807`78e566f0     : 00000000`00000047 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76
ffffa30a`7941f0a0 fffff807`78ece6cd     : ffffd28e`6b723080 ffffbd01`36000180 ffffa30a`7941f270 ffffd28e`6ff3cbd0 : nt!KiSwapThread+0x6b0
ffffa30a`7941f170 fffff807`78ecd34f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x39d
ffffa30a`7941f200 fffff807`0add3010     : ffffa30a`7941f318 ffffd28e`00000000 00000000`00000000 ffffd28e`81a51000 : nt!KeWaitForSingleObject+0x71f
ffffa30a`7941f2e0 fffff807`0add2d1c     : ffffa30a`7941f300 00000000`00000004 ffffb5a5`6af59298 00000000`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0x2d0
ffffa30a`7941f370 fffff807`0adabc50     : ffffd28e`76eb9790 ffffd28e`76eb9790 ffffd28e`81a51180 ffffd28e`81a51030 : dxgkrnl!DpiFdoDispatchPower+0x1c
ffffa30a`7941f3a0 fffff807`78eedc6b     : ffffa30a`00000001 ffffd28e`81a51030 ffffd28e`81a51030 ffffbd01`00000000 : dxgkrnl!DpiDispatchPower+0xe0
ffffa30a`7941f4c0 fffff807`79081afa     : 00000000`00000000 ffffd28e`6b723080 fffff807`78eeda10 00000000`00000000 : nt!PopIrpWorker+0x25b
ffffa30a`7941f570 fffff807`7929ef84     : ffffbd01`361d3180 ffffd28e`6b723080 fffff807`79081aa0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffa30a`7941f5c0 00000000`00000000     : ffffa30a`79420000 ffffa30a`79419000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .process /r /p 0xffffd28e6b67a040; .thread 0xffffd28e6b723080 ; kb

FAILURE_BUCKET_ID:  0x9F_3_DXG_POWER_IRP_TIMEOUT_IMAGE_ACPI.sys

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {647b8107-c400-6fbe-5ce8-dc5911f35388}

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

UPDATE1 (17/10/2025):
Ticket opened to FW support and bug report send to AMD using crash reporter.

danibash · October 20, 2025, 6:17pm

UPDATE2 (20/10/2025):
Support answer very fast (during weekend) but maybe this issue in my case are fixed disabling “PCI Express” power saving under active power plan settings.
So far, I’ve been 3 days without any BSOD regarding this.

danibash · October 23, 2025, 10:24am

UPDATE3 (23/10/2025):
Still no BSOD on IDLE, only a few Windows freezes while playing Fornite with AMD Adrenalin v25.9.1.

Topic		Replies	Views
Windows 11 BSOD DRIVER_POWER_STATE_FAILURE Intel Audio Driver Framework Laptop 13	1	812	April 8, 2022
AMD 7040 13 - BSOD Issues Out of the Box Framework Laptop 13	9	1778	December 21, 2023
[TRACKING] Instant power loss Community Support hardware	133	23411	April 26, 2023
Help Requested: Repeated BSOD - Internal Power Error Framework Laptop 13	0	503	November 9, 2021
Unable to wake from sleep Framework Laptop 13	87	20231	November 1, 2023

[FW13][W11] BSOD when IDLE a few minits and screen off

Related topics