Unexpected Shutdowns, Event 41 Category 63

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

i've mentioned before that i am extremely anti-stress testing, i don't see the point it thrashing components to death, especially when the issue is happening with absolutely no stress on the system at all. if i was crashing out during heavy gaming it could be worth it, but i am loathe to stress anything, especially for 48 hours.

Thanks for the info, Ztruker.
To be honest, i'm still thinking this is a hardware issue. The last time it crapped out on me, it started the reboot process and quit after a second or two about three times before fully powering up again; in my mind, that would mean that it's probably not driver/software related as it barely got to loading the BIOS. I've had HWInfo running for hours over several days though, and there's nothing that jumps out to me as to being a power or heat problem.

Looking at the original details posted for the Event 41, I would lean towards hardware. The machine rebooted without enough time to record any information about any error codes. This makes it more likely to a hardware event than a software event. I would suspect something like a NMI ( Non-Maskable Interrupt) . This could be caused by a driver, the hardware rebooted before the OS could write anything to disk which is how the event captures some of the data it displays, in this case there really wasn't anything written that was captured.