PC shuts down randomly, no warning

xFuchs23

Honorable
May 10, 2014
33
0
10,530
Okay, so I've been searching for a few hours now and nothing seems to be the same issue as mine, so if anyone could help, it would be greatly appreciated.
Okay, so my PC literally just shuts down randomly. No errors in reboot, no errors before shut down, it just powers down and the power switch LED just blinks. I can't turn it off until I take all power away from PSU and then back on. I have tried everything I can think of and nothing see to be working.
Things I've tried:
Running a time test: there is no certain time it shuts off
Running hardware intensive games: again, doesn't really show a pattern of any sort.
Changing PSU: didn't help
Needless to say, I'm confused beyond belief. I have never seen anything like it and even though the parts are old-ish, the PC has maybe 100 hours on it.
Also, it doesn't power back on if I let it sit, the power led continues to blink until I take the power and then back.

PARTS:
AMD FX 9370
MSi 980a- g46
Thermaltake 600w
Gt 630( ik its pathetic
 
1. If PC is set to auto-restart after a failure... make it stop, a web search on "stip windows from [insert what you want here]" works.

2. The primary diagnostic tool is Event Viewer... use Windows help to find it if ya don't know how to start it up. Event Viewer as it's name implies, let's you view all the system logs . Start looking at Windows Logs / System. Events are logged latest 1st, so if ya noted the time your system failed, it should be easy to find.

3. ya can narrow these things down by running stress tests... RoG Real Bench for CPU, Furmark for GOU, memtest86+ for memory.

4. How old is that CPU, what model is it ?

5. What does HWiNFO64 show as the voltage on 3.3, 5 and 12 volt rails ... if it' varies by more than 5%, replace PSU
 

lifespill

Reputable
Oct 25, 2015
520
0
5,360
Your mobo is propably a MSi 970a- g46 not a MSi 980a- g46 as you say,if so your cpu is not compatible with your motheboard.It has very high tdp and this propably overloads the vrm's causing overheat and eventually a shutdown.
 

xFuchs23

Honorable
May 10, 2014
33
0
10,530
I'm literally sitting next to the MoBo box lol, its a 970. Anyways, I checked that compatibility before I bought it and after these issues began. Everywhere I check, its compatible. and Jack, I'm checking those issues now, I haven't had time to bother with it until now.
 


1. Never use more than 1 at a time ... i recommend HWiNFO64 as it tells you EVERYthing

2. What load ? Not every game puts on the same load, so if everyone is using a different yardstick, impossible to compare results ... that's what Furmark is for.




Take the entire message from the "General" tab and paste into the search window of your browser

Typically something like:

"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Of course this is the error you that is generated during the reboot process saying "Just letting ya know, the *&^%#%$ hit the fan a little while ago". ... there is usually a previous error telling you why it went down.

https://support.microsoft.com/en-us/kb/2028504

Copy the entire message in the Details box and paste it into the search bar of ya web browser.

 

xFuchs23

Honorable
May 10, 2014
33
0
10,530
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.
This is the only error on my event viewer other than the Kernal-Power thing. I put this in and nothing like my issues shows up. I checked my PSU's heat and its fine, the only thing i can't check is voltages, my meter broke lol. This means that more than likely its a PSU issue right? I'm probably wrong, but I'm really frustrated and idk what else to do!