Windows 11 Blue Screen While Playing DirectX 12 Game - Freshly Formatted Windows Install

Question

Windows 11 Blue Screen While Playing DirectX 12 Game - Freshly Formatted Windows Install

David G 1

I just installed Windows 11 Pro onto a freshly formatted C: drive. When gaming, I intermittently get a blue screen.

CPU: AMD 5950x
Motherboard: Asus Crosshair VIII Hero
GPU: Nvidia 3080

I have done all windows updates and updated all of my chipset drivers to the latest available. I have pasted the minidump contents below:

28: kd> !analyze -v

                   Bugcheck Analysis                                    *

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80418705330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:

------------------

*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***

*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***

*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***

*** Type referenced: TickPeriods ***

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec  
Value: 2421  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 5814  

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

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0x133  

Key  : Bugcheck.Code.KiBugCheckData  
Value: 0x133  

Key  : Bugcheck.Code.Register  
Value: 0x133  

Key  : WER.OS.Branch  
Value: co_release  

Key  : WER.OS.Timestamp  
Value: 2021-06-04T16:28:00Z  

Key  : WER.OS.Version  
Value: 10.0.22000.1

FILE_IN_CAB: 082822-9109-01 - Copy.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80418705330

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffbe8d6bddf560 -- (.trap 0xffffbe8d6bddf560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000003ee44569 rbx=0000000000000000 rcx=ffffbe8d6bddf758
rdx=ffffbe8d6fa37698 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80417d22600 rsp=ffffbe8d6bddf6f0 rbp=00000000ffffffff
r8=ffffbe8d6fa37450 r9=ffffbe8d6fa37460 r10=0000fffff80417d8
r11=ffffc67ade600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x20:
fffff804`17d22600 5b pop rbx
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd680d5fe69e8 fffff80417cd800e : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
ffffd680d5fe69f0 fffff80417cd7a91 : 0000066d1626649d 0000000000000500 0000000000000297 fffff80417c4f660 : nt!KeAccumulateTicks+0x39e
ffffd680d5fe6a60 fffff80417cd4ac6 : 0000000000020506 000000000001342b 00000004d0ae1345 0000000000000000 : nt!KiUpdateRunTime+0x61
ffffd680d5fe6ac0 fffff80417cd5dd2 : ffffbe8d6bddf560 0000000000000000 fffff8041862b238 0000000000000000 : nt!KiUpdateTime+0x686
ffffd680d5fe6eb0 fffff80417cd3702 : ffffbe8d6bddf560 ffffbf8f75738470 ffffbf8f00000000 0000000000000002 : nt!KeClockInterruptNotify+0x272
ffffd680d5fe6f40 fffff80417c0d2d0 : 00000004d0edde4f ffffbf8f757383c0 0000000000000001 fffff80417e1c69b : nt!HalpTimerClockInterrupt+0xe2
ffffd680d5fe6f70 fffff80417e1c8fa : ffffbe8d6bddf5e0 ffffbf8f757383c0 0000065d470ded1d 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa0
ffffd680d5fe6fb0 fffff80417e1cec7 : 0000000000000000 00001f8000e102d4 000000003ee3dc45 ffffbe8d6bddf758 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffbe8d6bddf560 fffff80417d22600 : 0000000080000000 fffff80417d81c69 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffbe8d6bddf6f0 fffff80417d81c69 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeYieldProcessorEx+0x20
ffffbe8d6bddf700 fffff80417cc7c11 : ffffbe8d6bddfac0 000000003ee44569 0000000000000000 0000000000000000 : nt!ExpGetPoolTagInfoTarget+0x149
ffffbe8d6bddf750 fffff80417cc6c12 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExecuteAllDpcs+0x491
ffffbe8d6bddf950 fffff80417e1ec6e : 0000000000000000 ffffd680d5fcb180 0000000000000000 ffffd680d5fd7840 : nt!KiRetireDpcList+0x2a2
ffffbe8d6bddfc00 0000000000000000 : ffffbe8d6bde0000 ffffbe8d6bdd9000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22000.918

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 39e

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

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

7 answers

Your answer

Answer 1

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

David G 1

Here's the link: https://drive.google.com/drive/folders/1Be-9kRVykbYNzD1U8tDmuFfNejBrZgL7?usp=sharing

Dumb question - do I need to be running this before I get a crash, or does it just collect previous crash logs?

Answer 3

Please run the V2 after any BSOD to collect available mini dump and supporting files.

There were no collected mini dump files.

1) Make sure that there is no overclocking during the troubleshooting.

The CPU supports RAM up to 3400 MHz

https://www.amd.com/en/products/cpu/amd-ryzen-9-5950x

At the time the log collector ran the RAM was overclocked at 3600 MHz.

Turn off XMP during the troubleshooting.

2) Open administrative command prompt and copy and paste:

PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post a separate share link with only the compressed memory dump into this thread.

3) Run:

(bat scripts by design prompt antivirus software and require manual overrides)

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

https://www.elevenforum.com/attachments/tuneup_plus_log-bat.36285/

Post a share link into this thread.

LastWriteTime Size (MB) FullName

8/28/2022 5:07:47 PM 1734.68 C:\Windows\MEMORY.DMP

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 4

David G 1

What can I do to assure that the program will retrieve the dump file? Do they delete themselves after a couple of restarts?

Also, the RAM is rated for DDR 3600, and I have only had this issue a year or more after I installed it: https://www.newegg.com/g-skill-64gb-288-pin-ddr4-sdram/p/N82E16820232865

Answer 5

When purchasing RAM it is best to view the Qualified Vendor List for the CPU.

Using RAM at speeds higher than the CPU supported level is an overclock.

Overclocking, temperature related problems, etc. are common causes of BSOD.

So there should be no overclocking during the troubleshooting so that the computer environment can be evaluated form misbehaving drivers and malfunctioning hardware.

There are BSOD in which there are failures to create mini and / or memory dump files.

(these were not present on your computer: Dump file creation failed due to error during dump creation; Crash dump initialization failed!)

If mini dump files were created and disappear, it is not clear why some computer environments lead to the deletion of mini dump files.

Make sure that you do not perform cleaning: Windows disk cleanup, Ccleaner, Glary Utilities, etc.

For this BSOD it is fortunate that the memory dump is available.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Share via

Windows 11 Blue Screen While Playing DirectX 12 Game - Freshly Formatted Windows Install

7 answers

Your answer