Patch 1.0.6.1 Crashing My PC Constantly Now

• Bungie Account Name - AdamKxZ#5808
• Platform - Steam
• Description of Issue - I have played Marathon almost every single day since launch without a single crash of the game or my PC at all. But now every single day since I updated to Patch 1.0.6.1 on Tuesday at 5:30 PM EST via Steam update, Marathon has been hard crashing (Black Screen of Death) my computer. Now, I understand the initial gut reaction to reading that is probably "Sure..", but bare with me here. I will back this up. I write custom software for an MSP I work at for internal usage. I understand I can use WinDbg to look at the previous crashes in Windows. I understand how to use Event Viewer and check recent Windows Updates, DDU drivers, etc.
  I have played this game everyday since launch. 100% the game has never crashed or closed once in my entire 250+ hours. 250+ straight hours of a perfect record, all changed Tuesday after the patch dropped. I now can't play the game for more than an hour without risking crashing my computer.
  I analyzed every single bug check dump, and it's all the same! dxgkrnl driver is the culprit. In fact, we can even see the exact system calls being made below and every single time the system is trying to display frames.
• I have taken multiple steps on my system BEFORE making this post.

1. DDU Uninstall GeForce drivers and AMD Chipset drivers
2. DISM using local Windows installation media as a source (work for MSP I have an Visual Studio Enterprise subscription so I just download clean fresh latest ISOs to repair with.) along with SFC
3. I checked Windows Updates and confirmed NO UPDATEs installed since April 14th. I played the game everyday since launch and from the 14th to the 21st morning I played the game without a single problem. Literally. Never.

SYMBOL_NAME:  dxgkrnl!DxgkCompositionObject::OpenDwmHandle+105

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.26100.8115

STACK_COMMAND: .cxr 0xffffd50ef7b053a0 ; kb

BUCKET_ID_FUNC_OFFSET:  105

FAILURE_BUCKET_ID:  AV_dxgkrnl!DxgkCompositionObject::OpenDwmHandle

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {80527a60-a717-dbe1-33bb-5c3a4559d0e2}

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

4: kd> .cxr 0xffffd50ef7b053a0 ; kb
rax=ffff8284128be968 rbx=ffffbe8a63293540 rcx=7fffbe8a63293540
rdx=0000000000000000 rsi=ffffd50ef7b06160 rdi=f7ffbe8a6c781880
rip=fffff807ea448ff3 rsp=ffffd50ef7b05dd0 rbp=ffffd50ef7b05ef0
 r8=0000000000000000  r9=0000000000000000 r10=ffff8284128be080
r11=ffffbe8a7c1bdaf0 r12=ffff8284128be080 r13=0000000000000000
r14=0000000000000000 r15=ffffbe8a7c1bdae0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!ObpCreateHandle+0x763:
fffff807`ea448ff3 488b4708        mov     rax,qword ptr [rdi+8] ds:002b:f7ffbe8a`6c781888=????????????????
  *** Stack trace for last set context - .thread/.cxr resets it
 # RetAddr               : Args to Child                                                           : Call Site
00 fffff807`ea44fec4     : 00000000`00000000 00000000`00000040 ffffbe8a`7c1bdb10 ffff8284`009ffc50 : nt!ObpCreateHandle+0x763
01 fffff807`7c01aed5     : 00000000`000061a8 00000000`0000c350 00000000`000186a0 ffff8284`16276000 : nt!ObOpenObjectByPointer+0x1c4
02 fffff807`7c01c27f     : 00000000`00000000 ffffbe8a`62c68720 00000000`00000000 ffffd50e`f7b06468 : dxgkrnl!DxgkCompositionObject::OpenDwmHandle+0x105
03 fffff807`7c01bdf9     : 00000000`00000001 00000000`00000000 ffffbe8a`00000000 00000000`00000000 : dxgkrnl!NotifyPendingFlipPresent+0x233
04 fffff807`7c3017ab     : 00000000`00016529 ffffd50e`f7b065c9 ffffbe8a`67497b08 00000000`00000000 : dxgkrnl!DxgkQuerySwapChainBindingStatus+0x2d
05 fffff807`7c2ed6c4     : 00000000`00000000 ffff8284`28a44050 00000000`00000001 ffffbe8a`674979a0 : dxgkrnl!SubmitPresentHistoryTokenPreparation+0x1d3
06 fffff807`7c41e72c     : 00000000`00000000 00000000`00000000 ffffd50e`f7b074e0 00000000`00000001 : dxgkrnl!DXGCONTEXT::Present+0x384
07 fffff807`ea2bd958     : ffff8284`128be080 ffff8284`128be080 00000058`5919d130 0000016b`ed8ba700 : dxgkrnl!DxgkSubmitPresentToHwQueue+0x19bc
08 00007ffa`007e3f34     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
09 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`007e3f34

• Rough Date and Time of issue - 7:11 PM EST 4/23/2026 was the most recent. It happened 30 minutes prior. I happened 3 times yesterday. And it happened 4 times on Tuesday immediately after patching...
• Repro steps - Install update 1.0.6.1 and play the game. Seriously, not being a smart ass here. All I need to do is just play the game and eventually it'll lock up, audio freezes and my system automatically reboots from the bug check. 
• LINKS: https://imgur.com/rtf3mqN

I am sort of at a loss right now... I just lost TWO 10K kits because of this happening :/ I have played every single day and I WANT TO KEEP PLAYING!!! But... I now cannot drop into a run without massive fear... I can't play the game anymore, I can't. It blows my mind this is happening. Literally ONLY after updating Tuesday morning did this start happening. Something is wrong here.