Store Page
ELDEN RING
All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

ELDEN RING

Store Page
View Stats:
Global Achievements
ELDEN RING > General Discussions > Topic Details
IlMika Apr 3, 2022 @ 6:56am
Elden Ring Crashes PC
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)
Last edited by IlMika; Apr 9, 2022 @ 2:54am
< >
Showing 1-15 of 215 comments
Komarimaru Apr 3, 2022 @ 7:09am 
Looks like a memory issue, which begs the question...

You're on a 3000 series AMD CPU. What memory speed are you running, and are you using DOAC in your Bios for said memory. (Some AMD Bios show XMP still)
#1
IlMika Apr 3, 2022 @ 7:19am 
Originally posted by Komarimaru:
Looks like a memory issue, which begs the question...

You're on a 3000 series AMD CPU. What memory speed are you running, and are you using DOAC in your Bios for said memory. (Some AMD Bios show XMP still)
Thanks for responding.

I'm on 3200 Mhz with XMP activated in BIOS.
#2
Komarimaru Apr 3, 2022 @ 7:22am 
Originally posted by IlMika:
Originally posted by Komarimaru:
Looks like a memory issue, which begs the question...

You're on a 3000 series AMD CPU. What memory speed are you running, and are you using DOAC in your Bios for said memory. (Some AMD Bios show XMP still)
Thanks for responding.

I'm on 3200 Mhz with XMP activated in BIOS.
ok. XMP profiles, while most times are stable, can be unstable since they also change the memories timings. No two sticks of memory are alike, even paired sets. So there's a few options.

One, manually set your Memory Speed to 3200Mhz in Bios with XMP/DAOC Disabled.
Two, check your memories default timings and see if an XMP profile in bios is close to them.
#3
dark-breed Apr 3, 2022 @ 7:25am 
Originally posted by 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
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

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)


c0000005 is a RAM error during overheating or fatal damage to it.

the offset is around the same offset so it seams your first RAM module is defect or in the worst case your CPU RAM controller is defect.

it can be caused alo to some wrong configurations to your ram but according to your writing that it was running a while without problems i would point to a defect.
Last edited by dark-breed; Apr 3, 2022 @ 7:32am
#4
IlMika Apr 3, 2022 @ 7:30am 
Originally posted by Komarimaru:
Originally posted by IlMika:
Thanks for responding.

I'm on 3200 Mhz with XMP activated in BIOS.
ok. XMP profiles, while most times are stable, can be unstable since they also change the memories timings. No two sticks of memory are alike, even paired sets. So there's a few options.

One, manually set your Memory Speed to 3200Mhz in Bios with XMP/DAOC Disabled.
Two, check your memories default timings and see if an XMP profile in bios is close to them.
I will give option one a try.
Simply setting the speed to 3200 Mhz is enough, no need to fiddle around with the timings?
#5
Komarimaru Apr 3, 2022 @ 7:38am 
Originally posted by IlMika:
Originally posted by Komarimaru:
ok. XMP profiles, while most times are stable, can be unstable since they also change the memories timings. No two sticks of memory are alike, even paired sets. So there's a few options.

One, manually set your Memory Speed to 3200Mhz in Bios with XMP/DAOC Disabled.
Two, check your memories default timings and see if an XMP profile in bios is close to them.
I will give option one a try.
Simply setting the speed to 3200 Mhz is enough, no need to fiddle around with the timings?
No need to fiddle with timings, most Bios are smart enough to auto detect them. If not, can just add them manually since your memory should list their rated speeds.

If by some off chance ya get a defunkt kit, e.i. One stick is separate timings then the other(hardly ever happens, seen it once in like 20 years), use the largest number of the two to fill in ya timings section.
#6
dark-breed Apr 3, 2022 @ 7:39am 
Originally posted by Komarimaru:
Originally posted by IlMika:
Thanks for responding.

I'm on 3200 Mhz with XMP activated in BIOS.
ok. XMP profiles, while most times are stable, can be unstable since they also change the memories timings. No two sticks of memory are alike, even paired sets. So there's a few options.

One, manually set your Memory Speed to 3200Mhz in Bios with XMP/DAOC Disabled.
Two, check your memories default timings and see if an XMP profile in bios is close to them.
the problem is it appeared after 75 hours so it is with a high chance a defect the offset is around the same segment so i would think it is the first Moduleslot with this offset where the error occured.
#7
Komarimaru Apr 3, 2022 @ 7:54am 
Originally posted by dark-breed:
Originally posted by Komarimaru:
ok. XMP profiles, while most times are stable, can be unstable since they also change the memories timings. No two sticks of memory are alike, even paired sets. So there's a few options.

One, manually set your Memory Speed to 3200Mhz in Bios with XMP/DAOC Disabled.
Two, check your memories default timings and see if an XMP profile in bios is close to them.
the problem is it appeared after 75 hours so it is with a high chance a defect the offset is around the same segment so i would think it is the first Moduleslot with this offset where the error occured.
I am well aware of the implications, but offset errors occur in majority due to strain on the memory and unable to function at the timings it was set at, thus loosening the timings or setting to default fixes the issue in 90% of cases. Implying the memory is bad as your first theory, is a poor one.
#8
IlMika Apr 3, 2022 @ 7:58am 
OK, disabled XMP profile, manually set speed to 3200 Mhz, left the timings at the default values.

I'll try Elden Ring and see if I still face the issue.
#9
dark-breed Apr 3, 2022 @ 7:58am 
Originally posted by Komarimaru:
Originally posted by dark-breed:
the problem is it appeared after 75 hours so it is with a high chance a defect the offset is around the same segment so i would think it is the first Moduleslot with this offset where the error occured.
I am well aware of the implications, but offset errors occur in majority due to strain on the memory and unable to function at the timings it was set at, thus loosening the timings or setting to default fixes the issue in 90% of cases. Implying the memory is bad as your first theory, is a poor one.
it worked for 75 hours. if the timing gone out of range it is indeed a defect caused. you can try to change the timings to compensate a defect but in the future he will get additional problems.
#10
Komarimaru Apr 3, 2022 @ 8:03am 
Originally posted by dark-breed:
Originally posted by Komarimaru:
I am well aware of the implications, but offset errors occur in majority due to strain on the memory and unable to function at the timings it was set at, thus loosening the timings or setting to default fixes the issue in 90% of cases. Implying the memory is bad as your first theory, is a poor one.
it worked for 75 hours. if the timing gone out of range it is indeed a defect caused. you can try to change the timings to compensate a defect but in the future he will get additional problems.
And like many in these forums, they get the error when entering the exact zone as the OP has. There's a problem in the zone that strains hardware, you can look at the forums history for crashing in this particular area. It doesn't hurt for them to simply test and set the memory to default timings and speed to test and takes no time.

Again, claiming hardware suddenly going bad, is never the right option. Re-seating the memory, yes. Trying it in different slots, yes. Claiming it's bad? Never.
#11
dark-breed Apr 3, 2022 @ 8:10am 
Originally posted by Komarimaru:
Originally posted by dark-breed:
it worked for 75 hours. if the timing gone out of range it is indeed a defect caused. you can try to change the timings to compensate a defect but in the future he will get additional problems.
And like many in these forums, they get the error when entering the exact zone as the OP has. There's a problem in the zone that strains hardware, you can look at the forums history for crashing in this particular area. It doesn't hurt for them to simply test and set the memory to default timings and speed to test and takes no time.

Again, claiming hardware suddenly going bad, is never the right option. Re-seating the memory, yes. Trying it in different slots, yes. Claiming it's bad? Never.

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).
#12
IlMika Apr 3, 2022 @ 8:22am 
Originally posted by IlMika:
OK, disabled XMP profile, manually set speed to 3200 Mhz, left the timings at the default values.

I'll try Elden Ring and see if I still face the issue.
Nope, no luck.

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

Error report from Problem Details:
Source ELDEN RING™ Summary Stopped working Date ‎03/‎04/‎2022 17:19 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: 2057 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)

Followed by "Hardware error":
Source Windows Summary Hardware error Date ‎03/‎04/‎2022 17:20 Status Not reported Description A problem with your hardware caused Windows to stop working correctly. Problem signature Problem Event Name: LiveKernelEvent Code: 141 Parameter 1: ffffcc8604fa4460 Parameter 2: fffff8021badde38 Parameter 3: 0 Parameter 4: 2180 OS version: 10_0_19043 Service Pack: 0_0 Product: 256_1 OS Version: 10.0.19043.2.0.0.256.48 Locale ID: 3072
Last edited by IlMika; Apr 3, 2022 @ 8:26am
#13
Komarimaru Apr 3, 2022 @ 8:27am 
Originally posted by IlMika:
Originally posted by IlMika:
OK, disabled XMP profile, manually set speed to 3200 Mhz, left the timings at the default values.

I'll try Elden Ring and see if I still face the issue.
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.


Originally posted by dark-breed:
Originally posted by Komarimaru:
And like many in these forums, they get the error when entering the exact zone as the OP has. There's a problem in the zone that strains hardware, you can look at the forums history for crashing in this particular area. It doesn't hurt for them to simply test and set the memory to default timings and speed to test and takes no time.

Again, claiming hardware suddenly going bad, is never the right option. Re-seating the memory, yes. Trying it in different slots, yes. Claiming it's bad? Never.

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.
#14
dark-breed Apr 3, 2022 @ 8:28am 
Originally posted by IlMika:
Originally posted by IlMika:
OK, disabled XMP profile, manually set speed to 3200 Mhz, left the timings at the default values.

I'll try Elden Ring and see if I still face the issue.
Nope, no luck.

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

@Komarimaru

what i told you ?

you can try to remove your first RAM module if you have enough RAM to test if the problem accoure at a different offset you have a damaged CPU.
#15
< >
Showing 1-15 of 215 comments
Per page: 1530 50

ELDEN RING > General Discussions > Topic Details
Date Posted: Apr 3, 2022 @ 6:56am
Posts: 215

Discussions Rules and Guidelines