Elden Ring Crashes PC

[IlMika]

I've bought Elden Ring at release, played since release with the usual known problems (stuttering, small hiccups, etc.). I didn't crash once, not even CTD. It was pretty OK and progressed far.

Fast forward to last week, about 75 hours in. I reach Mountaintop of the Giants and face my first crash: Screen goes black, display turns off, fan (I think CPU) fan starts spinning extremely fast. If I have a YouTube video running in background, sound still continues. I have to hard reboot my PC to recover. I cannot reproduce the crash, it's random. Sometimes I can play an hour, sometimes 5 minutes, before the same crash occurs.

Build information: https://pcpartpicker.com/list/zNnWp2
Note: 16 GB of RAM @ 3200 MHz, default timings
Playing on a mix of Medium/High settings, but it doesn't change anything...

No issues anywhere else or any other game...

Checked event viewer, the dreaded 0xc0000005 error is present. Same in Control Panel\System and Security\Security and Maintenance\Problem Details

Tried:
- Updating Windows
- Updating GPU drivers
- Verifying game in Steam
- Reinstalling game in steam
- Clearing local shaders in Nvidia folder
- Disabling XMP and manually setting RAM speed to 3200 Mhz (2022-04-03)
- Switching places of RAM sticks (2022-04-04)
- Reinstalling Nvidia drivers after DDU (2022-04-05)
- Disable EAC and play offline. (in progress)
- Update BIOS (v F36) (2022-04-06)
EDIT:
- Updated chipset to v3.10.22.706 (2022-04-07)
Updated following through Windows Update (2022-04-07):
- Advanced Micro Devices Inc. - SecurityDevices - 4.15.0.0
- AMD - System - 20.50.0.0
- Advanced Micro Devices Inc. - System - 5.12.0.38
- Advanced Micro Devices Inc. - System - 2.2.0.130


- Update Windows version (Not necessary for now)

I appreciate any help.

Error excerpt 1:

Source
ELDEN RING™

Summary
Stopped working

Date
‎02/‎04/‎2022 14:46

Status
Report sent

Description
Faulting Application Path:	H:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe

Problem signature
Problem Event Name:	APPCRASH
Application Name:	eldenring.exe
Application Version:	1.3.2.0
Application Timestamp:	62358cd3
Fault Module Name:	eldenring.exe
Fault Module Version:	1.3.2.0
Fault Module Timestamp:	62358cd3
Exception Code:	c0000005
Exception Offset:	0000000001ded3a0
OS Version:	10.0.19043.2.0.0.256.48
Locale ID:	3072
Additional Information 1:	c9d8
Additional Information 2:	c9d80bbd6162e9788836710e6ae7e0c2
Additional Information 3:	13fc
Additional Information 4:	13fc46ac96ea449f8fda2819867f5b97

Extra information about the problem
Bucket ID:	7f851eb9fd1e97f187dd568e8d56b0c3 (1719625802982011075)

Error excerpt 2:

Source
ELDEN RING™

Summary
Stopped working

Date
‎03/‎04/‎2022 12:29

Status
Report sent

Description
Faulting Application Path:	H:\SteamLibrary\steamapps\common\ELDEN RING\Game\eldenring.exe

Problem signature
Problem Event Name:	APPCRASH
Application Name:	eldenring.exe
Application Version:	1.3.2.0
Application Timestamp:	62358cd3
Fault Module Name:	eldenring.exe
Fault Module Version:	1.3.2.0
Fault Module Timestamp:	62358cd3
Exception Code:	c0000005
Exception Offset:	0000000001dda322
OS Version:	10.0.19043.2.0.0.256.48
Locale ID:	3072
Additional Information 1:	7bd5
Additional Information 2:	7bd5de1edb388a625d5032900effd57b
Additional Information 3:	e80e
Additional Information 4:	e80ecbef6d379075f1a24204b1a72cce

Extra information about the problem
Bucket ID:	cdc5ca8157d4e18167fe0aa825e96e7f (1728831024263687807)

[dark-breed]

Αναρτήθηκε αρχικά από Komarimaru:

Αναρτήθηκε αρχικά από IlMika:

Nope, no luck.

Started playing at 17:02, teleported to Limgrave at aroud 17:15, crashed 17:19.

Could very well be faulty hardware, but to be sure, try re-seating your memory modules. If that doesn't work, try changing the slots they are in.

Also, I forgot to have you check your fclk settings. Not sure if you have it on auto or set to the speed of your memory.

Αναρτήθηκε αρχικά από dark-breed:

i'm a technician i fix pc's, Laptops and GPU's in my store and i always see completely wornout stuff by wrong configurations and i hear every time this one sentence:

"yesterday it was working"

without a professional analysis of the modules (what is not possible in a PC, you need special hardware to do this) you have no chance to reveal a defect RAM capacitor but changing the timings you used for hours and days sometimes weeks will fix it for some days, weeks, months and than it is game over.

listen it has worked for at least many days and now suddenly it will not work with the settings he has chosen indicates a defect more likely than a not revealed misconfiguration. (apart from the fact that there are only a few RAM modules that have temperature monitoring).

A technician troubleshoots, not make forwards claim of certainty. I know, since it's part of my job as well.

You're not helping, at all. You're spamming and trying to start an argument. If you worked for me, you'd be suspended if not removed from your position due to lack of protocol.

There's nothing wrong with troubleshooting and helping someone first, before declaring the end of the world, since that error, when AMD is involved, can be due to so many reasons like Fclk settings etc.

I would never work for someone it is my shop, dude.

as you have seen it does not work your advice and now he is back to the normal errorhunting procedure.

lack of protocol ? na you doing stuff that is against the normal protocol of troubleshooting and if you would work for me i would not suspend you i would fire you and call the organisation that had given you the certification.

[Komarimaru]

Αναρτήθηκε αρχικά από dark-breed:

Αναρτήθηκε αρχικά από Komarimaru:

Could very well be faulty hardware, but to be sure, try re-seating your memory modules. If that doesn't work, try changing the slots they are in.

Also, I forgot to have you check your fclk settings. Not sure if you have it on auto or set to the speed of your memory.



A technician troubleshoots, not make forwards claim of certainty. I know, since it's part of my job as well.

You're not helping, at all. You're spamming and trying to start an argument. If you worked for me, you'd be suspended if not removed from your position due to lack of protocol.

There's nothing wrong with troubleshooting and helping someone first, before declaring the end of the world, since that error, when AMD is involved, can be due to so many reasons like Fclk settings etc.

I would never work for someone it is my shop, dude.

as you have seen it does not work your advice and now he is back to the normal errorhunting procedure.

Because that's how you're supposed to do it. And his exception code also triggers towards the GPU data transfer from memory, not CPU. The fact you insulated that shows me you are lacking in this expertise and simply want to argue and not help.

Speaking which which, IlMika. Since the exception code is in relation to data transfer of shared memory between GPU and CPU, have you tried a fresh driver installation by the DDU method of clean removal first? For stable known drivers, Nvidia has been 511.79. AMD GPU's have been dependent on which AMD GPU you have.

[dark-breed]

Αναρτήθηκε αρχικά από Komarimaru:

Αναρτήθηκε αρχικά από dark-breed:

I would never work for someone it is my shop, dude.

as you have seen it does not work your advice and now he is back to the normal errorhunting procedure.

Because that's how you're supposed to do it. And his exception code also triggers towards the GPU data transfer from memory, not CPU. The fact you insulated that shows me you are lacking in this expertise and simply want to argue and not help.

Speaking which which, IlMika. Since the exception code is in relation to data transfer of shared memory between GPU and CPU, have you tried a fresh driver installation by the DDU method of clean removal first?

this is totally pointless and false too so i think you have never a diploma in computer science and not a MCSE certification at all.

[IlMika]

Αναρτήθηκε αρχικά από Komarimaru:

Αναρτήθηκε αρχικά από dark-breed:

I would never work for someone it is my shop, dude.

as you have seen it does not work your advice and now he is back to the normal errorhunting procedure.

Because that's how you're supposed to do it. And his exception code also triggers towards the GPU data transfer from memory, not CPU. The fact you insulated that shows me you are lacking in this expertise and simply want to argue and not help.

Speaking which which, IlMika. Since the exception code is in relation to data transfer of shared memory between GPU and CPU, have you tried a fresh driver installation by the DDU method of clean removal first? For stable known drivers, Nvidia has been 511.79. AMD GPU's have been dependent on which AMD GPU you have.

I haven't, that process is foreign to me.
I will try swapping memory slots. If the crash still occurs and the memory address is different but consistent with the new value, I'll try the driver installation.

[IlMika]

Αναρτήθηκε αρχικά από dark-breed:

Αναρτήθηκε αρχικά από Komarimaru:

Because that's how you're supposed to do it. And his exception code also triggers towards the GPU data transfer from memory, not CPU. The fact you insulated that shows me you are lacking in this expertise and simply want to argue and not help.

Speaking which which, IlMika. Since the exception code is in relation to data transfer of shared memory between GPU and CPU, have you tried a fresh driver installation by the DDU method of clean removal first?

this is totally pointless and false too so i think you have never a diploma in computer science and not a MCSE certification at all.

I appreciate you trying to help, but can we please focus on fixing this issue instead of quarreling in this thread? You're more than welcome to hash it out elsewhere, but I'd rather open my Steam notifications to fix suggestions than an off-topic discussion.

Thanks.

[Komarimaru]

Αναρτήθηκε αρχικά από dark-breed:

Αναρτήθηκε αρχικά από Komarimaru:

Because that's how you're supposed to do it. And his exception code also triggers towards the GPU data transfer from memory, not CPU. The fact you insulated that shows me you are lacking in this expertise and simply want to argue and not help.

Speaking which which, IlMika. Since the exception code is in relation to data transfer of shared memory between GPU and CPU, have you tried a fresh driver installation by the DDU method of clean removal first?

this is totally pointless and false too so i think you have never a diploma in computer science and not a MCSE certification at all.

My degrees are none of your concern, and the fact you think there's only one MSCE is disturbing and tells something about your fallacies.

Αναρτήθηκε αρχικά από IlMika:

Αναρτήθηκε αρχικά από Komarimaru:

Because that's how you're supposed to do it. And his exception code also triggers towards the GPU data transfer from memory, not CPU. The fact you insulated that shows me you are lacking in this expertise and simply want to argue and not help.

Speaking which which, IlMika. Since the exception code is in relation to data transfer of shared memory between GPU and CPU, have you tried a fresh driver installation by the DDU method of clean removal first? For stable known drivers, Nvidia has been 511.79. AMD GPU's have been dependent on which AMD GPU you have.

I haven't, that process is foreign to me.
I will try swapping memory slots. If the crash still occurs and the memory address is different but consistent with the new value, I'll try the driver installation.

DDU is Display Driver Uninstaller. It helps remove all remains of your previous driver after basic removal.
https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Just be sure and download the drivers for your GPU to be ready to install them again before hand, saves some time in the process. Reasons to use DDU is sometimes there's errors in left over files or current ones and registry entries, DDU just gives you a clean slate, helps in trouble shooting problems.

[IlMika]

Αναρτήθηκε αρχικά από Komarimaru:

Αναρτήθηκε αρχικά από dark-breed:

this is totally pointless and false too so i think you have never a diploma in computer science and not a MCSE certification at all.

My degrees are none of your concern, and the fact you think there's only one MSCE is disturbing and tells something about your fallacies.

Αναρτήθηκε αρχικά από IlMika:

I haven't, that process is foreign to me.
I will try swapping memory slots. If the crash still occurs and the memory address is different but consistent with the new value, I'll try the driver installation.

DDU is Display Driver Uninstaller. It helps remove all remains of your previous driver after basic removal.
https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Just be sure and download the drivers for your GPU to be ready to install them again before hand, saves some time in the process. Reasons to use DDU is sometimes there's errors in left over files or current ones and registry entries, DDU just gives you a clean slate, helps in trouble shooting problems.

OK, will give it a try.

Right now, I switched the RAM sticks (and grabbed the opportunity to clean out my PC physically) and will test the game again.

[IlMika]

Αναρτήθηκε αρχικά από IlMika:

Αναρτήθηκε αρχικά από Komarimaru:

My degrees are none of your concern, and the fact you think there's only one MSCE is disturbing and tells something about your fallacies.




DDU is Display Driver Uninstaller. It helps remove all remains of your previous driver after basic removal.
https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Just be sure and download the drivers for your GPU to be ready to install them again before hand, saves some time in the process. Reasons to use DDU is sometimes there's errors in left over files or current ones and registry entries, DDU just gives you a clean slate, helps in trouble shooting problems.

OK, will give it a try.

Right now, I switched the RAM sticks (and grabbed the opportunity to clean out my PC physically) and will test the game again.

Looks promising so far. Had a 2 hour uninterrupted session, will continue tomorrow for longer if I have the time.

Thanks a lot!

[dark-breed]

Αναρτήθηκε αρχικά από IlMika:

Αναρτήθηκε αρχικά από IlMika:

OK, will give it a try.

Right now, I switched the RAM sticks (and grabbed the opportunity to clean out my PC physically) and will test the game again.

Looks promising so far. Had a 2 hour uninterrupted session, will continue tomorrow for longer if I have the time.

Thanks a lot!

i be shure you will have problems in the future because you swapped the modules and it solved your problem what is a indication of a damaged module or overheating problem at the first slot (maybe because you cleaned the rig it will take a while till next error).

[IlMika]

Αναρτήθηκε αρχικά από dark-breed:

Αναρτήθηκε αρχικά από IlMika:

Looks promising so far. Had a 2 hour uninterrupted session, will continue tomorrow for longer if I have the time.

Thanks a lot!

i be shure you will have problems in the future because you swapped the modules and it solved your problem what is a indication of a damaged module or overheating problem at the first slot (maybe because you cleaned the rig it will take a while till next error).

Could be, but to be fair, I am not the only one facing this issue. People with new RAM, new rigs and fresh installs are also getting it...

It's just odd that 75 hours in, no issues, but then suddenly it's breaking the game.

[dark-breed]

Αναρτήθηκε αρχικά από IlMika:

Αναρτήθηκε αρχικά από dark-breed:

i be shure you will have problems in the future because you swapped the modules and it solved your problem what is a indication of a damaged module or overheating problem at the first slot (maybe because you cleaned the rig it will take a while till next error).

Could be, but to be fair, I am not the only one facing this issue. People with new RAM, new rigs and fresh installs are also getting it...

It's just odd that 75 hours in, no issues, but then suddenly it's breaking the game.

this game utilizes your hardware in a way nothing else can do it even a burn benchmark is not able to get this amount of stress.

after version 1.03.1 i got a overheating problem at my RAM during the game that a even a burn benchmark does not can do. i had to coll it down with a additional fan.

[Komarimaru]

Αναρτήθηκε αρχικά από dark-breed:

Αναρτήθηκε αρχικά από IlMika:

Could be, but to be fair, I am not the only one facing this issue. People with new RAM, new rigs and fresh installs are also getting it...

It's just odd that 75 hours in, no issues, but then suddenly it's breaking the game.

this game utilizes your hardware in a way nothing else can do it even a burn benchmark is not able to get this amount of stress.

after version 1.03.1 i got a overheating problem at my RAM during the game that a even a burn benchmark does not can do. i had to coll it down with a additional fan.

Please stop spreading misinformation. Any problems you had were due to using still on DDR3 and AMD FX series CPU which is not supported by the game. It won't randomly overheat hardware in such a way you describe and even if it did, DDR3 memory can withstand a lot of temperature before instability.

Also, claiming damaged modules even after they did some changes is again fear mongering and spreading misinformation. You nor I know what steps they took to fix their problem, and since it's obvious due to your current hardware and lack of actual expertise in the field, you don't have any real experience. Thus I would like to request you no longer "Help Others" since your posts are half baked and untrue thus far in these forums.

[dark-breed]

Αναρτήθηκε αρχικά από Komarimaru:

Αναρτήθηκε αρχικά από dark-breed:

this game utilizes your hardware in a way nothing else can do it even a burn benchmark is not able to get this amount of stress.

after version 1.03.1 i got a overheating problem at my RAM during the game that a even a burn benchmark does not can do. i had to coll it down with a additional fan.

Please stop spreading misinformation. Any problems you had were due to using still on DDR3 and AMD FX series CPU which is not supported by the game. It won't randomly overheat hardware in such a way you describe and even if it did, DDR3 memory can withstand a lot of temperature before instability.

Also, claiming damaged modules even after they did some changes is again fear mongering and spreading misinformation. You nor I know what steps they took to fix their problem, and since it's obvious due to your current hardware and lack of actual expertise in the field, you don't have any real experience. Thus I would like to request you no longer "Help Others" since your posts are half baked and untrue thus far in these forums.

and now you show that you never be a technician he has only swaped the modules and has not done your DDU stuff.

https://steamcommunity.com/app/1245620/discussions/0/3278065083964867982/?tscn=1649007330
https://steamcommunity.com/app/1245620/discussions/0/3278065083967156386/?tscn=1648994383
https://steamcommunity.com/app/1245620/discussions/0/3278065083965123235/?tscn=1648884638
https://steamcommunity.com/app/1245620/discussions/0/3278065083964359039/?tscn=1648843341
https://steamcommunity.com/app/1245620/discussions/0/3183488224891817488/?tscn=1648838879
https://steamcommunity.com/app/1245620/discussions/0/3278065083960090124/?tscn=1648741269
https://steamcommunity.com/app/1245620/discussions/0/3278065083958936744/?tscn=1648720319
https://steamcommunity.com/app/1245620/discussions/0/3177859849529299197/?tscn=1648534861
https://steamcommunity.com/app/1245620/discussions/0/3177859358963213953/?tscn=1648284962
https://steamcommunity.com/app/1245620/discussions/0/3177859358958591290/?tscn=1648227882
https://steamcommunity.com/app/1245620/discussions/0/3177859358955190899/?tscn=1648245450

if this is not enough evidence that you have no clue about this stuff this is only the last week where i solved the problem at others rig.

You also have no clue why this game is running at linux at my "outdated" hardware with 55-60 fps or why it runs with special k with more than 60 fps at my rig.

the fail temp at my RAM is 91 celsius

[Komarimaru]

Αναρτήθηκε αρχικά από dark-breed:

Αναρτήθηκε αρχικά από Komarimaru:

Please stop spreading misinformation. Any problems you had were due to using still on DDR3 and AMD FX series CPU which is not supported by the game. It won't randomly overheat hardware in such a way you describe and even if it did, DDR3 memory can withstand a lot of temperature before instability.

Also, claiming damaged modules even after they did some changes is again fear mongering and spreading misinformation. You nor I know what steps they took to fix their problem, and since it's obvious due to your current hardware and lack of actual expertise in the field, you don't have any real experience. Thus I would like to request you no longer "Help Others" since your posts are half baked and untrue thus far in these forums.

and now you show that you never be a technician he has only swaped the modules and has not done your DDU stuff.

https://steamcommunity.com/app/1245620/discussions/0/3278065083964867982/?tscn=1649007330
https://steamcommunity.com/app/1245620/discussions/0/3278065083967156386/?tscn=1648994383
https://steamcommunity.com/app/1245620/discussions/0/3278065083965123235/?tscn=1648884638
https://steamcommunity.com/app/1245620/discussions/0/3278065083964359039/?tscn=1648843341
https://steamcommunity.com/app/1245620/discussions/0/3183488224891817488/?tscn=1648838879
https://steamcommunity.com/app/1245620/discussions/0/3278065083960090124/?tscn=1648741269
https://steamcommunity.com/app/1245620/discussions/0/3278065083958936744/?tscn=1648720319
https://steamcommunity.com/app/1245620/discussions/0/3177859849529299197/?tscn=1648534861
https://steamcommunity.com/app/1245620/discussions/0/3177859358963213953/?tscn=1648284962
https://steamcommunity.com/app/1245620/discussions/0/3177859358958591290/?tscn=1648227882
https://steamcommunity.com/app/1245620/discussions/0/3177859358955190899/?tscn=1648245450

if this is not enough evidence that you have no clue about this stuff this is only the last week whare i solved the problem at others rig.

You also have no clue why this game is running at linux at my "outdated" hardware with 55-60 fps or why it runs with special k with more than 60 fps at my rig.

Again, you're proving my point. Don't "Help Others" and flagging you for spreading misinformation.

[dark-breed]

Αναρτήθηκε αρχικά από Komarimaru:

Αναρτήθηκε αρχικά από dark-breed:

and now you show that you never be a technician he has only swaped the modules and has not done your DDU stuff.

https://steamcommunity.com/app/1245620/discussions/0/3278065083964867982/?tscn=1649007330
https://steamcommunity.com/app/1245620/discussions/0/3278065083967156386/?tscn=1648994383
https://steamcommunity.com/app/1245620/discussions/0/3278065083965123235/?tscn=1648884638
https://steamcommunity.com/app/1245620/discussions/0/3278065083964359039/?tscn=1648843341
https://steamcommunity.com/app/1245620/discussions/0/3183488224891817488/?tscn=1648838879
https://steamcommunity.com/app/1245620/discussions/0/3278065083960090124/?tscn=1648741269
https://steamcommunity.com/app/1245620/discussions/0/3278065083958936744/?tscn=1648720319
https://steamcommunity.com/app/1245620/discussions/0/3177859849529299197/?tscn=1648534861
https://steamcommunity.com/app/1245620/discussions/0/3177859358963213953/?tscn=1648284962
https://steamcommunity.com/app/1245620/discussions/0/3177859358958591290/?tscn=1648227882
https://steamcommunity.com/app/1245620/discussions/0/3177859358955190899/?tscn=1648245450

if this is not enough evidence that you have no clue about this stuff this is only the last week whare i solved the problem at others rig.

You also have no clue why this game is running at linux at my "outdated" hardware with 55-60 fps or why it runs with special k with more than 60 fps at my rig.

Again, you're proving my point. Don't "Help Others" and flagging you for spreading misinformation.

you are a person claiming to be a professional technician, you are just a spammer with no clue about hardware and windows insulting me.
you have never a diploma in this field or a MSCE certificate, i have both.

YOU ARE A LIAR