Constant crashes - game is not playable

Technical Support
21

Set the paging file to a fixed size. Do not use different values for minimum or maximum settings. Set both boxes to the same value, so the paging file isn’t dynamically trying to adjust when it thinks it needs to.

Exact instructions here:

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

Now, that may not help you in your case, but it will help the system performance overall.

Here’s another possibility:

Perhaps your card is having issues when the demand is high. Have you run any stress tests on your hardware to see if there are any issues, such as Furmark?

You can use these tools to run stress/diagnostics on your GPU to see if it has issues:

https://geeks3d.com/furmark/

https://benchmark.unigine.com/heaven

https://benchmark.unigine.com/valley

https://benchmark.unigine.com/superposition

https://www.passmark.com/products/performancetest/

See if any of those show any issues.

22

I feel your pain keyboard and mouse lock up as soon as I start can’t even use esc to exit

23

Reset the page size - no change.
Furmark 30+ min - my card runs warm 83-85C, hot spot 103 - 107. But until Diablo IV I never heard the GPU fans, they have been running on and off since the 1st Beta. The fans run on and off not all the time (actually the Furmark test makes it sound like it normally runs during D IV. 40 min no change on the Furmak scores (I am running it at 2560x1440 - my native resolution). I’ll clean my PC inside to see if I can improve the air flow…

UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
This is a standard exception error that can be caused by a bad file . Update your drivers and operating system to resolve any compatibility issues. Configure your security software’s exception list to allow Blizzard applications to run. Close all other applications to resolve software conflicts and free up resources.

Found this, lowered my resolution to 1920x1440 - still crashes
(Game crash (UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)))

24

That is way hotter than I would like to see on any card. Either poor thermals (either design, clogged or general air flow), old paste, or the actual sensor is buggered.

As for the error, yes, I have seen that description.

The problem is its very generic. It could indicate any of the following:

  • Damaged game file
  • Damaged driver file
  • Damaged Windows file
  • Incompatible or problematic driver
  • Other software running while the game is running
  • CPU or Memory problems
  • GPU problems
  • Heat problems
  • Power problems

Problems like this are what makes me want to sometimes pound my head on a desk. The only way to try to resolve it is to change the environment. You had recently updated to 11 I think you stated in the beginning as well. Lots of variables here.

The way I would approach a problem like this, if things we had tried so far were not successful, would be to:

  • Try running the game on a different PC as a test if I had one that could run it.
  • If I had a spare drive laying around (hopefully an SSD) shutting down, connecting just that drive and doing a clean install of 11, updates, drivers, and install the bnet launcher, then the game and test again.
  • If neither of those choices were available, then I would have to clean install on the existing hardware, only installing that which was required for the computer to run the game.
  • Basically eliminate the chance its a software issue. If that didn’t work, then I would have to approach it at a hardware level. Clean out the system, reseat the cables, the components, things like that.

But this is not something many are going to want to deal with. Nor should we have to.

However to eliminate any chance of it being something with the system, it maybe necessary to go to a few extremes.

But that’s all I got at the moment.

25

I apricate the ideas - I am going to work on cleaning the PC when I have a chance, I ran D III today for giggles…and my GPU fans came on - that never happened before. I do find the heat concerning - the GPU fans have been running about the same with D IV, but the D III issue causes a bit of pause. Doesn’t happen in Immortal, but that’s a different ball of wax.

I don’t have another gaming machine available, so I’ll have to tinker around with things for a bit. I added a new SSD when I upgraded - gave Windows 250GB more and put Diablo and other programs on my new 2 TB SSD (again over a month before anything started acting up). But that precludes me from going back to Win 10 - and I did an OEM version when I built this PC.

I was going to build a new PC in Dec…I may have to change my time frame or jump at a 4070, not sure if I want to pay for the 4070Ti.

I think D IV is worth the time to keep tinkering with things…but Sat/Sun are the only days I have enough time to do that.

I will update this thread from time to time…hopefully with progress.

26

I get that. If you do either of the 4070s, get the super versions. The 4070 Super is the better of the base 4070, the 4070 Ti Super is a bottom 4080 base card, whereas the 4080 Super is the best version of the 4080 card. (A 4080 Ti could have been a cut down version of a 4090, but they never released one)

The first time I played this game during the beta was on a 1660 that I had been using for a while. Then I tried a used 2060. Then a new 3060. (all of those were MSI Ventus models) When the game launched I picked up a used MSI Gamer X Trio 3070Ti. Ran on that till January of this year and pulled the trigger on the newly released (then) nVidia 4080 Super FE. Been a nice card, but I’m already looking ahead to the 5090 or 5080, depending on where they price at. Though the 5090 is rumored to be a lot higher than the 4090 was launched at… I’m not going to spend a crazy amount on a video card. 1K was painful enough for the current one. But at least I can sell the 4080 for near its list price, even now.

My problem is, I may have to pick up a new PSU. Mine has been acting up lately. Every couple of weeks it randomly powers down and starts blinking the lights. lol I have to power down, reseat the power cables and then it boots again and is fine for awhile. Corsair AX1200i. Another 400-500 bucks I don’t want to spend. Ugh.

27

I use old drivers 536.23 and it is very stable! I have i5-2400F, 32 GB RAM, 1 TB SSD and graphic card 3060.

28

I was running the game at launch last year with drivers from June when I installed the 3070Ti. And I stayed on those drivers till I bought the 4080 Super. I had to install the newest drivers then to support that card, but I haven’t upgraded the drivers since then.

1 Like
29

Uninstall and reinstall did not work. Maybe this weekend Ill have more time to tinker.

Drivers are now 556.12 (I know I ran later drivers and didn’t have issues)

Crashes occur on all starting screens, loading screens, logging on to Diablo servers etc., character screens, character creation screen (took 4 attempts to create a new character), cut screens, in town, fighting out of town (I made it to level 4 - took about 30 - 40 restarted due to constant crashes).

Same errors:
UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
DBG-OPTIONS
DBG-ADDR<00007FF6D29C1680>(“Diablo IV.exe”)
DBG-OPTIONS<>

Found some 3 - 5 month old posts to try fixes. I would really like to play D IV - but until there is an update that fixes whatever caused this - it probably won’t happen.

2 - 3 weeks before this started I did upgrade to Win 11, added another 2 TB SSD (needed the space only had a 480 GB b/4). All my Diablo games Orig, D II Resurrected, D III, Diablo Immortal, D IV - were on the 480 SSD as D:, recreated a larger D: on the new 2 TB drive…everything ran fin for a couple of weeks.

I may not have played D IV for a couple of days - but the crashes started on the 22 of Sept. I manually update drivers - they had not changed for weeks. I did try the latest ones - but it didn’t help.

Oh - changed graphic settings - lowered (looked like carp) raised, went to GeForce experience and changed them, manually changed them in the gamer - no difference.

So the saga continues - Nothing else crashes - only D IV

Well, well, well… non-seasonal runs without crashing. Starting a non-seasonal spiritborn. I ran 3 characters - 2 from last season (Storm Slide Druid and Sorc) that were crashing as seasonal characters…no issues. Ran a Necro for 2 seasons back - no issue.

Spiritborn just crashed standing in town at the starting point…twice. Crash loading…crash sitting on character creation…Seems like a lot of crashes happen at “downloading data” on the loading screen (2 in a row) - game does not like me clicking on “Blizzard or Vessel of Hatred” screens.

Trying a Necro seasonal…no good keeps crashing. Now can’t get to the game through all the loading screen crashes.
Now the Eternal characters are crashing…loading, cut screens, in town…

I’ll just uninstall this from my PC - tired of wasting my time trying to fix it.

Not sure what changed - I did get a Realtek update - so for giggles I reinstalled Diablo IV…so far it’s running…

UPDATE: The game usually crashes twice (sometimes a few more times) on trying to load , usually before the character screen - occasionally at the character screen or in town.

Once I start playing - things are usually good for a couple/three hours (I very seldom play longer than that at one time). I have had a couple of crashes during game play but at least I get a lot of game play in now (a month late into the season).

Crashes - same as before:
UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
DBG-OPTIONS
DBG-ADDR<00007FF754786476>(“Diablo IV.exe”)

Diablo III (I was playing more when D IV was unavaiable)…started crashing, and guess what:

***** UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005)

So far no issues with Immortal. Still sending my error reports in Hoping Blizzard will fix this since most errors are loading the game.

30

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.