Solved BSOD: kernel_security_check_failure windows 8.1 - 64

UPDATE 24May15: it's looking like the removal (uninstall) of Windows (optional) Update KB3022345 has solved the BSOD and File Corruption Problems.

I am amazed/angry that MS put out an update - even if optional - that can cause such major problems! Just another disheartening example of the quality of MS and their ability to get to grips with such things. If they need to put out such updates they should find another and better means to do this, or create a third update category – such as “only for certain computers” or some such name! It gives little encouragement for the coming new version – there is simply a mentality problem at MS towards the people who use their products!

I am hoping everything is now okay and marking this thread as solved


UPDATE 23May15:

It “might be possible (????)” that I am on the right track to solving this problem – but at this moment it is only a “unclear might” – as I am a complete novice at this

The problem might be (or now might have been) caused by a recent WINDOWS UPDATE

I found the following: Windows 7: Windows 7 update (KB3022345) causing corrupt files
Windows 7 update (KB3022345) causing corrupt files - Page 2 - Windows 7 Help Forums

and through this post I found this: Windows 8 update (KB3022345) causing corrupt files
The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files

Checking my Windows 8.1 Update History I saw that I also had this (optional) Update KB3022345

The Tech Cookbook article said:

The two corrupt files are:

Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]”telemetry.ASM-WindowsDefault.json” :
Found: {l:32 b:X5paRQlbw2v00Wlbryh/shTCSngPuV5NMY9IyDEs/HI=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json do not match actual file [l:24{12}]”utc.app.json” :
Found: {l:32 b:JUC5i/5VApK5qT3QXfHsgN0T00T8uKFsDtICSI+MdPc=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

And offered a download solution (but with a warning):

SFCFix Script
Warning: this fix is specific to the above corruptions only, do not run these fixes if you do not have these corrupt files.


Since I was not sure if the corrupt files were the same ones for me – I decided not to use this SFCFix Script just yet – instead I went to Update History and chose the uninstall option for this update (since it was an optional update anyway – although I do not yet know what this update was for!!!)

I do not know if this was the right action to take - but due to my lack of tech no-how - I decided this might be the safest as I did not want to make things worse ??????

After the computer restart I ran another “sfc /scannow” = no corrupt files found !

BUT – it is too early to say if this was the problem – because I have run other sfc /scannow since the BSOD last Monday and not found any corrupt files – but later – after another scan – corrupt files were found (with sometimes being fixed – other times having to do an additional Dism /Online /Cleanup-Image /RestoreHealth)

I will first have to run several more sfc /scannow today and tomorrow before I am sure on this???????

STILL NOT SOLVED - BUT ????????

* * * *

just checked KB3022345

Notice
The current version of this hotfix, Version 2, was published on May 6, 2015. The previous version of this hotfix was Version 1.005. Both versions provide the same functionality and protection except that Version 2 includes a minor update to support devices that do not contain U.S. English language files. However, the current hotfix is not a compatible upgrade to Version 1.005 and may cause an error (800F0922) if it is installed over the old version. We recommend that you install this hotfix if you have not already installed it. If you have installed the original version of this hotfix and you want the added functionality, we recommend that you wait for an upcoming version that will be a compatible upgrade to either version.

This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.　


https://support.microsoft.com/en-us/kb/3022345
--------------------------------------------------------------------------------------


UPDATE 22May15 - -Problem not solved - REQUEST URGENT HELP

(Please also see update in my last post)

request help with kernel_security_check_failure from today (18/05/2015)

DM Log collector Tool has been done - result in attachment (hope there is no information that should not be put online!)

also did a sfc /scannow after = corrupt files found - unable to repair

scan CBS log also in attachment
(log was too large to upload - have split it into 2 - CBS_2 is the part covering today - CBS_1 covers before todays date 18May15)

Windows 8.1 64 Bit

my thanks

PS: experience/knowledge in this area is limited - have a little past experience with blue-screens but I am still very limited

DISM /Cleanup-Image - successful

Just ran a DISM /Cleanup-Image and was informed that this was successful

So at least the file corruption is resolved – for now – but why/what caused this? How to resolve whatever the problem is???



Are Driver update software’s (such as SlimDrivers) reliable for finding a out-dated/incorrect driver?

Thanks again

SFC /scannow found corrupt files again

After a successful DISM /Cleanup-Image yesterday – another sfc /scannow run today (next day) once again found corrupt files – although it repaired them this time!

Clearly there is something wrong in system – but I don’t know what (driver? which?) - or how to find the problem as I have too little technical knowledge!!


Any help out there, really appreciate it - and many thanks


UPDATE - one day later (20 May) - just ran another sfc /scannow = no corrupt files found

History recap: Monday 18 May: BSOD = kernel_security_check_failure
sfc /scannow = corrupt files found = unable to repair
later ran: DISM /Cleanup-Image = successful
Tuesday 19 May: sfc /scannow = corrupt files found = repaired
Wednesday 20 May: sfc /scannow = no corrupt files found


UPDATE-2 (20may) just ran another sfc /scannow = corrupt files found - unable to repair


UPDATE-3 (22 May) PROBLEM UNRESOLVED

sfc /scannow finds problems - sometimes can repair them - other times I have to do a DISM /Cleanup-Image - luckily up to now I have managed to keep repairing - however, problem (corrupt files) keeps returning

request urgent help