IRQL_NOT_LESS_OR_EQUAL Windows 10

[shadowbuster4204]

I have been experiencing quite a lot of BSODS recently with the error code IRQL_NOT_LESS_OR_EQUAL
CRASH DUMP:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`e340d000 PsLoadedModuleList = 0xfffff803`e37c71f0
Debug session time: Thu Jun 28 07:36:14.742 2018 (UTC - 4:00)
System Uptime: 0 days 2:43:57.464
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffa78d6d2fc042, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803e35ad80a, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

OVERLAPPED_MODULE: Address regions for 'mrxsmb20' and 'dump_storpor' overlap

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffa78d6d2fc042

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlCompareMemory+6a
fffff803`e35ad80a f3a6 repe cmps byte ptr [rsi],byte ptr [rdi]

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

TRAP_FRAME: ffffcc851f1b1710 -- (.trap 0xffffcc851f1b1710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000006
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803e35ad80a rsp=ffffcc851f1b18a8 rbp=0000000000000000
r8=0000000000000006 r9=0000000000000001 r10=ffffb780a6716180
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!RtlCompareMemory+0x6a:
fffff803`e35ad80a f3a6 repe cmps byte ptr [rsi],byte ptr [rdi]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803e35b5f69 to fffff803e35a5430

STACK_TEXT:
ffffcc85`1f1b15c8 fffff803`e35b5f69 : 00000000`0000000a ffffa78d`6d2fc042 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffcc85`1f1b15d0 fffff803`e35b2be5 : 00000000`fffffffc fffff80b`51a132b1 ffffa78d`6799ca40 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffcc85`1f1b1710 fffff803`e35ad80a : 00000000`00000000 ffffa78d`626a19c8 fffff80b`519c9c50 ffffa78d`66e48f80 : nt!KiPageFault+0x425
ffffcc85`1f1b18a8 fffff80b`519c9c50 : ffffa78d`66e48f80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlCompareMemory+0x6a
ffffcc85`1f1b18c0 fffff80b`519cb4f3 : ffffa78d`6d2fc042 ffffa78d`6a577900 ffffa78d`6d2fc038 00000000`00000000 : wdiwifi!CRxPeerTable::RxPeerGetPeerId+0xa4
ffffcc85`1f1b1920 fffff80b`519cab32 : ffffa78d`626a1970 00000000`00000003 00000000`00000003 00000000`00000001 : wdiwifi!CRxMgr::RxClassify+0xf7
ffffcc85`1f1b1a00 fffff80b`519c7413 : ffffa78d`6a577780 fffff80b`00000003 ffffcc85`1f1b1ba0 00000000`00000000 : wdiwifi!CRxMgr::RxInOrderDataInd+0x22e
ffffcc85`1f1b1aa0 fffff80b`51466d1b : ffffa78d`626c0000 fffff80b`51731000 00000000`00000005 00000000`00000010 : wdiwifi!AdapterRxInorderDataInd+0x83
ffffcc85`1f1b1ae0 fffff80b`51465fff : ffffa78d`626c2000 fffff80b`516eb501 ffffa78d`62c00000 fffff80b`516ed811 : rtwlanu!wdi_NotifyPeerData+0x363
ffffcc85`1f1b1b50 fffff80b`514df385 : ffffa78d`00000000 ffffa78d`62c00000 ffffa78d`63446050 ffffa78d`63447024 : rtwlanu!WDI_NotifyDataInQueue+0x97
ffffcc85`1f1b1ba0 fffff80b`516eafe2 : ffffa78d`626c35d8 ffffa78d`63445fa0 ffffa78d`678783b8 ffffa78d`62c00000 : rtwlanu!RxNotifyThreadCallback+0xcd
ffffcc85`1f1b1be0 fffff803`e34f1cd7 : ffffa78d`67998040 00000000`00000080 fffff80b`516eaf60 ffffa78d`63445fa0 : rtwlanu!Ndis6ThreadCallback+0x82
ffffcc85`1f1b1c10 fffff803`e35ac8d6 : ffffb780`a6716180 ffffa78d`67998040 fffff803`e34f1c90 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffcc85`1f1b1c60 00000000`00000000 : ffffcc85`1f1b2000 ffffcc85`1f1ac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
wdiwifi!CRxPeerTable::RxPeerGetPeerId+a4
fffff80b`519c9c50 4883f806 cmp rax,6

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: wdiwifi!CRxPeerTable::RxPeerGetPeerId+a4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdiwifi

IMAGE_NAME: wdiwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 21f05d84

FAILURE_BUCKET_ID: X64_AV_wdiwifi!CRxPeerTable::RxPeerGetPeerId+a4

BUCKET_ID: OLD_IMAGE_wdiwifi.sys

Followup: MachineOwner
---------




This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)

 

[Colif]

wdiwifi.sys = Windows Driver Framework. Can't say I seen that crash recently.

What are specs of the PC?
IRQ errors are normally caused by drivers, can also be caused by bad ram.

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

dump files will show what drivers were running at time of crash and may give us a clue as to what caused this. Its often old drivers that are the cause

Can you download and run memtest86, it creates a bootable USB which can be used to check the ram sticks. Test 1 stick at a time, up to 8 passes. Any error count higher than 0 is too many, and is a sign you should remove/replace the stick

 

[shadowbuster4204]

My specs are

CPU: RYZEN 5 1500X 3.5ghz
GPU GTX 1060 6GB
SSD: Samsung 850 evo 250gb
HDD: Seagate Barracuda 7200.14 2TB
RAM: Corsair Vengeance LPX DDR4 2400 C16 2x8GB
I have already done memtest 86 and there were no errors I even tried mem diagnostics no problem with that either and I will put my next crashes in a small minidump

 

[shadowbuster4204]

Here is the minidump file I had before because I already had the small memory dump thing on https://www.dropbox.com/s/ymw17priia54fpf/062818-6562-01.dmp?dl=0

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/lU9E.html

File: 062818-6562-01.dmp (Jun 28 2018 - 07:36:14)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: wdiwifi.sys (Process: System)
Uptime: 0 Day(s), 2 Hour(s), 43 Min(s), and 57 Sec(s)

BIOS information was not included in the dump file. This can sometimes mean you are using an older BIOS. Look for updates. Note: Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

what motherboard do you have?

No old drivers showing

I think running driver verifer might be fastest way to figure this out. It has a habit of boot looping after the test so there are precautions. 1st, set up a system restore point.
Search cortana for restore
1) open "create a restore point"
2) create a new Restore Point now for C-drive


Download the Windows 10 media creation tool and use it to make a win 10 installer on USB -as a boot drive so you can access windows recovery environment so you can run system restore to roll back to a working windows
boot from installer, on 2nd screen after languages, choose repair this pc, not install
choose troubleshoot
choose advanced
choose system restore

You might not need it but its a valuable precaution just in case.

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

 

[shadowbuster4204]

My mobo is a Asrock AB350M HDV

 

[shadowbuster4204]

Ok so now my computer crashed with the same error code here is the dump file
https://www.dropbox.com/s/1yxcejqhwj4q5t5/062918-13593-01.dmp?dl=0

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/Brk5.html

File: 062918-13593-01.dmp (Jun 29 2018 - 00:31:40)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)]
*** WARNING: Unable to verify timestamp for rtwlanu.sys
Probably caused by: rtwlanu.sys (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 02 Min(s), and 21 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

rtwlanu.sys = Realtek wireless LAN drivers

See drivers here: http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=62&Level=5&Conn=4&DownTypeID=3&GetDown=false