Windows 10: Keyboard (tapping print screen + f12) causes PC to shutdown.

Thanks for the suggestions both of you!

I did some testing to determine if this issue is related to software, hardware or both.

I used 2 PCs:
1) My problematic PC
2) Another PC in the house.
Both of these are running Windows 10 Professional X64.

I used 3 keyboards:
1) KUL ES-87 (Keyed Up Labs - ES-87 Tenkeyless Mechanical Keyboard)
2) Leopold 750R
3) Regular full sized OEM keyboard which was part of a package.

The first 2 keyboards listed are "tenkeyless" or TKL boards which only 87 keys (basically no numberpad). The other keyboard is just a regular 104 ANSI that was included with a prebuilt PC.

I tried to be as scientific as possible, each keyboard was tested individually and in the same (recommended) USB port. The goal was to try to replicate this error by hitting F12 and then subsequently hitting Print Screen.

Keyboards: Other PC My PC My PC (cleanboot) Kul ES – 87 No error Error - restart No error Leopold 750 R No error Error - restart No error Regular OEM No error No Error No error.
First thing is that the other PC with all keyboards seems to be normal. It doesn't seem like the keyboards (at least the hardware itself) are causing the crashes.

On my PC, both the TKL boards seem to be problematic. However, cleanboot is okay for all three keyboards.

I think this is because the TKL boards have similar implementations and probably send the same keycodes - at least for the involved keys. What I think is happening is that the input keycodes (F12 and then Print Screen) are triggering/causing a problematic service or driver to fail. Having no errors in cleanboot and the other PC seems to support this.

I'm not sure if this reasoning is 100% and I don’t want to steer us in the wrong direction but are there any sort of problematic services or things like that have stuck out in the logs?

Also thanks for all your help so far!

 

Have you ever installed a driver for any of the keyboards? Seeing as it works okay when you Clean Boot, follow the directions in the Clean Boot link I gave you to isolate the cause.