IRQL NOT LESS OR EQUAL blue screen

zard

Distinguished
Sep 11, 2010
8
0
18,510
Hi I am getting an IRQL_NOT_LESS_OR_EQUAL BSOD which I believe began when I installed a new GTX 1070. I can't tell for sure as I upgraded to the latest drivers, which precipitated the blue screen, and rolling back to 375.95 seemed to fix the issue ... for a little bit.

I was also getting near-constant blue screens of various sorts but these may have been due to system drivers. I did a fresh install of Win10 and this time manually installed the Intel INF and Intel Management Engine Interface and stopped getting the constant BSOD.

Here is the summary from WhoCrashed:

System Information (local)

Computer name: DESKTOP-48BTO9B
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: Z170X-UD5, Gigabyte Technology Co., Ltd., Z170X-UD5-CF
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17129934848 bytes total



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 1/1/2017 10:52:53 AM your computer crashed
crash dump file: C:\Windows\Minidump\010117-17953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFD089BD61E370, 0x2, 0x0, 0xFFFFF802694F40C1)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 1/1/2017 10:52:53 AM 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: 0xA (0xFFFFD089BD61E370, 0x2, 0x0, 0xFFFFF802694F40C1)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.


I have my memory dumps here:

minidump: https://drive.google.com/file/d/0B2pRW7JYSgOZVTMwRkNzc0Z2V00/view?usp=sharing
memory.dmp: https://drive.google.com/file/d/0B2pRW7JYSgOZbTZVQjM4X2dOaHM/view?usp=sharing
 
D

Deleted member 217926

Guest
IRQL_NOT_LESS_OR_EQUAL is often a memory error. What RAM do you have and is XMP enabled? I have the same Z170X UD5/6700K setup.
 

xiaoshen

Commendable
Jan 2, 2017
4
0
1,510
It is maybe the memory error.Set all BIOS setup to default to try and then run Memtest to sure OK. If the problem goes on ,try other memorys.It is often the compatibility issues.
 

zard

Distinguished
Sep 11, 2010
8
0
18,510
My RAM is Geil Super Luce DDR4 2400, yes I have XMP enabled, but I ran 3 full runs of memtest86 without error and before that I had already run Windows Memory Diagnostics so while it may be the RAM, this seems unlikely. The IRQL message I believe started when I installed my Geforce 1070 but it also seems I haven't gotten a crash with MSI Afterburner closed, which I have read can cause blue screens.

If somebody could check my memory dumps? It would be helpful if I could identify the culprit beyond 'ntoskrnl' or whatever.

Thanks