Windows 10: Kernel_Security_Check _Failure BSOD

Real quick I can't find anything in the logs that could cause a shutdown/restart crash.
The last power problem
Code: Event[6823]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2016-01-03T00:39:42.539 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: EnthooLuxe Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] The last bluescreen
Code: Event[6181]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2015-12-31T00:47:53.444 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: EnthooLuxe Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe001cc052060, 0xffffd0010a5fe890, 0xffffe001dbc86bd0). A dump was saved in: C:\WINDOWS\Minidump\123115-6593-01.dmp. Report Id: d5e241ad-6dd9-4b4d-9cfa-2c6b2049b0e9.[/quote] Remove the bypasses/cracks on your system before proceeding!
Code: Event[6801]: Log Name: System Source: Service Control Manager Date: 2016-01-02T22:59:00.571 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: EnthooLuxe Description: A service was installed in the system. Service Name: WinDivert1.1 Service File Name: C:\Program Files\KMSpico\WinDivert.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:[/quote] Forum rules

 

The last bluescreen
Code: Event[6181]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2015-12-31T00:47:53.444 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: EnthooLuxe Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe001cc052060, 0xffffd0010a5fe890, 0xffffe001dbc86bd0). A dump was saved in: C:\WINDOWS\Minidump\123115-6593-01.dmp. Report Id: d5e241ad-6dd9-4b4d-9cfa-2c6b2049b0e9.[/quote] Remove the bypasses/cracks on your system before proceeding!
Code: Event[6801]: Log Name: System Source: Service Control Manager Date: 2016-01-02T22:59:00.571 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: EnthooLuxe Description: A service was installed in the system. Service Name: WinDivert1.1 Service File Name: C:\Program Files\KMSpico\WinDivert.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:[/quote] Forum rules[/quote]
Hmm, I had no idea what Kmspico was, it has been removed (Will upload another scan by the dm log collector, if requested). Any ideas to what could have caused the restart from earlier? I had to uninstall both HW Monitor and Aida64 as they started to be unresponsive and had processes that were unstoppable (which also resulted in the computer being unable to restart and would have the be shut off manually)

The computer is going to be constantly on for the next 72-96 hours, I'll report back if anything happens

 

Looking at the logs there doesn't seem to be any reason for a sudden shutdown.
It could however be caused by many other reasons that aren't logged.

Usually a sudden shutdown/restart is being caused by

• a bad PSU,
• wrong 3.3v, 5v or 12v values in the BIOS,
• a circuit problem.

Sometimes it is also caused by

• (corrupted) tasks in the task scheduler that says to shutdown/restart the system for some unknown reason,
• power issue in a component (too much or less power),
• overheating/overheated hardware where in the BIOS is defined to shutdown/restart the system after a certain temperature has been reached.

This includes also logged events.

 

Reporting back. Safe to say my problem has been resolved. What I did to resolve it:

I had carried over a windows install from z97 to z170 (instead of installing a fresh copy, which you should always do, I was lazy). I went into device manager and uninstalled all drivers and devices that were no longer in use (everything from a old usbs to the 4670k to drivers for the z97 platform). I also removed many unused/not needed scheduled tasks from the task scheduler ( For example, start menu reviver still had a task that would always fail, as expected).