Ck3 Crashes while playing after picking character- Unhandled Exception C0000005 (EXCEPTION_ACCESS_VIOLATION)

[Erik Sandstrom]

Hello, Ck3's has been until recently a great game. I've played around 130 hours and no major problems until this new patch1.1.3 my game has near instantly crashed when ever I've try to start a game. I can pick a bookmarked character load in and after a few seconds crash quite reliably.

Game Version 1.1.3

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled?
No, UN-subscribed and deleted local mods.

Have you tried verifying your game files (Steam only)?
Yes

Have you tried reinstalling your game (Steam only)?
Yes

Have you tried Checking if MS Security is Blocking App ?
yes, I've disabled MS ransomeware, Add an allowed app; both ck3.exe and steam.exe. As well as allowed the whole C:\Program Files (x86)\Steam folder to the control folder access.

Have you Checked if drivers are up to date?
yes, windows and graphics have both been checked

Hardware:
AMD Ryzen 5 3600 6-Core Processor
Radeon RX Vega

I've zipped the whole crash folder below

A preamtive thanks for your assistance and thank you for this excellent game.

 

[satoru]

Seeing that the GPU seems to be causing issues which is odd.

I'm curious if you roll back to 1.0.3 in steam do you have the same issues?

Could you also attach a dxdiag

 

[AndrewT]

Please do a full **clean** re-install:

- move any valued save games elsewhere
- "uninstall" in Steam-CK3
- manually delete both the Steam/SteamApps/common/CK3 AND Documents/Paradox/CK3 folders
- re-install game in Steam, run a Steam Verify when done.
- add CK3.exe to the exceptions list of your antivirus app; ESPECIALLY if you have Windows Defender, add it to the Ransomware "Apps Allowed Through" list.
- start the game with no mods active and test

In particular make sure there are no files or folders left under either the Steam CK3 or Documents CK3 locations, before installing again.

 

[Erik Sandstrom]

Seeing that the GPU seems to be causing issues which is odd.

I'm curious if you roll back to 1.0.3 in steam do you have the same issues?

Could you also attach a dxdiag

Thanks for the suggestion, i've tried rolling back to 1.0.3 but that didn't help. Heres the requested DxDiag

 

[Erik Sandstrom]

Thank you for the quick reply, Still the same crash. I've again done a clean install, manually deleted both the Steam/SteamApps/common/CK3 AND Documents/Paradox/CK3 folders and run a Steam Verify after re-installing game. I also checked and CK3.exe is still in the exceptions list of the Windows Defender, same for the Ransomware "Apps Allowed Through" list.

heres the newest crash folder zipped.

 

[Erik Sandstrom]

Still crashing after I've updated Windows and Windows Security, checked all drivers to be up-to date and did a second **clean** re-install of the game paying attention to follow all steps. I even tried disabling windows security and ransomware protection and running the game, still crashing.

still Unhandled Exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at address 0x00007FF7D34F8578

 

[AndrewT]

Interesting, the second case I've seen with Vermintide in this thread today ... anyway we're still seeing the errors in the graphics card area there. Please try this:

- uninstall the AMD video driver with this tool:

https://support.amd.com/en-us/kb-articles/Pages/AMD-Clean-Uninstall-Utility.aspx

- reboot
- install the one from May 2020 from here:

http://support.amd.com/en-us/download

- reboot again

Also, if you run the Windows Updater app you should see a whole new Windows 10 version is available to install. Can you try that please?

 

[Erik Sandstrom]

I've followed your instructions and It seems to be working again, I've not run into any more crashes and I believe that the graphics driver was to blame. Oddly enough it also now works with the latest driver too ( I had tested the old may 2020 driver and the latest 22/09/2020 version ). I have no idea why or how but I am grateful for all your help in resolving this issue.

Thanks for the help, this issue is now resolved