pb86ed is sending this to you. Hope it will help us. SageOwl - Pastebin.com
Actually its kind of vague:
UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
DBG-OPTIONS
DBG-ADDR<00007FFF743D4D40>(ânvrtum64.dllâ)
DBG-OPTIONS<>
The initial crash starts here, looks like it happened during a teleport:
E 2024.10.18 00:38:51.069048 782 [Crash] Thread ââ handling fatal error
The file referenced above is an nVidia driver file. It is possible its hating on the version installed. If its the latest version, this may be the case. There are several that reported having to go back to an earlier driver to fix issues.
Which version? How do I do that?
She updated yesterday. But it was crashing before that too.
13th gen Intel ⌠good luck explaining that one
Tried to rollback but couldnât. The option to do so was greyed out and canât select it???
Not going to. They both have the same system setup.
That happens if the system clears the updates.
So.
What you will probably need to do is this:
-
Visit the DDU website:
-
https://www.guru3d.com/download/display-driver-uninstaller-download/ -
Please read the website and the instructions. You want to follow them for best results.
-
Download this version of the nvidia driver for your 4090: 561.09
-
https://www.nvidia.com/en-us/drivers/details/232538/ -
Once you have downloaded both items, then follow the directions on the DDU site.
-
You will need to disconnect the internet (this is to prevent Windows from trying to download updates for the GPU before you get a chance to install the driver manually)
-
They recommend doing this from safe mode, but it can work in normal mode, as long as the user has full admin rights. If it fails, you can try again with that mode, just follow the process exactly.
-
After the current driver is removed and you have restarted the PC, you can then install the driver you downloaded above. During the install, be sure NOT to install GeForce Experience or any updaters. This is not required for the base driver function. All other features and settings will be fine.
-
Once the driver is installed and you have restarted the system again, then reconnect to the internet.
-
At this point you should be free to try again. However I will also recommend you delete the LocalPrefs.txt file in Documents\Diablo IV\ as a precaution. Make sure to exit Battlenet prior to doing this and before you launch the game the first time after the above.
Let me know if this solves the issue or not.
Ok will try doing it sometime tomorrow. Thanks for the help
Actually the person who built our computers will be here Saturday. Will probably wait and have him decide the best way to proceed.
Thatâs fine. Feel free to let them read over the suggestion if it will help them.
Since you have the builder coming by, you may want to ask about this:
What Nitro was referring to here, was a problem that had come about with 13th and 14th gen Intel processors.
Essentially they had a coding issue where they were incorrectly requesting power from the motherboard and were allowed to do so.
This had the effect of potentially causing permanent damage to the CPU. This affects processors more if they are a higher power model. As you are running on the most powerful type, i9 CPU, this puts your processor squarely in the crosshairs of potential failures, if prevention hasnât been taken.
What needs to be done:
The motherboard BIOS must be updated. Included with those updates are fixes to prevent damage. However if damage has already occurred, it canât be fixed after the fact. In those cases, the processor would need to be replaced, hopefully under Intel warranty.
Here is a write up on the issue as it stands now:
https://www.theverge.com/24216305/intel-13th-14th-gen-raptor-lake-cpu-crash-news-updates-patches-fixes-motherboards
Video from Jay on how to check for the issue:
-https://www.youtube.com/watch?v=P7Eyv5d2Rq8
This is not a joke, this is a real issue. Let your builder know about it as well, they can take action to help the issue and prevent a failure if one hasnât occurred yet.
Good luck.
1 Like
Actually my wife has not crashed today. I reset her Nvidia settings to default which changed some settings after she had done the latest update a couple of days ago. So fingers crossed that all is well. I will have my computer guy take a look at your message about intel processor to see what he has to say.
1 Like
Ok not good news for you to here. My computer guy says this is a load of crap. Should not have to do these things to make game playable. If my processor was âbrokenâ I would be having more issues other than just with this game. The issue is with Blizzard. What it sounds like to us is that Blizzard made a new game and it is incompatible with high end top of the line equipment. It could be a RAM issue too. Just saw a recent post from someone who saw something from Rax. The game keeps sucking up all the memory until it crashes. This is also why I may crash less now because I do not keep a browser open anymore. I donât know who works for Blizzard but they seem like apprentices and not experts in their field. There is no reason for all these constant crashes and having to tweak equipment to make the game work. All other games and computer functions are fine except for D4. Blizzard needs to get some competent people to get the game to work for everyone. Didnât play a lot of D3 on computer but never had these issues. My computer guy did full diagnostics on whole computer and everything is running perfectly.
Just saw a video from Rhykker. First time I have seen a content creator talk about problems with crashing too. A lot of his community said the same thing and talked about rolling back to previous versions of Nvidia as a potential fix. This is a Blizzard ISSUE!!! My guess most of these pertain to the RTX 4090. They have been having issues with Nvidia since at least season 4. Blizzard needs to figure out how to make the game work with Nvidia without crashing all the time.
No offense to your âguyâ but they donât seem to be very open minded.
The information about the CPU is very important. If he is refusing to believe there could be a problem, even if there isnât one right now, and doesnât take steps to prevent an issue by updating the BIOS and doing those steps to protect your builds, you need a different tech.
The info on 13th and 14th gen CPUs is a real thing. A tech burying their head in the sand and not taking steps to protect their customer builds is laughably bad.
I know when I built a couple with those gens, I took a lot of steps to ensure there wouldnât be issues, and did follow up checks.
As for the virtual memory adjustments, they do help. And I agree, we should not be needing to go through those lengths.
The video driver thing is a constant pain, and the blame is really on both. I just go back a version or 3 and move on. You do NOT have to be on the latest version at all times.
But as I read your response, you went from being somewhat reasonable to explain things to, to kinda busting my chops here.
So hope you fix your problems, take your guys word, thatâs fine. Wait for Blizzard to fix it. IF they will fix it.
In the meantime, I will go on and play the game just fine as usual.
Good luck.
aside from the rest of the good information youâve tried to provide the above quote is the best part of this.
No I appreciate your input. I have no knowledge of the CPU thing. I can only take the word of people who know a hell of a lot more about than me. My main point is that the only game that mine or my wifeâs computer has is with D4. No other game whatsoever. Why is this? So I canât help but feel that once again I have to put the blame squarely on Blizzard, especially with the graphic card and video driver issue. And today⌠a new patch and another round of crashes being reported all over the place. Canât help but think Blizzard is incompetent. These issues that keep cropping up sure seem to confirm it. I personally didnât play yet today because of said crash problems. I have been waiting to see if something has been done to remedy the issue. Thanks for your help and please continue to keep me âinlineâ and informed.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.