Windows 10: PC Keeps crashing randomly - No bluescreen - assorted event viewer errors - PLEASE HELP!

Hi. The issue:My PC for the past month has randomly been shutting down and self rebooting immediately after. There is no bluescreen, there is no sound, no error. My monitors just go black and the PC fans start up again after 1 second. It's very jarring. What I've tried:-underclocking the CPU-Fixing hundreds of event viewer errors including loads of "The application-specific permission...", although I've checked event viewer after a crash and there's loads of warnings within the span of a minute-Lowering RAM speeds-Updated literally every driver I have-Reinstalled Nvidia drivers t

:)

 

Event Viewer - Kernel Power 41 - Bluescreen Timeline

I am trying to debug a bluescreen I've been having.

I am looking through event viewer and I believe I've narrowed down potential events related to the crash, but I need a reference point so I can refer to the timestamps on the events.

Kernel Power 41 is within this list.

When does the Kernel Power 41 Error occur in the span of a BSOD?

Is it logged to event viewer after rebooting from a bluescreen? Does it occur the moment a BSOD finishes collecting errors? Or does it occur at a different time?

Additionally, are there any events that can act as reference points in the timeline of a bluescreen? Does event viewer even log events during a bluescreen's "collecting" phase?

Thanks.

 

"New" PC crashes: No video signal,no Bluescreen, no Event Viewer entry

I guess according to that article you linked memtest86+ is the better option. Okay, another quick question: I can't seem to find where to change the number of passes in memtest86+:





Or does it run indefinitely? I want to run it overnight. I've seen how it's done in memtest86 (unless that video is out of date), but not memtest86+. PS: Sorry for not replying to everyone. *Sad

 

"New" PC crashes: No video signal,no Bluescreen, no Event Viewer entry

Thanks, I'll be looking into that, need to type up a post for that other sub-forum first.

My first thought too of course. One thing I do want to point out though: All the Event Viewer entries you mentioned happened on restarting the PC after the crash, not "right before the crash". I admit, I've only recently started looking at the "Windows Logs > System" section of the Event Viewer, as opposed to just "Administrative Events". However, I haven't seen any obvious entries that happened right before crashing. Most of the time, the most recent entry before a crash happened minutes prior. The most extreme case is a crash where the Event Viewer has NOTHING preceding the crash at 13:22:



(The PC was turned off at ~4:30 in the morning, then booted up around ~13:22. Then again on 13:28.) ...And I checked the "Windows Logs" sections too, the only entries I could even find were under "Windows Logs > Security", and it was just generic phrases like "Special privileges assigned to new logon", "An account was successfully logged on", etc... which doesn't seem related, I think.

This is actually the Event Viewer log from the crash shown in the video here, while no peripherals other than keyboard and monitor were attached. (Also no internet.) In that case, there isn't a single entry in Event Viewer between bootup and crash, except "Windows Logs > security". All other logs only recommenced after restarting the PC after the crash. So... yeaargh. *Sad

"volmgr" and "kernel power" are definitely referring the crash that happened earlier, however to my (admittedly untrained) eyes, "vbox" ("Oracle VM Virtual Box", perhaps?), "tablet service" (presumably my 2008 Wacom drawing tablet, or Windows's built-in drivers for handling tablets), and "win32k" (maybe the mouse?) happen a lot more frequently on bootup (always? I'd have to double-check that), this isn't usually followed by a crash. And crashes aren't limited to bootup either. So my guess would be to dismiss these as unlikely culprits. I may be wrong of course. - - - Updated - - -

Okay, thanks!

@NTN, I've installed OCCT, but haven't run it yet. The test I should be running is "Test -> Power", right?

Default duration for all tests was "infinite / Test will run until cancelled". ...Yeah no. *Eek What duration is recommended? 10 minutes? 30 minutes? Again, is OCCT safe? I've also noticed that in Settings > Security, the default for "stop on error / critical temperature / stop of WHEA error" is "disabled". I think I'll turn all those on, just to be safe. "Stop any running test 90°C" is the default temperature for that, that's sensible, right?

It would be quite idiotic if I damaged my system in pursuit of finding errors. ^_^;; Is running "Test -> Power" enough, or should I run other tests too? Are there any other settings I should change from the default? *Think