IRQL_NOT_LESS_OR_EQUAL Error in Windows 10

[coyoteee]

Hi guys! I was playing some games then suddenly a BSOD showed up and it said IRQL_NOT_LESS_OR_EQUAL, i was told it's a driver issue, can someone tell me what was causing it?
Here are my dump files
https://drive.google.com/open?id=0B3PmW_CgoUIMVmY1NXowNTdrajA
Thank you guys in advance

 

[Colif]

I can't read dump files myself but this can, Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

what are specs of PC?

 

[johnbl]

your machine has extra copies of overclock drivers running. you need to remove them.
C:\Program Files (x86)\MSI\MSI OC Kit\Driver_Service\NTIOLib_X64.sys Wed Sep 7 19:55:34 2016

C:\Program Files (x86)\MSI\MSI OC Kit\ActiveX_Service\NTIOLib_X64.sys Tue Apr 12 00:04:16 2016
(same driver from two different directories)
and
RTCore64.sys
: RivaTuner/EVGA Precision/MSI Afterburner

remove the overclock drivers and see if you still bugcheck.

the bugcheck showed access to a bad memory address but the stack shows a IDLE cpu.
see if removing the overclock drivers helps

 

[coyoteee]

sorry for the late response here is the summary i got from WhoCrashed

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 05/04/2017 17:40:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050417-3921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 05/04/2017 17:40:51 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 04/21/2017 15:47:21 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042117-3718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04/15/2017 1:06:55 your computer crashed
crash dump file: C:\WINDOWS\Minidump\041517-3781-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0x56B8C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFAA42F1256B8C, 0xFFFF828186CBEE10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 standard 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 Fri 04/14/2017 17:58:08 your computer crashed
crash dump file: C:\WINDOWS\Minidump\041417-3687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3D (0xFFFF828005275D38, 0xFFFF828005275570, 0x0, 0x0)
Error: INTERRUPT_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 bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I also checked the Even Logs and it said the problem was caused by Kelnelbase.dll

 

[johnbl]

invalid memory addresses being handed to drivers.
you need to delete the overclock drivers if you have not done so.

then provide a actual copy of the minidumps. (delete the old memory dumps)
you can run cleanmgr.exe to remove them.

sorry for the late response here is the summary i got from WhoCrashed

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 05/04/2017 17:40:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\050417-3921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 05/04/2017 17:40:51 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 04/21/2017 15:47:21 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042117-3718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04/15/2017 1:06:55 your computer crashed
crash dump file: C:\WINDOWS\Minidump\041517-3781-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0x56B8C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFAA42F1256B8C, 0xFFFF828186CBEE10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 standard 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 Fri 04/14/2017 17:58:08 your computer crashed
crash dump file: C:\WINDOWS\Minidump\041417-3687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3D (0xFFFF828005275D38, 0xFFFF828005275570, 0x0, 0x0)
Error: INTERRUPT_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 bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I also checked the Even Logs and it said the problem was caused by Kelnelbase.dll

 

[coyoteee]

Thanks a lot guys i thought my oc on the memory was a little bit too high so i lowered it down. No problem since then