Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
i was really wondering when topics like this pop finally up.
like, i was already wondering if ubisoft managed what many triple A devs cant do nowadays, aka testing a wide range of rigs if the game runs or not on it without problems lol xD.
I think I read someone else having an issue with some memory anti cheat protection or something. I think...
🔎 How to check:
(I'm having this issue too. I've been talking to Ubi support, and if I find out anything new, I'll let you guys know)
And 0xc0000005 means access violation. I.e. some kind of C++ buffer overrun or something. Good luck with that!
So I followed your steps and I found a similar error in my event log. tied to Event 1002. I searched for that and found a random forum post stating that it was tied to screen display sacaling set to 125%. I just happened to have my display scaled to 125% so I knocked it down to 100%, rebooted my system, and now the game launches!
It's sad the game crash from some system settings like that. Cant blame Unreal5, since they use Ubisoft Anvil... But great that you found out a fix for you :)