Tried it did not help.
after the little Patch it still keep crashing
I had the same issues. In my case it was video driver/game (donât know which one it is exactly) issues. With newest nvidia drivers i had fenris crashes every 10-30 min. I rolled back to 531.68 if youâre using nvidia card. Newest, diablo launch drivers result in constant crashes. It might be the same for amd.
P.S. Been playing on old drivers for at least 12 hours and so far 0 crashes
Not saying this will 100% work, but it helped me. I heard that some said disabling nvidia overlay helps too.
2 Likes
just wanna know how edited by moderation refunds work
2 Likes
try turn FPS 400 to the origin 150 and window mode (not full screen window) then finally I can finish the end boss fight , 42 NEC solo win LilysïŒ hope help u guys
I have been fighting with these errors too. I played for the first three hours just fine, but I accidentally let my computer go to sleep with the game open as I got distracted during some chores, and it has been constant crashing ever since. I canât rollback my drivers on my graphics card, but I have tried basically everything else that is on the internet currently.
Edit:
GPU: RTX 4090
CPU: Ryzen 7950x
RAM: 32GB DDR5
HD: 2TB SSD NVMe 2.3
I shouldnât have issues running the game.
I had the same problem, i change my fps to max 60 fps and havent crashed since , i have a 1070, and i can see some of you have very very good cards, so 60 fps isent good ofc, but blizz has to fix it soon, while we wait try setting it to 60 fps max
1 Like
Thx mate. Its work.
Before that I spent 12 hours and tried everything!
Unfortunately, downgrading to 531.68 did nothing for me. Tried everything in this thread.
Bloody hell, Blizzard, find the problem and fix it.
1 Like
After todays patch I started having those crashes too. Been playing since the start, no problem. Today the crash hell began. Latest crash code was E29540C7-60DD-4517-AB31-FF497073511E
Im on pc, win 10, 13700KF, 32Gb Ram, GeForce 1070 with latest drivers. Game is on nvme
Looks like it worked. Lowered the FPS limit to 60, and set the settings to âHighâ instead of âUltraâ. At the moment there are no crashes for 15 minutes.
Testing continuesâŠ
Done the same last night after a series of crashes in short period. Super odd, because yesterday throughout the day I had some hours of no crashes with capped 120 FPS.$
Checked temperatures too âjust in caseâ. Seems top CPU (Ryzen 5 5600x) temp is around 65°C and GPU (MSi GeForce RTX 3070 Ti) 45°C.
Today, almost 4 hours uptime (and counting as of writing this post)
Edit 12 hours later: with some pauses I havenât been crashing anymore at 60 fps. Maybe I should have mentioned earlier that my game is installed on a NVME SSD as well, for what itâs worth it.
1 Like
My crash code is this :B7BF8DAE-C6EF-4F5D-AAF9-B994951EC2E1
Crashed going into the map and previously crashed just leaving a town.
Says this topic is solved but it isnât, the game has now crashed 4 times in 10 minutes
1 Like
So crashes havenât stopped(
1 Like
Did you change the FPS from the LocalPrefs.txt file or somewhere else?
I am facing the same issue as well on Windows 10 + nVidia 472.19 (HP Omen Laptop, Manufacturer provided driver).
My friend who bought the same exact laptop (as we got them on a good deal) is facing also the same issues but he opted for latest Win11 + Latest nVidia 535.98.
Can you guys press start and type âevent viewerâ and open it. Then click on Event Viewer (Local) on the top-left side.
Now, under âSummary of administrative eventsâ, expand âErrorâ and look for ânvlddmkmâ under âSourceâ column. Double click it. Me and my friend see many (~90-100) errors at exactly the same time (down to the second) as when the crash occured. All of them are a variation of:
âThe description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.â
- the only thing that changes between them:
Graphics SM Global Exception on (GPC 5, TPC 3, SM 1): Multiple Warp Errors
Graphics SM Warp Exception on (GPC 5, TPC 3, SM 1): Out Of Range Register
Graphics Exception: ESR 0x52dfb0=0x3000d 0x52dfb4=0x4 0x52dfa8=0xf812b60 0x52dfac=0x1104
Where the numbers for GPC, TPC, SM change for each error, and also the hexadecimal numbers change for the ESR one.
Now, if you click again on Event Viewer (local), and again under summary, but this time expand âWarningâ and Double click âDisplayâ under Source column. Here we see 1 error per crash with the message:
âDisplay driver nvlddmkm stopped responding and has successfully recovered.â
which points to the fact the nVidia driver crashes, which I assume the message we get in the FENRIS output â[Prism] Device removal detectedâ is making sense. From the point of view of the game, the driver which it needs shuts down.
I do not think there is anything wrong with the nVidia driver, or our hardware or anything, but all has to do with the game.
Again, we are talking about a 2 year old driver (mine) + the newest driver, all exhibiting the same exact errors.
I have no clue why this happens, is the game trying to call some invalid functions of the nvidia driver? Only Blizz knows, but thatâs why I want to check if everyone has the same errors in event viewer, so we can provide as much detail as possible.
I want to add that besides this crash, for us the game is running perfectly, no overheating, no apparent issues up until it crashes, between every few hours down until even like 20 minutes.
5 Likes
I was try everithing wat ppl recomend in this and other topics
FPS with cap of 60 or no limit ⊠game crash after 1 min play and reboot a copm
Rename dsstorage.dll to .dllbackup ⊠game crash after 1 min play and reboot a copm
Installing game to new or old disc ⊠game crash after 1 min play and reboot a copm
Installing game with HD or not ⊠game crash after 1 min play and reboot a copm
Waiting for ingame shop upload before start game ⊠game crash after 1 min play and reboot a copm
Updating and downgrading drivers ⊠game crash after 1 min play and reboot a copm
With paging file crash after 1 min. Out of him game crash to desctop with errors but not reboot a comp
Change a setings to Ultra - COOL !!! 5-6 min. play before game crash and reboot a copm
Thanks alot to blizzard for sell me a preorder!
Hi all,
When it comes to crashes, thereâs very rarely one simple fix that works for absolutely everyone, because of the huge array of software and hardware configurations out there.
Quite a few of the crashes weâve been seeing, that arenât because of not meeting the minimum requirements, have ultimately been down to either outdated video card drivers, or other software hooking into the game, whether thatâs to be able to show an overlay, extract data to control RGB lighting, direct capture or share game footage, etc.
So the first thing we recommend is to make sure your drivers are updated. If your system has both an integrated and dedicated graphics card, be sure to update both, especially in laptops or all-in-one systems, where both cards share a single output. Itâs also a good idea to make sure that your monitor is plugged into your dedicated graphics card.
After that, what weâd suggest would be to first close down everything that might interfere, then try again. To do that, the best thing to do is to clean boot Windows. This will disable all applications running in the background and should rule out any possible software conflicts:
- Press Windows Key+R.
- Type msconfig and press Enter.
- Select Selective startup and uncheck Load startup items.
- Select the Services tab.
- Check Hide all Microsoft services.
Note: Skipping this step may prevent your computer from rebooting correctly. - Click Disable all, then Apply then click OK. And click Restart.
When youâre done testing, you can simply reverse the process to turn things back on, and I would suggest only turning them on a couple at a time, so that if it suddenly stops working again, youâll be able to narrow down exactly whatâs causing it.
If you still have issues after all of that, please be sure to open a ticket and include the requested system diagnostic files, ideally generating those files while in that Selective Startup state.
Donât you think, considering problems have started after 3rd of June patch, it has to do with that patch? And disabling services wonât help.
Iâm just guessing
BTW guys in the next topic might be up to something. And driver nvlddmkm might be involved, since errors in âevent viewerâ were about it
This is happening to me, get up to the boss of a dungeon and boom, iâm out. iâve only been able to kill one boss so far.