Computer automatically restarting

ModDirty

Honorable
Aug 24, 2013
6
0
10,510
Hello,
I recently bought a new gaming desktop. I'm a novice to computers but I bought and installed a Geforce gtx 660 factory overclock, and it worked well. However every couple of days, my computer will instantly shut down as if it ran out of power, and then automatically start up in a couple of seconds. I thought this might be because of a cheap power supply, so I bought a 500W ATX Corsair, installed it, and it would still occur. I tried updating the drivers and BIOS and still nothing.

The restart only occurs when gaming, but not during particularly intense games. I used software to monitor the heat of my CPU and graphics card. The CPU temperature is fine and the graphics maxes out at about 83 degrees celsius. The computer manufacturer is CyberpowerPC.

Any recommendations to fixing this problem?
 
83 degrees Celsius is completely fine. My 6870 Twin Frozr 2 sits at 80-85 during furmark/skyrim.

What were your temps while running furmark + prime95?

Uhm, perhaps run furmark and GPU-z at the same time to see if your VRM/Vram is overheating?
 

ModDirty

Honorable
Aug 24, 2013
6
0
10,510
Well I ran furmark and GPU-Z and this is what I got:

(All of these are maxes)
GPU Temp: 82 degrees
Fan Speed: 55%
Memory Used: 235 MB
GPU Load: 99%
Memory Controller Load: 67%
Video Engine Load: 0%
Power Consumption: 111.1% TDP
VDDC: 1.0500 V

Could this point to anything?
 
Interesting. I mean this might be a simple fix or it could be something more obscure such as voltage spikes (though if they were bad enough to cause a psu failure then other devices in your house would feel it aswell)

Now I don't think this will come back with anything fruitful but does Event Viewer come back with anything useful in its logs?

Also do you get a windows error message when you reboot? (not the "start into windows normally" dos prompt but the usual error message after a BSOD)

To stop the pc from auto restarting theres an option the bios. its probably called "auto reboot on power failure" or something easy to identify like that.

What are your full specs? And if I may ask do you have time to run diagnostics (such as running memtest overnight or prime95 + furmark for about 30 minutes, keep an eye on temps for the first 10 or 15 minutes, you don't have to watch it constantly but just come back every so often)

Kind of wish that it did BSOD so we had something to work with. Its not being very helpful. The only thing I can think of is PSU issue but you replaced that so...

Ah one more idea, when running Prime95 keep an eye on the VRM temps of the mobo, they might be overheating and causing sporadic issues, Southbridge also might cause it if the heatsink isn't properly installed. I think the free trial of Aida64 can monitor all these things.
 

ModDirty

Honorable
Aug 24, 2013
6
0
10,510
There is no BSOD before the reboot. It shuts off as if I pulled the power cord.

I ran memtest86 overnight and it passed 4 tests. The restarts only happen after gaming, so maybe the RAM fails only when the system is stressed?

Intel® Core™ i5-3470 3.2GHz Processor
16GB DDR3 SDRAM
2TB (7200 RPM) Hard Drive
Microsoft® Windows 7 Home Premium (64-bit)
EVGA GeForce GTX 660 factory superclocked
Corsair CX500 PSU
Gigabyte B75M-D3H

However I think I might have found something in the system logs event viewer. I found the spots where my computer restarted, marked by a critical level, with a generic "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

But there are always two events that precede it. One of these events is 10 seconds before the crash and the other is the same time as the crash:

File System Filter 'FileInfo' (6.1, ‎2009‎-‎07‎-‎13T16:34:25.000000000Z) has successfully loaded and registered with Filter Manager.

&

File System Filter 'KLIF' (6.0, ‎2013‎-‎03‎-‎26T08:07:33.000000000Z) has successfully loaded and registered with Filter Manager.

I cannot find these events anytime the computer doesn't restarted, and literally every critical error in the event viewer is preceded by this.