RenderThread Handling Fatal Error

PC Bug Report
1

Hey Guys, this has happened to me twice. Seeing if anyone else has experienced it. Error as follows following initial gamelog:

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

Then there is a Frame Dump following a Noncontinuable_Exception as follows:

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

**If I can later I’m going to attach the entirety of the report. For now just curious if anyone else has experienced this and if they know what hardware is actually causing it. **

I’m assuming this is due to an engine failure since it’s proprietary and they’ll have kinks to overcome.

1 Like
2

i have probably close to 50 of these reports i just found them trying to find a way to fix my crashing issues. i have no clue ive tried scanning and repairing doesnt work ive tried closing baclground apps nada closed msi and rivatuner nope turned on msi and rivatuner still nothing cleared cache etc etc it seems to be a gamble whether youre gonna be able to play for more than a few minutes and im extremely angry not just because what i jave played its an amazing game but becayse so far i wasted almost 100$ which is BS and trying to contact them or get a refund is an even bigger headache

1 Like