[SOLVED] IRQL_NOT_LESS_OR_EQUAL Blue screen when playing games

[boatjesus]

I recently did a clean install of Windows 11 on my laptop, and hoped that it might resolve some of my previous issues. However, I still get blue screens when playing games. I suspect it is a RAM issue, however I don't want to pay for new RAM and repair without making sure. Minidump file is as follows:


Loading Dump File [C:\Windows\Minidump\010822-12390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff800`26800000 PsLoadedModuleList = 0xfffff800`27429750
Debug session time: Sat Jan 8 17:21:40.937 2022 (UTC - 5:00)
System Uptime: 0 days 15:16:40.591
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`26c159c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff800f`2eca04d0=000000000000000a
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000006160, 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: fffff80026a14fd6, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2858

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 18609

Key : Analysis.Init.CPU.mSec
Value: 436

Key : Analysis.Init.Elapsed.mSec
Value: 34337

Key : Analysis.Memory.CommitPeak.Mb
Value: 78

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 010822-12390-01.dmp

BUGCHECK_CODE: a

BUGCHECK_P1: 6160

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80026a14fd6

READ_ADDRESS: fffff80027505450: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000006160

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Risk of Rain 2.exe

TRAP_FRAME: ffff800f2eca0610 -- (.trap 0xffff800f2eca0610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000614f
rdx=ffffd20b73c571c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80026a14fd6 rsp=ffff800f2eca07a0 rbp=ffff800f2eca0849
r8=ffffd20b520f8c30 r9=000000000000001e r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiAbTryIncrementIoWaiterCounts+0x6:
fffff800`26a14fd6 80791100 cmp byte ptr [rcx+11h],0 ds:00000000`00006160=??
Resetting default scope

STACK_TEXT:
ffff800f`2eca04c8 fffff800`26c285a9 : 00000000`0000000a 00000000`00006160 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff800f`2eca04d0 fffff800`26c24700 : fffff800`22f3d000 ffffd20b`52174040 00000000`ffffffff 00000000`00000105 : nt!KiBugCheckDispatch+0x69
ffff800f`2eca0610 fffff800`26a14fd6 : fffff800`27535bc0 00000000`00000001 ffffd20b`73c570c0 fffff800`22cc8180 : nt!KiPageFault+0x440
ffff800f`2eca07a0 fffff800`26b34132 : fffff800`22cc8180 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KiAbTryIncrementIoWaiterCounts+0x6
ffff800f`2eca07d0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff800`22cc8180 ffffd20b`73c570c0 : nt!KiAbProcessContextSwitch+0x242


SYMBOL_NAME: nt!KiAbTryIncrementIoWaiterCounts+6

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22000.376

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 6

FAILURE_BUCKET_ID: AV_nt!KiAbTryIncrementIoWaiterCounts

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a14e8f1a-d7bc-4995-3770-3a2d50e87f2d}

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

Really hope someone can decipher anything important in the dumb file, I know I cant
Thanks in advance

 

[Colif]

GPU drivers caused that crash

Crash mentions dxgmms2!VidSchiWorkerThread+0xca
dxgmms2 = directX. 99% of time I see it I can say its GPU, other 1% is sound drivers.
Rest of line looks to me to be Video Scheduler Worker which sure looks like GPU work

Dec 15 2021

nvlddmkm.sys

Nvidia Graphics Card driver http://www.nvidia.com/

I seen a few people with problems with those drivers recently.
could have been why Risk of Rain crashed on last BSOD as well.

There aren't any newer yet as I can see Ge force Experience offering me those drivers now. (Decides to skip them for now)
Try running DDU in safe mode and either
1. reinstall drivers from Nvidia or
2, After restarting from safe mode, run windows update and let windows find older Nvidia drivers from its update Catalog

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

 

[Colif]

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it, just to make it.

 

[boatjesus]

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it, just to make it.

I've run memtest several times with several passes each, never came up with any errors. Minidump is here: https://drive.google.com/file/d/1fFjuccjVor-TMhXCIbFyig5gpkj6J3_j/view?usp=sharing

 

[Colif]

i have to send link to a friend, he probably won't reply until later as he in a different time zone.

he might have an answer for you or he will drop a link I can use to read dump results.

 

[boatjesus]

Appreciate it

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/nb2xwe1m/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	010822-12390-01.dmp (Jan 8 2022 - 17:21:40)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: Risk of Rain 2.exe)
Uptime:	0 Day(s), 15 Hour(s), 16 Min(s), and 40 Sec(s)

Comment: I'm not sure what this driver is: rtucx22x64.sys Potentially a rootkit, or maybe a Realtek driver. More searching/study is needed.

System: ROG Zephyrus G14
Homepage: https://rog.asus.com/us/laptops/rog-zephyrus/rog-zephyrus-g14-series/

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

update razer, this is way too old

Jul 26 2008

Razer Synapse Service.sys

Razer Synapse driver

I have seen other razer drivers cause BSOD recently

this is an unknown

rtucx22x64.sys

can only find one reference to this file, maybe a virus. I would run an AV scan

 

[gardenman]

can only find one reference to this file, maybe a virus. I would run an AV scan

I just found it on another site, and it's described as a Realtek driver. I'm going to add that to my descriptions until/unless we find more info.

 

[Colif]

its initials did make me wonder if it was a realtek driver. I didn't find it on that link, i had looked.

After further digging
rtump64x64.sys: v10.45.0308.2021 - Realtek USB GBE Ethernet Controller Driver
rtucx21x64.sys: v10.46.0406.2021ucx is also a network driver.

I just don't like mysteries. New drivers are okay.

 

[boatjesus]

I got a new, similar crash with the only program open being zoom. Same ntoskrnl.exe that BlueScreenView says failed. Minidump file is here: https://drive.google.com/file/d/17jGua1ajMPXC6wBvH8aHXzqUE3BDVc0r/view?usp=sharing

I'm going to open up the laptop in a day or two, once I get the tools to do so, and see if there' any visible damage/issue with the RAM, I think there's a chance it could be that.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/5rfsvznb/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	011022-15109-01.dmp (Jan 10 2022 - 16:17:54)
Bugcheck:	KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 16 Hour(s), 39 Min(s), and 27 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

GPU drivers caused that crash

Crash mentions dxgmms2!VidSchiWorkerThread+0xca
dxgmms2 = directX. 99% of time I see it I can say its GPU, other 1% is sound drivers.
Rest of line looks to me to be Video Scheduler Worker which sure looks like GPU work

Dec 15 2021

nvlddmkm.sys

Nvidia Graphics Card driver http://www.nvidia.com/

I seen a few people with problems with those drivers recently.
could have been why Risk of Rain crashed on last BSOD as well.

There aren't any newer yet as I can see Ge force Experience offering me those drivers now. (Decides to skip them for now)
Try running DDU in safe mode and either
1. reinstall drivers from Nvidia or
2, After restarting from safe mode, run windows update and let windows find older Nvidia drivers from its update Catalog

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

 

[boatjesus]

GPU drivers caused that crash

Crash mentions dxgmms2!VidSchiWorkerThread+0xca
dxgmms2 = directX. 99% of time I see it I can say its GPU, other 1% is sound drivers.
Rest of line looks to me to be Video Scheduler Worker which sure looks like GPU work

Dec 15 2021

nvlddmkm.sys

Nvidia Graphics Card driver http://www.nvidia.com/

I seen a few people with problems with those drivers recently.
could have been why Risk of Rain crashed on last BSOD as well.

There aren't any newer yet as I can see Ge force Experience offering me those drivers now. (Decides to skip them for now)
Try running DDU in safe mode and either
1. reinstall drivers from Nvidia or
2, After restarting from safe mode, run windows update and let windows find older Nvidia drivers from its update Catalog

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

I got rid of the drivers, and just let windows find drivers on its own. It hasn't crashed in 5 or 6 days. I wish I could get updated drivers but I don't think I can. Old drivers aren't so bad and are much better than constant crashes. Thank you