Ask a new question

IRQL_NOT_LESS_OR_EQUAL while gaming

Hi,

Im having this crash issue while gaming. My computer specs are as follow:

W10 Pro 64bits

i7 8700 3.2GHz

8192MB RAM

GTX 1070ti

After 2 crashes, using WhoCrashed I traced the first one to a file called hall.dll

The second one gave me the following report:

On Sat 15/02/2020 20:12:52 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+0x7EF9)
Bugcheck code: 0xD1 (0xFFFFF8041EC5DCDE, 0x2, 0x8, 0xFFFFF8041EC5DCDE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\021520-17234-01.dmp

Can someone please help me? I tried updating my drivers, cleaning the BIOS cache, disabling some USB ports, initiating a repair after rebooting the PC using the prompt command. Dont know what else to do.

Hi,
I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.

We need log files(called dump files) that tell us what lead to crash.
Please share them with us for a better analysis of the problem. Instructions can be found here:

https://answers.microsoft.com/en-us/windows/for...

To share files here, please see:

How to share diagnostic files/logs on Microsoft community

https://answers.microsoft.com/en-us/feedback/fo...
Sumit

Always include PC Specs, Make and Model of the device. Ensure all the latest quality updates have been installed. It may take multiple replies to reach a satisfactory answer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Sumit, thanks for helping me.

Bellow follows the link to the dump files:

https://1drv.ms/u/s!AtauLeCbIO1alU25xrcybKuWOe16?e=2xz4C5

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

So, another crash happened today. I uploaded a new dump file as "V2", and a file from the (recent created) Minidump directorie. Bellow is the report that WhoCrashed gave it to me:

On Sun 16/02/2020 10:41:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021620-15781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x139 (0x4, 0xFFFF9A0083585FF0, 0xFFFF9A0083585F48, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Sun 16/02/2020 10:41:14 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+0x8219)
Bugcheck code: 0x139 (0x4, 0xFFFF9A0083585FF0, 0xFFFF9A0083585F48, 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. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

Apologies for the delay. The crashes did not blame a specific 3rd party driver and memory corruption was noted.


Looks like a Memory test is required.

I suggest you to Run memory test for at least 8 passes, preferably Overnight.

https://www.tenforums.com/tutorials/14201-memte...

When the test completes post back the Image(You can use your phone's camera).

Disclaimer:
There are links to non-Microsoft websites which would provide accurate and safe information. Watch out for ads on the sites which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.
Sumit

Always include PC Specs, Make and Model of the device. Ensure all the latest quality updates have been installed. It may take multiple replies to reach a satisfactory answer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Sumit,

No problem for the delay. I run the test following the instructions of the tutorial you gave, letting it run for 8 passes. The end result was no erros, as the image bellow shows:

There was also two new crashes on monday. I already uploaded a new Memory.dmp (Memory_V3) and a new minidump file. Bellow is the reports WhoCrashed gave it to me:

On Sun 16/02/2020 15:29:07 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021620-15937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80007FD8D5E, 0x0, 0xFFFFC1005ECC0180)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 16/02/2020 15:29:07 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!memset+0x5B827)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80007FD8D5E, 0x0, 0xFFFFC1005ECC0180)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 16/02/2020 10:41:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021620-15781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x139 (0x4, 0xFFFF9A0083585FF0, 0xFFFF9A0083585F48, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

Let us try finding any misbehaving driver
Enable Driver Verifier:

http://answers.microsoft.com/en-us/windows/wiki...
(Must create a Restore point before)

Upload the newer dumps when you get Driver_Verifier_detected_voilation.

Please note that the system might crash before you reach the desktop-if it does please let us know so that we can guide you to disable Verifier.
Sumit

Always include PC Specs, Make and Model of the device. Ensure all the latest quality updates have been installed. It may take multiple replies to reach a satisfactory answer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

I followed the instructions, and it crashed while Windows was on the loading screen (just after showing the motherboard screen).

I already uploaded 2 Minidump Files, one from yesterday (not related to the test, happened while I was gaming), and one from today, after the test you described took place and the computer crashed while initializing.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Please reinstall everything of Razer as it looks to be causing the crashes.

*** WARNING: Unable to verify timestamp for rzendpt.sys

Let us know how that goes.
Sumit

Always include PC Specs, Make and Model of the device. Ensure all the latest quality updates have been installed. It may take multiple replies to reach a satisfactory answer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Ok, I updated all the drivers of Razer I could find.

I'll only be able to test it this weekend, but if the problem persist, should I do the step of using "Enable Driver Verifier" again?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated November 9, 2022 Views 707 Applies to: