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
EDIT: A friend had the same issue as well, but his was on a laptop, basically he had to end up tossing the whole thing.
I'm getting new drivers to see if it fixes it. I highly doubt it is the card since I just received this EVGA recert replacement for my old one that completely died. Died as in my system would not boot b/c it did not detect a card.
My CPU is water cooled and my case has 2 250 mm fans on the side and my PSU is an Antec 1000W with the card on its own dedicated rail. The video card is not under serious load in this game and why would it be? The game's graphics are good but not earth shattering and my card and system can handle a whole hell of a lot more than this game. I only seem to have this problem with Unity based games and only 2 of them at that. Unreal games (any Unreal version) have never caused this and neither have Euphoria or Gamebryo based games.
I will try to force my memory to the speed it should run on my system. Maybe the Auto setting is not working as expected at times. My memory can run 2300 but I can only run at 1866 due to my AMD FX8350 not supporting 2300. No way my memory is having timing issues when it so underclocked.
Same thing happened to me last year.
Probably a driver issue between Unity and Nvidia. Updating to the latest now.
Same thing happened to me.
Only game the pc would fail in was this. Then after a month it got worse, i could not play the game more than 3-5 minutes. I could restart it and play ets2 in 45 minuts, it suddently crashed it to.
I can play ETS 2 for hours. It has never crashed on me. I can play Elite Dangerous for hours as well. But doesn't matter b/c those games don't run on the same engine as this.
I really think it is my save game. Something is causing everything to lock up.
So it probably was throwing an unhandled exception somewhere and the render portion would just die while the rest of the game thread would keep running. No clue. But I can play on a new save just fine. Contrary to popular belief it IS possible to crash the driver b/c of bugs. I've done it in my own development. Drivers don't do bounds checking on vertex buffers, etc. This makes them faster at the expense of if you mess up you might get away with it for a bit and then....bam...it all comes crashing down. I've caused BSODs in W7 due to bad shaders and/or bad render code.
I don't know what caused this since I don't have the source code...but I'm glad I can play now. Maybe windowed mode would have given me more clue as to what happened. When games crash in full screen sometimes there isn't a way out.
Maybe revalidate the game cache? sometimes with games (not sure about this one) updates can leave unwanted files that end up causing unexpected crashes like this.