Crashing Constantly with Blue Screens of Death

Technical Support
1

Hello,
I am experiencing crashes constantly when playing this game, even bluescreens once/twice a day. So far this is the only game that has managed to blue screen my system.
These crashes happen when afking/browsing in the main menu, lobby, or even mid-game while fighting or doing whatsoever. Doesn’t seem to have any special trigger to it. These crashes only happen after the game has been running for at least 1hr or more.

  • I’m not overclocking, I have updated all drivers, scanned and repaired corrupt game files, and I am running everything as an administrator. Got no overlays either, nor is my PC overheating. And my PC should easily be able to run this game, see below.

My specs:
MOTHERBOARD ROG STRIX X570-F GAMING
GPU NVIDIA GeForce RTX 3070 Ti
CPU AMD Ryzen 9 5900X (12-core)
RAM Corsair Vengeance LPX DDR4 3200 MHz 16 Gt x2 (32 total)
DISK DRIVES Samsung SSD 980 PRO (For OS) - Samsung SSD 980 (Diablo installed)

(EDIT) I’ve had these issues since the launch, nothing has changed with the patches.

4 Likes
2

On the topic of blue screens:

This issue is not supported by Blizzard Customer Service as it is not caused by a Blizzard product.

Source:

I would pay special attention to step 6 due to your description of the issue.

3

I am having the exact same issue. It is not our hardware. If it is…the game is forcing the restart… you can say it isn’t. But iv been playing the game since release no issues, only normal crashes. Other games work completely fine there is no crashing at all. Just last night my whole system started to blue screen constantly. 5 min to each game. Then I couldn’t even launch the blizzard client after a boot up without blue-sreen memory error. Blue screen after blue screen if I touch the blizzard client or launch d2. Literally everything else works and won’t cause blue screen… It is not the hardware.

1 Like
4

The command to stop hardware function can’t be issued by a game client, only Windows can make that call.

5

Okay…well the game is causing windows to make that call by somehow forcing some sort of memory problem… windows makes the call…because the game or something attached to it is forcing the shutdown… alot of people with the same problem. Is there any fix??

7 Likes
6

Hi there,
i assume your problem is a different one than the OP posted.
According to your post you get blue screens as soon as you start the game. That‘s not necessarily the game‘s fault.
Faulty memory can cause those issues as well and i believe that‘s the case here.
I am currently at work and i am writing this from my phone, but i‘d suggest crating your topic and describe your issues there. I don’t want to interrupt the OPs troubleshooting. Attaching a dxdiag.txt will certainly help with the troubleshooting. If you have blue screens make sure to get the error because that will be a clear indicator of what‘s wrong. If you missed them you can also check the error section of the msinfo or check the event viewer.
As long as i am at work i won‘t be able to help you but as soon as i am home i‘ll check back with you. :slight_smile:

9

You may be correct that it only happens with D2R but that is because the game has different requirements. If the cause is faulty memory then it will happen in other games as well with similar requirements.
To determine that you will need to do some digging and i don‘t want to do that here.
There are several steps you can do to narrow down the cause and it will take some time.

There is no need for guessing here.

10

Thanks for posting this. None of these can fit in the description I have given or the bluescreens that I am experiencing. As stated in my post my hardware is not overheating, my 2nd screen is constantly monitoring my temps, voltage, fan RPM, memory usage and so on. My Bluescreens doesn’t happen when I launch the game but when the game has been running some time already. For example I got my first bluescreen in beta when I was about to finish act 2. In Full release I experienced my first bluescreen towards the end of act 1. So it can happen 1 hour or 2 hours in, no triggers to this it seems.

1. [Update your drivers and operating system] to resolve any compatibility errors.
All drivers are updated

2. Check your system for potentially unwanted programs and malware with a [security scan].
No malware or unwanted programs are on my PC, if there were I would be experiencing bluescreens in other games aswell, but this is not the case.

3. Security programs can prevent your drivers or hardware from being accessed correctly.
This is the only option that has a slight chance of being cause of this BUT I am more than certain that this is not the case

4. Use [System File Checker] to scan your operating system files for errors.
Already done and my PC is pretty fresh

5. Overclocked hardware can cause system instability. Disable any active overclocking on your hardware, including factory overclocking.
Not overclocking

6. Overheating hardware can cause Windows to crash. [Check for overheating components.]
Check! my 2nd screen is ALWAYS monitoring my system’s health and activity. My temps have never reached high levels

7. Improperly slotted or failing Memory can cause system crashes. [Scan your RAM for errors]
I got brand new sticks, placed correctly and no scan has showed memory issues, besides memory issues would mean bluescreens in other games too, which again is not the case

8. Consult your computer manufacturer or a local technical troubleshooter for further assistance. Blizzard Customer Service cannot assist with this issue as it is not caused by a Blizzard product.
These bluescreens are happening ONLY when Diablo 2 is running, Beta and now.

1 Like
11

What are the error codes saying from those blue screens?
If you remember when they happend you could check your msinfo to find them. They will clearly show you and point you in the right direction.

12

You have absolutely no clue what you’re talking about. Applications, any application, can cause blue screens to manifest in a Windows environment if they are designed poorly.

If you did know what you were talking about, you’d be directing people to the Windows Event Viewer and determining what caused the fault.

There are myriad people who are logging threads because of this game and this kind of a response is totally unacceptable when people have purchased a product that is not working as advertised.

And telling people that it’s not Blizzard’s problem goes beyond that. It’s callous, rude and not behaviours indicative of people looking to support others.

For me personally, and, I doubt I’m alone in this, I don’t start threads because of people like you and the support staff. You have absolutely no idea what you’re doing and are part of the problem why solutions from the developer take so long, because they rely on this as a resource to get precise information.

Now you’ve just informed one of these individuals, having such troubles, that the problem is on their end. Brilliant.

Is there a means to directly contact the developers and give them the information required to fix this game vs being stonewalled by support staff who rely on scripts vs critical thinking and experience in tech?

That would be my question.

10 Likes
13

I will have to write them down to be sure from this point on, I went to event viewer and looked for these bluescreen error codes but I had experienced several minor warnings conserning missing (AppData\Local) -folder. This is not able to cause bluescreens and was well known issue in older windows updates. So I just now fixed that by creating a folder with another one inside it.
Gotta start taking down these crash error codes too for further investigation.

14

Edit: Got to correct that with the IDs. Not all blue screens have the event Id: 1001 I’ll do some more research on this and get back. :slight_smile:
You can find those unter Windows protocols → system. If you sort all entries after the event ID then you shouldn’t have a hard time finding the old ones.
EDIT2: Here is a picture of my blue screens:
https://imgur.com/a/tdfo1eM
The source seem to be “bugcheck” and it is specifically stated in the error message below that the system restarted because of it.

1 Like
15

I got the same. People are speaking of memory issues with this one but I haven’t found any resolves to it. My memory checks are giving O-kay and greenlight. With zero issues and Diablo 2 is the only game that has caused bluescreens on my system so it’s most likely some sort of memory leak in their program(?)

Source BugCheck
EventID 1001
Guid ABCE23E7-DE45-4366-8631-84FA6C525952

param1 0x00000124 (0x0000000000000000, 0xffffba0b29302028, 0x00000000bc800800, 0x00000000060c0859)

param2 C:\WINDOWS\MEMORY.DMP

param3 831df6a2-2128-4e2e-8407-a16ac612d5e2

1 Like
16

Some sources suggest that it is an issue with the voltages for the CPU but the circumstances are diverse to say the least. There are settings in the bios to adjust those but i am certainly not capable of giving any advice there.
You could contact microsoft support and explain them your problem, maybe they can assist you in resolving the root cause for it.
I am sure they won’t tell you not to play Diablo II: Resurrected anymore. :smiley:

17

This is misleading, so let me explain why this is our stance on Bluescreens and all the help that Customer Support will provide for them.

A Blue Screen of Death is a windows-level error which happens due to instability at a critical software or hardware level which is protected by Windows. Typically it occurs at the kernel level. Very few programs get direct access to this level of the operating system. Those types of programs are Windows itself, drivers, and some security programs. A kernel event can also be triggered by hardware failure.

While a program like a game can be the trigger which sets off one of these already malfunctioning pieces it cannot cause a BSOD itself. This is because Windows has protections in place to prevent that from happening. If a program causes instability to a degree that windows would otherwise have a BSOD, Windows crashes the program or restarts the drivers that are about to cause the blue screen.

If this is not happening, it means there is a problem with Windows, hardware, or one of the critical pieces of software in your PC with kernel access, regardless of whether or not you only see it when playing a certain game. Every game will access your drivers and memory differently, but none of them can access them in a way that Windows would allow to cause a BSOD.

If you suspect the issue is software related (Drivers, Security, or the Windows OS itself), you can reach out to Microsoft for help or do the quick and dirty fix of reformatting your PC and reinstalling it from scratch. When testing this you want fully update windows and your graphics/audio/network drivers and avoid reinstalling security programs or anything but the most basic devices like a mouse and keyboard. If that doesn’t fix it, that rules out absolutely everything but hardware, as long as you don’t reinstall security or corrupted drivers.

In that case, if you can’t diagnose the issue on your own using the information in the link I posted above or this thread, you need to contact a PC tech for hardware tests. There are several parts of your PC that you can’t test with software and that can be dangerous for both you and your PC to mess with. The reason we can’t help with those is that fixing any of them requires reaching inside of the PC and you could hurt yourself trying to test something you’re unfamiliar with, so this is why we recommend talking with a licensed PC technician.

Others in this thread can try to help you uncover what’s happening with the BSODs but as long as they’re occurring it’s outside of our scope. Hope that clears things up at least, and best of luck whatever you choose to do about the problem.

18

It is possible for poorly designed software to cause BSODs. I don’t know what they’re on about. Stating that since the error is happening at the kernel level, they’re not going to move further with you. Utterly ridiculous.

I’m sorry you keep getting stonewalled on this.

For me, I’m not getting a BSOD but it is having to shut down Diablo 2 because something is happening when loading data, that shouldn’t, according to the blizzard logs. I just hope that the devs are aware, will patch it and it’ll resolve itself.

If you’re more curious about the error, Microsoft has a debugging tool that can give you more information about the crash as well.

5 Likes
19

Sorry you’re going through this. I was having the same exact problems as well. It’s definitely something on the D2R side that’s causing something screwy. I noticed I haven’t had any issues with random blue screens or random restarts since my last restart and deciding not to play. Go from 2-3 random restarts (sometimes with blue screens) to running flawlessly. Hopefully they get this fixed sometime.

3 Likes
20

I have crash to desktop on 2 clients (pc and notebook) every 30min - 2 hours.
If both are in a game they crash at the same time.

Same on alle buddys that play d2r.
Many times all crash at the same time.
Its the similar crash like the beta and alpha, looks like blizzard did not fixed any mayor bugs.
The only fixed thing is the map bug.

5 Likes
21

Update to my situation
I’ve played some 4 hours today with 2 crashes and 1 bluescreen. Nothing has changed as of yet and I’ve had my PC fully checked. I did more memory-related scans with good results, had my CPU voltages checked and overall everything in my PC is as they should. I have installed even additional gadgets to see every tiny detail of my PC’s activity and health as it runs.

End results
My PC is executing everything flawlessly and passing through every test with outstanding results, as one can expect from freshly built PC. The fact that I am having this issue ((ONLY)) when playing Diablo 2 added with the fact how lots of people are experiencing weird crashes, much confirms that the issue is not on my side and it is out of my reach to fix. There is something very wrong with this software.

If you tell me that my PC is unable to run this game without issues with my current high-end parts then you’ve got one heck of a game here, and I’ll be expecting full refund.

My specs:
MOTHERBOARD ROG STRIX X570-F GAMING
GPU NVIDIA GeForce RTX 3070 Ti
CPU AMD Ryzen 9 5900X (12-core)
RAM Corsair Vengeance LPX DDR4 3200 MHz 16 Gt x2 (32 total)
DISK DRIVES Samsung SSD 980 PRO (For OS) - Samsung SSD 980 (Diablo installed)

2 Likes
22

Ryobi,

I am not saying your hardware is insufficient. I’m saying that something is causing a Bluescreen outside of the scope of the game client, and because we are not Microsoft technicians or PC techs who can get our hands on your machine to fix the problem ourselves, we can’t help any further. If you get the BSODs handled through Microsoft or a PC tech we can take a look if the game client keeps crashing after, but it’s unlikely that would occur. More information at my previous post.

Also, keep in mind that hardware is not the only thing that can cause a BSOD. As mentioned in that post, the OS itself and security software can cause it. If you’re confident the hardware is in good condition those would be places to start, and you can always work with Microsoft for OS issues or reinstall windows entirely after a reformat to rule out all software conflicts. If you do that and it’s still crashing, you know it’s hardware or an issue with the specific drivers you’re using. We haven’t heard mass reports of BSODs on any recent drivers, though.