[SOLVED] Random IRQL_NOT_LESS_OR_EQUAL (and others) BSOD

Sep 28, 2019
4
0
10
I had this problem in my laptop from months & I couldn't figure it out, The system starts normaly & I'm able to use my laptop but it randomly crashes, showing IRQL_NOT_LESS_OR_EQUAL , KERNEL_SECURITY_CHECK_FAILURE BSOD & others
I tried running a memory test, no errors
Tried updating bios & drivers, still the same
Tried changing my HDD (which means reinstalling windows 10 too) still the same, I even tried downgrading to windows 7.
Tried using "sfc.exe /scannow " & It kept crashing before it finishes.
Tried using driver verifier & I got the following

Crash reports from "WhoCrashed"

On Sat 28/09/2019 3:43:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8189)
Bugcheck code: 0x139 (0x4, 0xFFFF8A81DA3B7FF0, 0xFFFF8A81DA3B7F48, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 28/09/2019 3:05:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092819-41968-01.dmp
This was probably caused by the following module: verifierext.sys (0xFFFFF8077CB36328)
Bugcheck code: 0xC4 (0x2001F, 0xFFFFF8077CB36328, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 28/09/2019 2:59:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092819-39640-01.dmp
This was probably caused by the following module: verifierext.sys (0xFFFFF80715136328)
Bugcheck code: 0xC4 (0x2001F, 0xFFFFF80715136328, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 28/09/2019 2:50:44 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092819-34546-01.dmp
This was probably caused by the following module: verifierext.sys (0xFFFFF80460136328)
Bugcheck code: 0xC4 (0x2001F, 0xFFFFF80460136328, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 28/09/2019 2:46:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092819-35328-01.dmp
This was probably caused by the following module: verifierext.sys (0xFFFFF8017CF36328)
Bugcheck code: 0xC4 (0x2001F, 0xFFFFF8017CF36328, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\verifierext.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Extension du vérificateur de pilotes
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

and using BlueScreenViewer:
View: https://imgur.com/a/hA9IM1W



==================================================
Dump File : 092819-41968-01.dmp
Crash Time : 28/09/2019 3:05:05 PM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 000000000002001f Parameter 2 : fffff8077cb36328
Parameter 3 : 0000000000000000 Parameter 4 : 0000000000000000
Caused By Driver : VerifierExt.sys
Caused By Address : VerifierExt.sys+25386
File Description : Extension du vérificateur de pilotes
Product Name : Système d’exploitation Microsoft® Windows®
Company : Microsoft Corporation
File Version : 10.0.18362.356 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+1c10a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MiniDump\092819-41968-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 18362
Dump File Size : 879 076
Dump File Time : 28/09/2019 3:07:21 PM
==================================================

I can say I'm giving up on solving this on my own, I need help
 
Solution
can you go to C:\Windows\Minidump
copy the minidump files to another folder
Upload the copies to a file sharing website and show link here.

Strange for the driver verifer to trip over itself like that

Which memory test?

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Have you tried SFC in safe mode?

Colif

Win 11 Master
Moderator
can you go to C:\Windows\Minidump
copy the minidump files to another folder
Upload the copies to a file sharing website and show link here.

Strange for the driver verifer to trip over itself like that

Which memory test?

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Have you tried SFC in safe mode?
 
Solution