ER Crashfest

[nav1205]

I have about 150 hours on Elden RIng and I have experienced crashes throughout my whole time playing. When fighting Litchdragon Fortisaxx my GPU had 12 strokes and I had to fully DDU my drivers, that is a known issue with my GPU, so I let that slide. However my game also crashes to desktop randomly wherever I might be in game.
SPECS:
R3 3100
RX 580
16GB 3200MHZ CORASIR
550W Corsair PSU
B450 Motherboard Gigabyte
So far I have:
Re-installed Windows/Elden Ring fully
DDU GPU drivers
Memtest
ATM I think it might be something to do with my CPU memory controller, this is because about 6 months ago I used to face horrendous blue screening and I "fixed" it by upping my CPU's voltage ever so slightly in BIOS, and since then I have not had any BSOD's, but I have these ER crashes instead.


Problem Event Name: APPCRASH
Application Name: eldenring.exe
Application Version: 2.0.0.0
Application Timestamp: 648ff746
Fault Module Name: eldenring.exe
Fault Module Version: 2.0.0.0
Fault Module Timestamp: 648ff746
Exception Code: c0000005
Exception Offset: 0000000001a458a6
OS Version: 10.0.19045.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 931a
Additional Information 2: 931a8ee3a068475e8ca409d71dc90db3
Additional Information 3: 2793
Additional Information 4: 27932c786d45746d809802df0adebfb8

Problem Event Name: BEX64
Application Name: eldenring.exe
Application Version: 2.0.0.0
Application Timestamp: 648ff746
Fault Module Name: StackHash_8890
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_71_FROM_ntdll+0x000000000009DB64
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 10.0.19045.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 8890
Additional Information 2: 8890b5ec897b4f6f674681320c249aba
Additional Information 3: 6495
Additional Information 4: 6495698030de16371b172739ada83d55

Any help is appreciated, thanks to all.

[Sparhawk 59]

Many of us are getting same. Try verify game files restart steam verify again. If using windows 10 in search type CMD run as admin then in new box flashing icon type sfc /scannow

[nav1205]

I have now formed a little conspiracy. Can you or anyone else go to the "Underground Roadside" site of Grace, then go out the little door, and walk to the right where you will see an Omen, my game literally crashes doing that every-single-damm time.

[Lord Bob]

Originally posted by nav1205:

I have now formed a little conspiracy. Can you or anyone else go to the "Underground Roadside" site of Grace, then go out the little door, and walk to the right where you will see an Omen, my game literally crashes doing that every-single-damm time.

What sparhawk said.
If the crash is repeatable it is likely due to missing or corrputed files, verifying will solve the issue most likely.

[dark-breed]

Originally posted by nav1205:

I have about 150 hours on Elden RIng and I have experienced crashes throughout my whole time playing. When fighting Litchdragon Fortisaxx my GPU had 12 strokes and I had to fully DDU my drivers, that is a known issue with my GPU, so I let that slide. However my game also crashes to desktop randomly wherever I might be in game.
SPECS:
R3 3100
RX 580
16GB 3200MHZ CORASIR
550W Corsair PSU
B450 Motherboard Gigabyte
So far I have:
Re-installed Windows/Elden Ring fully
DDU GPU drivers
Memtest
ATM I think it might be something to do with my CPU memory controller, this is because about 6 months ago I used to face horrendous blue screening and I "fixed" it by upping my CPU's voltage ever so slightly in BIOS, and since then I have not had any BSOD's, but I have these ER crashes instead.


Problem Event Name: APPCRASH
Application Name: eldenring.exe
Application Version: 2.0.0.0
Application Timestamp: 648ff746
Fault Module Name: eldenring.exe
Fault Module Version: 2.0.0.0
Fault Module Timestamp: 648ff746
Exception Code: c0000005
Exception Offset: 0000000001a458a6
OS Version: 10.0.19045.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 931a
Additional Information 2: 931a8ee3a068475e8ca409d71dc90db3
Additional Information 3: 2793
Additional Information 4: 27932c786d45746d809802df0adebfb8

Problem Event Name: BEX64
Application Name: eldenring.exe
Application Version: 2.0.0.0
Application Timestamp: 648ff746
Fault Module Name: StackHash_8890
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_71_FROM_ntdll+0x000000000009DB64
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 10.0.19045.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 8890
Additional Information 2: 8890b5ec897b4f6f674681320c249aba
Additional Information 3: 6495
Additional Information 4: 6495698030de16371b172739ada83d55

Any help is appreciated, thanks to all.

the first one is a crash that could be realted to damaged gamefiles, the second one is critical it could point to a chipset failure, a dead CPU core, damaged RAM, instable RAM, PSU failure and a lot more things.

some questions:

bios is uptodate ?
RAM is in the compatible list of the mainboard ?
are there background apps in use ?
is process lasso in use ?

also are there other suspicious logs in event viewer not related to elden ring ?

[ToXiCEngel]

There are a few things you can do to help resolve BEX64 events: https://windowsreport.com/bex64-error/

I'd start there and also make sure your BIOS is up to date.

[nav1205]

Yes my BIOS is up to date. I have tried CMD sfc scans and stuff, my RAM is compatible and there is no background apps (like DIscord etc), I have no idea what project lasso is;

[Lord Bob]

Originally posted by nav1205:

Yes my BIOS is up to date. I have tried CMD sfc scans and stuff, my RAM is compatible and there is no background apps (like DIscord etc), I have no idea what project lasso is;

Have you tried the easiest fix yet, verifying your game files with steam?

[nav1205]

Yes nothing was detected

[nav1205]

I turned XMP off and I haven't full crashed since but I have a lot of stutters (I did also delete the shader cache so unsure if these stutters are due to the cache rebuilding or not)

[dark-breed]

Originally posted by nav1205:

I turned XMP off and I haven't full crashed since but I have a lot of stutters (I did also delete the shader cache so unsure if these stutters are due to the cache rebuilding or not)

stutters are mostly related to some sort of problems with a lot of things a deeper analysis is needed if your problems are related to the RAM modules or a problem in windows.

[nav1205]

I reinstalled windows 2 days ago so I do not think its that. I will try playing tomorrow with just 1 ram stick at a time to see if we have any crashes/stutters.

[dark-breed]

Originally posted by nav1205:

I reinstalled windows 2 days ago so I do not think its that. I will try playing tomorrow with just 1 ram stick at a time to see if we have any crashes/stutters.

how it is looking in the event viewer ? are there other problematic logs ?
is the windows installation a complete clean new installation or a overinstallation ?

if you need help to analyse the system you can add me like hundreds have done here for detailed analysis and more direct talk via chat.

[0wnz0r]

one time i added a fan to my pc case n unknowingly knocked a ram stick loose.

things ran mostly fine, but crashed in games. i turned off xmp, n it ran fine, but xmp was off...

i asked for advice cuz it was weird, n so many idiots told me i needed a new power supply or new ram or a new motherboard.... after i troubleshooted a lil, i opened my pc case to make sure my connections were all secure... i was sure i had faulty ram n almost bought a new pair...

n then i found, after i checked my connections, that i had one latch on one end of one stick popped.

i resinserted, turned xmp on again, n had no issues since.

sometimes, its the simple, easy to overlook things bro. if u recently did stuff to ur pc, make sure watever u did was done correct, n double check to make sure everythin is how its supposed to be.

[dark-breed]

Originally posted by 0wnz0r:

one time i added a fan to my pc case n unknowingly knocked a ram stick loose.

things ran mostly fine, but crashed in games. i turned off xmp, n it ran fine, but xmp was off...

i asked for advice cuz it was weird, n so many idiots told me i needed a new power supply or new ram or a new motherboard.... after i troubleshooted a lil, i opened my pc case to make sure my connections were all secure... i was sure i had faulty ram n almost bought a new pair...

n then i found, after i checked my connections, that i had one latch on one end of one stick popped.

i resinserted, turned xmp on again, n had no issues since.

sometimes, its the simple, easy to overlook things bro. if u recently did stuff to ur pc, make sure watever u did was done correct, n double check to make sure everythin is how its supposed to be.

yeah and the event viewer would have shown a memory error log related to the memory bank where it happens in this case.

this is the problem with ppl without expert knowledge, first checking detailed if there are logs that would point to the cause and than eliminate one by one any possible cause.

[0wnz0r]

Originally posted by dark-breed:

Originally posted by 0wnz0r:

one time i added a fan to my pc case n unknowingly knocked a ram stick loose.

things ran mostly fine, but crashed in games. i turned off xmp, n it ran fine, but xmp was off...

i asked for advice cuz it was weird, n so many idiots told me i needed a new power supply or new ram or a new motherboard.... after i troubleshooted a lil, i opened my pc case to make sure my connections were all secure... i was sure i had faulty ram n almost bought a new pair...

n then i found, after i checked my connections, that i had one latch on one end of one stick popped.

i resinserted, turned xmp on again, n had no issues since.

sometimes, its the simple, easy to overlook things bro. if u recently did stuff to ur pc, make sure watever u did was done correct, n double check to make sure everythin is how its supposed to be.

yeah and the event viewer would have shown a memory error log related to the memory bank where it happens in this case.

this is the problem with ppl without expert knowledge, first checking detailed if there are logs that would point to the cause and than eliminate one by one any possible cause.

well yea part of the reason i thought i had faulty ram was due to the event viewer.

but like i said, even the most seasoned vets overlook simple things. thats y its important to be thorough.

i checked event viewer n looked up the error codes, tested xmp on/off, ran memtest86 which i had already installed on a spare usb, n i was almost positive i had a bad ram stick.

not a single person who i asked for advice to make sure i didnt overlook somethin told me to double check to make sure its inserted correct.

i literally had a hunch. i figure i better check it again before i order a new pair.

everybody thinks theyre an expert n never make mistakes, so its important to check the small things, get as much info as u can, n do ur own research.

even if somebodys advice is correct, it could be wrong for ur specific problem based off how its described or interpreted.