Question BSOD when gaming, help with Memory.DMP ?

Logan31 · Dec 7, 2023

Hi,

Sometimes when gaming, my pc reboots out of nowhere, and sometimes I get the BSOD. I installed windbg app to read the memory.dmp file. I'm getting the following. It is the first time I read one of these files, from what I can see it's a problem with my PCI Express device (GPU). I'm running this setup:

CPU: AMD Ryzen 5 2600
Motherboard: Gigabyte B450 AORUS M

RAM: Kingston HyperX Predator DDR4 3200 PC4-25600 16GB 2x8GB CL16

GPU: Gigabyte GeForce RTX 2060 OC 6GB GDDR6

I got the latest drivers for my GPU, BIOS and I think everything else. I'll appreciate any help with this issue.

The memory dump file reads the following.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3015

Key : Analysis.Elapsed.mSec
Value: 5313

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

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

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

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x9f

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 1000

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

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

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : Failure.Bucket
Value: 0x9F_3_USBXHCI_IMAGE_pci.sys

Key : Failure.Hash
Value: {0c1c47d4-b16d-d687-dd86-c4bda0eafae4}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 0

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16777216

Key : Hypervisor.Flags.ValueHex
Value: 1000000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Version
Value: 10.0.22000.1

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe5883997c360

BUGCHECK_P3: ffff888457cb57d0

BUGCHECK_P4: ffffe5883c126010

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff80739e90000 pci

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8884`57cb5798 fffff807`37fc2d47 : 00000000`0000009f 00000000`00000003 ffffe588`3997c360 ffff8884`57cb57d0 : nt!KeBugCheckEx
ffff8884`57cb57a0 fffff807`37fc2c61 : ffffe588`3c56a208 00000000`00000080 ffff8884`57cb5af8 ffff8884`57cb5af0 : nt!PopIrpWatchdogBugcheck+0xdf
ffff8884`57cb5810 fffff807`37ca8324 : 00000000`00000000 ffffd280`00000001 ffff8884`00000000 00000000`00000002 : nt!PopIrpWatchdog+0x31
ffff8884`57cb5860 fffff807`37ca6914 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff807`33e61dc8 : nt!KiProcessExpiredTimerList+0x204
ffff8884`57cb5990 fffff807`37e1bcbe : 00000000`00000000 ffffd280`c3efb180 ffffd280`c3f07340 ffffe588`45d6d080 : nt!KiRetireDpcList+0x714
ffff8884`57cb5c40 00000000`00000000 : ffff8884`57cb6000 ffff8884`57cb0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

IMAGE_VERSION: 10.0.22000.832

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_USBXHCI_IMAGE_pci.sys

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0c1c47d4-b16d-d687-dd86-c4bda0eafae4}

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

ubuysa · Dec 8, 2023

Please upload the dump file to a cloud service with a link to it here - be sure to make it public.

Logan31 · Dec 8, 2023

ubuysa said:
Please upload the dump file to a cloud service with a link to it here - be sure to make it public.

Thanks for the reply, here are the memory dump files

MEMORY.zip

drive.google.com

ubuysa · Dec 9, 2023

The BSOD happened because a device failed to complete a power transition (from low power to normal power) in a timely manner. The dump gives us pointers to help identify the device...

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

Argument 4 is the address of the IRP (interrupt request packet) that Windows uses to manage the power transition....

Code:

11: kd> !irp ffffe5883c126010
Irp is active with 7 stacks 6 is current (= 0xffffe5883c126248)
 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
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffffe5883997c360 00000000 00000000-00000000
           \Driver\pci
            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe5883c28d8f0 00000000 fffff80737da03b0-ffffe5883c56a208 Success Error Cancel pending
           \Driver\USBXHCI    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe5883c56a208

            Args: 00000000 00000000 00000000 00000000

At the bottom of the IRP list above, you can see that the drivers involved were pci.sys and usbxhci.sys - this latter driver is the one holding up the IRP, so we know it's a USB3 device (that's what the usbxhci.sys driver is for).

Argument 2 is the address of the device object (DevObj) that Windows uses to manage the device having the problem...

Code:

11: kd> !devobj ffffe5883997c360
Device object (ffffe5883997c360) is for:
 NTPNP_PCI0021 \Driver\pci DriverObject ffffe588383f06f0
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
SecurityDescriptor ffffc0819ba98ce0 DevExt ffffe5883997c4b0 DevObjExt ffffe5883997cc68 DevNode ffffe58839a21ca0
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe58839a92e00 \Driver\ACPI
Device queue is not busy.

The most important information in there for us is the address of the device node (DevNode) which describes the actual device...

Code:

11: kd> !devnode ffffe58839a21ca0
DevNode 0xffffe58839a21ca0 for PDO 0xffffe5883997c360
  Parent 0xffffe58839933c40   Sibling 0xffffe588397f6c40   Child 0xffffe5883c56c760
  InstancePath is "PCI\VEN_1022&DEV_43D5&SUBSYS_11421B21&REV_01\4&288c77c7&0&000B"
  ServiceName is "USBXHCI"
  State = DeviceNodeEnumeratePending (0x30e)
  Previous State = DeviceNodeStarted (0x30a)
  StateHistory[13] = DeviceNodeStarted (0x30a)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[10] = DeviceNodeStarted (0x30a)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[07] = DeviceNodeStarted (0x30a)
  StateHistory[06] = DeviceNodeStartPostWork (0x309)
  StateHistory[05] = DeviceNodeStartCompletion (0x308)
  StateHistory[04] = DeviceNodeStartPending (0x307)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x306)
  StateHistory[02] = DeviceNodeDriversAdded (0x305)
  StateHistory[01] = DeviceNodeInitialized (0x304)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  Flags (0x6c0000f0)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
                      DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
                      DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
  CapabilityFlags (0x00002000)  WakeFromD3

The VEN_1022&DEV_43D5 identify the actual device, if you look that up you find it's your AMD USB3.1 Host Controller. You can also see at the bottom of the above that the device is capable of waking from D3 - this is a lower power state, so the device should be able to manage this power transition.

The driver for this device is part of the AMD chipset driver package so I suggest that you first run the AMD Driver & Support Tool and use that to check for AMD chipset driver updates. However, this BSOD could also be caused by a device that you have plugged in to a USB3.1 port, so I suggest you investigate those devices and look for driver updates for them (if available).

I can also see in the dump that you have three drivers for the Logitech G Hub product installed; logi_joy_bus_enum.sys, logi_joy_vir_hid.sys, and logi_joy_xlcore.sys - all three drivers are known to cause BSODs on Windows 10 and Windows 11 systems. I would seriously reconsider your use of G Hub. TBH in my (long) experience Logitech software often causes problems, one reason I actively avoid Logitech products.

Search

Question BSOD when gaming, help with Memory.DMP ?

Logan31

ubuysa

Distinguished

Logan31

MEMORY.zip

ubuysa

Distinguished

TRENDING THREADS

Latest posts

Moderators online

Share this page