Framework Desktop Crashes

Nix1 · April 21, 2026, 9:58pm

Have hard crashed BSOD again with Roblox.
AMD Adren Edition Vers. 26.3.1

WinDBG

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

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

Implicit thread is now ffff888d`186ea040

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1343

    Key  : Analysis.Elapsed.mSec
    Value: 1511

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    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_VRF_3_DXG_POWER_IRP_TIMEOUT_IMAGE_ACPI.sys

    Key  : Failure.Hash
    Value: {4450b202-fb03-b620-ae4a-e3d5e61fa358}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

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

BUGCHECK_P3: fffff800adb99000

BUGCHECK_P4: ffff888d2b426c10

FILE_IN_CAB:  FULLMEMORY.DMP

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


DUMP_FILE_ATTRIBUTES: 0x21800

FAULTING_THREAD:  ffff888d186ea040

DRVPOWERSTATE_SUBCODE:  3

ADDITIONAL_DEBUG_TEXT:  DXG Power IRP timeout.

IRP_ADDRESS: ffff888d2b426c10

DEVICE_OBJECT: ffff888d186ca040

DRIVER_OBJECT: ffff888d18ed3da0

IMAGE_NAME:  ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff800ac230000 ACPI

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFF800ADBA1FB0

STACK_TEXT:  
fffff185`1e01efa0 fffff801`1a258204     : ffffdd01`c8ea2180 ffffdd01`c8ea2198 00000000`00000000 ffff888d`18819040 : nt!KiSwapContext+0x76
fffff185`1e01f0e0 fffff801`1a221eed     : 00000000`00000000 00000000`00000000 fffff185`1e01f270 fffff801`1a18c369 : nt!KiSwapThread+0x6d4
fffff185`1e01f170 fffff801`1a2200e9     : 00000000`00000000 00000000`00000000 ffffe776`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x39d
fffff185`1e01f200 fffff800`abd4923b     : fffff185`1e01f318 ffff888d`00000000 00000000`00000000 ffff888d`2b75c000 : nt!KeWaitForSingleObject+0x859
fffff185`1e01f2e0 fffff800`abd48f4c     : fffff185`1e01f300 00000000`00000004 ffffe552`d1b9c1ec 00000000`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0x2cb
fffff185`1e01f370 fffff800`abd28990     : ffff888d`2b426c10 ffff888d`2b426c10 ffff888d`2b75c180 ffff888d`2b75c030 : dxgkrnl!DpiFdoDispatchPower+0x1c
fffff185`1e01f3a0 fffff801`1a41a557     : fffff185`00000001 ffff888d`4e80f420 ffff888d`4e80f400 ffff888d`00000000 : dxgkrnl!DpiDispatchPower+0xe0
fffff185`1e01f4c0 fffff801`1a3b782a     : 00000000`00000000 ffff888d`186ea040 fffff801`1a41a180 00000000`00000000 : nt!PopIrpWorker+0x3d7
fffff185`1e01f570 fffff801`1a5db324     : ffffdd01`c8c64180 ffff888d`186ea040 fffff801`1a3b77d0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff185`1e01f5c0 00000000`00000000     : fffff185`1e020000 fffff185`1e019000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .process /r /p 0xffff888d186b4040; .thread /r /p 0xffff888d186ea040 ; kb

FAILURE_BUCKET_ID:  0x9F_VRF_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:  {4450b202-fb03-b620-ae4a-e3d5e61fa358}

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

!irp ffff888d2b426c10 !devstack ffff888d22af0060 !devobj ffff888d186ca040 !irp ffff888d2b426c10 !blackboxacpi

0: kd> !devstack ffff888d22af0060
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffff888d2b75c030 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\kipudrv.inf_amd64_1a1aa059597c4810\ipustack.sys, Win32 error 0n2
 \Driver\IpuMcdmDriverffff888d2b75c180  
  ffff888d186ca040  \Driver\ACPI       ffff888d21ae94a0  
> ffff888d22af0060  \Driver\pci        ffff888d22af01b0  NTPNP_PCI0034
!DevNode ffff888d22aeeba0 :
  DeviceInst is "PCI\VEN_1022&DEV_17F0&SUBSYS_000AF111&REV_11\4&7deae8d&0&0142"
  ServiceName is "IpuMcdmDriver"
0: kd> !devobj ffff888d186ca040
Device object (ffff888d186ca040) is for:
  \Driver\ACPI DriverObject ffff888d18ed3da0
Current Irp 00000000 RefCount 0 Type 00000032 Flags 00000000
SecurityDescriptor ffff9886519f48e0 DevExt ffff888d21ae94a0 DevObjExt ffff888d186ca190 
ExtensionFlags (0000000000)  
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffff888d2b75c030 \Driver\IpuMcdmDriver
AttachedTo (Lower) ffff888d22af0060 \Driver\pci
Device queue is not busy.
0: kd> !irp ffff888d2b426c10
Irp is active with 6 stacks 4 is current (= 0xffff888d2b426db8)
 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
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff888d186ca040 00000000 fffff800ab9deb60-fffff1851e01f318 Success Error Cancel pending
	       \Driver\ACPI	dxgkrnl!DpiFdoPowerCompletionRoutine
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff888d2b75c030 00000000 fffff8011a28b320-ffff888d4e80f420 Success Error Cancel pending
	       \Driver\IpuMcdmDriver	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff888d4e80f420    

			Args: 00000000 00000000 00000000 00000000

Irp Extension present at 0xffff888d2b426e90:
0: kd> !blackboxacpi

Nix1 · April 22, 2026, 1:44am

Second crash today with a different game on Roblox. One that’s not even that intensive with the GPU at all.
AMD Adren Edition Vers. 26.3.1

WinDBG

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

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

Implicit thread is now ffff888d`186ea040

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1343

    Key  : Analysis.Elapsed.mSec
    Value: 1484

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    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_VRF_3_DXG_POWER_IRP_TIMEOUT_IMAGE_ACPI.sys

    Key  : Failure.Hash
    Value: {4450b202-fb03-b620-ae4a-e3d5e61fa358}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

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

BUGCHECK_P3: fffff800adb99000

BUGCHECK_P4: ffff888d2b426c10

FILE_IN_CAB:  FULLMEMORY.DMP

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


DUMP_FILE_ATTRIBUTES: 0x21800

FAULTING_THREAD:  ffff888d186ea040

DRVPOWERSTATE_SUBCODE:  3

ADDITIONAL_DEBUG_TEXT:  DXG Power IRP timeout.

IRP_ADDRESS: ffff888d2b426c10

DEVICE_OBJECT: ffff888d186ca040

DRIVER_OBJECT: ffff888d18ed3da0

IMAGE_NAME:  ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff800ac230000 ACPI

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFF800ADBA1FB0

STACK_TEXT:  
fffff185`1e01efa0 fffff801`1a258204     : ffffdd01`c8ea2180 ffffdd01`c8ea2198 00000000`00000000 ffff888d`18819040 : nt!KiSwapContext+0x76
fffff185`1e01f0e0 fffff801`1a221eed     : 00000000`00000000 00000000`00000000 fffff185`1e01f270 fffff801`1a18c369 : nt!KiSwapThread+0x6d4
fffff185`1e01f170 fffff801`1a2200e9     : 00000000`00000000 00000000`00000000 ffffe776`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x39d
fffff185`1e01f200 fffff800`abd4923b     : fffff185`1e01f318 ffff888d`00000000 00000000`00000000 ffff888d`2b75c000 : nt!KeWaitForSingleObject+0x859
fffff185`1e01f2e0 fffff800`abd48f4c     : fffff185`1e01f300 00000000`00000004 ffffe552`d1b9c1ec 00000000`00000000 : dxgkrnl!DpiFdoHandleDevicePower+0x2cb
fffff185`1e01f370 fffff800`abd28990     : ffff888d`2b426c10 ffff888d`2b426c10 ffff888d`2b75c180 ffff888d`2b75c030 : dxgkrnl!DpiFdoDispatchPower+0x1c
fffff185`1e01f3a0 fffff801`1a41a557     : fffff185`00000001 ffff888d`4e80f420 ffff888d`4e80f400 ffff888d`00000000 : dxgkrnl!DpiDispatchPower+0xe0
fffff185`1e01f4c0 fffff801`1a3b782a     : 00000000`00000000 ffff888d`186ea040 fffff801`1a41a180 00000000`00000000 : nt!PopIrpWorker+0x3d7
fffff185`1e01f570 fffff801`1a5db324     : ffffdd01`c8c64180 ffff888d`186ea040 fffff801`1a3b77d0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff185`1e01f5c0 00000000`00000000     : fffff185`1e020000 fffff185`1e019000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .process /r /p 0xffff888d186b4040; .thread /r /p 0xffff888d186ea040 ; kb

FAILURE_BUCKET_ID:  0x9F_VRF_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:  {4450b202-fb03-b620-ae4a-e3d5e61fa358}

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

Nix1 · April 24, 2026, 6:11pm

Would be going back and forth with another person in regards to possibly finding out what’s up, just still working on it, sharing the link if any Framework team members want to collect info of any of the logs or actions I’ve been doing.

https://www.elevenforum.com/t/persistant-bsod-when-trying-to-use-the-framework-desktop.46308

Nix1 · April 25, 2026, 8:03pm

Based on my assumptions, it seems like the drivers for the AMD RZ717 Wi-Fi 7 is still very moderately buggy, may consider others that want to test something, use a Wi-Fi dongle and remove/disable their Wi-Fi drivers if this stops your crashing.

Being that it’s still moderately difficult to find direct downloads for this driver is a little iffy other than downloading the ones from the Framework driver bundle, version 5.6.0.4444

I have that driver disabled and hadn’t had any BSOD’s while doing a heavy driver verification test and google results for this driver says other Framework laptops encounter " DRIVER_POWER_STATE_FAILURE" BSOD’s with this Wi-Fi device and driver, which I had encountered earlier in this thread.

Maddious · April 26, 2026, 11:30am

It has been interesting reading the other forum posts. But as for me, I didn’t have a singe BSOD, just a system freezing problem while gaming. Still that it can be a Wi-Fi driver is still interesting, here is a link to the MS Update Catalog, for some verified ms drivers that are more up to date.

Look for a 25H2 version of 5.7.0.5115, I’m still on 5.60.4444, and waiting on driver pack update from framework. While I take my time with establishing a baseline, as my life priorities put this on the backburner for now.

PS, You should just disable BitLocker while testing, and to boot in Windows Recovery Environment (WinRE) to manually get in to safe mode from there, hold down the “Shift” key on your keyboard and click Restart from the Power menu. The 3 power cycle option can get your windows/ssd corrupted.

David_Kwok · April 26, 2026, 3:16pm

Had a similar issue - it’s caused by the most recent driver release from AMD. Remove the driver from the system reinstall the framework driver and disable auto updates. Framework Desktop doesn’t play well with other drivers.

RobG · April 26, 2026, 4:52pm

Not sure why, but searching this way doesn’t show the latest MediaTek WiFi and Bluetooth drivers, current version for both is 26.30.3.60

MediaTek WiFi

MediaTek Bluetooth

Maddious · April 26, 2026, 5:12pm

That is yes and no, ASUS uses a different version number according to AI, that is a higher number (26.30.3.59) for Wi-Fi.

25.30.3.59 and 5.7.0.5115 should be the same, but I’ll just stick with more global version number (5.7.0.5115)

It’s a bit confusing. Just use driver pack original version numbers as reference.

Nix1 · April 27, 2026, 10:11am

Framework does want to try to support the public release of the drivers from AMD, so it seems they intend to support just straight from manufacturer drivers.

But totally, if you’re looking for current stability, disable all driver auto updates after using the framework driver bundle.

Nix1 · May 1, 2026, 11:55pm

As a trick for users that frequently have to enter safe mode, you can add it as a boot menu option, in which you can choose every time the system boots, and still keep bitlocker on safely without having to re-enter the recovery key to enter safemode.

bcdedit /copy {current} /d "Safe Mode"
bcdedit /set {  <GUID-FROM-PRIOR-COMMAND>  } safeboot minimal
bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /timeout 10

Then can remove/add it an alternative way, through msconfig > Boot.

Topic		Replies	Views
Instability while Gaming (AMD Graphics Drivers Crash -- Alot) Framework Desktop gaming	34	3952	February 6, 2026
Random hard freezes fw13 amd7840u win11 Community Support amd-7040 , freezing-crashing	485	35988	April 17, 2026
Framework Desktop General Stability Framework Desktop	30	1010	May 22, 2026
FRWK16 - AMD Software: Adrenalin Edition 24.9.1 - ISSUES Framework Laptop 16 framework-laptop-16-amd-7040	200	13284	April 5, 2026
Framework Laptop 13 Ryzen 7040 BIOS 3.05 Release and Driver Bundle Framework Laptop 13 bios-announcement	294	43577	March 14, 2025

Framework Desktop Crashes

Related topics