IRQL_NOT_LESS_OR_EQUAL. What's going on?

[ledones]

Hi everyone,

I don't know what's happening here. I formated my PC on friday because I screw up when I used SlimDriver to upgrade the drivers, which I never did before. After that, all is crashing. Now I'm getting this (Minidump on "spoiler") and I don't know what to do.

I guess my mobo is dying. That's my guess. Am I righ? (Or possibily wrong?).

If you guys need more information, just ask!

Thanks!!

PC:
Intel i7 3770
16GB Corsair Vengeance
Intel dz77bh-55k
GTX 660 3GB SC
SSD Corsair Neutron 120GB
HDD WD Black 2TB
Corsair cx-750
Win 10

Spoiler

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 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.0.amd64fre.rs1_release.160715-1616
Machine Name:
Kernel base = 0xfffff801`39c8a000 PsLoadedModuleList = 0xfffff801`39f8f060
Debug session time: Mon Aug 7 15:31:55.189 2017 (UTC - 4:00)
System Uptime: 0 days 2:58:11.882
*******************************************************************************
* *
* 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: ffff8a0096b8300a, 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: fffff80139dda1aa, address which referenced memory

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

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

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
ffff8a0096b8300a

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlCompareMemory+6a
fffff801`39dda1aa f3a6 repe cmps byte ptr [rsi],byte ptr [rdi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

TRAP_FRAME: ffff8a008d837720 -- (.trap 0xffff8a008d837720)
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=fffff80139dda1aa rsp=ffff8a008d8378b8 rbp=00000000c0010015
r8=0000000000000006 r9=0000000000000001 r10=0000000000000034
r11=ffff8a008d837900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!RtlCompareMemory+0x6a:
fffff801`39dda1aa f3a6 repe cmps byte ptr [rsi],byte ptr [rdi]
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80139ddf129 to fffff80139dd3f90

STACK_TEXT:
ffff8a00`8d8375d8 fffff801`39ddf129 : 00000000`0000000a ffff8a00`96b8300a 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8a00`8d8375e0 fffff801`39ddd707 : ffffd78c`7c924300 00000000`00000000 fffff808`194a7000 ffff8a00`8d8377b0 : nt!KiBugCheckDispatch+0x69
ffff8a00`8d837720 fffff801`39dda1aa : ffffd78c`70b99910 00000000`00000000 fffff808`196e96be 00000000`00000004 : nt!KiPageFault+0x247
ffff8a00`8d8378b8 fffff808`196e96be : 00000000`00000004 ffff8a00`8d837968 00000000`00000004 ffff8a00`8d837970 : nt!RtlCompareMemory+0x6a
ffff8a00`8d8378d0 fffff808`196eae6a : ffff8a00`96b8300a ffffd78c`70086780 ffff8a00`96b83000 00000000`00000000 : wdiwifi!CRxPeerTable::RxPeerGetPeerId+0xae
ffff8a00`8d837920 fffff808`196ea4ed : ffffd78c`70b998b8 00000000`00000003 00000000`00000003 00000000`0000001f : wdiwifi!CRxMgr::RxClassify+0xfe
ffff8a00`8d837a00 fffff808`196e7163 : ffffd78c`799ff030 fffff808`00000003 ffff8a00`8d837ba0 fffff808`192051df : wdiwifi!CRxMgr::RxInOrderDataInd+0x231
ffff8a00`8d837aa0 fffff808`1920550f : ffffd78c`71643000 fffff808`194a7000 00000000`00000005 00000000`00000010 : wdiwifi!AdapterRxInorderDataInd+0x83
ffff8a00`8d837ae0 ffffd78c`71643000 : fffff808`194a7000 00000000`00000005 00000000`00000010 00000000`00000000 : rtwlanu+0x4550f
ffff8a00`8d837ae8 fffff808`194a7000 : 00000000`00000005 00000000`00000010 00000000`00000000 ffff8a00`8d837ba0 : 0xffffd78c`71643000
ffff8a00`8d837af0 00000000`00000005 : 00000000`00000010 00000000`00000000 ffff8a00`8d837ba0 fffff808`194a7000 : rtwlanu+0x2e7000
ffff8a00`8d837af8 00000000`00000010 : 00000000`00000000 ffff8a00`8d837ba0 fffff808`194a7000 ffffd78c`70c4b000 : 0x5
ffff8a00`8d837b00 00000000`00000000 : ffff8a00`8d837ba0 fffff808`194a7000 ffffd78c`70c4b000 00000000`00000001 : 0x10


STACK_COMMAND: kb

FOLLOWUP_IP:
wdiwifi!CRxPeerTable::RxPeerGetPeerId+ae
fffff808`196e96be 4883f806 cmp rax,6

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: wdiwifi!CRxPeerTable::RxPeerGetPeerId+ae

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdiwifi

IMAGE_NAME: wdiwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 57899aa2

FAILURE_BUCKET_ID: X64_AV_wdiwifi!CRxPeerTable::RxPeerGetPeerId+ae

BUCKET_ID: X64_AV_wdiwifi!CRxPeerTable::RxPeerGetPeerId+ae

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

 

[Colif]

can you upload the minidump to a cloud server and share link here as there is more info in them that that screen reveals

wdiwifi.sys = WDI Driver Framework Driver

driver update programs are a trap. they seem to make updating drivers much easier but they can get it wrong.

 

[ledones]

Unfortunally I don't have anymore, but I guess solved the problem. I downloaded whocrashed and said that rtwlanu.sys caused this. Corresponds to my wifi usb adapter. So I installed the driver from TP-Link website and it's working until now.

 

[Colif]

problem solved anyway