DOOM
RuleofTwo Oct 8, 2016 @ 6:51pm
Doom reboots my computer after restarts/level changes
Sometimes when I restart a level, it shuts off my computer completely. This is a new rig with a 1080, no other game does this. It has turned off on vulkan and whatever the normal thing is called. Does turning vsync on actually work? Any fixes? Wish I hadn't played over two hours so I can get my money back
< >
Showing 1-10 of 10 comments
RuleofTwo Oct 13, 2016 @ 9:00am 
bump. Tried vsync with vulkan on. Still reboots my computer. Any help? Again, DOOM is the only game ive ever seen do this in my entire life.
Samael Oct 13, 2016 @ 12:24pm 
What is your Power supply ?

What is your temperature on the CPU, GPU at idle and full load ?
Salamand3r- Oct 13, 2016 @ 1:15pm 
Uncapped FPS on loading screens is the cause. Tripping either surge protection on the motherboard or OCP on the PSU.

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.
RuleofTwo Oct 13, 2016 @ 7:28pm 
No I didn't cheap out.

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.
RuleofTwo Oct 13, 2016 @ 7:29pm 
My temps are normal, this game can turn off after 2 minutes of play. By the way I really appreciate the info. This game runs sooooo smooth except for this issue.
Last edited by RuleofTwo; Oct 13, 2016 @ 7:31pm
Salamand3r- Oct 13, 2016 @ 7:44pm 
Originally posted by Furi0sa:
No I didn't cheap out.

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?
Sean Lawn Oct 14, 2016 @ 1:07am 
goto game properties (right click doom in games list) in the general tab click launch options and add this

+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.
Last edited by Sean Lawn; Oct 14, 2016 @ 1:08am
RuleofTwo Oct 14, 2016 @ 8:54am 
Capping the game to 60 fps seems to have FINALLY fixed this problem. Still a little paranoid over another corrupted save. Guess this menu issue will never be getting patched
Legion Apr 29, 2019 @ 9:52am 
Anyone still experiencing this issue?

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.
Salamand3r- Apr 29, 2019 @ 11:39am 
Originally posted by Legion:
Anyone still experiencing this issue?

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.
< >
Showing 1-10 of 10 comments
Per page: 1530 50

Date Posted: Oct 8, 2016 @ 6:51pm
Posts: 10