BSOD Windows 10 IRQL_NOT_LESS_THAN_OR_EQUAL

durrkness

Prominent
Mar 22, 2017
12
0
510
This issue has been ongoing for quite some time.

I just recently did a fresh install of Windows to see if it was some corrupted data and there was no effect on the crashes.

The crashes seem to occur under higher stress loads. Mostly when playing video games. I have a feeling it is driver related but I'm unsure of the best way to proceed and diagnose this problem.

At first it was only some graphics intensive games but then it started to happen frequently for non-graphics intensive games. But for the non-graphic intensive games the BSOD's didn't occur at the start and then started ramping up over time.

I can usually recreate the crash and get similar crash codes.
IRQL_NOT_LESS_THAN_OR_EQUAL
MEMORY MANAGEMENT

 

Colif

Win 11 Master
Moderator
those two errors can be drivers or ram related as they both data errors.

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 :)

might also pay to run the free version of memtest86 on the ram sticks, 1 at a time. It creates a bootable USB so can run without windows. Any errors means ram is bad and needs to be replaced
 

durrkness

Prominent
Mar 22, 2017
12
0
510
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: GA-78LMT-USB3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-4100 Quad-Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 12882333696 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 3/22/2017 8:46:41 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x8B6711)
Bugcheck code: 0xA (0x730E0, 0x2, 0x1, 0xFFFFF802D58B7AA0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispiwu.inf_amd64_b67dc924fff8de6d\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.53
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.53
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.53 , NVIDIA Corporation).
Google query: NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL


Also, thanks for taking your time to do this. You guys the best.

I'll do the memtest if the dump doesn't prove to be helpful.
 

MaDDD

Reputable
Jan 13, 2016
268
0
4,860
Are you overclocked? Also it would be good to know CPU & GPU temps?

A good start would be to go to bios and load optimised defaults & re-install the GPU drivers (Clean install).

Oh, and perhaps PSU specs as your system/GPU may be demanding too much power for it.
 

Colif

Win 11 Master
Moderator


For Nvidia errors, I would try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html
 

durrkness

Prominent
Mar 22, 2017
12
0
510
Not overclocked.

I've already had a friend check into temps and he gave the okay.
it usually runs at about 60C I believe.

PSU is 700W

Going to try the fresh install of NVIDIA driver
 

MaDDD

Reputable
Jan 13, 2016
268
0
4,860


60 degrees would be considered too hot if idle, at max usage 60 would be fine.

The PSU could be good or bad quality and causing the issue, when I meant the spec of it I meant, what make and model, it may be the answer to why you are getting this issue.
 

durrkness

Prominent
Mar 22, 2017
12
0
510
So, after doing a clean install of the Nvidia Drivers there was no crashing while using it for about 8 hours. Then it crashed and I got the
KMODE_EXCEPTION_NOT_FOUND error code.

Here is the new crash log from Who Crashed

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 3/23/2017 6:02:39 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032317-23765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80389214937, 0x0, 0x1)
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 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 3/23/2017 6:02:39 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1BD3D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80389214937, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.





The PSU is:
Cooler Master i700 Power Supply Alimentation
Module: RS-700-ACAA-B1
Output Power: 700W
PFC: Active PFC
Form Factor: ATX 12V V2.3
Dimensions: 140 x 150 x 86
Coating: Black
Fan Type: 120 mm Sleeve Bearing Fan
Fan Speed: 2200RPM
Input Voltage: 100-240V
Efficiency: 80 Plus Bronze
Connector Types: 20+4 Pin for M/B, 4+4 Pin for CPU, PCI-e 6+2Pin, Peripheral 4Pin, Floppy 4Pin, SATA
 

MaDDD

Reputable
Jan 13, 2016
268
0
4,860
50 degrees at idle is pretty high, I'd be interested in seeing the temps when it starts getting a heavy load on it. It still doesn't cancel out that the PSU could be the issue, I wouldn't imagine that it is a well made one but I could be wrong (Hopefully someone who knows PSUs more finds this and can add more info on that).
 

durrkness

Prominent
Mar 22, 2017
12
0
510
Rechecked the temps using HWiNFO

CPU (processor) at idle is 18.5C
CPU (motherboard) idle is 40C
GPU at idle is 41C


Just got another blue screen while trying to run a game while tracking temps
Page Fault in Nonpaged Area

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 3/24/2017 4:01:20 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032417-24093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x50 (0xFFFFFFFF99C93309, 0x2, 0xFFFFF803EBD5E9C4, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 3/24/2017 4:01:20 PM 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: 0x50 (0xFFFFFFFF99C93309, 0x2, 0xFFFFF803EBD5E9C4, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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.

How do I upload the DMP file to onedrive? just copy pasta it and send a link?
 
Update the driver for this ArvoFltr.sys ROCCAT Arvo Keyboard driver it's 8 yrs old

Old drivers can crash windows

This driver is 7 yrs old ElcMouLFlt.sys ELECOM USB Mouse Driver

This driver is 5 yrs old t_mouse.sys. It maybe belong to an Iball mouse

Looks like EasyAntiCheat.sys can also cause one of these stop errors
 

durrkness

Prominent
Mar 22, 2017
12
0
510
Crashed again while searching for driver updates.

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 3/24/2017 5:16:49 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032417-30250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80096101342, 0xFFFFE68033FE3720, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 3/24/2017 5:16:49 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xCBBED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80096101342, 0xFFFFE68033FE3720, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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.
 

durrkness

Prominent
Mar 22, 2017
12
0
510
I downloaded the newest drivers from the manufacturer's website.

There have been no crashes yet. So, we may have found the problem.

I'm going to leave the thread open for a couple days to do some more testing and if no crashes by then I'll pick the solution.
 

durrkness

Prominent
Mar 22, 2017
12
0
510
Alrighty, so no more blue screens but....

I've been getting frequent crashes now that result in either:

the screen freezing with a looping sound.
The screen freezing.
computer black screens and restarts.

My head hurts from this and it is my birthday. All I am wishing for is a solution!

Could my windows be corrupted?
Maybe bad hardware?
 

durrkness

Prominent
Mar 22, 2017
12
0
510
So, before I could run memtest86 my computer crashed again and went into automatic repair loop.

To try and escape the loop I tried to do a reset of my system because I had no important files that weren't backed up.

The reset failed and then my computer restarted.

Now I am getting no signal to my monitor but all the fans are running.
 

durrkness

Prominent
Mar 22, 2017
12
0
510
My guess is my motherboard is bad.

But, due to all the other issues im thinking I had a registry problem with windows. If I am getting replacement parts where would you guys suggest I start?

Also, no BIOS beeps or noises.