In the last few months, my computer has started rebooting seemingly at random. It cuts out instantly, as if I'd pressed the reset button, and boots up as normal. There are no common traits I can identify; sometimes it happens in games, sometimes in applications, sometimes just at the desktop with nothing demanding happening at all. There is no indication of updates, installations, electrical anomalies or temperature spikes that coincide with the reboots, nor are there any BSODs or dump files to be found.

The Event Viewer is singularly unhelpful; I get criticals from Kernel-Power that "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." (Event ID 41, Critical, category 63, keywords (70368744177664),(2)) These messages are typically timestamped about 15 seconds before the log time of the reboot.

On the subsequent restart I'll get an error from EventLog that "The previous system shutdown at was unexpected." (Event ID 6008, Error, no category, keywords Classic) There will also be an information event from Kernel-Boot that "The last shutdown's success status was false. The last boot's success status was true."

My computer runs Win 10 (64-bit), with an Asus Z370-P, an Intel 8700 running at 3.20 GHz, 16 GB of Corsair RAM, and a GeForce GTX 960.

I've tried using Performance Monitor and various other systems to look for the usual signs of instability, but without luck. I'd rather avoid having to rebuild the whole system if at all possible.

Any advice?

5 Answers 5


Analyzing elusive restarts is very hard, because many causes are possible. I list below some steps which might help localize the problem.

Windows tools

  • The Event Viewer (already analyzed by the poster)

  • Reliability Monitor, accessed via Start > View reliability history. A red X denotes a problem, so click on it for details. Clicking "View technical details" gives more information.

  • Undo Windows Automatic Restart to have more time to see the error message (if there is one). This is done in Control Panel > System > Advanced system settings > Advanced > Startup and Recovery > Settings, uncheck "Automatically restart", click OK.

  • chkdsk

  • sfc /scannow

  • Update device drivers (download them where appropriate from the manufacturer's website)


  • Unplug every possible device to reduce the possibilities

  • Check the SMART data of the disk by a utility such as Speccy

  • Check for heating problems of the CPU and GPU. Useful utilities are SpeedFan, HWMonitor and the Open Hardware Monitor, but there are many others.

  • Run Memtest86 or Memtest86+ for as many iterations as you can.

  • Good question - those are all good ideas that I'll try when I get home. :-) Commented Nov 4, 2019 at 13:58
  • 2
    I would add the following to the collection (feel free to add to the answer for completeness if it seems sensible): * Disable automatic reboots without displaying a BSOD * Check for PSU failure (I have experienced "sudden resets" of that kind first hand. It was, however, on an old server if it matters)
    – linux-fan
    Commented Nov 5, 2019 at 21:40
  • Event Viewer - System + EventID 6008 hint on date/time of unexpected reboot. Reliability Monitor nicely summarize events in graph, no details, as there is not much in Win Event Log which is a source. Use date and time (to seconds level) to track in Event Viewer / Administrative events. Interesting ones on Error level. Dumps are missing as event 161 src: volmgr claims dump creation failure. In my case I have ID: 28680 src: PRIVMAN events from app + ID: 0 src: hcmon complaining on unrecognized USB drivers.
    – Tom Silver
    Commented Jan 19, 2022 at 8:34

Please try the following steps:

  • Open event viewer
  • expand Windows Logs
  • click on system to view it
  • right-click on system and select Filter Current Log
  • in Event Sources: select User32
  • change <All Event IDs> to 1074
  • click OK

You'll now have a list of shutdown and reboot events. scroll through them and you should be able to see what process caused which reboot. The information will look like this example:

The Process "C:\Windows\system32\svchost.exe (COMPUTERNAME)" has initiated a reboot on behalf of "NT-AUTHORITY\SYSTEM" for the following reason: "Operatingsystem: Service Pack (planned)" Reason code: "0x80020010" Shutdown type: "reboot" Comment: ""

Here's a picture of the Filter to use in eventviewer, from my german system:

EventViewer Picture

  • 6
    If I understand it correctly, this applies only in case the system reboots "normally". The question describes more like a sudden "hard-reset" which seems to leave no traces on the system beyond Windows recognizing that it did not shutdown cleanly.
    – linux-fan
    Commented Nov 5, 2019 at 21:36
  • @linux-fan i think it's definetly worth a try going through these log informations.
    – SimonS
    Commented Nov 6, 2019 at 9:03
  • 1
    I've gone through the logs in the past, but not with that specific filter, so I'll give it a go just in case. :-) Commented Nov 6, 2019 at 22:33
  • @SimonS I think this just apply for example into a company if you want to know which user did a reboot (in what hour and time) or if was a customer. This is not exactly what Andrew want to know...
    – Marlon
    Commented Nov 10, 2019 at 17:46
  • 2
    @Marlon No, this shows you exactly what process caused the reboot, e.g if your Antivirus Software initiated a reboot, or a service or anything else that is not critical.
    – SimonS
    Commented Nov 11, 2019 at 6:46

It seems like Windows is just as surprised as you are that it's been shut down.

That is often the symptom of a hardware failure, since most kinds of software failures would leave some sort of clue in your event log. (Normally from a BSOD)

Here's a couple things you could try:

  • Try a different power bar.
    Unplug everything but the PC from that power outlet to be sure the problem is the PC itself.
  • Use a power supply tester to see if the PSU is providing the correct voltages.
  • If you have a spare PSU, try running the PC from that one instead.
  • Run a temperature monitoring app that records temperature to a file. Some CPU models can cause an instant system shutdown/reboot if they get too hot.
  • Try to run a live OS from a usb stick without storage drives and just the bare-minimum hardware connected. If the problem still occurs then you at least narrowed it down to your CPU, motherboard, RAM, or PSU.
  • Run a CPU & GPU intensive stress test to see if you can reproduce the shutdown quicker. (Will help you narrow down the problem & save time troubleshooting.)
  • I addition of tools that @Romen said I should you consider options 1) and 3) from these live CDs. makeuseof.com/tag/5-best-rescue-disks-windows-system-restore They are very helpfull to diagnose hardware failures.
    – Marlon
    Commented Jan 2, 2020 at 14:12
  • @Andrew Perry - I think the final reply for you are the addition of 1st) and 2nd) replies marked with 3 points.
    – Marlon
    Commented Jan 2, 2020 at 14:23

Alternate suggestion: the issue is related to software installed to your system.

I would reboot into safe mode and allow the computer to run without shutting down for an amount of time longer than the average it takes to reboot. If it does not unexpectedly reboot, start disabling an application/service that starts up with Windows. These can be found in Task Manager and Services; you'll want to start with 3rd party services that come with user-installed applications.

To reboot into safe-mode, run msconfig and tick 'Safe mode' in the Boot section. Untick it and reboot to turn off safe mode when you're done diagnosing.

To open Task Manager, run Tskmgr.exe. To open Services, run services.msc.

In the past I have attempted to load a custom library to an older application and would have the system freeze seconds after loading, with the event viewer similarly having no useful information.


The most possible symptoms of unexpected reboot are hardware failures, and they do random or frequently depending on usage. For example in this case could be memory...

I will try to check with these live CD tools here

You have to do by exclusion of hardware and finally if you don't get succesfully try some tools like Live CDs.

The first one and second one are great...

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .