IRQL Not LESS OR EQUAL Error in Windows 10

xtremelegend101

Reputable
Feb 25, 2014
19
0
4,510
I've had 2 crushes in one day related to IRQL Not Less Or Equal while my brother is playing FFXIV. The first crash happen after 4 hours of game time and the second one was after 7 hours. I've updated all drivers and windows updates as well I have also updated by bios since it was outed by a couple of years. No problems when using the computer for any other activity but the PC crashes when playing games for a long period of time.
Here is what I got from whocrash
System Information (local)
--------------------------------------------------------------------------------

Computer name: XANXUS
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0
CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17070915584 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 6/10/2016 3:01:09 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
uptime: 09:02:22
This was probably caused by the following module: Unknown (0xFFFFF8019F302E98)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8019F302E98)
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.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL



On Tue 6/7/2016 6:25:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\060716-15406-01.dmp
uptime: 02:47:32
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xC8, 0x2, 0x0, 0xFFFFF802E2C9308E)
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.
here is the link to the minidump file that appears on my folder but I don't have any for today. https://drive.google.com/open?id=0B39iJ3AjIsfNaDhoQWs3M25mVlk
This link is for my msinfo32 file
https://drive.google.com/open?id=0B39iJ3AjIsfNM3doYTJfYmpLem8.
I'm using windows 10 pro 64bit
16GB DDR3
2 R9 290s
PSU 1000W Gold
Hope someone can help me figure out what is wrong and I've done chkdsk and it didn't found anything wrong and I've also ran sfc /scannow and it did fix some files that were corrupted successfully.

 
Solution
\C:\WINDOWS\xhunter1.sys Fri Mar 11 06:02:07 2016
sets off a bugcheck if you run a hacked game.

looks like you were runing ffxiv_dx11.exe at the time of the bugcheck.

The bugcheck was called because some driver attempted to use a bad memory reference (memory address c8)

I would think if it is not the xhunter anti cheat driver then you would have to change the memory dump to kernel, then run verifier to look for drivers that are corrupting memory.

ie start cmd.exe as an admin then run
verifier.exe /standard /all
reboot and wait for the next bugcheck.
be sure to know how to get into safe mode on your machine in the case that the system bugcheck on the next boot.

to turn off verifier functions you run
verifier.exe /reset

turn...

xtremelegend101

Reputable
Feb 25, 2014
19
0
4,510
I'm using water cooling and it does the job well My CPU doesn't go past the 60C with heavy load and without the panel on the case heat doesn't build up. I've check this before thinking maybe my CPU was getting too hot but the highest I've seen is 60C and usually stays between 50C-60C during gaming .
 
\C:\WINDOWS\xhunter1.sys Fri Mar 11 06:02:07 2016
sets off a bugcheck if you run a hacked game.

looks like you were runing ffxiv_dx11.exe at the time of the bugcheck.

The bugcheck was called because some driver attempted to use a bad memory reference (memory address c8)

I would think if it is not the xhunter anti cheat driver then you would have to change the memory dump to kernel, then run verifier to look for drivers that are corrupting memory.

ie start cmd.exe as an admin then run
verifier.exe /standard /all
reboot and wait for the next bugcheck.
be sure to know how to get into safe mode on your machine in the case that the system bugcheck on the next boot.

to turn off verifier functions you run
verifier.exe /reset

turn it off after you are done testing or your machine will run slowly until you do.

 
Solution

TRENDING THREADS