Help analyzing BSOD dump

Question

My computer has been BSODing quite often lately with the code IRQL_NOT_LESS_OR_EQUAL. I was able to get the dump file but I need help understanding it.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80119400000 PsLoadedModuleList = 0xfffff8011a02a1d0
Debug session time: Tue Jul 20 23:16:44.099 2021 (UTC - 7:00)
System Uptime: 0 days 1:34:24.738
Loading Kernel Symbols
...............................................................
................................................................
.........................Page 1db3a0 not present in the dump file. Type ".hh dbgerr004" for details
.......................................
...............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d4`c3f3d018). Type ".hh dbgerr001" for details
Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
7: 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: ffff838339dda000, 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: fffff801196cb748, address which referenced memory

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.Sec  
Value: 2  

Key  : Analysis.DebugAnalysisProvider.CPP  
Value: Create: 8007007e on BRIANSCOMPUTER  

Key  : Analysis.DebugData  
Value: CreateObject  

Key  : Analysis.DebugModel  
Value: CreateObject  

Key  : Analysis.Elapsed.Sec  
Value: 4  

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

Key  : Analysis.System  
Value: CreateObject  

BUGCHECK_CODE: a

BUGCHECK_P1: ffff838339dda000

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801196cb748

READ_ADDRESS: ffff838339dda000 Paged pool

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

TRAP_FRAME: ffffc1826638f350 -- (.trap 0xffffc1826638f350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff838339dda000 rbx=0000000000000000 rcx=ffff838316c04898
rdx=ffff838316c04888 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801196cb748 rsp=ffffc1826638f4e0 rbp=0000000000000000
r8=ffff8383445ed000 r9=0000000000000000 r10=0000000000000000
r11=00000000000002cd r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlpHpLfhSubsegmentFreeBlock+0x2a8:
fffff801196cb748 483930 cmp qword ptr [rax],rsi ds:ffff838339dda000=ffff838346ff8000
Resetting default scope

STACK_TEXT:
ffffc1826638f208 fffff80119808e69 : 000000000000000a ffff838339dda000 0000000000000002 0000000000000000 : nt!KeBugCheckEx
ffffc1826638f210 fffff80119805169 : fffff8012fa61073 00000000000000ff 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69
ffffc1826638f350 fffff801196cb748 : fffff8012f7b403a ffff838346ffdaf0 ffffc1826638f6c0 0000000000040286 : nt!KiPageFault+0x469
ffffc1826638f4e0 fffff80119689422 : ffff838316c00340 fffff80119a024ff 0000000000040283 0000000000000000 : nt!RtlpHpLfhSubsegmentFreeBlock+0x2a8
ffffc1826638f590 fffff80119db3149 : fffff80100000000 0000000000003c00 0000000000000076 0100000000100000 : nt!ExFreeHeapPool+0x362
ffffc1826638f670 fffff8012fe58cd7 : 0000000000003c78 ffffaf0f65be3080 fffff8012f6c0000 0000000000000008 : nt!ExFreePool+0x9
ffffc1826638f6a0 fffff8012fe122a5 : fffff801196d7910 fffff80119608270 0000000000000001 0000000000000001 : vgk+0x798cd7
ffffc1826638f6f0 fffff8012fe11c63 : 0000000000000000 0000000000000904 0000000000003c78 ffffaf0f65be3080 : vgk+0x7522a5
ffffc1826638f760 fffff80119a02491 : 0000000000000000 ffffc1826638f7f9 ffffaf0f541f2670 fffff80101046000 : vgk+0x751c63
ffffc1826638f790 fffff80119a1d264 : ffffaf0f65be3000 ffffaf0f65be3080 0000000000000000 0000000000000000 : nt!PspCallProcessNotifyRoutines+0x255
ffffc1826638f860 fffff80119ab0682 : ffffaf0f65f994b8 0000000000000000 0000000000000000 0000000000000000 : nt!PspExitProcess+0x70
ffffc1826638f890 fffff80119ab3bbe : ffffaf0f00000000 0000000000000001 ffffffffffffffff 000000d4c3f3e000 : nt!PspExitThread+0x5b2
ffffc1826638f990 fffff80119808dee : ffffaf0f65be3080 ffffaf0f65f99080 ffffc1826638fa80 ffffaf0f00000000 : nt!NtTerminateProcess+0xde
ffffc1826638fa00 00007ffa508ad3a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x2b9
000000d4c4b7f908 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`508ad3a4

SYMBOL_NAME: nt!ExFreePool+9

IMAGE_NAME: Pool_Corruption

MODULE_NAME: Pool_Corruption

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9

FAILURE_BUCKET_ID: AV_nt!ExFreePool

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: Pool_corruption

Answer 1

Hi Devouring Waffle, glad to help!

Answer 2

Got it I'll give that a try! Thanks for helping me understand the issue!

Answer 3

Hi Devouring Waffle

Your minidump file indicates a driver (vgk.sys) associated to the Vanguard Anti-Cheat engine is causing your system crashes, the best option would be to re-install that software, because vkg.sys is known to cause a lot of Blue Screens.

Answer 4

Here you go!

https://1drv.ms/u/s!AlmH1f1Yce8qiV-JXiaGPODxSLJ0?e=ToCLvS

Answer 5

Hi Devouring Waffle,

I am Dave, an Independent Advisor, I will help you with this.

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.