Windows 10: kernel_security_check BSOD occur repeatdly in random times

tomerst said:

I ran verifier and couldn't boot, had to use system restore

When people use Windows driver verifer we would like the process to have less distress and make the process easier. Please explain the difficulties that you encountered turning off Windows driver verifier and needing to use restore.

Were you able to navigate to startup options?
Did it allow you to restart?
Were you able to choose safe mode with command prompt?
Were you able to enter the command verifier /reset?
Did the command not turn off Windows driver verifier?
Were you able to navigate to command prompt?
Did the box open with title bar: Administrator: X:\windows\system32\cmd.exe?
Were you able to enter the command: verifier /bootmode resetonbootfail
Did the command not turn of Windows driver verifier?

Code:

BugCheck 1A, {41201, ffff87002de7f410, b1, ffffa3864da14530}Page 20ba6c not present in the dump file. Type ".hh dbgerr004" for detailsProbably caused by : memory_corruption

Code:

MEMORY_MANAGEMENT (1a)    # Any other values for parameter 1 must be individually examined.Arguments:Arg1: 0000000000041201, The subtype of the bugcheck.Arg2: ffff87002de7f410Arg3: 00000000000000b1Arg4: ffffa3864da14530Debugging Details:------------------Page 20ba6c not present in the dump file. Type ".hh dbgerr004" for detailsBUGCHECK_STR:  0x1a_41201DEFAULT_BUCKET_ID:  CODE_CORRUPTIONPROCESS_NAME:  WerFault.exeCURRENT_IRQL:  2ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8031cc2b5cd to fffff8031cbf73f0STACK_TEXT:  ffff8e80`e9bb0748 fffff803`1cc2b5cd : 00000000`0000001a 00000000`00041201 ffff8700`2de7f410 00000000`000000b1 : nt!KeBugCheckExffff8e80`e9bb0750 fffff803`1cb12a53 : ffff8700`2de7f410 00000000`00001000 00000000`000000b1 ffffa386`00000000 : nt!MiGetPageProtection+0x1183cdffff8e80`e9bb07a0 fffff803`1cb125ae : 0000005b`00000000 ffffa386`4daf1000 00000000`00000000 ffffa386`50d7bcc0 : nt!MiQueryAddressState+0x2b3ffff8e80`e9bb0830 fffff803`1cf17fef : 000001e0`00000000 00000000`00000001 00000000`00000000 0000005b`cfe82000 : nt!MiQueryAddressSpan+0x12effff8e80`e9bb08e0 fffff803`1cf17891 : ffff5687`ba4d1de1 ffffa386`50d7b7c0 0000005b`cfdd8770 00000000`00000000 : nt!MmQueryVirtualMemory+0x74fffff8e80`e9bb0a40 fffff803`1cc02313 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`e00019ff : nt!NtQueryVirtualMemory+0x25ffff8e80`e9bb0a90 00007ffd`a6695814 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x130000005b`cfdd84c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`a6695814

WerFault.exe


hal
storachi
dxgkrnl
nvlddmkm
ntfs
fltmgr

Code:

ffff8e80`e9bae838  fffff80d`17196730Page 17c1af not present in the dump file. Type ".hh dbgerr004" for detailsPage 17c1af not present in the dump file. Type ".hh dbgerr004" for details*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x1e6730

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx Get from OEM for laptops

1) Uninstall all Nvidia drivers/software
The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website.

When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

Just a quick response - the driver that Driver Verifier found for you is from an Avatron Software Air Display
http://www.avatron.com/support/downloads/

Perhaps the driver needs updating.

Once you have updated, you can try Driver Verifier again and see if any other drivers are found to be a problem.

Hi zbook, thanks for joining in-
I ran verifier countless times during this troubleshooting so I was not alarmed by testing it one more time, this time I used this sites tutorial step by step.
1) In non of my attempts I was able to boot to safe mode.
2) Usually typing verifier /reset at command prompt successfuly disabling it.
3) /bootmode resetonbootfail executed as wanted but I couldn't boot afterwards aswell, moreover, trying to use /reset from that point had to effect, hence I had to use system restore (which was no issue since I created a recent restore point)

I must agree though in this case using Driver Verifier is a stressful process at first, since you don't have a sense of control over it.

Other findings from the prior event log:

Code:

Event[277]:  Log Name: System  Source: Microsoft-Windows-Eventlog  Date: 2017-05-24T16:37:02.970  Event ID: 22  Task: Service startup  Level: Error  Opcode: Info  Keyword: Service availability  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Tomer-PC  Description: The event logging service encountered an error while initializing publishing resources for channel AirSpaceChannel. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.

Code:

Event[278]:  Log Name: System  Source: Microsoft-Windows-Eventlog  Date: 2017-05-24T16:37:02.995  Event ID: 22  Task: Service startup  Level: Error  Opcode: Info  Keyword: Service availability  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: Tomer-PC  Description: The event logging service encountered an error while initializing publishing resources for channel DebugChannel. If channel type is Analytic or Debug, then this could mean there was an error initializing logging resources as well.

Code:

Event[975]:  Log Name: System  Source: Application Popup  Date: 2017-05-31T20:01:55.251  Event ID: 26  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Tomer-PC  Description: Application popup: TslGame.exe - Application Error : The instruction at 0x00007FF97BB90E67 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.Click on OK to terminate the program

Code:

Crash dump initialization failed!

Code:

Startup Repair failed.

Code:

Event[980]:  Log Name: System
  Source: Display
  Date: 2017-05-31T20:34:42.921
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Tomer-PC
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

Event[1928]:  Log Name: System
  Source: Display
  Date: 2017-06-13T01:09:12.930
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Tomer-PC
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.

Please make sure that there is no over clocking.

Sometimes there are problems in the bios that produce bsod.

The bios in your computer: BIOS Version/Date American Megatrends Inc. F4e, 6/28/2013


Please check to see if this is the most up to date version.


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


Sometimes there can be failure to boot after resetting the bios.

So please make sure your files are backed up. Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free
And please create a restore point.


Please post an updated zip file so we can troubleshoot the logs: BSOD - Posting Instructions - Windows 10 Forums