Blue Screen of Death

kgash · Sep 8, 2023

I got a BSOD and my PC shut down. After restarting it, I tried to reboot it and it hung as soon as the Restarting appeared on the screen.
The BSOD screen said Driver Power State Failure.

Windows 10 home 64, V. 22H2 Build 22621.2134
ASRock B450 Pro4 MOBO
MSI Radeon RX 5700 DirectX 12 RX 5700 EVOKE
Crucial P1 1TB NVMe PCIe
AMC Radeon RX 5700 GPU (Driver er. 19.30.02)
16 GB DDR4 DRAM
EVGA 650 B5 PSU
2 Viewsonic monitors, 1 on HDMI and 1 on DP
Microsoft HD Webcam C615 (Microphone)

FreeBooter · Sep 8, 2023

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

kgash · Sep 8, 2023

Link to .zip file

KEN-DESKTOP-(2023-09-08_08-53-22).zip

Shared with Dropbox

www.dropbox.com

zbook · Sep 8, 2023

Please perform the following steps:

1) Uninstall and reinstall these drivers:

a) amdkmdag.sys

b) netr28ux.sys

c) rtwlanu.sys

amdwddmg amdwddmg c:\windows\system32\driverstore\filerepository\u0395510.inf_amd64_266bc083bb7590df\b395348\amdkmdag.sys

netr28ux RT2870 USB Extensible Wireless LAN Card Driver c:\windows\system32\drivers\netr28ux.sys

rtlwlanu Realtek Wireless LAN 802.11n USB 2.0 Network Adapter c:\windows\system32\drivers\rtwlanu.sys

For the AMD GPU uninstall using DDU.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.1.0.0

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

https://www.amd.com/en/support

2) Open administrative command prompt and copy and paste:

msdt.exe -id WindowsUpdateDiagnostic
msdt.exe -id DeviceDiagnostic

3) The BIOS Version/Date American Megatrends Inc. P3.90, 12/12/2019

Upgrade the BIOS to the most up to date non-beta BIOS.

ASRock > B450 Pro4

Supports AMD AM4 Socket Ryzen™ 2000, 3000, 4000 G-Series, 5000 and 5000 G-Series Desktop Processors; Supports DDR4 3200+ (OC); 2 PCIe 3.0 x16, 4 PCIe 2.0 x1; AMD Quad CrossFireX™; Graphics Output: HDMI, DisplayPort, D-Sub; 7.1 CH HD Audio (Realtek ALC892 Audio Codec), ELNA Audio Caps; 6 SATA3, 1...

www.asrock.com

Code:

Name    AMD Radeon RX 5700
PNP Device ID    PCI\VEN_1002&DEV_731F&SUBSYS_38141462&REV_C4\6&24B00ECC&0&00000019
Adapter Type    AMD Radeon Graphics Processor (0x731F), Advanced Micro Devices, Inc. compatible
Adapter Description    AMD Radeon RX 5700
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\u0395510.inf_amd64_266bc083bb7590df\B395348\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0395510.inf_amd64_266bc083bb7590df\B395348\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0395510.inf_amd64_266bc083bb7590df\B395348\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0395510.inf_amd64_266bc083bb7590df\B395348\amdxc64.dll
Driver Version    31.0.21031.1005
INF File    oem63.inf (ati2mtag_Navi10 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0395510.INF_AMD64_266BC083BB7590DF\B395348\AMDKMDAG.SYS (31.0.21031.1005, 95.43 MB (100,066,240 bytes), 9/6/2023 8:36 AM)

Code:

Name    [00000021] TP-Link Wireless USB Adapter
Adapter Type    Ethernet 802.3
Product Type    TP-Link Wireless USB Adapter
Installed    Yes
PNP Device ID    USB\VID_0BDA&PID_C820&MI_02\8&1D92DF5B&0&0002
Last Reset    9/8/2023 7:49 AM
Index    21
Service Name    RtWlanu
Driver    C:\WINDOWS\SYSTEM32\DRIVERS\RTWLANU.SYS (1030.44.531.2021, 11.61 MB (12,172,096 bytes), 9/4/2023 10:19 AM)

kgash · Sep 8, 2023

Thank you Zbook for your detailed response. I'm somewhat new at this so after I uninstall a driver how do I reinstall it?

zbook · Sep 8, 2023

Please see:

Redirecting

For networking drivers > download new drivers to the desktop > disconnect from both Ethernet and Wifi > uninstall driver (s) > install diver displayed on the desktop

kgash · Sep 8, 2023

Thanks again for the information. I am getting the feeling that I am about to descend into a rabbit hole.
Even though I have built my own system I do not understand drivers very well. Since the first thing I did after the initial BSOD a couple of days ago was to do a full update of the Radeon GPU and the network drivers I assumed all appropriate drivers were installed.
I'm concerned that if I install a wrong driver it will mess things up.
I need a break now and will try to pick up this thread in a day or so.

FreeBooter · Sep 8, 2023

If you wonder how to update specific device drivers for Windows 10 and Windows 11, you will find all you need to know in this guide.

zbook · Sep 8, 2023

When there are BSOD the most common causes are misbehaving drivers and malfunctioning hardware.

Drivers are files and can become corrupt.

Uninstall drivers and replace them with any version seeking a stable computer environment.

If the computer remains unstable with different versions then swap test hardware.

ubuysa · Sep 9, 2023

This would appear to be a problem with a Realtek USB attached WiFi/Bluetooth adapter. Of the five dumps, four are a 0x9F bugcheck (DRIVER_POWER_STATE_FAILURE), the other is an (unusual) 0xA0000001 bugcheck, which is a bugcheck code for an unknown reason.

The 0x9F bugchecks happened because a device failed to complete a power transition in a specific time. The power transition is managed by a structure called an IRP (Interrupt Request Packet) and since these are scare system resource they cannot be held for too long. In the dumps we get some important information about this bugcheck...

Code:

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

Argument 4 contains the address of the IRP that's being held for too long (it's said to be 'blocked'). If we display this IRP we get...

Code:

1: kd> !irp ffffd186a576c040
Irp is active with 22 stacks 20 is current (= 0xffffd186a576c668)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     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
 [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
 [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
 [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
 [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
 [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_WAIT_WAKE(0)]
            0  0 ffffd1868fe240a0 00000000 fffff80445977db0-ffffd1868fe951a0 
           \Driver\usbccgp    ndis!ndisSetDevicePowerOnComplete
            Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd1868fe95050 00000000 00000000-00000000    pending
          Unable to load image \SystemRoot\System32\drivers\rtwlanu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rtwlanu.sys
 \Driver\RtlWlanu
            Args: 00041100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd1868fc449c0 00000000 fffff804432d5ee0-ffffd1868fc8c1b0 Success Error Cancel pending
           \Driver\vwifibus    nt!PopRequestCompletion
            Args: 00041100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffd1868fc8c1b0 

            Args: 00000000 00000000 00000000 00000000

You can see at the bottom there the driver vwifibus.sys and the function is IRP_MJ_POWER, so this is the driver that's failed the power transition and is holding the IRP for too long. The vwifibus.sys driver is the WIndows virtual wifi bus driver and it's not at fault (because it's a Microsoft driver), but we know the problem device is a wireless device. Above the vwifibus.sys entry you can see another driver involved in this power transition; usbccgp.sys, this is the Windows USB common class generic parent driver, it's the high-level USB driver. Because it's a Microsoft driver this is not the cause of the BSOD either. We knopw from this however, that we're looking for a USB attached wireless device.

Argument 2 above give use the device object address of the actual device. If we display this device object we get...

Code:

1: kd> !devobj ffffd1868fe240a0
Device object (ffffd1868fe240a0) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\usbccgp DriverObject ffffd18690b84300
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00003040
SecurityDescriptor ffff8000b73b2d60 DevExt ffffd1868fe241f0 DevObjExt ffffd1868fe24760 DevNode ffffd1868fe2dbb0
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffd1868fe95050 \Driver\RtlWlanu
Device queue is not busy.

This is the WIndows internal representation of the device, it includes the address of the device node (DevNode) which describes the actual device. Displaying the device node we get...

Code:

1: kd> !devnode ffffd1868fe2dbb0
DevNode 0xffffd1868fe2dbb0 for PDO 0xffffd1868fe240a0
  Parent 0xffffd18690b35c00   Sibling 0000000000   Child 0xffffd186a3ec6730
  InstancePath is "USB\VID_0BDA&PID_C820&MI_02\8&1d92df5b&0&0002"
  ServiceName is "RtlWlanu"
  State = DeviceNodeStarted (0x30a)
  Previous State = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[10] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[09] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[08] = DeviceNodeStarted (0x30a)
  StateHistory[07] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[06] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[05] = DeviceNodeStarted (0x30a)
  StateHistory[04] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[03] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[02] = DeviceNodeStarted (0x30a)
  StateHistory[01] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[00] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[19] = DeviceNodeStarted (0x30a)
  StateHistory[18] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[17] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[16] = DeviceNodeStarted (0x30a)
  StateHistory[15] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[14] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[13] = DeviceNodeStarted (0x30a)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30e)
  Flags (0x4c000130)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_DEVICE_FILTERS,
                      DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
  CapabilityFlags (0x00001c03)  DeviceD1, DeviceD2,
                                WakeFromD0, WakeFromD1,
                                WakeFromD2

The key information there is the USB\VID_0BDA&PID_C820 details. The VID and DEV numbers identify the physical device, if you look those up you'll find they relate to a Realtek-based USB WiFi and Bluetooth adapter.

Your problem then is that your USB wireless adapter has failed to perform a power transition (from low power to high power, or vice-versa) in a reasonable time. This may be the adapter itself, but it's more likely to be the driver for the adapter. Visit the website for the specific make and model wireless adapter and check for an updated driver. Alternatively you could go into the settings for the power plan in use and disable the USB selective suspend setting to stop the USB device doing power transitions at all.

BTW. Since I don't believe in coincidences, I suspect that the lone 0xA0000001 bugcheck was also caused by the wireless adapter, but we'll find out once you solve the adapter issue.

kgash · Sep 11, 2023

On Saturday I removed the wireless WiFi adapter and have had no BSODs since then. I know this is not a complete solution but since I really don't need WiFi on my desktop pc it should suffice for now.
Thanks to everyone for their detailed analyses and suggestions. I learned a great deal about device drivers and crash analysis.

Blue Screen of Death

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Similar threads