[SOLVED] BSOD IRQL NOT LESS OR EQUAL

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
R

rng223

May 7, 2021
24
0
10
So this happened twice already to me, just this moment and yesterday.
Yesterday it happened when i was was supposed to click shutdown when it suddenly BSOD and showed the error code IRQL NOT LESS OR EQUAL
And the second one happening after i closed VALORANT and once i clicked on my Opera browser it BSOD

After the first BSOD i looked into the internet for some solutions and updated my windows and drivers.
After the second BSOD what i did was i did a Windows Memory Diagnostic test, and came out with nothing and normal system

I checked for the Event Viewer log for the specific time it BSOD earlier, and it showed
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffb982ad779e63, 0x0000000000000002, 0x0000000000000000, 0xfffff8012ab11f34). A dump was saved in: C:\WINDOWS\Minidump\061321-11531-01.dmp. Report Id: 6900f948-d008-484b-a1da-8b4ac2a26ea0."

Will be attaching the minidump file at the bottom
https://1drv.ms/u/s!AnUU8guFS_5Par-AmzL7ZJPXz6A?e=oeUnDw

Any solutions to avoid this happening again in the future?



UPDATE: I did an "sfc /scannow" command in CMD and found a corrupt windows file. Checked the logs and it says "Repairing file \??\C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\\mscormmc.dll from store" and says that "Windows Resource Protection found corrupt files and successfully repaired them"
I dont know if this fixed the problem, but id be taking more solutions if ever it comes up
 
Last edited:
Solution
Colif
SO apart from it blaming Vanguard. other files I am not sure about are:
Nov 23 2020unirsdt.sysTencent driver (Tencent Technology)
not sure what this is. Wechat? most results are in Chinese.
search results hint it might be a virus. If you don't know what it is I would run Malwarebytes or https://www.bitdefender.com.au/solutions/free.html and check PC out.

I don't know if it might be the VPN. Vanguard might not like it.

thats about it, everything else seems normal.
Sort by date Sort by votes
Colif said:
what are specs of the PC?

I will ask a friend to convert dumps for us.
Click to expand...

It's a Lenovo IdeaPad 3 15ARE05 model 81W4


UPDATE: I did an "sfc /scannow" command in CMD and found a corrupt windows file. Checked the logs and it says "Repairing file \??\C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\\mscormmc.dll from store" and says that "Windows Resource Protection found corrupt files and successfully repaired them"
I dont know if this fixed the problem, but id be taking more solutions if ever it comes up
 
Upvote 0 Downvote
Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/fk3r6cdz/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:061321-11531-01.dmp (Jun 13 2021 - 10:27:46)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for vgk.sys
Probably caused by:Pool_Corruption (Process: VALORANT-Win64)
Uptime:0 Day(s), 8 Hour(s), 17 Min(s), and 33 Sec(s)

Comment: 2 or more types of RAM are installed. (Common on laptops).

System: IdeaPad 3 15ARE05

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
gardenman said:
I think it might from Tencent according to this: https://www.bleepingcomputer.com/forums/t/749889/cant-delete-unirsdtsys/
and a few other sites. I've update the description to say:
Tencent driver (Tencent Technology)
Click to expand...

Ok so it makes sense how this happens right after i close down VALORANT. I've heard some issues regarding complications with the Easy Anti-cheat and VANGUARD, since i had Apex installed in here. It's been a problem with the community since Valorant had ever existed, and to my belief i think there is still no fix for this. Thanks for all the info tho, it was greatly appreciated! If you do know some ways to actually fix this, would be a great help and would be appreciated
 
Upvote 0 Downvote
Who would have guessed 2 anti cheat applications don't get along. It would be like having two Anti virus, they likely see each other as a threat. They would both be scanning system... wonder if it slows pc down

I don't have any proof it was that driver, it was just an unknown in the driver list, but if it has a history of conflicts. its could be it.

Do both always have to be running, even if you not using a game that uses them? Why is anti cheat on if you playing Valorant?

or is it other way around as it appears 1 year ago having vgk.sys on system and trying to play a game that uses anti cheat would cause BSOD - link
Only solution was to uninstall Valorant, since Vanguard runs even when you aren't playing Valorant.

hmm, Easy anti cheat & VGK.sys both work at kernel lvl - link - Talk about wanting to control the system.

Isn't BattlEye and Easy Anti-Cheat kernel drivers that only get started when the game starts?

If this is the case I think most people are asking about why it needs to be on startup of the system instead of startup of the game. And that the concern people are raising is about what it could do when it's running when you're not playing the game.
Click to expand...

same link as above

I already feel Vanguard would be classified as malware if it didn't do something else as well.
 
Upvote 0 Downvote
Colif said:
Who would have guessed 2 anti cheat applications don't get along. It would be like having two Anti virus, they likely see each other as a threat. They would both be scanning system... wonder if it slows pc down

I don't have any proof it was that driver, it was just an unknown in the driver list, but if it has a history of conflicts. its could be it.

Do both always have to be running, even if you not using a game that uses them? Why is anti cheat on if you playing Valorant?

or is it other way around as it appears 1 year ago having vgk.sys on system and trying to play a game that uses anti cheat would cause BSOD - link
Only solution was to uninstall Valorant, since Vanguard runs even when you aren't playing Valorant.

hmm, Easy anti cheat & VGK.sys both work at kernel lvl - link - Talk about wanting to control the system.



same link as above

I already feel Vanguard would be classified as malware if it didn't do something else as well.
Click to expand...

I couldn't replicate it again no matter how much tries i do. Either i already fixed it, or i have no idea how it happens in the first place at all and have no clue how to replicate it. Not knowing how to replicate the problem is too a problem. Im having doubts about the Easy Anti-Cheat being the problem as I didn't even initiate it a single time during both sessions where it BSOD'd. As long as Riot, the devs for Valorant and Vanguard, doesn't release something talking about this issue or bother creating a hotfix for it, i think id still persist for some and maybe for me. I couldn't tell if i already fixed it with the solutions i did above, as i couldn't even replicate it at the first place for me to test if it does happen ever again.

EDIT: I also ran Malwarebytes but it didn't pick up anything
 
Upvote 0 Downvote
Colif said:
just wait a week or so. If BSOD are going to happen, they will.

only way to tell with some is when they stop happening.
Click to expand...

Hey Colif, speaking here 2 weeks after. It happened again...
Same error code, IRQL NOT LESS OR EQUAL. Just checked my Event Viewer Logs, doesn't say anything about it creating a minidump again. But did say that was a previous system shutdown that was unexpected, the error code before that, was the vgc service being terminated and crashing unexpectedly, which is the VANGUARD service. Safe to say that yes the VANGUARD is the one causing the BSODs. Still no fix from RIOT, would still persist

EDIT: The event ID of the unexpected shutdown code is 6008, dont know if it matters but im just going to say it anyway

EDIT 2: Did another sfc /scannow and Malwarebytes scan, nothing came up. Everything is perfectly normal and fine. Prime suspect is def VANGUARD
 
Last edited:
Upvote 0 Downvote
I can think of one solution but if you want to play Valorant, it won't work... its uninstall valorant and vanguard. then the other game anti cheat won't cause the problem

Vanguard thinks it owns your PC, and thinks you should only play Valorant, none of those other games... talk about jealous :)

At least cause is known, its how long are you willing to put up with it?
 
Upvote 0 Downvote
Colif said:
I can think of one solution but if you want to play Valorant, it won't work... its uninstall valorant and vanguard. then the other game anti cheat won't cause the problem

Vanguard thinks it owns your PC, and thinks you should only play Valorant, none of those other games... talk about jealous :)

At least cause is known, its how long are you willing to put up with it?
Click to expand...

Dang.. It's the only thing that me and my friends religiously play everyday so theres no chance that's happening lol. Until then i guess, until RIOT doesn't release a fix, this would still persist, but though it doesn't really happen whilst im doing something, usually only happens when i do close it.
 
Upvote 0 Downvote
Colif said:
I can think of one solution but if you want to play Valorant, it won't work... its uninstall valorant and vanguard. then the other game anti cheat won't cause the problem

Vanguard thinks it owns your PC, and thinks you should only play Valorant, none of those other games... talk about jealous :)

At least cause is known, its how long are you willing to put up with it?
Click to expand...

Hello Colin, here speaking another month after, still months after, crashing still persists, although this time it did not do a BSOD, but instead froze for a solid 10 seconds with a glitched audio (had happened whilst watching a youtube video) and had the system unexpectedly restart on its own. Had check the EV Log and it created a minidump file, which i had analyzed with the WinDbg tool, also did a sfc /scannow with the result showing "Windows Resource Protection did not find any integrity violations." which i had no idea if it was either a good or bad result, either way it didn't do anything else. No Malwarebytes results either.


This is what the Debugger analyzed the minidump with.

***
  • *
  • 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: ffffd5857db7de03, 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: fffff805102891e4, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2702

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6524

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

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

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: a

BUGCHECK_P1: ffffd5857db7de03

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff805102891e4

READ_ADDRESS: fffff80510cfa390: 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
ffffd5857db7de03

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

TRAP_FRAME: fffff90e4e2d8500 -- (.trap 0xfffff90e4e2d8500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80510000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805102891e4 rsp=fffff90e4e2d8690 rbp=fffff90e4e2d87c0
r8=0000000000000001 r9=0000000000000001 r10=ffffe58346613668
r11=0000000000000076 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExFreeHeapPool+0x124:
fffff805102891e4 f646f304 test byte ptr [rsi-0Dh],4 ds:fffffffffffffff3=??
Resetting default scope

STACK_TEXT:
fffff90e4e2d83b8 fffff80510408e69 : 000000000000000a ffffd5857db7de03 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff90e4e2d83c0 fffff80510405169 : 0000000000000000 ffffd585821eba38 ffffd5856f000100 fffff80510289422 : nt!KiBugCheckDispatch+0x69
fffff90e4e2d8500 fffff805102891e4 : 0000000000002734 fffff80510602491 0000000000040283 0000000000040286 : nt!KiPageFault+0x469
fffff90e4e2d8690 fffff805109b3149 : fffff80515f52420 0000000000002700 0000000000000076 0100000000100000 : nt!ExFreeHeapPool+0x124
fffff90e4e2d8770 fffff80516678cd7 : 0000000000002734 ffffe583466130c0 fffff80515ee0000 0000000000000008 : nt!ExFreePool+0x9
fffff90e4e2d87a0 0000000000002734 : ffffe583466130c0 fffff80515ee0000 0000000000000008 fffff80515ee0000 : vgk+0x798cd7
fffff90e4e2d87a8 ffffe583466130c0 : fffff80515ee0000 0000000000000008 fffff80515ee0000 0000000000000001 : 0x2734
fffff90e4e2d87b0 fffff80515ee0000 : 0000000000000008 fffff80515ee0000 0000000000000001 0000000000000000 : 0xffffe583466130c0 fffff90e4e2d87b8 0000000000000008 : fffff80515ee0000 0000000000000001 0000000000000000 0000000000002734 : vgk fffff90e4e2d87c0 fffff80515ee0000 : 0000000000000001 0000000000000000 0000000000002734 fffff90e4e2d8840 : 0x8 fffff90e4e2d87c8 0000000000000001 : 0000000000000000 0000000000002734 fffff90e4e2d8840 fffff805166322a5 : vgk fffff90e4e2d87d0 0000000000000000 : 0000000000002734 fffff90e4e2d8840 fffff805166322a5 fffff805`102d7910 : 0x1


SYMBOL_NAME: nt!ExFreePool+9

IMAGE_NAME: Pool_Corruption

IMAGE_VERSION: 10.0.19041.1110

MODULE_NAME: Pool_Corruption

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9

FAILURE_BUCKET_ID: AV_nt!ExFreePool

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2ae0a97e-dcd7-47ef-dbfb-430f2cbf58a1}

Followup: Pool_corruption
 
Upvote 0 Downvote
its not often I see Valorant being crashed by vgk.sys
vgk.sys = Vanguard anti cheat.

can you upload the minidump to same place as last time and I look to see if something might be tripping vgk.sys up but that error is pretty clear,
generally if you see a driver name in

STACK_TEXT:
fffff90e4e2d83b8 fffff80510408e69 : 000000000000000a ffffd5857db7de03 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff90e4e2d83c0 fffff80510405169 : 0000000000000000 ffffd585821eba38 ffffd5856f000100 fffff80510289422 : nt!KiBugCheckDispatch+0x69
fffff90e4e2d8500 fffff805102891e4 : 0000000000002734 fffff80510602491 0000000000040283 0000000000040286 : nt!KiPageFault+0x469
fffff90e4e2d8690 fffff805109b3149 : fffff80515f52420 0000000000002700 0000000000000076 0100000000100000 : nt!ExFreeHeapPool+0x124
fffff90e4e2d8770 fffff80516678cd7 : 0000000000002734 ffffe583466130c0 fffff80515ee0000 0000000000000008 : nt!ExFreePool+0x9
fffff90e4e2d87a0 0000000000002734 : ffffe583466130c0 fffff80515ee0000 0000000000000008 fffff80515ee0000 : vgk+0x798cd7
fffff90e4e2d87a8 ffffe583466130c0 : fffff80515ee0000 0000000000000008 fffff80515ee0000 0000000000000001 : 0x2734
fffff90e4e2d87b0 fffff80515ee0000 : 0000000000000008 fffff80515ee0000 0000000000000001 0000000000000000 : 0xffffe583466130c0
fffff90e4e2d87b8 0000000000000008 : fffff80515ee0000 0000000000000001 0000000000000000 0000000000002734 : vgk
fffff90e4e2d87c0 fffff80515ee0000 : 0000000000000001 0000000000000000 0000000000002734 fffff90e4e2d8840 : 0x8
fffff90e4e2d87c8 0000000000000001 : 0000000000000000 0000000000002734 fffff90e4e2d8840 fffff805166322a5 : vgk
fffff90e4e2d87d0 0000000000000000 : 0000000000002734 fffff90e4e2d8840 fffff805166322a5 fffff805`102d7910 : 0x1

it is the cause. that one is there 3 times.
 
Upvote 0 Downvote
Here's the link
Colif said:
its not often I see Valorant being crashed by vgk.sys
vgk.sys = Vanguard anti cheat.

can you upload the minidump to same place as last time and I look to see if something might be tripping vgk.sys up but that error is pretty clear,
generally if you see a driver name in

STACK_TEXT:
fffff90e4e2d83b8 fffff80510408e69 : 000000000000000a ffffd5857db7de03 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff90e4e2d83c0 fffff80510405169 : 0000000000000000 ffffd585821eba38 ffffd5856f000100 fffff80510289422 : nt!KiBugCheckDispatch+0x69
fffff90e4e2d8500 fffff805102891e4 : 0000000000002734 fffff80510602491 0000000000040283 0000000000040286 : nt!KiPageFault+0x469
fffff90e4e2d8690 fffff805109b3149 : fffff80515f52420 0000000000002700 0000000000000076 0100000000100000 : nt!ExFreeHeapPool+0x124
fffff90e4e2d8770 fffff80516678cd7 : 0000000000002734 ffffe583466130c0 fffff80515ee0000 0000000000000008 : nt!ExFreePool+0x9
fffff90e4e2d87a0 0000000000002734 : ffffe583466130c0 fffff80515ee0000 0000000000000008 fffff80515ee0000 : vgk+0x798cd7
fffff90e4e2d87a8 ffffe583466130c0 : fffff80515ee0000 0000000000000008 fffff80515ee0000 0000000000000001 : 0x2734
fffff90e4e2d87b0 fffff80515ee0000 : 0000000000000008 fffff80515ee0000 0000000000000001 0000000000000000 : 0xffffe583466130c0
fffff90e4e2d87b8 0000000000000008 : fffff80515ee0000 0000000000000001 0000000000000000 0000000000002734 : vgk
fffff90e4e2d87c0 fffff80515ee0000 : 0000000000000001 0000000000000000 0000000000002734 fffff90e4e2d8840 : 0x8
fffff90e4e2d87c8 0000000000000001 : 0000000000000000 0000000000002734 fffff90e4e2d8840 fffff805166322a5 : vgk
fffff90e4e2d87d0 0000000000000000 : 0000000000002734 fffff90e4e2d8840 fffff805166322a5 fffff805`102d7910 : 0x1

it is the cause. that one is there 3 times.
Click to expand...


Here is the link: https://1drv.ms/u/s!AnUU8guFS_5Pb9g6fwLDqFjx3no
 
Upvote 0 Downvote
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/jao7feyu/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:072121-12281-01 - Copy.dmp (Jul 20 2021 - 12:04:40)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for vgk.sys
Probably caused by:Pool_Corruption (Process: VALORANT-Win64)
Uptime:0 Day(s), 1 Hour(s), 47 Min(s), and 28 Sec(s)

Comment: 2 or more types of RAM are installed.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
SO apart from it blaming Vanguard. other files I am not sure about are:
Nov 23 2020unirsdt.sysTencent driver (Tencent Technology)
not sure what this is. Wechat? most results are in Chinese.
search results hint it might be a virus. If you don't know what it is I would run Malwarebytes or https://www.bitdefender.com.au/solutions/free.html and check PC out.

I don't know if it might be the VPN. Vanguard might not like it.

thats about it, everything else seems normal.
 
  • Like
Reactions: X4Phenom
Upvote 0 Downvote
Solution
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom