Pc keeps getting random shutdowns, PSU faulty?

danisun · Dec 21, 2016

Hey everybody. Been having this problem for a while now, and it is annoying me so much since I can't figure out what's causing it.

So my computer just restarts, everyday. And this isn't a good restart either. The system just clicks off, then starts up again. I can't find out what's causing this.

All I've found is that I get event ID 41 or event ID 6008.
Been browsing the web, and if I do a specific search on User32 and ID 1074, I find that runtimebroker.exe has initiated alot of restarts.

Anyone got some helpful tips?
I have reformatted before, but for some reason, it did not help.

I have also been reading that the PSU could be the sinner in this mystery. But can't find anyone having the specific problem. Maybe but I can't find it.

drkatz42 · Dec 21, 2016

please list your specific system configuration

danisun · Dec 21, 2016

drkatz42 :

Oh, sorry about that.

MB: Asus maximus VII gene
CPU: i7 4790k
Mem: corsair vengeance pro ddr3 2400mhz
PSU: corsair rm750
HDD1: Kingston ssd now 240gb
HDD2: Seagate barracuda 3tb
GPU: msi geforce 980 twin frozr

MeanMachine41 · Dec 21, 2016

If runtimebroker.exe has initiated a lot of restarts or eating up a lot of CPU, you can disable it.
The Time Broker, can be disabled through editing the registry.

Right-click on the Start Menu Icon. Go to RUN and type regedit.exe and select OK.

Go to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker]

Modify the DWORD to 4 which will disable it then restart the system.
You also have other options, 4 is Disabled, 3 is Manual and 2 is Automatic startup.
Before editing your Registry save a system restore point incase you make any mistakes.

danisun · Dec 22, 2016

MeanMachine41 :

Hmm, there are 4 DWORD in this folder, ErrorControl (1), ServiceSidType (1), Start (3) and Type (32)
Is it anyone of those?

MeanMachine41 · Dec 22, 2016

Start is the one you need to modify. Right click on it and if its set to 3 then change its Hexadecimal value to 4.
This does not kill Timebroker completely however it should help.
I have heard that killing the Timebroker will prevent all metro Apps from working. Not 100% sure tho.

Dark Lord of Tech · Dec 22, 2016

Sounds like a PSU issue to me.

danisun · Dec 22, 2016

Okay, I have changed the value to 4 now. So we'll see if this will solve the problem.

But SR-71 Blackbird, do you have any valid tests for me to run so I can find out if this is the case? I've been trying to read it's voltages, but it might aswell be greek for me (I don't speak greek). They seem normal, as far as I can tell.
Will post some tests, if I could know what programs or where to get those.

danisun · Dec 22, 2016

I got this from the event viewer too, seem to be related?

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

danisun · Dec 23, 2016

I don't have any freezing issues. It just restarts. But not the good kind of restart where the OS says: Restarting. The computer just turns off with a click, even when I'm not doing anything. Then it starts up again.

I downloaded hwinfo, the 3.3v has 3.344v, 5v has 5.080v, 12v has 12.000v. This is normal, right?

Billy Blaze · Dec 23, 2016

Good luck, and please do post if you are able to solve the issue as I'm having almost the exact same symptoms (exept for automatically booting back up again). From what I can gather it's either an issue with a short / leaky caps on the mobo, an aging power supply or an error with the GPU itself. Your local hardware store should be able to run some tests with other components to help narrow things down.

Those voltage readings are great btw (a 5-10% variance seems to be the acceptable range), but I would question that almost-too-perfect 12v reading if it doesn't fluctuate

danisun · Dec 23, 2016

MeanMachine41 :

It just did the same thing as it always does, so that can't be the main reason atleast.

MeanMachine41 · Dec 23, 2016

To run a test on the PSU under load, Download HWMonitor and AIDA64 and put them side by side on your desktop.
In AIDA64, go to the Tools menu and choose the stress test. Run the test for CPU,FPU and Cache.

Observe your temps during the test and take screen shots at the 10min mark. If temps reach 80C then stop the test. I want to see all rail voltages in HWMonitor, that is 12V, 5V, 3.3V with 100% utilization on all cores.
Link your screen shots here for analysis.

danisun · Dec 24, 2016

MeanMachine41 :

MeanMachine41 · Dec 24, 2016

Nothing wrong with the PSU. Your Core temperatures are a little high at 79C during the test. An extended test is required to see if temps climb to an unacceptable level on the Core. Run the test for 30mins and see if it throttles or shuts down the system.

Your problem probably lies elsewhere so lets see if your Windows files check out OK.
Run "sfc /scannow" without the quotation marks in an elevated command prompt.
This will scan your Windows files for corruption and attempt to fix any found.

Event 41 is a kernel error caused when the system was not shut down correctly and event 6008 is similar. They are not a cause.

danisun · Dec 24, 2016

MeanMachine41 :

Yeah, it is a little wierd. I also have a corsair H75 water cooling unit on the CPU. The fans on the radiator are sett to blow out of the case though.
Windows Recource Protection did not find any integrety violations.
If I go throug PC doctor, I find that some of the crashes was caused by an unknown driver (C:\Windows\system32\drivers\hiber_iastora.sys). But other than that I got nothing. It does not say that in the crash I got a minute ago. Just that the crash was unexpected.,

danisun · Dec 24, 2016

Here is a run with 38 min:

MeanMachine41 · Dec 24, 2016

I see no problems with temperatures nor voltage at 4.4GHz so your cooler and PSU are doing their job.
No Windows file corruption so yea its mysterious.
Have you checked Device Manager for bad drivers, Yellow Triangles.?
The only other thing I can think of is a Virus or Malware.?
Have you checked with your Virus detection software.?

AlexP1 · Dec 24, 2016

If none of the above have worked, one thing I would suggest is to check your build/cabling, as it could be simply that something is shorting and causing the current protection (if your PSU has that included) to shut the system down.

A couple of things that could cause this are your standoffs not being installed correctly (causing MOBO to touch metal case and shorting...unlikely if it is running for any length of time, or your front panel not being wired up correctly.)

If it switches off when you touch the case, I wouLd suggest the latter (I have had this before.) Double check all your wiring to be sure, but apart from that, I don't know....

rverma87 · Dec 24, 2016

MeanMachine41 :

Not to hijack the thread but I'm having a similar issue and I ran the tests you recommended and my 12V rail minimum voltage is 11.160V, but it was only like that when I started HWmonitor. During the stress test the voltage dropped to 11.088V at minimum and I saw 11.3V or lower more than a couple times. My PSU is a Corsair HX750 that's only 2 years old. Is my PSU failing?

MeanMachine41 · Dec 24, 2016

Quote; rverma87 said:

Not to hijack the thread but I'm having a similar issue and I ran the tests you recommended and my 12V rail minimum voltage is 11.160V, but it was only like that when I started HWmonitor. During the stress test the voltage dropped to 11.088V at minimum and I saw 11.3V or lower more than a couple times. My PSU is a Corsair HX750 that's only 2 years old. Is my PSU failing?

You paid a handsome price for your Platinum Certified Corsair HX750.
If voltage regulation is out of spec (which it is) then submit a ticket with Corsair explaining the situation and get an RMA. You have a 7 year Warranty. Its not with 100% certainty but has to be checked out as it could also be the MB failing to regulate consistently however less lightly.

danisun · Dec 25, 2016

MeanMachine41 :

Yeah, I have checked and it has no triangles in device manager.
Can run a scan for anyting, with malwarebytes and security essentials, don't really have any virus detection software, other than windows standard.

And to AlexP1, it's funny that you suggest that, because I took the whole rig apart yesterday just to check if anything was loose. I am going to do that again soon, with a complete wipe of the system, since I got a new case for christmas.

I do appreciate all the help from you guys! Thanks!

But the problem still persists.

danisun · Dec 28, 2016

Okay, here's an update so far.

I got a new case, so I took everything apart, then reassembled everything into the new case. Then I deleted everything and reformatted every disk, installed Win10 pro x64 and updated everything. This is now 3 days ago. Started installing games, and trying different things out like settings and monitoring temps. Nothing out of the norms there. In the last days I have not gotten any restarts like before. I suspected I got a restart at night when I was updating, since I saw it in event viewer. But havent actually seen a restart since. That is since today. I started up my oc normally, and a friend told me to come play 7 days to die with him. So I installed that from steam, and started up the game. It goes through the usual when you first load a game, like install redist and visuals. I maxed out settings, loaded a game, an a few minutes went by, then it happened again.

That was a long one. But I can't seem to wonder if it has something to do with my PSU? Any suggestions?

danisun · Jan 18, 2017

Another update in my quest to find a solution to this problem. I ordered a new PSU, but the problem still persisted. So I returned that, and put the old one back in. So I went into BIOS, and my RAM was running at 1333Mhz, and it should be 2400Mhz. The problem actually stopped for some weeks after bumping the Mhz to 2400. But now it is back again. I am now suspecting either RAM or motherboard.

MeanMachine41 · Jan 18, 2017

danisun :

When in Bios you can enter your Primary Timings and Voltage manually. Your RAM SPD info can be got from within Bios Tools section or from CPUz in Windows. A slight increase to DRAM voltage or changing DRAM Command rate from 1T to 2T can sometimes help.
You can test your RAM modules by using Memtest86 from a USB stick. run the test for 3 passes on each module in a slot that is working. If they prove OK then the problem is the MB.

Pc keeps getting random shutdowns, PSU faulty?

Reputable

Honorable

Reputable

Judicious

Reputable

Judicious

Retired Moderator

Reputable

Reputable

Reputable

Commendable

Reputable

Judicious

Reputable

Judicious

Reputable

Reputable

Judicious

Reputable

Commendable

Judicious

Reputable

Reputable

Reputable

Judicious

Share this page