I:R 2.0.5.2 crashes on start (Win10, GOG)

[dolorez]

I tried:
- validating installation through GOG
- running with all mods disabled
- adding imperator.exe to firewall exceptions
- downgrading to 2.0.4 that used to work but no longer does
- reinstalling C++ and .NET packages

exception.txt has this error message:
Unhandled Exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at address 0x0000000010003654

logs/error.log says:
[pdx_ugc.cpp:42]: No UGC backend available for current platform.

attaching the latest crash folder

 

[AndrewT]

Well, if a game version that used to work no longer does, something local must have changed to cause this to you!


What happens if you run imperator.exe directly from file explorer? Any error when it crashes then?


What antivirus app do you use? You need to make sure all these apps are in its exceptions lists:

imperator.exe (in the Steam imperator/binaries folder)
dowser.exe (in the Steam imperator/launcher folder)
C:/users/{username}/AppData/Local/Programs/Paradox Interactive/launcher-v2.2025.6.1/paradox launcher.exe
C:/users/{username}/AppData/Local/Programs/Paradox Interactive/bootstrapper-v2.exe


If that doesn't help:
DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.

IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

 

[dolorez]

Thanks a lot for responding so quickly!

One thing changed for sure - nvidia drivers were updated several times since I last played Imperator

Attaching dxdiag.txt

I'm using windows defender, whitelisted all the above (though I don't have launcher-v2.2025.6.1 in my AppData/Local - I have launcher-v2.2025.3 , launcher-v2--openbeta--2025.6-rc.1 and launcher-v2--openbeta--2025.7-rc - whitelisted all three).

Launching Q:\Program Files (x86)\GOG Galaxy\Games\ImperatorRome\binaries\imperator.exe directly results in crashdump window (presumably crash_reporter) but without the usual error window

 

[AndrewT]

I'm using windows defender, whitelisted all the above (though I don't have launcher-v2.2025.6.1 in my AppData/Local - I have launcher-v2.2025.3 , launcher-v2--openbeta--2025.6-rc.1 and launcher-v2--openbeta--2025.7-rc - whitelisted all three).

That looks like you've opted into the beta programme of the launcher, is that right? If so please opt out. But that won't be causing your game problem.

You whitelisted the game in the WD Ransomware function, is that right? I ask because folks sometimes do it in the firewall function, which is unrelated and can't cause this problem.

One thing changed for sure - nvidia drivers were updated several times since I last played Imperator

The game runs fine on my Nvidia system with the latest driver version, from mid-May. But if GeForce Experience or the Nvidia app are running, exit them before starting the game.


We see several LiveKernelEvent entries in that dxdiag. They happen when the PC is forcibly downed, or reboots itself. Have you seen those happen, are they related to this game or something else?

There's also a crash in Stellaris in there, in DirectX11. There are also crashes in Chrome and Galaxy; would you say you are having general problems on this PC, outside this game?


You might try this Windows repair tool

Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

Describes how to use the System File Checker tool to troubleshoot missing or corrupted system files in Windows.

support.microsoft.com

Good luck!

 

[dolorez]

I whitelisted entire directories (both of them - where launcher and imperator.exe reside) in the ransomware, but it didn't help; the same error. Neither did opting out of the beta launcher.

I'd say I have occasional crashes around the time new drivers come out, and updating to newest ones seems to solve the problem. With chrome, I reckon it might be related to the chrome updates themselves.

Windows repair tool found and removed some issues, yet it didn't solve my I:R issues. Sucks to be me, I guess...

Anything else I could do to attempt to debug the issue?

 

[AndrewT]

Try making a new Windows user profile on this PC, and test the game under that - any better?

 

[dolorez]

New user in Windows, just GOG Galaxy + Paradox Launcher running, still the same issue and error. Also, running imperator.exe directly under this new user doesn't help.

 

[AndrewT]

That's a shame, I'm running out of ideas here. Do you have access to any other PC to test this game on under that GoG account? Just to confirm it is not an issue with that build (GoG is the one version I don't have access to).

 

[dolorez]

I managed to run it on an M1 Mac, but that's a different architecture.

I don't think it's that specific build at fault, because when I subscribed to 2.0.4 on GOG, the same issue persisted (and 2.0.4 used to run back when it was the current version on GOG). I'll try it out on one of my sons' machines when they get back from school and report back.