The crashes continue

I know the topic has been raised many times, but they are all closed. The remaster is 14 months old. Patch after patch is released. But the stability of the game is still the worst I’ve seen.

The game crashes regardless of the computer configuration, the composition of the running software, in-game settings.

The only thing is that it crashes much less often in Legacy mode. But did I buy a remaster for him? The game crashes 50% when switching graphics, changing any graphics settings, entering a portal or waypoint, exiting a lobby, going to the character screen. Often it is enough just to go inside the game или walk a few meters and immediately find yourself on the desktop.

Maybe it crashes when trying to load some models or sounds. Maybe even a music track that plays at some time, and this explains the randomness of the crashes. I don’t know, and why should I know? I can’t fix it.

Act 5 crashes especially often, for example, it is almost impossible to get to Areat Pletau from Frigid Highlands - the game will crash after 1-5 minutes from the start. It also crashes very often near the mercenary merchant in Act 2. In addition, it crashes in any other places, although a little less often (after 2-10 minutes instead of 0-1, lol).

It is impossible to play as a summon necromancer: I went in, created skeletons and threw them away after a few minutes.

In this case, sometimes there is a bug report, but usually not.

Despite all this, my friend and I completed the entire game by 1.5 times. Only I understand less and less “why”, and I do not want to continue further.

I have several ordinary computers without viruses, my friends too: usually these are new laptops or desktop computers on Windows 10 or 11 that fully meet all the stated requirements. Graphic cards are different: Nvidia, Radeon, built-in vega7… On more powerful computers, it crashes at least as often as on weak ones.

I checked: I have no overheating, the memory has not run out. Although I noticed that before the crash the game looked like it was frozen, it started up a couple of times for 0.1 seconds and threw it out completely.

I tried to find patterns, adjust settings, deleted everything from the computer except Diablo and the browser - nothing helps, and there seems to be no dependence on this.

I tried to play at the lowest settings with everything turned off, but I did not find any dependence: it throws out no less than at high or medium.

It seemed to me that early in the morning it throws out less often, somehow I played for about an hour (this is an achievement, right?) without throwing out. But it rarely takes more than 20 minutes.

What to do, and will there be a correction of the situation? Keep all stupid advice like “update drivers” or “check the installation of the game for errors” to yourself: it’s been a year since everyone has been writing this, but it doesn’t affect anything. All the newest, cleanest, and problems with only this one game.

We paid money, we spent a lot of time trying to play and figure out why we can’t play what we paid for. I’m really looking forward to the answers.


Wonderful. My answer was just silently deleted. What’s the point of doing business with a company like this?

In it, I wrote what steps I took and that I created a similar topic on a technical forum. Is this the worst message to be silently deleted without explanation?

I will continue until I am banned, if they find for what. I don’t care. All four Blizzard games I tried were terrible (wc3, d2r, immortal, blizzard arcade). Three of them are broken technically.

It is on your end. Ever since they fixed server issues last year I have zero issues on either my main 4 year old PC, my 12 year old gaming PC and on our switches… if you can’t figure it out, go get it on console…

Well, keeping your system drivers up to date is one of the things that you should keep doing, in addition to letting Blizzard know that you’re experiencing issues. However the General Discussion forum is not the best place to let Blizzard know about it. The complaints would be better placed in the Technical Support forum, as any posts there have a much better chance of getting Blizzards eyes on the issue:

ive crashed twice so far this season.

one was right after shenk died , couldnt reproduce after that.

one was while idling in town, couldnt reproduce either.

so its still not perfect but at least its not frequent or easily reproduceable i guess.

the ratio seems pretty good aka i’m not running around scared on my hardcore character :wink:

What can I do? Something to remove, install, check and change some registry setting? Most of all it looks like a sound or model loading error. But everyone has fresh SDD in their computers, RAM is not broken. I’m not the only one, several friends and I bought this product and everyone has the same, regardless of the composition of the computer.

I am more than an experienced computer user and programmer, I have a rough idea of ​​​​how programs and games are arranged and I can guess the reason for the behavior of the program.

As an experiment, I’ll try to install the game on an external usb3 flash drive. It’s even interesting what happens.

Well, keeping your system drivers up to date is one of the things that you should keep doing

I agree, but everything is the newest, computers are on average about a year old or less, the OS and all drivers are the latest known versions.

Once again, I’m not writing this as someone who only knows the power button on a computer.

I’ll try to duplicate the thread on the tech support forum, I didn’t know about it. I have seen similar threads here.

From what you have described, I’m positive this is on your end. Sounds like your running out of Memory. Either on your mainboard or your GPU. Could also be your processor less likely tho imo. Game runs great on my setup. Good luck

2 Likes

Ive never once had a crash and ive played since launch and im not on the best pc either i have a build from like 2014.

You should post your specs.

Don’t do that, what do you think it’s going to achieve?

Is there anything in common between all of your computers? Are you all using the same RAM? Have you all fiddled with the timings? PSU? Voltage issues? Same mobo? Anything?

For reference, I’m use a base-model laptop with integrated graphics that doesn’t even meet the minimum requirements for the game and I play on NA servers from Australia with a 250ms ping - the game doesn’t crash.

Common… AMD Vendor and Ryzen 5 processors. All other components different.

My current notebook:
AMD Ryzen 5 5600U with Radeon Graphics 2.30 GHz
8,00 GB (available: 7,35 GB)
500GB SSD

Also has desktop
AMD Ryzen 5 1600
Radeon RX580
16GB RAM (8+8 dual)
1TB SSD

My friend play on Intel + Geforce (discrete) notebook and catch equal count of crashes.

Out of memory is the first thing I thought. But no. The system uses memory compression and a huge swap file. Applications work quickly and stably even if the memory is 99% occupied.

I tried to delete and close everything that is possible, while diablo crashed the same way at 99, 95 90, 75% of the occupied memory. Not a single program crashed even by 99%, because the system effectively reallocates physical memory.

There is one more suspicion: although the game is x64 bit, I have not seen that it occupies more than 3.7GB in working condition. It looks like x32 bit addressing. As soon as something requests memory beyond the 3.7GB range, the game will crash.

The version is interesting, but it crashed by 2GB, 1GB, even 300MB with a couple of gigabytes of pure RAM.

I agree with op. This game is very poorly optimized.

I have recently also issues with game freezing and then stopping to work. In just random places. Weird thing is that it happened multiple times on my hardcore sorceress, but it didnt happen on softcore barb and even on my hardcore druid.

1 Like

I saw some articles saying that the latest Windows 11 update messed up some games/apps, and a fix is pending.

had my third crash of the season, right after shenk still.

i doubt its on the user’s end really. i play 12 hour sessions on a bunch of games and this one is the only one that crashes, albeit rarely. looks like something about shenk’s death itself in my case, and not every time.

win11pro/13900kf/3080ti12GB/32DDR5-6000/kingstonM.2

nothing gamebreaking just… weird. feels like there’s more chances for it to happen if i stick around to enjoy the show vs leaving as soon as he dies.

the only reason im not too worried about it is that its a “safe” place to crash… most things are already dead and if not they’re being killed by the light show anyways. easy to survive.

If your memory is running at 99% and ur using Virtual RAM, that very well could be causing your issue. I’ve had a similiar issue on my old PC with an other blizzard title. VRAM is terrible for gaming. D2R uses quite a bit more memory then the original. You could try downloading a Prioritization Engine to help clear up a gig or two more memory and see if that makes a difference.

1 Like

Sometimes yes, sometimes no. Normally this is good advice, but another piece of good advice is if you’re super stable, you don’t go updating until absolutely necessary. I’ve yet to have a crash in any Blizzard game in the last few months with the exception of Diablo: Immortal. I’ve tried both my stable OS (Win 10 v1903 w/ available security updates installed) and the latest for both Windows 10 and my nVidia drivers. Neither OS or driver combo yielded a stable D:I client and the kernel backtrace from the crash showed it to be an internal overflow crash that has yet to be fixed on Blizzard’s end. Every other game is rock solid stable. I’ve even managed a good 400 additional hours in Bloostained: Ritual of the Night without crashes after they fixed the Fatal Error that the 1.3x patches had (UE4 engine conflict with SDL/FNA).

I’d be willing to bet D2R is hyper sensitive to RAM timings. Many people add new RAM to bolster their setup after the fact and fail to realize that DIMMs were designed to work in matched sets. That means when going for more RAM, say from a setup with a single 8 GB stick to 16 GB, it’s better to purchase a full 16 GB matched kit rather than put in just a new 8 GB stick to total 16 GB because the unmatched DIMMs will have different timings even if they are listed at the same timings whereas a matched set are guaranteed to have the exact same timings. It’s one of the most common causes of crashes and instability on both Macs and PCs. Matched CAS latency is essential for stability as RAM timings are the foundation on which your system operates.

2 Likes

A good move to DDR5 eh? Built in ECC?

Progression is key.

:slight_smile:

Ahaah))
Diablo 2 resource recovery requires under 4 gigabytes of frames even in legacy mode, while the original spent 50 mb. That’s “a little more”.

But you misunderstand memory allocation a little. It’s okay that the memory is 90-99% occupied, most of this is warmed up caches and can be immediately released or thrown into a swap. Almost 15 gigabytes of less than 8 actual gigabytes are now allocated in the system, and this does not spoil or slow down the work of programs in any way. On the contrary, heated caches == busy memory, speeds up programs.

In the case of diablo, there is no realistic justification for taking up 4 gigabytes. This is just a nightmare optimization: the game asks for more than 50 times more than the original.

But as I wrote, it’s not a lack of memory: it crashes in the same way when there is more than 2 gigabytes of clean memory, and the diablo process still takes 300-500 mb.

The reason is different. Maybe some instruction comes from the server that crashes the client. But the legacy mode, although it crashes, is much less common. True, 50% crashes when it is turned on or off, but it is not turned on by default and must be turned on every game.


I have the standard BIOS settings, the memory is not overclocked. The laptop doesn’t even have that option. In general, yes, on a laptop, as I remember, 3200 MHz RAM, and on a desktop 2600, it drops much less often there. There is no opportunity and desire to lower timings on a laptop.

I played the old diablo on both computers, it never crashed anywhere. It turns out that the requirement for timings cannot be explained by the basis of the old game engine.

Yes, many old games behave strangely on new hardware, but this is not the case either.

i barely crash at all anymore. extremely stable compared to release.

The game’s file sizes have also increased, thus the RAM usage increase. Even if you’re “just” using Legacy mode, the modern files are always in use in the background waiting to be switched to. And being a 64-bit app also increases RAM usage. 4 GB is pretty much the bare minimum most 64-bit games are going to eat these days. This is nothing new nor is it anything to get your knickers in a knot over. It’s normal.

I just explained it. You’re welcome.