Windows 10: KERNEL_SECURITY_CHECK_FAILURE after USB short

Update 1/14/2017: The thread has been marked as "solved", however the drives with the installations lost their partition information after BSODs, so there was no actual resolution to this issue.

Went to plug in my USB mouse and plugged it into a broken USB port causing my system to short out. The system boots up with several "KERNEL_SECURITY_CHECK_FAILURE" screens, and an automatic repair results in another blue screen, some kind of power up related screen. I can get to a "restore checkpoint" feature, but the system freezes during the restore. After a hard reset, the computer might boot up. I am currently on the machine and it is running, but I am scared to turn it off or restart.

:)

 

Windows 10 installation bootable media USB gives 'KERNEL_SECURITY_CHECK_FAILURE'

Recently, 32 bit version of Windows 10 successfully installed on windows 7 laptop. All running fine.

I have installed a full 8Gb of memory into the laptop, expecting to be able to install 64 bit version of windows 10.

Computer is still working fine with 32 bit upgrade version of windows 10 and this 8Gb of memory (although only 3.4Gb being used).

Downloaded media creation tool, and made bootable USB for installing 64 bit windows 10.

However, after booting from this USB, the windows logo appears for short while followed by

Sorry need to restart.... KERNEL_SECURITY_CHECK_FAILURE, and it shuts down.

It still boots the old 32 version from hard disk happily.

Any ideas what the problem with the bootable USB is?

 

KERNEL_SECURITY_CHECK_FAILURE on USB Tethering

Hello I'm getting a blue screen with KERNEL_SECURITY_CHECK_FAILURE when I plug in my one plus5 phone and activate "USB Tethering" on the phone. After the update my window 10 ,the system is automatically restart again and again

 

Hi MrFreeman,

I would suggest to try the USB mouse on a different system to see if it is damaged after you connected it in the broken USB.
It is also a good idea to update the USB mouse drivers or reinstall them.
Code: 0: kd> lmvm FLxHCIc Browse full module list start end module name fffff801`d9d90000 fffff801`d9dd2000 FLxHCIc T (no symbols) Loaded symbol image file: FLxHCIc.sys Image path: \SystemRoot\System32\drivers\FLxHCIc.sys Image name: FLxHCIc.sys Browse all global symbols functions data Timestamp: Thu Jul 30 05:14:53 2015 (55B996AD) CheckSum: 0004C403 ImageSize: 00042000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

Thank you for the reply,

The mouse works fine on several machines, however I am confused with the error you posted which is now almost over a year old. My BSODs are very recent, within the last few days, and this did not start back in 2015 when I still was running Windows 7.

 

That is the date of the mouse driver, not when the dump was created. There is only one dump iun the zip file you uploaded, dated 6/19 at 6:55PM.

If you are using a disk cleaning program like CCleaner, stop until this problem is resolved. If usiong CCleaner, set it up as follows:

Attachment 86212

 

Ahha, I see. Interesting. Thank you for clarifying! Perhaps I have BSOD dumps disabled somewhere? I am 99.9% certain if I restart I will get the series of them again.

The mouse was unplugged, in fact I unplugged everything but the battery when attempting to boot back up into Win10 and it received the various BSODs. I can film it if necessary, however, Windows 10 BSODs seem to very lacking in any kind of information.

 

The UI change of the BSOD is to make it less scary for many users, it contains the same but with less text.

 

So is there any further information I can provide to assist in fixing the repeated BSODs I will get on my next reboot?

 

You need to provide a new zip AFTER BSOD have occurred, the current has been analyzed

 

There are no more startup BSODs, now it's just seemingly random BSODs...

 

Updated with BSOD that led into a startup BSOD

 

This driver is causing crashes, but I cannot relate it to any installed software.
Driver Reference Table - excsd.sys

Code: ffffd001`03b2a118 fffff801`57c42418Unable to load image \SystemRoot\system32\DRIVERS\excsd.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for excsd.sys *** ERROR: Module load completed but symbols could not be loaded for excsd.sys excsd+0x12418 7: kd> lmvm excsd Browse full module list start end module name fffff801`57c30000 fffff801`57ca9000 excsd T (no symbols) Loaded symbol image file: excsd.sys Image path: \SystemRoot\system32\DRIVERS\excsd.sys Image name: excsd.sys Browse all global symbols functions data Timestamp: Thu Jun 11 21:07:45 2015 (5579DC81) CheckSum: 000237D8 ImageSize: 00079000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Axe0, I found this:

ExpressCache is in services.txt.

Code: SERVICE_NAME: ExpressCache DISPLAY_NAME: ExpressCache TYPE : 10 WIN32_OWN_PROCESS STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0[/quote]

 

Had another several BSODs happen since, and am now getting corrupted software errors. I'm really hoping none of my drive data is getting corrupted from all this sudden stop of disk activity.