BSOD [Kernel security Check failure] in w10 1903

Post here if you encounter any problems or bugs with the software.

BSOD [Kernel security Check failure] in w10 1903

Postby venzo92 » 2019.08.11. 06:40

Hello, last week i've updated the pc to windows 10 1903 and since then i've noticed a constant bsod with the error Kernel security check failure upon shutdown or restart.
after some digging i've found out that hdd sentinel icons were not on the traybar, so i've tried to kill the hdd sentinel process and got instant bsod with the same error.
i've uninstalled hdd sentinel and installed the latest version, but i still get the bsod, if i try to open the exe nothing happens and there's no shortcut on the tray bar

I've also updated motherboard drivers, chipset etc but it was of no avail.
Crash dump has no useful informations, it just says that ntoskrnl caused the crash
Any suggestions on how to fix this issue?

TLDR: updated to windows 10 1903, upon shutdown, restart or killing the hdd sentinel process i get instant bsod
venzo92
 
Posts: 4
Joined: 2019.08.11. 06:11

Re: BSOD [Kernel security Check failure] in w10 1903

Postby hdsentinel » 2019.08.12. 08:42

This sounds interesting. Generally this should not happen with Hard Disk Sentinel, no other user reported anything similar.
Generally Hard Disk Sentinel is safe to use - there may be an issue with a chipset driver (even if updated to latest version).

> if i try to open the exe nothing happens and there's no shortcut on the tray bar
...
> upon shutdown, restart or killing the hdd sentinel process i get instant bsod

Sorry, I do not really understand....
So when you start, "nothing happens" or do you "get instant bsod" ?

If "nothing happens", it means that Hard Disk Sentinel is performing the detection, waiting for one or more device(s) to respond. Generally this should happen very quickly, but if a device is not working properly, a driver is not correct or similar, then this may take very long time or the software may even receive no response at all. This is generally an indication that there is something not stable (just like if the memory test tool may crash upon failed memory).

The best would be track down a bit, verify which device(s) may be affected. Maybe Windows update changed the associated driver too.

If possible, please try to

1) delete the file HDSentinel.ini and then try to re-start. This will re-set the settings to defaults while keeping all statistics/logs. It may be useful to try.

2) disconnect external disk drives, pendrives, memory card readers and further removable storage and then start Hard Disk Sentinel. In theory, they should cause no problems - but try to check, to verify if one may cause troubles.

3) we'd need to see what steps could be done by Hard Disk Sentinel and when it can't continue. That may also point on a device (eg. disk drive) or its controllers (eg. motherboard chipset driver).

For this, please start the software in a special "test" mode. This is generally safe, just logs different steps done by the software to a test file.

For this, please

1) if running, completely close Hard Disk Sentinel by File -> Exit (or by terminating from the task manager)

2) Then you'd need to start HDSentinel.exe with some command line parameters, to create text files to save the communication between the drives / devices and Hard Disk Sentinel itself. For this, please open an elevated command prompt by starting CMD.EXE and select "Run as administrator".

Then navigate to the folder of the software by entering

CD "C:\Program Files (x86)\Hard Disk Sentinel"

and then enter

HDSentinel.exe /ENABLETEST /REPORT /RAID

This should create some text files: a testmode.txt, RAID.TXT and a HDSentinel_5.50_PRO_report.txt into the folder of Hard Disk Sentinel.
The report file may not be created (as it would be created only if the complete detection happens).

If you do not see anything, then please allow it to run for longer time (eg 10-15 minutes), just to be sure.

Please send these files together (maybe compressed or as-is) to info (at) hdsentinel (dot) com as then I can examine the whole detection, investigate the responses. This may hopefully give further ideas about what happens on your system.
User avatar
hdsentinel
Site Admin
 
Posts: 2218
Joined: 2008.07.27. 17:00
Location: Hungary

Re: BSOD [Kernel security Check failure] in w10 1903

Postby venzo92 » 2019.08.12. 10:05

> if i try to open the exe nothing happens and there's no shortcut on the tray bar
...
> upon shutdown, restart or killing the hdd sentinel process i get instant bsod

Sorry, I do not really understand....
So when you start, "nothing happens" or do you "get instant bsod" ?


When i start the pc there's no bsod, and although there's icon of hd sentinel in the task bar, the hd sentinel service is running.
If i open hd sentinel exe to bring up the UI, nothing happens, if i try to close the process from the task manager i get instant BSOD with the same kernel error.
If i try to shutdown or restart the pc while the hd sentinel service is running, i get the BSOD


The best would be track down a bit, verify which device(s) may be affected. Maybe Windows update changed the associated driver too.

If possible, please try to

1) delete the file HDSentinel.ini and then try to re-start. This will re-set the settings to defaults while keeping all statistics/logs. It may be useful to try.

2) disconnect external disk drives, pendrives, memory card readers and further removable storage and then start Hard Disk Sentinel. In theory, they should cause no problems - but try to check, to verify if one may cause troubles.

3) we'd need to see what steps could be done by Hard Disk Sentinel and when it can't continue. That may also point on a device (eg. disk drive) or its controllers (eg. motherboard chipset driver).


HDSentinel.ini was deleted as i've uninstalled the software completely and manually removed the folder before reinstalling the latest version
I've tried to remove all the external drives, but it was of no avail, it kept crashing
First thing i tought after updating windows to version 1903 was the incompatibility of chipsed and/or drivers, so i've upgraded the bios, installed the latest chipset available (apr 19), but it didn't fix the issue



1) if running, completely close Hard Disk Sentinel by File -> Exit (or by terminating from the task manager)

if i terminate from the task manager i get the BSOD, can i disable hd sentinel startup on boot and proceed with part 2?

2) Then you'd need to start HDSentinel.exe with some command line parameters, to create text files to save the communication between the drives / devices and Hard Disk Sentinel itself. For this, please open an elevated command prompt by starting CMD.EXE and select "Run as administrator".

Then navigate to the folder of the software by entering

CD "C:\Program Files (x86)\Hard Disk Sentinel"

and then enter

HDSentinel.exe /ENABLETEST /REPORT /RAID

This should create some text files: a testmode.txt, RAID.TXT and a HDSentinel_5.50_PRO_report.txt into the folder of Hard Disk Sentinel.
The report file may not be created (as it would be created only if the complete detection happens).

If you do not see anything, then please allow it to run for longer time (eg 10-15 minutes), just to be sure.

Please send these files together (maybe compressed or as-is) to info (at) hdsentinel (dot) com as then I can examine the whole detection, investigate the responses. This may hopefully give further ideas about what happens on your system.


will do this in the next days and report back
venzo92
 
Posts: 4
Joined: 2019.08.11. 06:11

Re: BSOD [Kernel security Check failure] in w10 1903

Postby venzo92 » 2019.08.12. 10:08

Oh and if it may be of any help, this is the extended BSOD error code: 0x00000139 (0x0000000000000003, 0xffffdc8284dc6690, 0xffffdc8284dc65e8, 0x0000000000000000).
venzo92
 
Posts: 4
Joined: 2019.08.11. 06:11

Re: BSOD [Kernel security Check failure] in w10 1903

Postby venzo92 » 2019.08.14. 20:50

hello, here's an update, i've ran the exe with the extra commands through cmd, but i'm just getting the RAID.txt file with this inside:
14/08/2019 20:46:41.768 -- Starting --
14/08/2019 20:46:41.771 NumOfDrives: -1 DiskOffsets: 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 RaidInfo:
venzo92
 
Posts: 4
Joined: 2019.08.11. 06:11

Re: BSOD [Kernel security Check failure] in w10 1903

Postby hdsentinel » 2019.08.15. 14:21

Sounds interesting.
If the /ENABLETEST command line option specified, then the testmode.txt file should be saved too. It is more important, the RAID.txt shows nothing now...
Please check - as it would be more interesting.

Maybe if possible, please try to re-start Windows in SAFE mode and try to start Hard Disk Sentinel in that mode, with these command line switches, at least to see some, basic details about the disks, controllers, their drivers - as they may affect the operation in general.
User avatar
hdsentinel
Site Admin
 
Posts: 2218
Joined: 2008.07.27. 17:00
Location: Hungary

Re: BSOD [Kernel security Check failure] in w10 1903

Postby MacMcDonagh » 2019.09.03. 09:38

I also have this BSOD issue, the exact same symptoms. For me it started *before* Windows update 1903, I just installed 1903 and still have the Kernel Security Check Failure. I removed all disks apart from my NVME Intel Optane 900 C drive and the issue persists.
I had been removing/adding disks as I work through some configuration choices.

I have now returned 3 x unallocated NVME Intel drives to the configuration. My system is now all NVME drives, no SATA, no thumb drives and no RAID card.
After starting HDS with the 3 diagnostic switches.
'testmode' now states:
03/09/2019 00:11:41.432 Inquiry: 00 00 06 02 1F 00 00 02 4E 56 4D 65 20 20 20 20 49 4E 54 45 4C 20 53 53 44 50 45 32 4D 58 30 32 30 32 35 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........NVMe INTEL SSDPE2MX020252............................
03/09/2019 00:11:41.432 ==== INQ_F 0 31 0 0 2 -1
03/09/2019 00:11:41.433 SCSI_Readcapacity 0
03/09/2019 00:11:41.433 Bytes : 2000398933504
03/09/2019 00:11:41.433 Sectors : 3907029167
03/09/2019 00:11:41.433 BytePSec: 512
03/09/2019 00:11:41.434 ==== NVME ====
03/09/2019 00:11:41.434 NMVe VPD detect (last printed line)


RAID log now states

03/09/2019 00:11:41.144 Areca detect: 0
03/09/2019 00:11:41.145 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.145 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.145 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.145 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.145 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.146 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.146 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.147 HPT detect: 0 [1]
03/09/2019 00:11:41.147 0000 1C 00 00 00 48 50 54 2D 43 54 52 4C 14 00 00 00 HPT-CTRL
03/09/2019 00:11:41.147 0010 00 24 70 03 00 00 00 00 0C 00 00 00 00 00 00 00 $p
03/09/2019 00:11:41.147 0020 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.148 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.148 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.148 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.148 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03/09/2019 00:11:41.149 RAID controller LD: 0, PD: 0, Handle: 1320, Typ: 255, 31 ms
03/09/2019 00:11:41.150 NumOfDrives: -1 DiskOffsets: 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 RaidInfo:

03/09/2019 00:11:41.434 NMVe VPD SN CVPF627000A72P0PGN _00000001.
03/09/2019 00:11:41.434 ==== NVMe NVMe INTEL SSDPE2MX02 ====
03/09/2019 00:11:41.435 =NVMe start
03/09/2019 00:11:41.435 SGA start
03/09/2019 00:11:41.435 SGA end 1 0 0 0
03/09/2019 00:11:41.436 Addr : Port:1, PathID:0, Target:0, Lun:0 (last printed line)
MacMcDonagh
 
Posts: 2
Joined: 2019.09.03. 09:16

Re: BSOD [Kernel security Check failure] in w10 1903

Postby hdsentinel » 2019.09.04. 09:37

Thanks for your message and sorry for the troubles.

Seems the NVMe controller driver does not work properly: when Hard Disk Sentinel attempts to read back the NVMe identification information, the driver crashes. Very interesting, would be nice to know which driver installed for the SSD, which may require attention.

If possible, please check if there may be an updated, different driver available for the NVMe SSD.

Alternatively, you may try to install Windows "Standard NVM Express Controller" driver for the SSD, just to check if things may be different, hopefully better.

For this, please open Windows Device Manager and under Storage Controllers section, you can find the current NVMe SSD controllers and their drivers. After right click on them, you can select "Update driver" and then "Browse my computer for drivers". Select "Lt me pick from a list of available drivers on my computer". In the list, the "Standard NVM Express Controller" driver should be offered to install.

Hopefully after the change and restart, things may be better....
User avatar
hdsentinel
Site Admin
 
Posts: 2218
Joined: 2008.07.27. 17:00
Location: Hungary

Re: BSOD [Kernel security Check failure] in w10 1903

Postby MacMcDonagh » 2019.09.04. 21:50

Thank you for your response and interest.
I now believe my HDS issue was my error.
Having VROC issues for a new setup, I backed out my BIOS to an old level, but still a VROC array would not PCI enumerate. I found my BIOS had reset to AHCI mode. I set the BIOS back to Intel RST Premium Raid (a VROC requirement), and now HDS works again.
I have a few other disk programs installed, only HDS seems sensitive to the BIOS being incorrectly set. Thanks.
MacMcDonagh
 
Posts: 2
Joined: 2019.09.03. 09:16

Re: BSOD [Kernel security Check failure] in w10 1903

Postby hdsentinel » 2019.09.05. 10:37

Sounds interesting. Personally never encountered issues with VROC testing (when numerous NVMe SSDs used on VROC controller, both in RAID and standalone mode) and no other user reported similar.
May I ask the motherboard model / BIOS version you use? Will try to check.

So if I understand, now, after the change, things seem working correctly? If possible, I'd recommend to please use Report menu -> Send test report to developer option as then I can check the actual situation, examine the NVMe SSDs and how they managed by the VROC controller. This may give some thoughts about improving further and prevent issues in the future.
Thanks!
User avatar
hdsentinel
Site Admin
 
Posts: 2218
Joined: 2008.07.27. 17:00
Location: Hungary


Return to Bug Reports

Who is online

Users browsing this forum: No registered users