Game constantly crashing on PC

[Minho horselord]

Hi all. Pretty please I could use a little help or advice.

I'm using Windows 11, Nvidia RTX 3060, i7 processor, 16gb ram.
Pc is fairly new within a year.
Elden ring is unfortunately constantly crashing for me. Sometimes it doesn't crash for a half an hour, sometimes it doesn't crash for an hour or two. Other times it's crashing back to back and it's unplayable.

I've searched just about all links with fixes for crashes as well as watched several videos with crash fixes. I've got updated drivers, updated windows, I've re-installed the game already, tried my hardest to troubleshoot the reasoning behind the constant crashes. Other games I play don't crash despite running with higher tempartures than elden ring makes my pc run with.

The application crashes and leaves no error message, just freezes and pops up that the program is no longer working.

Recently I came across the event viewer application where I tracked down one of my crashes and found the general details, was hoping if anyone could translate what all this means:

Faulting application name: eldenring.exe, version: 2.0.1.0, time stamp: 0x65839fe5
Faulting module name: eldenring.exe, version: 2.0.1.0, time stamp: 0x65839fe5
Exception code: 0xc0000005
Fault offset: 0x00000000011642ea
Faulting process id: 0x0x30C0
Faulting application start time: 0x0x1DA6D481F7E7A6E
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Report Id: 1f3dfb89-8517-483d-9c88-aefd5c2e7451
Faulting package full name:
Faulting package-relative application ID:

Ty greatly

[dark-breed]

It is a unusual offset pointing to a problem with the gpu driver communication.
Since it is Windows 11 it could be related to the actual problems Windows 11 has, this offset appeared the last two weeks for some ppl and in every case it was Windows 11.

Actuall there is not much left, i would say wait till Microsoft fixed the actual problems of the os before starting a system check and repair process.

[Minho horselord]

Originally posted by dark-breed:

It is a unusual offset pointing to a problem with the gpu driver communication.
Since it is Windows 11 it could be related to the actual problems Windows 11 has, this offset appeared the last two weeks for some ppl and in every case it was Windows 11.

Actuall there is not much left, i would say wait till Microsoft fixed the actual problems of the os before starting a system check and repair process.

Hi @dark-breed , I actually just saw someone with a similar post last week and read all your responses and came to the same conclusion. Thanks a lot for responding & for the good work helping people! seems like windows 11 might be the huge culprit. hopefully things can get some changes and differences for the better and the OS can run Elden ring better.

[Hurricane]

C0000005 only means access denied. It could be anything but in this kind of setup it's likely the kernel or the drivers (e.g. GPU).

Take a look at this[support.microsoft.com] read carefully and follow instructions if you feel it's relevant to you.

[Lagow]

Game just crashed and I also have windows 11. It has crashed at least once every other day for the past week. 11700f 3070 32gb ddr4 3200mhz

[xXTombRaiderXx]

skill issue

[Minho horselord]

Originally posted by Hurricane:

C0000005 only means access denied. It could be anything but in this kind of setup it's likely the kernel or the drivers (e.g. GPU).

Take a look at this[support.microsoft.com] read carefully and follow instructions if you feel it's relevant to you.

Ty for the link. it seems informative and i've seen other people mention the same troubleshooting, but in this link specifically it never mentioned windows 11 so i'm not sure if it's relevant to me exactly. let me know though if i'm wrong.

[dark-breed]

Originally posted by Minho AUUUUGHHH:

Originally posted by Hurricane:

C0000005 only means access denied. It could be anything but in this kind of setup it's likely the kernel or the drivers (e.g. GPU).

Take a look at this[support.microsoft.com] read carefully and follow instructions if you feel it's relevant to you.

Ty for the link. it seems informative and i've seen other people mention the same troubleshooting, but in this link specifically it never mentioned windows 11 so i'm not sure if it's relevant to me exactly. let me know though if i'm wrong.

sfc /scannow is a part of normal troubleshooting (beside the dism /online /cleanup-image /restorehealth command), the problem is ppl have to know a lot of stuff about the error logs to determine if this could help.

with your specific log the chance is low that both commands will find any error that could be related to the problem you have because it was tested before with ppl that got the same error log in windows 11 and it found nothing.

but yes you could go the whole repair process if you want to find out if it helps.

here it is: (it is the same for windows 10 and 11)

Open command prompt as Administrator and run these commands

type into your taskbar

cmd

click with the right mouse button onto the command prompt and use the option start as administrator

run this command

dism /online /cleanup-image /restorehealth

After this is finished

Sfc /scannow

Repair the c++ redistributables

https://aka.ms/vs/17/release/vc_redist.x86.exe
https://aka.ms/vs/17/release/vc_redist.x64.exe

Check device Manager for faulty drivers

Do a clean reinstall of the gpu driver by deinstall it with DDU and install it fresh.

delete shader cache and temporary files too to prevent errors related version conflicts of the GPU driver related shaders.

have to add: you could also check for bios updates, GPU firmware updates and reinstall the motherboard drivers form the manufacturer support page.

[Madthunder]

I have the exact same exception code and fault offset.

[Hurricane]

Originally posted by Madthunder:

I have the exact same exception code and fault offset.

Would you mind giving your hardware specs to compare them with OP?

[Youshisu]

Originally posted by Minho AUUUUGHHH:

Hi all. Pretty please I could use a little help or advice.

I'm using Windows 11, Nvidia RTX 3060, i7 processor, 16gb ram.
Pc is fairly new within a year.
Elden ring is unfortunately constantly crashing for me. Sometimes it doesn't crash for a half an hour, sometimes it doesn't crash for an hour or two. Other times it's crashing back to back and it's unplayable.

I've searched just about all links with fixes for crashes as well as watched several videos with crash fixes. I've got updated drivers, updated windows, I've re-installed the game already, tried my hardest to troubleshoot the reasoning behind the constant crashes. Other games I play don't crash despite running with higher tempartures than elden ring makes my pc run with.

The application crashes and leaves no error message, just freezes and pops up that the program is no longer working.

Recently I came across the event viewer application where I tracked down one of my crashes and found the general details, was hoping if anyone could translate what all this means:

Faulting application name: eldenring.exe, version: 2.0.1.0, time stamp: 0x65839fe5
Faulting module name: eldenring.exe, version: 2.0.1.0, time stamp: 0x65839fe5
Exception code: 0xc0000005
Fault offset: 0x00000000011642ea
Faulting process id: 0x0x30C0
Faulting application start time: 0x0x1DA6D481F7E7A6E
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Report Id: 1f3dfb89-8517-483d-9c88-aefd5c2e7451
Faulting package full name:
Faulting package-relative application ID:

Ty greatly

Check windows event log

[Madthunder]

Originally posted by Hurricane:

Originally posted by Madthunder:

I have the exact same exception code and fault offset.

Would you mind giving your hardware specs to compare them with OP?

Windows 11 22H2
ryzen 5 5600
rx 6750 xt (23.11.1 driver)
16gb ram

Strange thing is the crash is not immediate. Visuals would freeze but the game still accepts input and I can hear the audio. It would crash maybe 10 seconds later.

[Hurricane]

Originally posted by Madthunder:

Originally posted by Hurricane:

Would you mind giving your hardware specs to compare them with OP?

Windows 11 22H2
ryzen 5 5600
rx 6750 xt (23.11.1 driver)
16gb ram

Strange thing is the crash is not immediate. Visuals would freeze but the game still accepts input and I can hear the audio. It would crash maybe 10 seconds later.

Both your CPU and GPU are different and of different brands.
It's unlikely to be an issue with the GPU driver then.
Maybe you've both stumbled on a bug in the game.

[dark-breed]

Originally posted by Hurricane:

Originally posted by Madthunder:

Windows 11 22H2
ryzen 5 5600
rx 6750 xt (23.11.1 driver)
16gb ram

Strange thing is the crash is not immediate. Visuals would freeze but the game still accepts input and I can hear the audio. It would crash maybe 10 seconds later.

Both your CPU and GPU are different and of different brands.
It's unlikely to be an issue with the GPU driver then.
Maybe you've both stumbled on a bug in the game.

Bs

[Hurricane]

Originally posted by dark-breed:

Originally posted by Hurricane:

Both your CPU and GPU are different and of different brands.
It's unlikely to be an issue with the GPU driver then.
Maybe you've both stumbled on a bug in the game.

Bs

Do you have even a clue of what these values mean?
They both have the same error address.
If one GPU is AMD and the other is Nvidia, then the driver code is different. There is no chance at all the addresses of the errors would be the same in the drivers.
It has to be in the calling code. That'd be the game or the at the very least in DX12.

[dark-breed]

Originally posted by Hurricane:

Originally posted by dark-breed:

Bs

Do you have even a clue of what these values mean?
They both have the same error address.
If one GPU is AMD and the other is Nvidia, then the driver code is different. There is no chance at all the addresses of the errors would be the same in the drivers.
It has to be in the calling code. That'd be the game or the at the very least in DX12.

A access violation at this offset is a directx to gpu driver communication fault and it plays no role what gpu they use, this is in most cases caused by a background app, gpu driver fault or directx itself.

The communication offsets are identical with all gpu's in use because this game is using the OS api and not a direct gpu driver call.

Just to add: i analyse and fix problems of this kind since the release of this game.