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
The game has always had this problem and had literally thousands of posts on the old Ubisoft Forums about it before they shut it down. Do a search for "crashing" and you'll like find another 1000+ posts complaining about it
https://www.windowscentral.com/how-change-virtual-memory-size-windows-10
Try run it without ubilauncher/connect (offline)!
%localappdata%
Ubisoft Game Launcher > setting.yaml
user:
offline: true (false)
I spent 2 days to get it to run smoothly.
First try changing compatibility mode.
Then almost always use gamewiki :
(compatibility change instruction and cpu utilazation fix are described in detail there)
https://www.pcgamingwiki.com/wiki/Assassin's_Creed_Valhalla
And when the game actually starts, so do your troubles. I documented my fix(es) here:
https://steamcommunity.com/app/2208920/discussions/0/4129305027398897618/#c4754200917403802877
So yeah just increase your page file to 15GB, minimum and maximum to the same value, don't use the system managed variant, or don't set the minimum too low, unless you like crashing.
I had this sort of issue in Marvel's Spider-Man, game kept crashing after I set my page file to system managed, that was when I only had 16GB ram, fps was fine when changing graphics settings to max while game was already running, but anything higher than low settings, instant crashing when on boot up, plus it would crash anyway soon after when some loading happened.
Increased the page file, and could max out the graphics settings, no more crashing, regardless if fps was tanking or not.