Computer reboots during gaming.

[deWaardt]

Hi all.

 

A few weeks ago I got the last parts to finish my budget gaming rig, specs are on my profile, but it's giving me some issues.

When gaming for a couple of hours, it sometimes randomly reboots.

No crash or freeze or so, it just reboots like I pressed the reset button.

 

I always actively track my CPU + GPU usage and those are good.

My CPU hangs around 55 degrees during gaming and my GPU around 65 degrees.

 

One of the things I thought could be the problem is a bad CPU overclock, but it passed a 24 hour stress test without an issue

 

One time it even went so crazy that it rebooted, gave me 5 audible beeps while posting normally and continuing to boot Windows like usual.

I looked up a manual for my motherboard and 5 beeps indicate that no graphics card was installed.

The strange thing is that the beeps occurred while it was posting like usual.

 

I later tried again by removing my graphics card, and it indeed beeped 5 times, the exact same as it did after the random reboot.

 

 

Now it usually works just fine, I can game for 5 hours straight without an issue, but the other day I'm in-game for 2 hours and it just reboots.

When I look in event viewer it just says the generic "pc shut down without cleanly shutting down first, this happens in case of freeze/blahblah" or basically, the same error you get when you pull the power cord out.

 

Usually reboots like this are caused by a power supply that's not powerful enough, but I'm pretty sure my Seasonic is perfectly fine and up to the task.

 

 

Does anybody know what else could be causing random reboots?

Thanks in advance  

[Enderman]

sometimes its not the PSU but the motherboard power delivery

[themctipers]

4 minutes ago, deWaardt said:

-snip-

Quote

Specs:

• CPUAMD Athlon II X4 860K @ 4.2ghz 1.375v
• MotherboardAsrock FM2A88M-hd+ REV 2.0
• RAM1*4gb + 1*8gb. R.I.P. Dual Channel.
• GPUGigabyte GTX 950
• CaseSharkoon VS4-W
• Storage1*Western Digital Scorpoin Green 1TB
• PSUSeasonic S12ii 520w
• Display(s)1*LG 22EN43
• CoolingModded stock cooler
• Keyboard10 euro kruidvat toetsenbord
• MouseLogitech M-U0007
• SoundJVC TH-A55 5.1 Surround + HP
• Operating SystemWindows 10 x64

I think you are pushing too much voltage for that clockspeed, go for a lower voltage amount.

 

[porina]

What stress test did you use? It might not stress the system in the same ways gaming does, so you might not be stable after all. To check if it is the overclocking, you can remove it temporarily and see if the problem goes away.

[deWaardt]

Just now, themctipers said:

I think you are pushing too much voltage for that clockspeed, go for a lower voltage amount.

 

No man, sorry.

Won't work. 1.375 is the minimum it can go.

Considering it came with a stock voltage of 1.4v @ stock speeds (3.7ghz) and I got it to 4.2 while actually dropping the voltage by .025 should actually be a good thing.

 

1 minute ago, porina said:

What stress test did you use? It might not stress the system in the same ways gaming does, so you might not be stable after all. To check if it is the overclocking, you can remove it temporarily and see if the problem goes away.

I used AIDA64 while running heaven benchmark in the background. I thought that would probably get about as close as possible to actually gaming itself.

 

I've not tried removing the OC for a long time, just tried it for like 2 days. I'll remove it again and try again.

It really only reboots like once in every few days, not like everytime I'm gaming.

[samcool55]

Always always, always turn off the OC and test again. Regardless of stress test results.

Also, +1 voor dat toetsenbord  Didn't know kruidvat sold that.

[deWaardt]

Few days later with the OC disabled, system still reboots randomly

I put everything back to stock, CPU Voltages and clock speeds, and I don't have my GTX 950 overclocked or any settings changed so I don't need to set anything back on that.

 

I'm thinking about motherboard components overheating, so I've put a few small fans over the chipset heatsink and the vrm's.

I'll report back to see if that fixes anything.