The game had a very odd crash upon getting to a certain point in Kyovashad. Once Lorath departs and the town starts to populate with other players, the game had a fatal error. I could not view the error because it not only crashed Diablo 4, it crashed my OBS and it also crashed my graphics driver by the looks of it because my monitors went black so had to reboot my pc.
Not sure if this was unique to me streaming but it was odd how it happened right when it brought in other players into a collective town instance.
**I had something similar, Happened to me twice. I’ll try and upload the entirety of this later if the Forum will let me. **
**I’m not getting specified hardware in the report so was wondering if anyone else had this narrowed down.
Below is a summary section only and is NOT the entirety of the crash, just what I’m pretty sure is the important stuff
I don’t think this is affecting streaming services only, I suspect just D4 engine failure**
I 2023.03.20 01:06:37.062888 [Crash] GetLastError() = 126
The specified module could not be found.
I 2023.03.20 01:06:37.303412 [Crash] Thread ‘RenderThread’ handling fatal error
I 2023.03.20 01:06:37.305930 [Crash] UnhandledExceptionFilter
I 2023.03.20 01:06:37.306348 [Crash] Crashed thread: ‘RenderThread’ (0x4810)
I 2023.03.20 01:06:37.306609 [Sigma] — OS memory stats -----
I 2023.03.20 01:06:37.306847 [Sigma] Virtual Mem Total: 36800.58 Mb
I 2023.03.20 01:06:37.307063 [Sigma] Virtual Mem Used: 29450.81 Mb
I 2023.03.20 01:06:37.307206 [Sigma] Virtual Mem Used by Process: 20566.00 Mb
I 2023.03.20 01:06:37.307353 [Sigma] Phys Mem Total: 32704.58 Mb
I 2023.03.20 01:06:37.307506 [Sigma] Phys Mem Used: 15744.22 Mb
I 2023.03.20 01:06:37.307652 [Sigma] Phys Mem Used by Process: 9149.27 Mb
I 2023.03.20 01:06:37.307787 [Sigma] — OS memory stats end-----
I 2023.03.20 01:06:37.308006 [Sigma] Opening dump file
I 2023.03.20 01:06:37.308342 [Sigma] Dump file opened
I 2023.03.20 01:06:37.308535 [Sigma] Starting dump
I 2023.03.20 01:06:38.401717 [Sigma] Saved dump file to ‘hiddendestination’
UNHANDLED EXCEPTION: NONCONTINUABLE_EXCEPTION (c0000025)
I 2023.03.20 01:06:38.416927 [Crash]
I 2023.03.20 01:06:38.417250 [Crash]
I 2023.03.20 01:06:38.417353 [Crash] ------------
I 2023.03.20 01:06:38.417451 [Crash] Stack Crawl:
I 2023.03.20 01:06:38.417542 [Crash] ------------
I 2023.03.20 01:06:38.430937 [Crash] DBG-ADDR<00007FFBECE1CD29>(“KERNELBASE.dll”)
I 2023.03.20 01:06:38.431070 [Crash] DBG-ADDR<00007FF68CEEB99A>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431166 [Crash] DBG-ADDR<00007FF68CEE72DA>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431257 [Crash] DBG-ADDR<00007FF68CF461AE>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431348 [Crash] DBG-ADDR<00007FF68CF4B569>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431445 [Crash] DBG-ADDR<00007FF68CF40F68>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431535 [Crash] DBG-ADDR<00007FF68CF62D6B>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431628 [Crash] DBG-ADDR<00007FF68CF63299>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431755 [Crash] DBG-ADDR<00007FF68CF586AF>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431890 [Crash] DBG-ADDR<00007FF68CEDD92B>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431985 [Crash] DBG-ADDR<00007FF68DD4C85E>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.432076 [Crash] DBG-ADDR<00007FF68DD68772>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.432166 [Crash] DBG-ADDR<00007FFBEE897614>(“KERNEL32.DLL”)
I 2023.03.20 01:06:38.432255 [Crash] DBG-ADDR<00007FFBEF4626A1>(“ntdll.dll”)
I 2023.03.20 01:06:38.432464 [Crash] 14 frames dumped
I 2023.03.20 01:06:38.432558 [Crash]
I 2023.03.20 01:06:38.434235 [Crash]
**Wondering if your experience is similar to mine. Happened to me twice. I’ll try and upload the entirety of this later if the Forum will let me. **
**I’m not getting specified hardware in the report so was wondering if anyone else had this narrowed down.
Below is a summary section only and is NOT the entirety of the crash, just what I’m pretty sure is the important stuff
Pretty sure it’s not streaming related, it’s just an engine dump**
I 2023.03.20 01:06:37.062888 [Crash] GetLastError() = 126
The specified module could not be found.
I 2023.03.20 01:06:37.303412 [Crash] Thread ‘RenderThread’ handling fatal error
I 2023.03.20 01:06:37.305930 [Crash] UnhandledExceptionFilter
I 2023.03.20 01:06:37.306348 [Crash] Crashed thread: ‘RenderThread’ (0x4810)
I 2023.03.20 01:06:37.306609 [Sigma] — OS memory stats -----
I 2023.03.20 01:06:37.306847 [Sigma] Virtual Mem Total: 36800.58 Mb
I 2023.03.20 01:06:37.307063 [Sigma] Virtual Mem Used: 29450.81 Mb
I 2023.03.20 01:06:37.307206 [Sigma] Virtual Mem Used by Process: 20566.00 Mb
I 2023.03.20 01:06:37.307353 [Sigma] Phys Mem Total: 32704.58 Mb
I 2023.03.20 01:06:37.307506 [Sigma] Phys Mem Used: 15744.22 Mb
I 2023.03.20 01:06:37.307652 [Sigma] Phys Mem Used by Process: 9149.27 Mb
I 2023.03.20 01:06:37.307787 [Sigma] — OS memory stats end-----
I 2023.03.20 01:06:37.308006 [Sigma] Opening dump file
I 2023.03.20 01:06:37.308342 [Sigma] Dump file opened
I 2023.03.20 01:06:37.308535 [Sigma] Starting dump
I 2023.03.20 01:06:38.401717 [Sigma] Saved dump file to ‘hiddendestination’
UNHANDLED EXCEPTION: NONCONTINUABLE_EXCEPTION (c0000025)
I 2023.03.20 01:06:38.416927 [Crash]
I 2023.03.20 01:06:38.417250 [Crash]
I 2023.03.20 01:06:38.417353 [Crash] ------------
I 2023.03.20 01:06:38.417451 [Crash] Stack Crawl:
I 2023.03.20 01:06:38.417542 [Crash] ------------
I 2023.03.20 01:06:38.430937 [Crash] DBG-ADDR<00007FFBECE1CD29>(“KERNELBASE.dll”)
I 2023.03.20 01:06:38.431070 [Crash] DBG-ADDR<00007FF68CEEB99A>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431166 [Crash] DBG-ADDR<00007FF68CEE72DA>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431257 [Crash] DBG-ADDR<00007FF68CF461AE>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431348 [Crash] DBG-ADDR<00007FF68CF4B569>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431445 [Crash] DBG-ADDR<00007FF68CF40F68>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431535 [Crash] DBG-ADDR<00007FF68CF62D6B>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431628 [Crash] DBG-ADDR<00007FF68CF63299>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431755 [Crash] DBG-ADDR<00007FF68CF586AF>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431890 [Crash] DBG-ADDR<00007FF68CEDD92B>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.431985 [Crash] DBG-ADDR<00007FF68DD4C85E>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.432076 [Crash] DBG-ADDR<00007FF68DD68772>(“Diablo IV.exe”)
I 2023.03.20 01:06:38.432166 [Crash] DBG-ADDR<00007FFBEE897614>(“KERNEL32.DLL”)
I 2023.03.20 01:06:38.432255 [Crash] DBG-ADDR<00007FFBEF4626A1>(“ntdll.dll”)
I 2023.03.20 01:06:38.432464 [Crash] 14 frames dumped
I 2023.03.20 01:06:38.432558 [Crash]
I 2023.03.20 01:06:38.434235 [Crash]
So didn’t see this until now, for some reason didn’t get a notification for it. However it definitely is memory based as your crash report says AND for me its definitely while running OBS while playing but not exactly?
This happened again since posting but right before the World Boss spawned, which sucked because I missed out on fighting it. Wanted to record the fight but Diablo 4 locked up, then OBS crashed and then went my monitors again that did not recover without a reboot. It wasn’t a hard crash because I eventually could restart my PC but the monitors would constantly come on and off, as mentioned it’s like it took out my graphics driver.
Yet I did play/stream it for 6+ hours on Saturday without any issue, very bizarre and unique issue.