PC has random reboots, can not seem to isolate the cause

Toggle sidebar Toggle sidebar
K

khemmeh

Commendable
Jan 9, 2017
6
0
1,510
Hi Folks, I was wondering if anyone has any ideas on what could be causing my issue - as I am out of ideas at this stage.

Spec:

Windows 10

FX6300 (not OC'ed) + Hyper Evo 212 Cooler

8GB Gskill

R970 Pro R2.0

2 x SSD Samsung EVO 120

PSU: Cooler Master B600

XFX R9 380 DD Black Edition OC

Case: BeQuiet Silent Base 900

OK - the issue is my PC will randomly rebooting during game, I play CS:GO and The Division. With CS:GO is during Map loading, and in the Division it just seemed random.

I have noticed randomly it will crash when a smoke pops on CSGO, not all the time - every time there is a crash in game, a smoke has just gone off in front / near me.

I have also recently noticed the screen flickers from time to time In game, but this seems to be a more recent symptom.

Limiting my frames in The Division to 60fps, seems to have stopped the crashing as often.

The crash is a clean reboot, as if someone has pulled hit Rest - no blue screen, no error message, and Windows log just shows a generic power issue:

Event 41: Kernal Power.

The system is home built, and is less than a year old. it was working fine for 3/4 months, and the restarting came out of the blue. I checked all event logs from the day it started, no new updates / software had been installed.

The restarts sometimes will be every time I play, other times I can play for days and not a single reboot.

I removed the PC from the powerstrip and plugged it directly into the outlet, and I didn't get a single crash for a week - I thought that had solved it but it started up again.

I have the latest Mobo drivers, flashed and updated bios.

I have tried various versions of AMD drivers.

The temperatures all seem well within safe range.

Reinstalled both games.

Run a Ram test - came back fine

Put it through prime and pushed it as hard - no reboots.

I am all out of ideas, so was hoping someone may have a few suggestions I can try, or some insight as to what could be causing these reboots.

My first thought was the PSU, but its less than a year old, and seems to have enough headroom for what I have in the machine - but I am open to suggestions if people feel that it could well be it - I do not have a spare to test sadly, and due to crashes being so random and unable to always replicate it, I am cautious about spending money on a new PSU and it turn out not to be the case.

If I have missed any info, or you need me to get you any additional specs, please just ask.

Thanks in advance for any help

J
 
Sort by date Sort by votes
A

Alerath

Commendable
Jan 16, 2017
1
0
1,510
I seem to be having nearly the exact same issue as you, except it only happens in rust. By chance are you getting any other errors in event viewer?
 
Upvote 0 Downvote
K

khemmeh

Commendable
Jan 9, 2017
6
0
1,510


I have a few random errors in event viewer, but none of them seem to be around the time of the failure.

These are the only ones I have:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S5). This can result in reduced resume performance.


The NetTcpActivator service depends on the NetTcpPortSharing service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.


The AODDriver4.3 service failed to start due to the following error:
The system cannot find the path specified.
 
Upvote 0 Downvote
K

khemmeh

Commendable
Jan 9, 2017
6
0
1,510


Hi George thank you for the input - it is one of things I think could possible be causing the problem - sadly on the PSU guide you linked to, mine has yet to be added / reviewed.

Just to clarify - a game under load equalling FPS drops could in fact cause a PSU to reboot? Would a bad / going bad PSU also be the cause of on screen flickering as well?

One thing I did notice is CPU-Z is incorrectly showing the GFX voltage (showing up in the 30,000's !!)

Thanks again for your help.
 
Upvote 0 Downvote
George Mulligan

George Mulligan

Reputable
Sep 20, 2014
922
0
5,360


Higher game load often equates to higher load on GPU and hence higher load on PSU. If the PSU isn't able to provide the needed power, a voltage drop is the likely result, which yes, can lead to GPU flickering (I would guess the GPU is providing the flickering output rather than your screen causing the flickering itself), as well as system reboots.

I've heard of inaccurate voltage readings on CPU-Z, but that's pretty wild- don't know what is going on there. Try another utility, like HWiNFO64 (it's free), which is really better at real time system monitoring.

Also, if you haven't already, go to Event Viewer, Windows Systems log and filter for Event ID 1074 to see the reboot information there.
 
Upvote 0 Downvote
George Mulligan

George Mulligan

Reputable
Sep 20, 2014
922
0
5,360
Regarding your particular PSU, I am not familiar with it directly, but I do know that that model had to be completely redesigned to meet EU regulations, so the original design may have had some issues... do you have the original B600 or the B600 v2? If the former, it's one more piece of circumstantial evidence it may be an issue. It's always hard to pinpoint a PSU issue for certain, so many of us always recommend getting your hands on another PSU to swap it out and isolate the problem that way.

I provided the link to help you choose a quality PSU should you choose to get another one.
 
Upvote 0 Downvote
K

khemmeh

Commendable
Jan 9, 2017
6
0
1,510



Hi George, once again thank you for your input buddy.

I am using the V2 of the PSU, so had hoped (after reading a few reviews before ordering) it would be up to the job. But I guess I should have saved a bit longer and perhaps gone for a better quality PSU.

I had a look in my events viewer for Event ID 1074, all of them are standard reboots on behalf of myself or a reboot due to an installer. Nothing out of the ordinary that I can see, or any errors.

Its definitely a PC issue not a screen issue, as I have swapped monitors and it occurs on both of them sadly! (checked cable and switched DVI port as well) - the flickering is ONLY in cs go - you would think more modern / heavier taxing games would cause more issues, but it doesn't seem to be the case.

HWinfo64 seems to be showing the correct voltage, so I guess its CPU-Z being buggy as always :D

Just wish I could replicate the fault on request, then I could borrow a PSU and try it out.

Ill do a few more stress tests to see if I can cause the issue intentionally.

Thank you for your help mate, ill report back once I have changed the PSU to close this off properly or incase anyone else has a similar issue.

J


 
Upvote 0 Downvote
K

khemmeh

Commendable
Jan 9, 2017
6
0
1,510


Ended up changing out the PSU for a Seasonic g650 - not had a reboot since then.

Just wondering if the old PSU did not have enough juice, or it was going bad .

Just wanted to come back and say thanks for your help mate!
 
Upvote 0 Downvote
George Mulligan

George Mulligan

Reputable
Sep 20, 2014
922
0
5,360
Glad to hear it.

A "bad" PSU is hard to describe. It could be fading/not enough current capability, voltage regulation issues, harmonics, inability to maintain different current loads on different rails... heck, if you plugged that "bad" PSU into a different machine with a significantly different setup, it might work just fine.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom