Very Frequent Game Crashes

did it… as well, as 64/64 on system with that many. fortunately, so rare crash don’t ruin me much, as I play solo causal content and … it’s not a big deal to enter again, heh.

same here i get crashes every day. its not as hardware problem for sure since im running an i9 cpu, 32ram and ti super 4070 and im only running settings on high, lowest shadows and without ray tracing.

im beginning to reach a point where i just ditch this game unless they get it worked out within a couple of weeks because it have been like this since voh went live.

I 2024.10.26 21:11:41.252673 456428 [Crash] GetLastError() = 126
The specified module could not be found.

[Prism] Device Removal - Win10/Dx12 BC:TiledLightingInit

E 2024.10.26 21:11:41.252917 456428 [Crash] Thread ‘RenderThread’ handling fatal error
E 2024.10.26 21:11:41.253437 456428 [Crash] UnhandledExceptionFilter
E 2024.10.26 21:11:41.253571 456428 [Crash] Crashed thread: ‘RenderThread’ (0x2f98)
I 2024.10.26 21:11:41.253671 456428 [Sigma] — OS memory stats -----
I 2024.10.26 21:11:41.253768 456428 [Sigma] Virtual Mem Total: 64956.00 MB
I 2024.10.26 21:11:41.253887 456428 [Sigma] Virtual Mem Used: 54623.98 MB
I 2024.10.26 21:11:41.253982 456428 [Sigma] Virtual Mem Used by Process: 27909.07 MB
I 2024.10.26 21:11:41.254082 456428 [Sigma] Phys Mem Total: 61116.00 MB
I 2024.10.26 21:11:41.254218 456428 [Sigma] Phys Mem Used: 31293.42 MB
I 2024.10.26 21:11:41.254357 456428 [Sigma] Phys Mem Used by Process: 12528.54 MB
I 2024.10.26 21:11:41.254469 456428 [Sigma] — OS memory stats end-----
I 2024.10.26 21:11:41.254613 456428 [Sigma] Opening dump file
I 2024.10.26 21:11:41.254819 456428 [Sigma] Dump file opened
I 2024.10.26 21:11:41.254938 456428 [Sigma] Starting dump
I 2024.10.26 21:11:41.656245 456428 [Sigma] Created dump after 1 attempts
I 2024.10.26 21:11:41.656482 456428 [Sigma] Saved dump file to ‘C:\Program Files (x86)\Diablo IV\Fenris-0.dmp’

this is what i keep getting every day 5-6 times a day and family members too

— OS memory stats -----
I 2024.10.26 19:12:00.679331 0 [Sigma] Virtual Mem Total: 64956.00 MB
I 2024.10.26 19:12:00.679334 0 [Sigma] Virtual Mem Used: 26971.88 MB
I 2024.10.26 19:12:00.679335 0 [Sigma] Virtual Mem Used by Process: 1146.75 MB
I 2024.10.26 19:12:00.679337 0 [Sigma] Phys Mem Total: 61116.00 MB
I 2024.10.26 19:12:00.679338 0 [Sigma] Phys Mem Used: 17698.15 MB
I 2024.10.26 19:12:00.679340 0 [Sigma] Phys Mem Used by Process: 1124.70 MB
I 2024.10.26 19:12:00.679341 0 [Sigma] — OS memory stats end-----
I 2024.10.26 19:12:00.684644 0 [Game] Application Activated.
I 2024.10.26 19:12:00.694812 0 [Game] [Prism] Opening Prism in 7680x2160 fullscreen window on monitor 0 (3D viewport in 7680x2160). Monitor refresh rate is 120.000 Hz

this is todays

I 2024.10.29 01:49:34.893314 321299 [Crash] GetLastError() = 126
The specified module could not be found.

[Prism] Device Removal - Win10/Dx12 BC:TiledLightingInit

E 2024.10.29 01:49:34.893503 321299 [Crash] Thread ‘RenderThread’ handling fatal error
E 2024.10.29 01:49:34.894116 321299 [Crash] UnhandledExceptionFilter
E 2024.10.29 01:49:34.894253 321299 [Crash] Crashed thread: ‘RenderThread’ (0x31bc)
I 2024.10.29 01:49:34.894352 321299 [Sigma] — OS memory stats -----
I 2024.10.29 01:49:34.894450 321299 [Sigma] Virtual Mem Total: 64956.00 MB
I 2024.10.29 01:49:34.894546 321299 [Sigma] Virtual Mem Used: 53700.16 MB
I 2024.10.29 01:49:34.894666 321299 [Sigma] Virtual Mem Used by Process: 31058.96 MB
I 2024.10.29 01:49:34.894813 321299 [Sigma] Phys Mem Total: 61116.00 MB
I 2024.10.29 01:49:34.894909 321299 [Sigma] Phys Mem Used: 30828.81 MB
I 2024.10.29 01:49:34.895019 321299 [Sigma] Phys Mem Used by Process: 13235.60 MB
I 2024.10.29 01:49:34.895158 321299 [Sigma] — OS memory stats end-----
I 2024.10.29 01:49:34.895298 321299 [Sigma] Opening dump file
I 2024.10.29 01:49:34.895551 321299 [Sigma] Dump file opened
I 2024.10.29 01:49:34.895679 321299 [Sigma] Starting dump
I 2024.10.29 01:49:35.346975 321299 [Sigma] Created dump after 1 attempts
I 2024.10.29 01:49:35.347227 321299 [Sigma] Saved dump file to ‘C:\Program Files (x86)\Diablo IV\Fenris-0.dmp’

i try reopen button after a crash but doesnt even reopen the game any more
i hope they look into this a fix it

See my posts, the problems is with Battle.net and communication with D4. I have tried to post, send bug reports everything I can think of. let me guess started at prepatch 2.0 or a bit earlier. my current solution, is uninstall d4 then either go into Battle.net and disable auto sign in at start or uninstall Battle.net and reinstall and then deselect auto sign in a computer boot up. this may clear the problem. The issue is that Battle.net and D4 have a link, if you disconnect in D4 it disconnects in Battle.net. The game tries and layers you many times every second, this causes massive information to be uploaded and downloaded. The causes memory lead or loss of packets. At 1% loss of packets you will experience rubber banding, lag, then disconnect from D4 and Battle.net. Programs to check what happens after DC are Ookla for speed, Cloud Fair for speed/jitter (instability), and packet loss for speed/packet loss upload and download. In game, deselect cross party and cross party chat, turn of music. Again, I have made posts about this but nothing is answered.

Crash city.

FEBF9E14-B379-4C77-B50A-AB7BD193996E

The fenris crashes are one thing, the BSOD and forced restarts really make me wonder if playing this game is actually risking bricking my $3000 PC.

Yup crashes here too
It started since the update.
My specs:
Dell 34’ Alienware AW3420DW
ASUS GeForce RTX 4090 TUF O24G OC
Asus ROG MAXIMUS Z790 HERO
Intel Core i9 13900KS
64gb DDR5 XPG Lancer RGB 6000Mhz
ASUS ROG Thor 1000W Platinum II.
XPG GAMMIX S70 BLADE 4TB Gen4x4 M.2 PCIe x2

Yea i get the fenris crash every 2 hours. Several people have said adding “-nostreamline” to the additional command line arguments in game settiings fixes this. I’ve got very little expectation as i’ve tried every fix ppl have suggested. but here goes nothing.

Same issue here. So is a friend of mine.

Im getting the freeze and crash right away as i start a game… Did everything people suggested… Also i noticed DLSS is gone in the game suddenly… but my biggest concern is : I CANT PLAY

5C7E2A70-8CC6-4D29-9DC4-0395462F02C3

crash

Thank you so much, I had given up on playing this game with all of the “out of memory” crashes I was getting. Just did this and I played for about an hour with no crash!

1 Like

I’m experiencing about 2 crashes an hour.

Gigabyte Aorus Z690 Pro
Gigabyte Aorus RTX 3080 Xtreme 12G WB
Intel Core i5 12600K
Corsair Dominator 5600 32GB

Temps are great. My PC is fully water-cooled. Most settings are totally maxed, except ray tracing. I have the middle option instead of high, and particle ray tracing disabled. I get about 50FPS consistently with DLSS balanced selected.

Husband’s computer:

Gigabyte Aorus Z690 Pro
MSI RTX 3080 Gaming Z Trio
Intel Core i5 12600K
TFORCE 4600 32GB

Temps aren’t totally bad, most settings are default. His computer is crashing literally as equally as mine. We play together and, interestingly, both our PCs crash simultaneously when we’re playing together in the same places.

Well there are still some unknowns here.

First off, what video driver version are you using for the video cards? The latest two have been very buggy with the game, so most people have been using 561.09 for better results.

Second, have either of you checked to see if you are getting any out of memory errors, or have tried to monitor the virtual memory? You can do this, simply by running the task manager, viewing the performance tab, and looking at the memory. The specific data you want to watch is “Committed”. This monitors your virtual memory, and if the amount in use nears the amount available, you can run out and crash while playing.

Third, you may want to ditch a few settings for now till some of these bugs are addressed:

  • Turn off all Ray Tracing
  • Turn off Peripheral Lighting (Chroma effects)
  • Turn off Distortion
  • Turn off Chromatic Aberration

See what those settings do for you. With regards to the driver, you can try to roll back, or use the DDU tool to remove it. If you use the DDU (Display Driver Uninstaller which you can get from their website) make sure you follow the directions on how to use the tool.

For more on this and to try disabling Direct Storage, go to this post:

-Vessel of Hatred Startup & Play performance since initial launch - #3 by DTMAce-1687

If the virtual memory is an issue, you can use this post I made a while back for instructions. The only change is to use 32GB for the swap. (32768):

-Diablo IV has run out of memory - #103 by DTMAce-1687

8FBF9D03-02D5-4EA5-8274-7BC80FF4C43C - This mistake has already gotten wildly annoying. You play the game for a little over an hour and that’s it. Then a flight and a spoiled mood! When will this error be fixed?

Yup… new patch which states “various stability improvements” (please don’t overload us with information!!) and in the last two hours I have not been able to play for more than maybe 5 minutes… at least a dozen or more game crashes… some as soon as I hit the “start game” button, during teleporting, and the last one, at the first pack of mobs in the pit (more resources lost)… no commonality, just constant game crashes…

And on a side note, the sound keeps dropping every few minutes as well… I guess after a few more patches like this we will just launch the game, it will fart in our face and uninstall itself.

This is just ridiculous… and from the probably hundreds of threads on this type of thing, it is not the systems… I have a very high end machine and D4 is the only program, game or anything that even causes my system to even hiccup, let alone crash a dozen times

i9 13000K
64GB DDR5
nvme drives
RTX4090
water cooled

Outside of D4, cpu temps never get above 50 (right now sitting at 40)… when running D4, it sits around 90 and can spike to 100… Fenris errors, general crashing to desktop and sometimes locking up the entire PC forcing a power cycle… this is just plain bad

FIX THIS!!

There were a few reports of this happening when running the latest drivers. And that this was resolved when going back to 561.09.

But I have not seen any recent reports of this. It has been a couple weeks since the last one I read.

But I will state this may not fix every situation. And for best results you should use the DDU tool to properly remove it. You can use this link for information on that:

-Season 6 is crashing for me! - #63 by DTMAce-1687

tried that before… multiple video drivers, various changes, testing etc… in the end it is the game

This latest 1GB patch they just released today (may have been yesterday, not sure as I was not on yesterday) has thrown everything in the trash yet again… was “somewhat” stable after last weeks DLSS disaster update was corrected, now this. again. Maybe the Tuesday maintenance will fix everything?!? Ha, doubt it.

We should not have to play this with the anticipation of wondering when today’s crash will happen… Will there ever be any compensation for the countless lost time… even if it some in game perk (I know they will never refund any money paid)… free Mythic, boatload of mats for all this lost during crashes etc… hell at this point I would be satisfied if a blue poster would start providing some feedback so the paying customers would at least know what the status is… time to start looking for a D4 alternative I guess

1 Like

I did all suggestions you mentioned first, then started re-adding until I recreated the issue. The game seems to be stable now with the following recommendations you mentioned:

Reverting to 561.09.

Ray Tracing, distortion, and chromatic aberrations were switched back on. I also kept the virtual memory recommendation on as well, as it’s not a bad idea to have a set page file instead of system managed. Peripheral Lighting has always been off by default as far as I’m aware.

An additional bonus reverting to 561.09 is that screen flickering (an issue I was also having but not mentioned here as this is specifically referring to crashes) has also resolved.

1 Like