Question Constant BSODs in Windows 10 - DRIVER_IRQL_NOT_LESS_OR_EQUAL

Pentacore · Sep 22, 2024

This started happening today while playing God of War Ragnarok on the PC. The machine is very stable otherwise and plays other games just fine. I've reported it, but in the meantime I thought I'd ask on here.

I analyzed the dump file with WinDbg and here's the basic output. I can post the full output, but it's very long.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000b49676dc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 00000000b49676dc, address which referenced memory

EDIT: Looking further into the analysis of the dump file, it says this:

BUGCHECK_CODE: d1

BUGCHECK_P1: b49676dc

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: b49676dc

FILE_IN_CAB: 092224-22968-01.dmp

FAULTING_THREAD: ffffbe021cf1d240

READ_ADDRESS: fffff804550fb390: 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
00000000b49676dc

PROCESS_NAME: Skype.exe

Would this mean freaking Skype caused this?! I'm going to kill it and see if that makes any difference.

Any ideas are welcome.
Thanks all!

Pentacore · Sep 22, 2024

For whatever this is worth as maybe this will help someone else out there, it actually was Skype. After killing Skype, no more BSODs, and the game runs fine.

Now I'm just wondering why Skype? Why would it cause this to happen? I would have never guessed it was Skype. So thankful for dump files.

mikeymikec · Sep 22, 2024

What's the PC spec? IMO it was Skype wanting something from one of your hardware drivers that it just couldn't handle.

Was Skype signed in?

NirSoft's BlueScreenView might point the finger at a particular driver. I would also check the Windows Event Viewer (Windows logs > system log) at events around the time of the crashes, maybe you've got a load of NDIS entries possibly indicating unhappy network drivers.

Pentacore · Sep 26, 2024

mikeymikec said:
What's the PC spec? IMO it was Skype wanting something from one of your hardware drivers that it just couldn't handle.

Was Skype signed in?

NirSoft's BlueScreenView might point the finger at a particular driver. I would also check the Windows Event Viewer (Windows logs > system log) at events around the time of the crashes, maybe you've got a load of NDIS entries possibly indicating unhappy network drivers.

Thank you for this info. I have not tried BlueScreenView before, so I will add that to my notes.

PC Specs are:
MSI Z390-A Pro mobo
i9-9900k
32GB Ram
EVGA 3080ti
Windows 10 Pro

Skype is always signed in on that machine, so after killing it the game runs fine. I haven't tried to dig any further into it as I'm sidetracked playing the game. As long as Skype is dead the games runs OK. Strange I know. I will research this later though, so thanks again for all the info.

Question Constant BSODs in Windows 10 - DRIVER_IRQL_NOT_LESS_OR_EQUAL

Pentacore

Member

Pentacore

Member

mikeymikec

Lifer

Pentacore

Member

TRENDING THREADS