Why does the game still crash this far into the season??
2 Likes
Latest word Nvidia drivers clashing with Buzzard games, And why aren’t they working to fix this? “Got on my computer and updated my Nvidia driver to 555.85, now the game crashes either on load after character select or randomly during play. Help”
Drivers are not the issue. Memory leak with newer hardware and newer features is.
1 Like
Yeah ABOUT That? **Nvidia* makes no money from Activison/*Blizzard* streaming their games.* [Nvidia Driver Issues]( https://us.forums.blizzard.com/en/wow/t/nNvidia-driver-issues-post-53758/1695973)
Look I tried the older drivers as some users suggested and my crashes continued. So it’s not a driver issue. The exact same “symptoms” were present. Which were high RAM usage with only 1/2 to 2/3rd VRAM usage, and the RAM usage exponentially growing over time. That and the error codes given for users experiencing BSOD with this, and only this game prove beyond any doubt that there is a memory leak. And it seems to be most commonly associated with users that have newer/newest hardware and/or utilize features of such hardware like DLSS. Which has been disabled on multiple occasions because Blizzard just can’t seem to figure out how to properly implement it. If it were simply a GPU Driver issue then a rollback would fix the issue for ALL users and furthermore, exponential RAM usage and an ever growing Pagefile with coinciding error codes pertaining specifically to pagefile errors would not be present. Seeing as how the GPU driver would have nothing to do with that.
I’m currently back on the latest driver and have had the least amount of crashes since then. I occasionally crash after long sessions as the system ram usage increases. I also crash anytime a patch is pushed out, as if I’m being forced to update via a forced crash.
And it would make perfect sense for another Blizzard product to be coded equally as poorly.
If a rollback helped you, cool. However I strongly believe this is only a placebo or possibly one small part of a much larger problem, which I believe stems from Blizzard’s coding and not actually anything wrong with or to do with the GPU driver.
NOT Just this game tho as YOU Claim but D3 as well so…? BTW If it’s As you say, While I don’t play any of Buzzards other games but D3 n D2R, D2R didn’t seem to have this issue so? I would expect it to go to WoW n Call of Duty as well, So unlike what someone else said in another crash thread that Buzzard better fix this bug fast or…
Well all I can say is they’d better Fix This VERY Quickly as When & If They Don’t! They should expect their career in gaming to go💀 or do you disagree on this Ms Cheetah?
Priorities:
1AAAAA Cash Shop
.
.
.
.
.
145. Bugs
How about this a bug report, Does this sound feasible? [Fenris Crashes? " TL;DR:
Turn OFF any kind of dynamic overclocking.
Examples include:
Asus Motherboard AI Optimized OC
Gigabyte Motherboard OC Guru
MSI Motherboard OC Genie
MSI GPU Afterburner Software
You may be able to turn on a static XMP RAM Profile, because it’s STATIC.
Anything that is DYNAMICALLY changing CPU or RAM will crash Diablo 4.
Longer explanation:
I only know a scant amount of what I’m about to explain here. It will be vague, it will be a little speculatory and it might be that all of this doesn’t work for you. Try not to berate me for being inaccurate in places of this post, I’m just trying to help.
That said, as of this writing, I can reproduce a Fenris crash on demand by simply turning on my motherboard’s dynamic over clocking feature. When it’s turned off, the game never crashes, never experiences any disconnects and runs as smooth as glass. Why that didn’t affect the game before patch 1.1.1, I do not know.
How I figured it out:
Fenris crashes create memory dump files in addition to the FenrisDebug text files. Those memory dump files are in the same format of a Windows memory dump file and are readable by WinDbg. I read several dump files using WinDbg then had it analyze the dump and give me some discernable information about them. The one thing they all had in common, was a memory address access violation. They all also appeared to be encountering that access violation when trying to access a memory address that the game had previously written data to, or had defined with a specific data type. Like any application, Diablo 4 writes a value into a variable in memory, runs some kind of routine or array that changed it and the tried to access that memory address for the end result of the routine or array, but then received an access violation when trying to read the data. The mystifying part of that to me however, was the access violation was from Diablo 4 itself, not Windows. The memory addresses were different in every dump file I analyzed but the access violation was the same.
Diablo 4 uses a proprietary game engine. It’s Blizzard’s design and implementation as far as we know. They used a similar version for Diablo 3. It’s their code, not an out of the box engine like Unreal, Havok, or the many other engines that are used to make games. Whereas those game engines may not care that memory and CPU speeds are dynamically changing based upon the load being placed upon the system, what I believe is that Diablo 4’s engine does care or isn’t setup to deal with it. I’ll also guess that this may be on purpose as a result of so many “trainer” type of cheat programs that have been used over the years to read Diablo’s running memory and manipulate it, but I digress. Elden Ring is a somewhat recent game that also uses their own, proprietary engine and it ran perfectly with dynamic over clocking. Diablo 4 does not.
Therefore what I believe the issue boils down to is Diablo 4’s code (I believe C or C+ language) being VERY specific about data to written and read in memory. If your PC is using a dynamic over-clocking method for your system or graphics card memory, the data written to a memory address and then read from that same memory address is being considered as different by Diablo 4. Or Diablo 4 recognizes the conditions that the memory address was written to as different from the conditions that memory address is read from, or the dynamic over clocking is putting that value somewhere Diablo 4 didn’t intend it to go and thus it’s different memory in any case and the access violation occurs, crashing the game.
I started troubleshooting this using these steps:
- Turn off all over clocking of everything.
- Disable any XMP profile in the BIOS.
- Uninstall graphics driver and all associated components.
- Reboot whether you need to or not and reinstall graphics driver.
- Play Diablo 4.
- Does it work? If so, then enable your static XMP profile for your RAM (and make sure it’s not being set to run faster than your CPU supports, of course).
- Try again. Does it still work? Then one by one, you can try and enable over clocking of your CPU or GPU, but this is where you will likely encounter crashing.
As previously stated this may not work for everyone, but I hope it works for you, Wanderer. Happy gaming." ](How I SOLVED my Fenris crashes from 1.1.1)
Limit virtual memory page file, if you have it expanded above your ram size something seems to go wonky with it when it fills up and crashes.
Mine used to crash on average every hour.
I capped my virtual at 24 gig even though have 64gig ram and it solved my hourly crashes.
I don’t know crap about code but something feels right about shadows code error explanation and the weird oc memory thing.
When memory isn’t limited the game can’t handle it.
I have not crashed since the start of the season and now I have crash 7 times in the last 24hrs.
I get that it did not work for you but why did it work for me then? I was crashing upwards of several dozen time and then I reverted to 561.09 and have not had a single crash since.
Different things work for different people is all I can imagine. And the driver revert was the only change I made.
I find that people on this forum often lie through their teeth when they want to be right, despite clear physical evidence to the contrary. I mean, there’s literal physical evidence that the game itself has a memory leak regardless of what driver you’re on. The only notable difference is that older hardware seems to be less susceptible to whatever is causing it.
That said if you’re really not crashing, hey good for you. However, the driver is not the issue.
I don’t think they arer lying, I think they only can see one machine, their own, so whether they are not crashing or crashing every hour or fixed their crashing, EVERYTHING they say is anecdotal. Especially given how many combinations of hardware there are, you can’t expect them to do otherwise.
But the issue is very much Diablo 4. All everyone else is doing is making sure they don’t hit that point where they experience the memory issue for longer…
Bud… I have an open post history if I was a liar, you could easily tell considering how much I do post.
You keep saying the driver was not it but I’m simply saying then why was it suggested to me as it could work. Why did it work and why has it worked for the couple of people that I have passed on the suggestion?
I will say that there were some that it did not help.
I am no expert but you simply dismissing examples of it working does not make you right.
I changed nothing but reverting and it fixed my issue. I have not crashed since. If you want, you could probably search my post history for these accounts since talking to people on these forums was how I came about the suggestion.
Do you have netflix installed?
Sitting on an older driver is not a permanent solution, nor does it mean the driver is the problem.
The crashing occurs on non nVidia card machines also.
Not to mention the new drivers don’t crash ALL other games.
Also there are plenty of people running on the latest drivers, issue free.
All these things point to one thing, the issue is not created by the nVidia drivers.
Well, I know that when I was ready to launch the expansion, the game asked me to install the latest driver which I did and thought nothing of it. Then I started to experience crashes. Mind you, not too many. But then that weekend they made that change to Evade since it was supposedly causing stability issues. After that change, I have no clue why but I started crashing on a pretty regular basis and it was not getting better but worse. In my frustration I came here to complain primarily about all my lost mats, time and instances that closed.
That is when someone suggested reverting back to 561.09
I remembered seeing that suggestion thrown out in another post. So I decided to give it a try. I honestly had nothing to lose at that point.
I think you were talking to me in that post because if you recall, you were skeptical and I said I would keep you updated on if I crashed anymore after the change.
And I have not.
Like I said, it’s the only change I made. I don’t OC my comp, all my settings are the same.
So in the end, I can only point to the one difference.
And I did share this with a few people and it did help some but not all.
So in the end…
1 Like
See this is where your mistake is.
There are 2 actors. The nVidia Drivers. How Diablo is implementing those drivers.
And for some reason you seem to think it is nVidia’s issue while most other games work with these drivers, minus a handful that crash.
I am glad the driver revert stabilized it for you. Do what works for you.
But many people use their computers for more than just Diablo.
I am curious why you asked this.