BSOD, KERNAL SECURITY CHECK FAILURE, Please Help

AlexHamilton · 25 Apr 2020

Windows 10 Ver 1809 (OS Build 17763.1158)
Cpu = i5-4690K, 16gb ram, Asus P5Q

Hello all,

My computer has been quite slow lately and constantly giving me a BSOD.
Stop code: KERNAL SECURITY CHECK FAILURE

I've tried doing a check disk scan and it found some faults that it cannot fix. I have also tried to update to Windows Ver 1909 but after it finished updating, the PC kept rebooting when I tried to login. (Also very slow boot).
So I then did a system restore back to Ver 1809. Everything works like before again but it still gives a BSOD every so and then with the same code.

Included is the V2 log report and I also included the chkdsk log.

Please let me know what I should do. Thank you.

zbook · 25 Apr 2020

Hi AlexHamilton,

Welcome to the Ten forums BSOD forum.

Run the DM log collector and upload results into this thread:
BSOD - Posting Instructions

Please make sure images are posted for all steps / tests:

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) Sometimes there are problems in the bios that produce BSOD

15) To ensure that there are no improper bios settings please reset the bios

16) Sometimes there can be failure to boot after resetting the bios

17) Backup the computer files to another drive or to the cloud

18) Make a free backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
Backup and Restore with Macrium Reflect

19) Create a brand new restore point.
Create System Restore Point in Windows 10

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)

20) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

21) Uninstall Avast using the applicable uninstall tool:
Avast Uninstall Utility | Download aswClear for Avast Removal

22) Uninstall Malwarebytes using the applicable uninstall tool:
https://downloads.malwarebytes.com/file/mb_clean

23) Make sure Windows defender is on

24) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

25) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
http://knowledge.seagate.com/article...S/FAQ/202435en

26) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

27) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

28) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

29) Download and install Minitool Partition Wizard > click launch > post an image of the results into this thread
https://download.cnet.com/MiniTool-P...-10962200.html

30) Find a flash drive that you can format (> or = 8 GB)

31) Create a bootable Windows 10 iso 1909
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

32) Download a Windows 10 is 1809 to the desktop:
https://heidoc.net/joomla/technology...-download-tool

33) Read these links on Windows driver verifier:

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

(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

34) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

35) Make sure each drive is tested with each:
a) HD Tune
b) Sea Tools for Windows
c) Chkdsk /r /v

36) These steps / tests can be ran overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test
c) Chkdsk /r /v

AlexHamilton · 26 Apr 2020

DM log attached and Here are steps 1-12, and apology for the change log I attached in first post. It was the sfc scan log.

Attachment 276331

Microsoft Windows [Version 10.0.17763.1158]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.1158

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.1158

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
833024 file records processed.
File verification completed.
32868 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
42766 reparse records processed.
1123770 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
42766 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
145374 data files processed.
CHKDSK is verifying Usn Journal...
40083672 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

314075320 KB total disk space.
232393368 KB in 523932 files.
384860 KB in 145375 indexes.
0 KB in bad sectors.
964360 KB in use by the system.
65536 KB occupied by the log file.
80332732 KB available on disk.

4096 bytes in each allocation unit.
78518830 total allocation units on disk.
20083183 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\LOC-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\LOC-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

zbook · 26 Apr 2020

First scannow:

Code:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Second scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Run sfc /scannow again and post results into the thread.

Please upload DM directly into the thread (similar to V2 in the opening post)

Open administrative command prompt and copy and paste:

Code:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Find the new text file on the desktop > post a share link into the thread using one drive, drop box, or google drive.

Post a share link for C:\Windows\Logs\CBS\CBS.log using one drive, drop box, or google drive.

AlexHamilton · 26 Apr 2020

Here is the Sfc scan and DM log attached. Also the sfclog and CBSlog

Microsoft Windows [Version 10.0.17763.1158]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

C:\WINDOWS\system32>

zbook · 26 Apr 2020

Third scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Code:

2020-04-25 23:39:11, Info                  CSI    00005969 [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.json from store
2020-04-25 23:39:11, Info                  CSI    0000596b [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.txt from store
2020-04-25 23:39:11, Info                  CSI    0000596d [SR] Repair complete
2020-04-25 23:39:11, Info                  CSI    0000596e [SR] Committing transaction
2020-04-25 23:39:11, Info                  CSI    00005973 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Code:

2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.json
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.txt
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml
2020-04-25 23:24:33, Info                  CBS    (p)	CSI Payload Corrupt	(w)	(Fixed)	amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1
2020-04-25 23:24:33, Info                  CBS    
2020-04-25 23:24:33, Info                  CBS    Summary:
2020-04-25 23:24:33, Info                  CBS    Operation: Detect and Repair 
2020-04-25 23:24:33, Info                  CBS    Operation result: 0x0
2020-04-25 23:24:33, Info                  CBS    Last Successful Step: Entire operation completes.
2020-04-25 23:24:33, Info                  CBS    Total Detected Corruption:	20
2020-04-25 23:24:33, Info                  CBS    	CBS Manifest Corruption:	0
2020-04-25 23:24:33, Info                  CBS    	CBS Metadata Corruption:	0
2020-04-25 23:24:33, Info                  CBS    	CSI Manifest Corruption:	0
2020-04-25 23:24:33, Info                  CBS    	CSI Metadata Corruption:	0
2020-04-25 23:24:33, Info                  CBS    	CSI Payload Corruption:	20
2020-04-25 23:24:33, Info                  CBS    Total Repaired Corruption:	20
2020-04-25 23:24:33, Info                  CBS    	CBS Manifest Repaired:	0
2020-04-25 23:24:33, Info                  CBS    	CSI Manifest Repaired:	0
2020-04-25 23:24:33, Info                  CBS    	CSI Payload Repaired:	20
2020-04-25 23:24:33, Info                  CBS    	CSI Store Metadata refreshed:	True
2020-04-25 23:24:33, Info                  CBS

AlexHamilton · 26 Apr 2020

Thank you Zbook. Looks like the corrupted files are now fixed. Should I continue along the steps or see if I still encounter anymore BSOD first?

zbook · 26 Apr 2020

Please continue with all steps.

The steps should fix the BSOD.

The bonus would be the upgrade failure.

MrPepka · 26 Apr 2020

Update Windows 10 to version 1909 - https://support.microsoft.com/en-us/...date-assistant

AlexHamilton · 27 Apr 2020

Steps 13-17 = Went into bios and reverted to default settings, no overclock now

Step 18 = Created a backup usb

Step 19 = Created new restore point, Reset bios to default settings

Step 20 =
Attachment 276574
Attachment 276575

Step 21 = Uninstalled Avast

Step 22 = Uninstalled Malwarebytes

Step 23 = Windows Defender is ON

Step 24 =
HD Tune Pro
Drive C:
Attachment 276576 Attachment 276577 Attachment 276578

Drive G:
Attachment 276579 Attachment 276580 Attachment 276581

Step 25 =
Seatools
Attachment 276582

That's all I've done so far. Will continue overnight.