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
Do you have Citrix installed on your rig? Can you check the Windows Event Viewer also regarding those crashes?
I do not have Citrix installed. For event viewer most of the crashes just froze my computer completely and i had to manually shutdown. I have 4 critical events that happened at time of the freezes and forced reboot
https://pastebin.com/2nyeELK9
One crash blue screened my computer and it left these two events. The first link is a critical similar to the other one linked just the bug check code is 59 instead of 0
https://pastebin.com/F62ykuhy
https://pastebin.com/HmjTgrMQ
Due to manual shutting down after freezing there are these errors after i rebooted
https://pastebin.com/480AyFQk
When first launching the game i got this error that calls out Outward.exe
https://pastebin.com/kQtBFq3D
That is most of the important events that happened at and around the time of the crashes. If you need more I can see if there are any more hidden somewhere.
Critical windows error.
The Fix for me was to fix windows. If you are running windows 10, do these steps.
Run Command Prompt as Admin. You can do this by either pressing windows + x or windows and type CMD right click the icon select run as administrator.
In the CMD window type the following. It can take a while to finish running but this will first figure out if you have anything wrong with your machine, if so then get a fresh image from online then repair via that image online.
sfc /scannow
Then: (don't type the then or next or so on.. lol)
dism.exe /online /cleanup-image /scanhealth
Next:
dism.exe /online /cleanup-image /restorehealth
Lastly:
dism.exe /online /cleanup-image /startcomponentcleanup
I stopped getting the error during normal game play and the game stopped crashing. It only happened on mine when in co-op. Probably is a small memory leak in the application that becomes more of an issue when running in co-op. It still can happen but takes longer for the error to happen.
So issue is with The game and with windows. You can easily replicate the error. Just leave the game pause in co-op for a about 45 mins - to an hour. It happens on most machines I install it on.