Massively disappointed by technical issues

Technical Support
1

I really can’t stand it anymore, I really want to play this game, finish this seasons journey, get my char to level 100… But the game does everything to prevent me. No, not the usual purposly added slow down mechanics. After the patches I really like the season, but by constantly crashing of the game.

I never had any issue in the early access days when game launched, since official launch I always had crashes from time to time. Each patch changed it, it became worse and better, worse and better. In around first half of Season 2 it was so extreme, that I reached out to support and asked for advice. I did everything I could, I even did the things that should not at all affect this only to proof it’s not the PC but nothing really helped… Until they dropped the patch with the malignant rings, after that it crashed very very rarely and I was able to enjoy the season.

Now, with season 3 start, crashes became worse again. I find myself so often on desktop during a seasson of 3-4 hours, it really frustrates me. It deletes sigils, it deletes elixirs and I don’t even want to attempt any boss tries to delete my materials to summon them, because it takes quite some time for me to obtain them. But in order to continue season journey I need to kill them, what should I do?

Beside all the stuff I did already that the support asked me to do, I went my self around and checked what I can do. Nothing helps. Oh and other games just run fine, tho. But D4 refuses to simply work. It runs totally smotth on 144FPS in 4K UHD on my machine, so it’s not about hardware limits at all. I also digged the forums to find “workarounds” but nothing really stops the game from crashing. I am constantly reporting the error codes and answer what I did when the crash happened. The problem is - here’s a summary of activities I did when the game crashed:

  • Opened the Inventory in town
  • Entered/Ported to Town
  • Left town to enter Helltide/ride to Worldboss/Legion Event
  • Port to another waypoint
  • Port to a NMD/Vault
  • Open Seaosnal Tab/Jounrey/BattlePass Window
  • Charged into a group of mobs during Helltide/NMD/Vault
  • Legion Event started
  • Worldboss defeated and was dropping loot
  • Opened Chests in Helltide/End of the Vault
  • Talked to Blacksmith/Juweler/Ocultist/Vendor/NPC
  • Stand in Town/Open World/Dungeon while comparing Items
  • …

It’s totally random… So there is nothing I can do to avoid that. I just need to wait until the next patch lands and hopefully fixes this issue again. Here my crash log I started after the first like 10 crashes to actually show the actual frequency of this:

Summary

After Season 3 Started
(Those are not all, I started after a while to save the codes)
9CA97776-246C-43C8-A009-E94F3E0A196D
3FF073FE-D459-4694-AC82-300548C5C840
937C4FDA-8AA8-4EC9-AFD7-33C8D5002737
46F852F5-E2BD-47C2-B3BC-E07321A95F54
64A7D012-6388-4FC2-9F76-64B6514FB8C0
2F22AA69-9EEC-4ECC-9078-F3135165B77F
8D3E1562-1EC9-4D58-9C0A-E30B473FBDDA
58F34945-F209-4586-8D00-45CAA7258572
FE6C5C4D-1A0E-4894-AD5C-FB8A868AD065
38A6DAF6-9FEC-4D11-8BA1-AB5A8F683FE0
27796568-DAE6-4100-AD73-B228E8AF3FBA
09FB24D1-3BEB-4EB9-A771-F833EE0CBFB0

After first patch (Here it seemed to be better, but the patch was not long available)
E3F93F8B-A2A8-4FA7-92E3-9F66EE54EF99

After 2nd Patch (Here it became even worse, this is the whole dicrect storage issue)
58C93B83-401F-44EB-9446-7907CDAFB33B
(NO ERROR CODE) Freeze on loading screen, had to shut down hardly
(NO ERROR CODE) Freeze on Char select, had to shut down hardly
(NO ERROR CODE) Freeze on loading screen again (Killed in task Manager and it worked again for a while until:)
98395CF2-4CCE-4984-9793-AEFF75522434

FC486512-4DF2-46B2-A940-69088475AAA6
(NO ERROR CODE) Freeze on loading screen, had to shut down hardly

3666A90E-2051-4DBE-8D77-9BC87C0D6B7B
597996E3-846D-4132-A8A5-0657567E7CCC
CFBBD386-B480-4ABC-B425-19A078CAA390
635C1AD0-8156-433F-8BE8-D513A6F52EC1
866A0CDE-B2CF-4CE1-AF83-51343E2DE567
6DA9CCCE-3D23-4636-A8AB-7109D4364C65
CB940F11-2631-4CAB-9682-CBEDE3F01082 -
(NO ERROR CODE) Freeze on Loading Screen, killed process via Taskmanager
212E6A15-CAA6-4118-A92E-679B3DAFB6E8
3C3D670C-1DBE-4D65-8F08-9A9D36A3C261
665E78E6-AC42-4AC2-9633-858AB62BE601
F829F608-13F9-4AE5-944F-265C2E4BB2B8
26D21A64-9758-4842-95EF-DD04089108D9
37FCD7AB-62D3-4458-9133-34A354AC2858
(NO ERROR CODE) Freeze on game bootup, had to kill process in task manager
E3DF4DE8-B6D5-41D1-B81B-9341A4943481
(NO ERROR CODE) Freeze on Loading Screen, had to kill process in task manager
14B44CA7-4684-4C48-927A-AFE537973DA3
(NO ERROR CODE) Freeze on bootup, had to kill process in task manager
52EE8894-8276-4FA8-A9FA-D4DAB83B514F
B1D58879-C068-40E2-B7F8-C067C4AB4CB2

Added workaround to disable direct storage via command line arguments (-disableds)
It started good and was kinda stable for like 2-3 hours. But random crashes appeared after a while again:
4E18E4A1-C028-446D-8853-956DB18F43FE
1118FDFA-2ABC-42FD-938F-5908A43AA242
F33E1D01-7141-480F-BE8F-498DCF4AB148
C76BB739-142D-4A1F-A9D9-07E79CE34551
05426072-9438-4663-B755-6BBE8811C287

After 3rd Patch (The patch that was ment to fix the direct storage issues…)
AC69B911-CC91-4608-8090-E9D12F84369D
// removed -disableds flag
9EE9623E-690D-4521-8A1D-91B6442B2F1C
B822E331-A01B-4D2F-A5C7-A9BC9871F308
41E40C5C-8FEA-411D-BA36-9E18EF77882C
// added -disableds flag again
D28153B2-7D79-46F0-B89D-450E5BC6C382
56BF2AD7-7000-4D6C-BE03-B97E8216151D
C2A0C12F-9143-4AA9-AA0B-A342541FECC1
9C482C0D-5FB2-4A04-BE94-D0C6CC206D53
03ADC3F4-41F7-45A3-ABC7-10921265D1BC

Directly after starting the game after 1 day of pause, I am in Game after loading, open the Map aaaand Boom:
9C87BE80-5543-41DF-A48D-C74DA9F02BAC
Just went out of town into helltide…
22BD698C-87BF-4138-84DF-2F9A95BF4E0E
2587EE65-7B8D-4936-A142-F6C8AB915ECA
E0B56DD5-5B2E-41D3-A063-4F366AB140F1
80470DD2-E969-4C5B-9234-AD41CC7E1EAB
82407C29-2210-4A63-94B4-D74BFFB734BF
29EE06DF-45BF-427C-A054-D966DFA3D355
A84CBC41-0156-4F7C-8E70-088E40120B23

Windows Update/NV Driver Update/Other Drivers updated

DA4DEDD3-E22A-477C-A9E4-DBC858D81BBC
E09D1A7D-6129-4EB0-9B05-A457CC9A7D8A

Uninstalled old Microsoft “Game Input Service”
4EE05A82-A336-4021-8713-4E7D22FC8F66
C5EC3F17-C6B7-4BE3-91BB-6B405BC9DDF3

Disabled LED lighting in game settings, played ~15 mins and:
4EF2EA43-17E7-46E9-9FBA-B3A3EF5B82BD
D25171C2-9F1F-4CC9-AC9F-9EE33B9EFDDC
12409F8B-38D6-4BB0-B930-582B56E53558
A18A7A4F-4FFB-4345-AC97-FD3C47CA8107
7A6186FF-D4CD-489C-90BB-5A8B02DE9F0F
D645A156-D5DF-4741-8865-3C5C8E2E2B1B
0E3483D6-088A-4507-9501-DC2F4A3A696E
99D6943D-1204-470F-AA72-1E651735992E
D136C44F-6144-4063-AAC5-2612A23607C9
8AB2A9F5-B78C-40EF-9105-609449A0AFE8
2A94CF20-433D-47A4-9F44-01765E86C74B
CF90A54E-A3B3-468F-8847-01706B6CBBB8

I am fully out of ideas here and no sign of reporting those errors seem to land anywhere, I do so since the beginning, they improve it in some patches, only to make it worse again in another.

For real, I don’t need a Leaderboard or any new content, I need the game to work first. Why isn’t that a priority?

1 Like
2
  1. Ensure you meet the minimum requirements
  2. Upgrade your PC
  3. Ensure your drivers arw all upto date
  4. Ensure you have a good ISP
  5. Make sure the games installed on an SSD
  6. Try posting on the bug fourm for advice

Games run flawless since the middle of S1. Its easier to point the finger at blizzard than admit you have a :potato:

1 Like
3
  • Do you think i9 13900K, RTX 4090, 64GB RAM, 2 TB Samsung 990 Pro NVMe fulfils minimal requirements? :smiley:
  • Upgrade to what?
  • All drivers are up to date
  • Do you think 1 Gigabit is enough in Up and Download?
  • It is on a SSD (NVMe)
  • Yeah, maybe I can move it there, that’s a good point :+1:
2 Likes
4

Not saying the following include your exact issue but there are issues I’ve found on other peoples computers which also included “other games run fine but ‘x’ game crashes”. This also includes “worked fine last patch, but crashes now” symptoms.

  • A chunk of memory went bad in a stick rarely accessed by other games. Run a system memory check, which is now included in windows 11. “Windows Memory Diagnostic”.

  • A chunk of hard drive went bad but it happens to be the exact location windows decided to place its virtual memory allocated file. Set virtual memory to off, run a drive diagnostic on the sector level. If everything comes back without issues (will take a long time for the test), turn virtual memory back on.

  • The game files might be fine but the local directx files (or whatever) might be corrupt or other system files that are involved. Open “command” in admin mode and type “DISM /Online /Cleanup-Image /RestoreHealth” to find and repair system files.

  • In a blue moon undeleted-temporary files can cause an issue… just delete then. Open file explorer and in the top address bar type "%temp%. Then ctrl+a to select all, then delete. If it can not delete a file check skip-all and continue.

Like I said all the above have effected other peoples computers and issues running games that spontaneously crash. maybe one will help you.

— also adding since this is more a modern day issue, check the temps on your nvme and make sure it’s not over heating.

1 Like
5

I believe it’s on your settings.

Mine have occassional hiccups becoz i am running at the highest resolution at 4K. If i would just be on standard HD monitors, i dont think i would have issues.

But i am used to 4k. It’s okay for me to lower other video settings as long as i could continue playing in 4K.

I had issues with gpu overheating due to thermal paste not doing its job anymore. But i fixed it already and i can see no more gpu overheating anymore. And i know when to replace it again.

6

Something I should note as well. under Upscaling I switched it to default (in game) and the issues i was having went away. I run a 3060 Ti (v1).

7

Thank you everyone for your answers!

I tried this back in S2, the diagnostic froze at 21%, after some digging this is a known issue on modern systems. Of course this could be possible, however the RAM is 1 year old and doesn’t RAM issues end up in blue-(nowadays green-)screens?

Hm, I will run a check, temps should be fine with 43°C/110°F, right?

I will check this out, not sure why this should appear on D4 but not on BG3 or CP2077 both running on max settings completely fine

Can check that as well, but kinda feels like pulling for straws, I mean why would behavior change between patches?

I tried with lower settings before, most error codes are from my settings without any frame generation, disabled high res textures, activating it didn’t help, didn’t make it worse, tho. In Season 2 I also tried lowest settings and also didn’t really help, sadly :frowning: That would have been the easiest fix.
GPU Temps are like 32°C, it’s a Watercooled one via AIO with 6 fans.
I also undervolted it by 40% to save some power. It’s still powerful enough for everything. (And no, disable this doesn’t change anything, that was the first thing I tried)

Had it even without any upscaling/framegeneration, saldy :frowning:

1 Like
8

Sadly it can happen. I remember when a new expantion came out for an MMo I played and the guildleaders wife’s computer just started randomly crashing. After talking with him and her, and running some tests… it came down to the ram she was using in one operating system… while he was using a newer operating system… I had them swap memory between the two machines and all crashing stopped. ← the tl:dr version

A lot of times in these patches and updates there are un-noted changes on how memory is handled that can directly impact us.

9

IF your memory is bad you will notice it all the time with bluescreens. There is 0 chance diablo will be the only thing that accesses your bad memory.

1 Like
10

Maybe, depends. if said other games are not accessing enough of the system memory, then defective stick may not be accessed at all.

the easiest way to get a hint on what’s happening is looking at the System Event Logs at the moment of the crash.

I believe starting with windows 10+ you have to enable the blue screen in order for it to display, otherwise it will just reboot the system.

11

If your mem is bad trust me it will crash all the time. You might crash restarting. Bad memory is really BAD! Use mem stress test program and if your mem is bad it will pretty much instantly tell you.

prime95 comes to mind but thats old now

12

Ohh I def agree. Above he mentioned that the mem test dose crash (not finish).

13

Crazy, I mean Computers can be strange, but it’s the frist time I hear that specific programms crash because of bad RAM and popup an Error-Reporter, as Urza stated, they usually come with blue/green screens and that was never an issue for me.

Game froze due to the direct storage issue (that was acknowledged by Blizzard) but keept crashing on software level sending me to desktop showing me an error reporter - In my world I would assume the crash happens in the client code and even tho there is a chance that it is related to some hardware issue, it normally should show up in other occurences as well, at least that’s what I learned in my 25+ years using windows PCs :smiley:

I finished the scan of my drives, the 1 TB system NVMe and the 2 TB games NVMe, Samsung Magican says all sectors are fine (And yes, full scan. The 990 Pros are quite fast, took me under 1h to scan them)

I also did a sfc /scannow
From the logs is seems it fixed 3 dlls in system32, so maybe that helped. Only time will tell

That’s my experience as well and I never had a blue/green screen on this system, so even the memory scan freezing at 21% didn’t worried me anymore, after I digged deep to find out that this is a known issue on Windows 11 with modern RAM.

14

Memory issues is like trying to find the source of a leak in a roof. heh.

I’m just throwing ideas out there what what’s worked for me in the past. Nothing more. :slight_smile:

1 Like
15

You delete that little file that was giving everyone fits that isn’t implemented in game but is still there? I saw it on the bug board and it seemed to fix a LOT of people’s issue.

16

Next time you crash… immediately check Administrator Tools → Event Logs → Programs (or) system for the timestamp… You should see a Red entry at the exact time. The code will give you a hint to what happened or what the OS is reporting what happened at that moment.

17

I didn’t delete it, I set -disableds on additional arguments, that resolved the freezes, but not the random crashes to the error reporter, sadly :frowning:

That’s what I did the last days, I discovered that there was an older Microsoft Game Input Service installed that nowadays exist in system32 so I uninstalled the old one, but not even sure if that is related at all, I am already pulling for any straws I can find.
There are no errors that occur on the crash times so nothing that gives a hint why the game closed and opened the bug/error reporter from blizzard, tho

2 Likes
18

At the beginning of the 3 season, there was a problem of mages randomly shuttling.
Now it has appeared again.

There are also various annoying tasks set up in the dungeon (but that task cannot be completed), which ultimately leads to leaving the dungeon and starting a new one.

There are too many problems like this. They are neither diligent in testing nor willing to open up PTR. The final result is that this game is filled with too many bugs.

19

Interesting.

Another straw since I don’t know anything about your system. Are you running very tight CPU and Memory Timings in the Bios? I’d try relaxing both, and even under-clock, just as a test and run the game for a few hours to see what happens.

I know other games are not effected but each game can handle the system differently. Like how people say to set the minimal background framerate to 4 or 8 frames, and the foreground framerate to the monitors max (or a little lower).

We are just chatting and troubleshooring, tossing around ideas. Chances are it’s Daiblo code…

20

mem stress prog crashes all the time because it test ALL the Ram if ram is bad
normal software uses ranges of memory and might not hit the defective ones