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
What is your temperature on the CPU, GPU at idle and full load ?
Vsync should fix it.
New build, did you cheap out or lowball the PSU at all? A PSU that is rated high enough to handle your rig should not display this issue.
Processor: Intel Core i7 6700 3.4GHz (Codename Skylake) (Quad Core) (Not Overclockable)
Motherboard: ASUS/GIGABYTE (Intel Z170 Chipset)
System Memory: 16GB DDR4 2666MHz Digital Storm Certified Performance Series
Power Supply: 750W EVGA/Corsair
I turned on vysnc in the game settings and it still reset. I have vsync off though in my graphics card settings. I already deleted the game, do you think setting vsync on the card would do anything? Tired of messing with it to be honest.
Which is it? EVGA or Corsair?
Vsync should fix it - were you running under OpenGL or Vulkan?
+r_renderAPI -0
then click ok and run the game,
if its still the same, try the gpu control panel for a reduction of graphic card functions.
V-Sync doesn't seem to correct this for me.
AMD R7 2700X
ASUS PRIME X470-PRO
16GB G-SKILL DDR4 3200 DUAL CHANNEL
7200RPM SEAGATE BARRICUDA (Drive the game is located on)
GIGABYTE GTX 980Ti G1
EVGA SUPERNOVA NEX750B 750W PSU
CPU temperature was at 51C at the time of the shutdown.
I do not allow my temperatures to exceed 70C for any prolonged length of time, after it hits 70-80C, I step in and adjust cooling as much as I can.
This is the only game that creates this issue, and was wondering if anyone else was experiencing it.
Seems like id managed to royally ♥♥♥♥ something up in the engine.
The odd thing is that this doesn't happen with my i7-8700K+2080 rig.
Shouldn't be the same root cause.
Shot in the dark, have you run a long term Prime95 small FFT or overnight memtest? I've had slightly - and I mean slightly as in 99.9% stable in everything else - unstable memory on every Ryzen system I've built. 3200mHz tends to be where they pop up in extremely unpredictable software loads.