[SOLVED] PC suddenly turns off - does not go into hibernation, does not complain when turned on

justbaffled

Distinguished
Mar 25, 2012
13
0
18,510
Hi and help.

Having fought win 10 so that it now appears to work I have suddenly run into a very odd problem. The PC will suddenly just turn off. It appears to be do this in the evening only and it does not appear to be related to the length of time it has been on.

It does not go into hibernation (or at least the power light does not flash). It just suddenly turns off. There is no shutdown, no BSOD and when I turn it back on it just starts as if nothing has happened.

I have run memory tests (no problems found) and thermals are fine.

This started after a recent update, but not the windows feature update to 1903.

Strangely it only seems to do so once a day. :/

Can someone let me know what log or other file I can examine (and also where these would be) to try and see why the PC is doing this?
 
Solution
event 41 is created on startup, after the restart. Windows runs a report and checks if the previous shutdown was expected or not. If it finds it wasn't, it creates event 41, Windows doesn't know why it restarted. Unlike what others think, it isn't automatically a PSU error.

I think every pc on earth has DCOM errors :)

With no bsod and only the error 41 showing as evidence anything actually happened, its likely its hardware causing it of some sort.

PC Tailor

Illustrious
Ambassador
Please post your entire system spec including PSU make and model.

Open up reliability history and see what error logs are present. Along with this, reviewing System erros in Event Viewer may shed a bit more light on what was happening leading up to the crash.

if it is just a random power off - you'll see an Error Event 41, so you'll want to see what leads up to it, Reliability History gives a more easy to read view of similar things.

Are you running any overclock or XMP at all?
Do you have latest BIOS?
Do you have latest drivers installed (GPU, MB / Chipset, Internet etc.)?
 

justbaffled

Distinguished
Mar 25, 2012
13
0
18,510
Many thanks for the replies. Am new to win 10 so do not know much about the various reliability etc apps.

PC does not turn of at same time.
No overclocking, most recent (but old as the mbo is old BIOS), all drivers up to date - with the exception of the GPU as trying to do that kept resulting in a black screen. The driver I have works and I am reticent to change right now unless this is definitely the cause of these power offs.

There are a lot of DistributedCOM errors in the event log - details such as

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable
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.

No idea what these are, but they are through-out the log and perhaps at the time of last nights suden power off, but not todays - below.

I was playing a game called towerunite this morning and the PC suddenly turned off while I was. This is the 1st time it had done so in the day. Looking at the reliability monitor however just shows that this game stopped working, with no other info, followed by the note that windows had not shut down properly. Well yes the PC just switched off.

There is a 41 error, but nothing obvious before it. Here's the log up until the 41 error

The other errors in the system log are a few of those distributedcom erros and one from windows update about it not being able to update to 1903. Not sure on that one either as its saying pending install in update manager. And the 6008 is windows moaning it did not shut down properly

Critical 24/08/2019 11:14:46 Kernel-Power 41 (63)
Information 24/08/2019 11:14:46 FilterManager 6 None
Information 24/08/2019 11:14:46 Ntfs (Microsoft-Windows-Ntfs) 98 None
Information 24/08/2019 11:14:46 FilterManager 6 None
Information 24/08/2019 11:14:45 FilterManager 6 None
Information 24/08/2019 11:14:45 FilterManager 6 None
Information 24/08/2019 11:14:45 Ntfs (Microsoft-Windows-Ntfs) 98 None
Information 24/08/2019 11:14:44 Ntfs (Microsoft-Windows-Ntfs) 98 None
Information 24/08/2019 11:14:42 FilterManager 6 None
Information 24/08/2019 11:14:40 FilterManager 6 None
Information 24/08/2019 11:14:40 FilterManager 6 None
Information 24/08/2019 11:14:40 FilterManager 6 None
Information 24/08/2019 11:14:40 FilterManager 6 None
Information 24/08/2019 11:14:54 EventLog 6013 None
Information 24/08/2019 11:14:54 EventLog 6005 None
Information 24/08/2019 11:14:54 EventLog 6009 None
Error 24/08/2019 11:14:54 EventLog 6008 None
Information 24/08/2019 11:14:39 Kernel-General 20 (6)
Information 24/08/2019 11:14:39 Kernel-Boot 32 (58)
Information 24/08/2019 11:14:39 Kernel-Boot 18 (57)
Information 24/08/2019 11:14:39 Kernel-Boot 27 (33)
Information 24/08/2019 11:14:39 Kernel-Boot 25 (32)
Information 24/08/2019 11:14:39 Kernel-Boot 20 (31)
Information 24/08/2019 11:14:39 Kernel-Boot 153 (62)
Information 24/08/2019 11:14:39 Kernel-General 12 (1)
Information 24/08/2019 10:37:30 WindowsUpdateClient 44 Windows Update Agent
Error 24/08/2019 10:37:30 WindowsUpdateClient 20 Windows Update Agent
Information 24/08/2019 10:36:43 FilterManager 6 None
Information 24/08/2019 10:34:28 Service Control Manager 7045 None
Information 24/08/2019 10:34:24 Service Control Manager 7045 None
Information 24/08/2019 10:34:24 Volsnap 33 None
Information 24/08/2019 10:33:58 Service Control Manager 7040 None
Information 24/08/2019 10:29:11 Service Control Manager 7040 None
Information 24/08/2019 10:25:24 WindowsUpdateClient 43 Windows Update Agent
Error 24/08/2019 10:19:38 DistributedCOM 10016 None
Error 24/08/2019 10:19:30 DistributedCOM 10016 None
Error 24/08/2019 10:19:30 DistributedCOM 10016 None
Error 24/08/2019 10:17:51 DistributedCOM 10016 None
Information 24/08/2019 10:17:11 Power-Troubleshooter 1 None
Information 24/08/2019 10:17:10 Winlogon 7001 (1101)
Information 24/08/2019 10:17:09 Kernel-Boot 32 (58)
Information 24/08/2019 10:17:09 Kernel-Boot 18 (57)
Information 24/08/2019 10:17:09 Kernel-Boot 27 (33)
Information 24/08/2019 10:17:09 Kernel-Boot 25 (32)
Information 24/08/2019 10:17:08 Kernel-General 1 (5)
Information 24/08/2019 10:17:09 BROWSER 8033 None

There is a v strange entry from last night -
Information 23/08/2019 22:48:59 User32 1074 None
which has the details
The process C:\Windows\System32\RuntimeBroker.exe (redacted) has initiated the power off of computer redacted on behalf of user redacted\redacted for the following reason: Other (Unplanned)
Reason Code: 0x0

I took out the PC and user ID. but what is this on about? Its around this time that the PC switched off last night - can't remember the exact time. Its only there and not in the morning log.

Here's the log from around it

Information 23/08/2019 22:49:09 Kernel-Power 107 (102)
Information 23/08/2019 22:49:06 BROWSER 8033 None
Information 23/08/2019 22:49:04 Kernel-Power 42 (64)
Information 23/08/2019 22:49:04 Kernel-Power 187 (243)
Information 23/08/2019 22:49:04 Winlogon 7002 (1102)
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:03 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:02 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Error 23/08/2019 22:49:01 DistributedCOM 10010 None
Information 23/08/2019 22:48:59 User32 1074 None
Error 23/08/2019 22:38:26 DistributedCOM 10016 None
Error 23/08/2019 22:30:41 DistributedCOM 10016 None
Error 23/08/2019 22:30:41 DistributedCOM 10016 None
Error 23/08/2019 22:26:33 DistributedCOM 10016 None
Error 23/08/2019 22:26:33 DistributedCOM 10016 None
Error 23/08/2019 22:22:18 DistributedCOM 10016 None
Error 23/08/2019 22:22:07 DistributedCOM 10016 None
Error 23/08/2019 22:22:07 DistributedCOM 10016 None
Information 23/08/2019 22:14:02 SRTSP 2003 None
Information 23/08/2019 22:14:02 FilterManager 6 None
Information 23/08/2019 22:14:02 FilterManager 6 None
Information 23/08/2019 22:13:57 Kernel-General 16 None
Error 23/08/2019 22:13:19 DistributedCOM 10016 None
Error 23/08/2019 22:13:19 DistributedCOM 10016 None
Error 23/08/2019 22:13:19 DistributedCOM 10016 None
Error 23/08/2019 22:12:34 DistributedCOM 10016 None
Error 23/08/2019 22:12:34 DistributedCOM 10016 None
Error 23/08/2019 22:12:11 DistributedCOM 10016 None
Error 23/08/2019 22:12:11 DistributedCOM 10016 None
Error 23/08/2019 22:12:04 DistributedCOM 10016 None
Error 23/08/2019 22:12:03 DistributedCOM 10016 None
Error 23/08/2019 22:12:02 DistributedCOM 10016 None
Error 23/08/2019 22:12:01 DistributedCOM 10016 None
Information 23/08/2019 22:11:21 Winlogon 7001 (1101)

There are far too many of those DistributedCOM errors for me to be comfortable with.

Here are the PC specs.

OS Name Microsoft Windows 10 Pro
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name redacted
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD Phenom(tm) II X4 955 Processor, 3200 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2001, 08/03/2011
SMBIOS Version 2.6
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASUSTeK Computer INC.
BaseBoard Product M4A87TD EVO
BaseBoard Version Rev 1.xx
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume5
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.17763.652"
Username redacted
Time Zone GMT Summer Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 16.0 GB
Available Physical Memory 10.6 GB
Total Virtual Memory 32.0 GB
Available Virtual Memory 25.0 GB
Page File Space 16.0 GB
Page File I:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Am going to run the 1903 update, since last power off PC has been fine, so I am at a loss.
 
Last edited:

justbaffled

Distinguished
Mar 25, 2012
13
0
18,510
Well Have run the update, thought all was OK, nope. PC still powering down randomly.

Have now stripped and cleaned all the fans, there was some dust but not anything that I'd class as excessive (as thermals were OK).

Been watching the PSU HW monitor, all the lines with the exception of the 12V are steady. The 12V is fluctuating very slightly between 12.003 v and 11.95v, could that be it?
 

PC Tailor

Illustrious
Ambassador
The distributed COM errors will be unrelated. Event viewer isn't great because it shrouds your problem in a million other problems. Did you check reliability history for maybe a bit of a clearer view?

Rails can fluctuate up to 5%. Your 12V rail is barely moving comparitively. As asked previously:
What is your entire system spec including PSU make and model and RAM models? Apologies if I missed it, can't see it anywhere!
 

justbaffled

Distinguished
Mar 25, 2012
13
0
18,510
Well Have run the update, thought all was OK, nope. PC still powering down randomly.

Have now stripped and cleaned all the fans, there was some dust but not anything that I'd class as excessive (as thermals were OK).

Been watching the PSU HW monitor, all the lines with the exception of the 12V are steady. The 12V is fluctuating very slightly between 12.003 v and 11.95v, could that be it?
The distributed COM errors will be unrelated. Event viewer isn't great because it shrouds your problem in a million other problems. Did you check reliability history for maybe a bit of a clearer view?

Rails can fluctuate up to 5%. Your 12V rail is barely moving comparitively. As asked previously:
What is your entire system spec including PSU make and model and RAM models? Apologies if I missed it, can't see it anywhere!

I have checked the reliability history and well there is virtually nothing there. It just states that windows was not properly shut down as I mentioned previously. Obviously it wasn't as the PC just powered off suddenly. There are no other issues reported.

Regarding the specs sorry I am confused here. I posted the PC's config as I thought that was what was needed, This includes the CPU, motherboard, bios etc, but reading through it noticed it does not include the GPU (a 6GB Nvidia 1060) as for the ram - how do I find that out? They are 16gb matched set (or bought as that), but the make and model not a clue.

Is there an easy way to dump a full config?

For some of the other parts that might be important(?).

PSU is an OCZ technology 80 plus white, 600w model OCZ600SXS2

Drives, Samsung HD103SJ, Samsung HD501LJ, Weston digital WD500G2B0A

Optical - blue ray HL-DT-ST-BD-RE BH17NS55

Sorry no idea if this info is of any help.
 

PC Tailor

Illustrious
Ambassador
No it's brilliant info thank you. How long have you had the PSU? OCZ StealthX is a more budget friendly unit and decent enough from my awareness. But it's usually the first port of call to look at for random shut downs.

Are you able to recreate the problem? I.e. does it only occur under load for example? Or only when opening games etc?
If so running in safe mode and seeing what happens may help identify if it's more likely hardware or software.
Did you say you had latest BIOS installed?
 

Colif

Win 11 Master
Moderator
event 41 is created on startup, after the restart. Windows runs a report and checks if the previous shutdown was expected or not. If it finds it wasn't, it creates event 41, Windows doesn't know why it restarted. Unlike what others think, it isn't automatically a PSU error.

I think every pc on earth has DCOM errors :)

With no bsod and only the error 41 showing as evidence anything actually happened, its likely its hardware causing it of some sort.
 
  • Like
Reactions: PC Tailor
Solution
Have you actually gone into the details of the active powerprofile? If your PC is in hibernation, nothing is going to blink, (as it does in sleep mode) and with Windows 10 the resume can look almost identical to a start/ restart.

Two easy ways to tell would be to view all the details of you active power profile, and leave something open the next few times you leave your computer, and see if they come back up the next time you have to start your computer.
 

TRENDING THREADS