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
Discussions Rules and Guidelines
Report this post
Might want to check your folder to get rid of those.
Random crashes ... are a blight and not easily to figure out. The 'sensible' approach would be to send the dump file + your dxdiag.txt to the devs aka official 'support' (not Steam).
Load an older save and play ... see if the game crashes again.
Start a 'new game' ... see, if the game crashes.
... both, to see, if the crashing is related to a (potentially corrupted) game save.
Another thing you can do is 'verify game cash" - always a good idea.
Another thing is to monitor your CPU/GPU in-game with (MSI Afterburner).
You can reduce the graphic settings and see if the crashes continue.
All these things are an attempt to 'exclude' what the issue can be:
Game.
Game Save.
Windows OS.
Hardware.
Drivers.
Games suddenly crashing randomly, which ran for a long time and are 'fine' on a PC that has not been updated or has other things installed recently that can interfere, mostly end up having two causes why this can happen:
The game is taxing your PC more than other games previously, causing hardware issues, you would otherwise not be made aware off. Playing a video game (CPU/GPU heavy) is like running a stress-test for long hours. It can reveal - or cause - hardware/drivers to fail.
The other common thing is: corrupt save file. This can happen without a hardware I/O (read-write) failure. Especially, with a new game, especially, with a RPG game which is tracking a ton of in-game states and can still be buggy. The kind of bugs a developer cannot see, but happens ONLY after many hours of gaming.
If your PC freezes or BSODs - that is a hardware/driver issue. MAYBE caused by the game, but not the game's fault.
These days PC games only CTD (Crash to desktop). They run in kernel user-mode. They do not cause a PC to BSOD or freeze or crash. If they do, it's on your hardware and the drivers.
Might want to check, if your PC or Laptop is not overheating.
Like others have said, these crashes are getting worse. I'm at the point now where I cannot complete a conversation without the game crashing.
FWIW, verifying the integrity of the local files does not help.
Also, CPU is maxing at 60C, chipset at 50C, and GPU at 65C. Well within thermal limits.
I started a new game to test and so far so good. I'll try to update with the number of hours (or minutes) between start and the first crash.
It is really feeling like it's a data corruption thing tied to the age of the save file or something. Nothing I tried with graphics or audio (since it was crashing in conversations) resolved the crashes in my 16 hour game.
Cannot avoid the Lodge and just do other activities because of "Protocol Indigo".
Tempted to just try and get a manual refund due to technical issues.
Just checked the Saves. Seems like the problem starts once the save file reaches around 2MB.
The Save file for my 16 hour game is over 3MB.
edit: my save files are 6mb by the way
And now that you mention it...
Give me a minute. I may owe you lunch.
Disabling Logitech G Hub and iCue actually got me through the conversation with the marshall and the conversation with the bank robbers. Game crashed while walking back to the marshall.
Still, it's progress. Thanks for the suggestion!
it could be because the author decided he needed devuno anti piracy protection for his paid mod.