Constant Crashes - Game is unplayable

PC Bug Report
41

Me too, after several updates this is still not fixed. I remember the crashing started some time after 4-5 updates earlier. COde 7F06F290-28B4-4892-A10D-1782BA3BCEFE

42

Please use the nVidia studio drivers I posted (based on a previous stable channel of drivers that didn’t push new features, only stability and bug fixes). For more details, see the post: Constant Crashes - Game is unplayable - #24 by secured2k-1181

43

It would be helpful to others if you could report the changes the nVidia app did. When you open the app, there will be a “current” and Preview Value (Recommended" column. The changes will be in bold.

44

High end machine, 7800X3D and a RTX 4090, crashing after about an hour of gameplay, constant same crash ever since October update. Doesn’t seem like the DLSS update “stabilized” the game. Can’t stand playing this game in this condition

45

I’m having exactly the same problem.

46

I’m using the previous driver version 566.03 with DLSS and Reflex on. Updating to the newest I had to disable DLSS and REFLEX, then it eliminated all the crashes. Reflex seems to be the catalyst, as others have said disabling DLSS alone didnt fix the crashes but DLSS + reflex did.

RTX 4090
I7-13700k
64GB DDR5 6400
990 pro SSD

47

I tried this, turning Reflex off (with DLSS, off too) and it still crashes.

I’m on a 7900X3D, 32GB 6000 Ram, and RTX 3080 12GB (latest drivers).

48

Revert back the drivers to 566.03, something happened in the newest drivers.

50

So I believe I have had a real improvement in stability. Currently what has let me play for 3 evenings without a single crash has been rolling back to Nvidia Driver version 561.09, using the -nostreamline command that you mentioned, as well as leaving off DLSS, Low Latency, and all ray tracing effects.

The driver rollback seemed to have made the greatest singular difference, but I will keep this combination of adjustments going since it seems to have made a significant improvement.

1 Like
51

Still crashing about once every hour or so. AF7ECE13-A3F5-478A-B1AC-F6CCD5DB83C0

52

English is not my native language, I am using Google Translate to report what I am doing. I’m sorry if there are any strange terms.

From the first public test until November 7th. I never had video problems on D4.
On November 8th. It happened:

  1. An update on D4;
  2. An Update to Windows 11.
  3. A BIOS update (DELL

What I did:
a) I contacted Blizzard support;
b) Same as DELL
c) Same as Microsoft

a) Blizzard Support:

  • In the first answer, I was told to post it on the forum in the “BUG REPORTS” area.
    From the second answer, I still can’t believe that they guided me to:
  1. Search websites for a solution;
  2. Hire an IT professional to resolve the issue.

I’m still thinking that Blizzard’s latest guidance is a huge aberration.

b) DELL Support sent a technician who did several stress tests on the CPU and found no problems. (I have a premium assistance contract that entitles me to be seen by a technician at my home)

c) Microsoft Support:
They performed remote access, ran some tests and reported that it was impossible to update on November 8th, which is causing the problem in D4.

Lastly, I contacted Nvidia Support. I have been there since November 10th, being attended to by an Nvidia technician, who has already ruled out a problem with the Nvidia card.

I have already been given a series of instructions, we have made several changes to the System and Video Card settings.

The last instructions, which showed an improvement, but did not solve the problem 100% were:

  1. Hardware acceleration - Turn off.

  2. Use version 555.99 Geforce Game ready drive

  3. File in the D4 folder: DSTORAGE.DLL

Step 1 − Rename to: DSTORAGE.DLLBAK.

Step 2 - Test, if the problem persists, delete the DSTORAGE.DLLBAK file.

There were no more “crashes” in the game, however, sometimes when I enter a PIT or other activity, the game freezes or freezes for a few seconds.

During the service, he requested the installation of a tool to generate LOGs, he said that every time the game starts, the tool simply stops taking any measurements.

He asked to test at the end of the week, and on Monday to present the results to Nvidia.

Of all, what surprised me was the guidance from local BLIZZARD employees, telling me to go searching for a solution on the web or hiring an IT technician to solve the problem.
Simply, surreal!

1 Like
53

By the way:

I looked for a Blizzard position in this post and couldn’t find it. Have Blizzard’s technical support staff said anything about this problem?

Or are you following what I read from Blizzard local support?

In other words, is it a problem for the players, should they find a solution?

54

Lastly, I tested the following games:

  1. D3
  2. D2R
  3. WOW
  4. FFXIV

With the latest driver version from Nvidia, none of them presented the problem present in D4.

1 Like
55

About nVidia Driver versions:

nVidia has generations of hardware such as Ampere (RTX 3000 Series) and Ada (RTX 4000 Series). When support for new hardware and/or features are introduced, the version number increases to a base series such as the 560.xx and now 565.xx. I’m betting the 560.xx series will have the next-generation code optimizations for the 5000 series (Blackwell) for next year. This means some of the new drivers may have some new code or features that have problems.

To ensure stability for the Enterprise customers, nVidia also maintains the older “stable” version where every update does NOT contain any new features, but just bug fixes.

If you want the most stable system, use the stable Studio or “Production Branch” driver. This is why my previous instructions were to download the older “555.99” driver as this is the latest stable channel driver of the 550 series. On the Enterprise side, the driver has been updated 10 times and is at 553.24 (U10). Notebooks are even further back (535.xx) due to compatibility concerns. The 560.xx drivers will probably eventually become the new stable drivers including blackwell support while the 565.xx is pushing the limits (mass public testing).

Unless you are playing a newly launched game and need a small performance or feature, you generally do not need the latest driver branch, especially if things are already working. Instead try using the stable branch (that still gets updates, but is less likely to break things).

1 Like
56

Realize it’s not working for everyone, but disabling DLSS and Reflex seems to have completely fixed the crashing for me. I can play for hours now whereas previous it’d crash after almost exactly an hour, like clockwork. This is on an Intel box with an RTX 3080. Performance still seems fine as well.

Also, it feels like the fans aren’t running as fast and things aren’t running quite as hot, but I admittedly haven’t actually measured any of that.

57

Here are some of my FENRIS crashes. This isn’t even half of them, as I accidentally saved over the doc file where I was recording them. Also, these are only the FENRIS crashes. The game crashes many times without this FENRIS code. Top is oldest, bottom is most recent.

B9EE9C92-7880-440A-A685-AC698C584036

F8C8CB3A-AE4B-49E8-B4F9-BE085219F3E8

4FE567B0-7822-47F3-8632-C058B50C3435

C04F2B85-D072-4DFA-829F-09FBD3035609

8BB6D225-90F1-4EF2-81AB-88D3B215253D

871A2960-82B2-4C95-BD67-BD92E81AC1B7

90C59A49-AE87-4747-8165-392054985EC6

9935F54D-1240-458C-927F-F6281C0F7A06

ECB56A7F-A1B3-4E29-B38D-7D01C41DD00F

CBB1951A-6E32-443E-BFB4-03C8C7FE653A

95F6C0D2-C40C-4C09-872E-FE35B8CF0F4A

5C5655D9-1ECC-49E0-ACE7-823D0161BD7A

DFC54D27-BCC6-4D80-9BFB-2C0BB60BE778

EBD998F2-8D54-4D80-9F2C-D596A7674969

6CBFD763-AA49-4354-9CC7-C8AE4EF3F096

ACB8D0E2-3FC1-4D53-A20C-17CC49F47C2C

8F33E7D6-614A-4C20-8048-65A9BF1CAB3E

7303A690-D25A-4E2F-92A3-2BC4D824FFE2

CC6CBC9F-98EC-4CE1-8469-14709E97D54A

3312D733-8744-4C21-8956-718020A2C68D

4DEA244F-0C7A-439B-820F-DCF489E36969

B46061F2-3732-422D-996B-0010A3A0AA30

2DB7D4F0-092C-4459-AD44-9AB6DC10A83E

4668E5DA-7124-40F4-82EC-D222995C4CBA

862B5DFB-9114-4AD9-A572-EC27F6C1FBF2

4E99FC2F-8E64-4B83-A389-844DA4678FA8

1B63F0AC-A012-4447-B883-D319E184B7B0

9FE363B0-CC3F-49E0-B291-6623555E1EAD

ABA8ED6A-FFA5-447B-9A77-E59EB438B540

9B83E56E-1C5A-4E1D-BEA9-A02216247160

469F95E5-8AA4-49E2-86AB-90B578F8F8E1

6294C382-A24D-4500-9F62-78B69AA74281

086BB4B8-8E30-42DD-A376-24AFD65A8A70

9EF0EA99-02FB-4FAE-843D-52F4231D82D4

769231DA-573C-4D49-A962-59B7B77144CC

081471B5-D157-42C8-985B-89BC66A39C16

340FC784-14A4-4871-9179-655BFC3B2ECB

D060F945-77DB-4C46-9383-6A1A2AA26B71

3E1F954F-451E-4AA2-9D53-744FD2B3F4C7

16B96A88-E783-4A3F-A2E5-ACB3214764BE

C1CF16CC-129E-4B3F-8126-36E0794E1CF9

B3669710-F18C-4BE9-870A-C3790BE32FD4

90F20105-AB1F-42ED-B977-8EC9B755F399

279348A0-84CF-4A9A-A8CB-5BF6317FDFFA

PS, I have the graphics set to the lowest settings possible.

58

My problem was solved only after I removed all overclocking and undervolting now everything works like clockwork thanks for your attention.

2 Likes
59

I resolved the problem today, received some guidance from Nvidia Technical Support, combined it with information from Microsoft support and received a visit from a DELL technician again.

Based on everything I did with Microsoft, Nvidia and DELL, I made a radical decision.

I accepted the DELL Technician’s suggestion, and he advised me to format the SSD, and leave the CPU at factory settings.

That done, I downloaded battle.net and reinstalled the game.

When returning the CPU to factory configuration, Nvidia came with the 556.12 - Gamer Ready driver.

Problem solved, I didn’t need to do any additional action, the game is running smoothly.

I don’t know if it can help those who continue to face difficulties and to make matters worse, Blizzard’s deafening silence.

My only fear now is that with the game being updated with the new patch on November 19th, problems will appear again. I hope not.

I’m lucky to have been so well attended to by Microsoft, Nvidia and DELL support.

I hope that the actions I took and leaving the Nvidia driver mentioned above can solve the problem for other players.

And light some candles, so the patch 2.0.5 update doesn’t bring new problems, which considering the launch of VOH to date, wouldn’t be new to be filled with new problems. I hope not.

So overall, I can only regret the silence of the DEVs and/or others responsible for D4, as well as deeply regret the guidance provided to me by Blizzard agents. (Search for a solution on the internet or hire an IT professional)

PS - It is worth noting that using the latest version of the Nvidia Gamer Ready Driver, it was possible to run the following games without problems:

a) D3
b) D2R
c) WOW
d) FFXIV
c) Throne and Liberty

The question remains: Is it because Nvidia’s latest driver runs the games above and doesn’t work with D4?

Hypothesis 1 - Is D4 far ahead of Nvidia?
Hypothesis 2 - Is D4 too far behind Nvidia?

I’m sorry for any terms and/or words and phrases that present some confusion. As I said in the first post, my native language is not English, and I am using Google Translate. Thank you to everyone who posted suggestions, and whether directly or indirectly they helped me solve the problem.

60

Your problem, like everyone else’s, lies in overclocking and undervolting the processor. Some games don’t play well with these things, for example, Escape from Tarkov also doesn’t like it when the processor is overclocked. The Dell specialist did a great job, but he helped you after I wrote that undervolting was the culprit. Formatting the SSD and installing an earlier version of the drivers is not necessary. You can be sure of that.

1 Like
61

If you have an MSI motherboard, use only Kombo strike for your processor. Do not use manual undervolting or overclocking. Let me know after checking.

1 Like