Random crash

[AnimeRaccoon]

I am getting random crash in BG3, it can be after 20-30 minutes of gameplay or after 2-3 hours. Latest drivers, no bloatware, 9900k, 32 ram, 2080 ti, ssd. In game ultra settings, without anti aliasing, fidelity fx sharp ~5%, dx11, average fps in game 90-140, gpu/cpu temp <65c. I opened crash dump and found this:

0xc0000005
The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

(you can found crash dumps in steamapps\common\Baldurs Gate 3\bin)

Has anyone experienced this? Is this related to the operating system or hardware, or is it more likely a problem with the game?

[アンジェル]

Originally posted by 𝅷:

Random crash
I am getting random crash in BG3, it can be after 20-30 minutes of gameplay or after 2-3 hours. Latest drivers, no bloatware, 9900k, 32 ram, 2080 ti, ssd. In game ultra settings, without anti aliasing, fidelity fx sharp ~5%, dx11, average fps in game 90-140, gpu/cpu temp <65c. I opened crash dump and found this:

0xc0000005
The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

(you can found crash dumps in steamapps\common\Baldurs Gate 3\bin)

Has anyone experienced this? Is this related to the operating system or hardware, or is it more likely a problem with the game?

Based on the fact that it is an individual issue, it is more likely a settings/hardware issue than a general game issue. Otherwise it would neither be random nor rare.

Check how much virtual memory and shader cache you have and increase virtual memory to 32 GB minimum, 64 GB maximum, shadercache 100 GB, considering your RAM size of 32 whatsoever units

[Anomander]

I have the same problem. Random crashes. Sometimes I can play for hours without any problem, and other times it crashes every 15 minutes.
I also checked the logs and I have the same error - 0xc0000005.
But it is a standard error (memory access violation, memory cannot be read) - so it doesn't really give us any details.
I have AMD CPU, I read in other threads that it can be an issue with AMD CPU.

This is definitely problem with the game, not with the system. It happens to many people.

[AnimeRaccoon]

After a lot of googling, I realized that the error "The thread tried to read from or write to a virtual address for which it does not have the appropriate access" could mean anything. And most of these errors, judging by the feedback from users were fixed at the software level. Only developers using the dmp file can find out exactly where the crash occurs in the game. And it's also annoying to reset all game settings after a crash.

[mevludin90]

I've been running into game crashes recently. I tried so many things. Running on Vulcan and Dx11. Fresh install. Run as admin... etc.
Then my programmer instincts kicked in... maybe it's just the version of dotnet(the thing that runs the game). So I uninstalled 6.0.11 and installed the latest 6.0.21.
https://github.com/dotnet/core/blob/main/release-notes/6.0/6.0.21/6.0.21.md

And no more crashes. Before, the game couldn't handle 15 minutes of gaming or like a couple of minutes of cutscreens/fighting but it's been like 30 minutes and survived all cutscreens and fights.

[アンジェル]

Originally posted by mevludin90:

I've been running into game crashes recently. I tried so many things. Running on Vulcan and Dx11. Fresh install. Run as admin... etc.
Then my programmer instincts kicked in... maybe it's just the version of dotnet(the thing that runs the game). So I uninstalled 6.0.11 and installed the latest 6.0.21.
https://github.com/dotnet/core/blob/main/release-notes/6.0/6.0.21/6.0.21.md

And no more crashes. Before, the game couldn't handle 15 minutes of gaming or like a couple of minutes of cutscreens/fighting but it's been like 30 minutes and survived all cutscreens and fights.

Maybe... It is really hard to say, because what you wrote I recommended in other threads as well. Unless the users lied, it never did anything for them. But I think you did exactly the correct thing as native game error messages indicates that as a common source of issue.