[SOLVED] Can someone help me to know what causes the BSOD

[ahmansour]

Hi here it is the analysis of the dump file by windbg :
***

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4592

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 65619

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: ffffe78c202cd763

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80360f11f34

READ_ADDRESS: fffff803618fb390: 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
ffffe78c202cd763

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

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

STACK_TEXT:
ffff8502601d43b8 fffff80361008b69 : 000000000000000a ffffe78c202cd763 0000000000000002 0000000000000000 : nt!KeBugCheckEx
ffff8502601d43c0 fffff80361004e69 : 0000000000000078 fffff80300000000 ffff8502601d45d0 ffffe78c2ff19938 : nt!KiBugCheckDispatch+0x69
ffff8502601d4500 fffff80360f11f34 : 0000000000000001 0000000000040286 0000000000000007 0000000000002ae0 : nt!KiPageFault+0x469
ffff8502601d4690 fffff803615b3149 : fffff803714c0000 ffffc009db3e6120 0000000000000000 0100000000100000 : nt!ExFreeHeapPool+0x124
ffff8502601d4770 fffff80371c4ae9e : 0000000000002ae0 ffffc009e83f8080 fffff803714c0000 0000000000000008 : nt!ExFreePool+0x9
ffff8502601d47a0 0000000000002ae0 : ffffc009e83f8080 fffff803714c0000 0000000000000008 fffff803714c0000 : vgk+0x78ae9e
ffff8502601d47a8 ffffc009e83f8080 : fffff803714c0000 0000000000000008 fffff803714c0000 0000000000000001 : 0x2ae0
ffff8502601d47b0 fffff803714c0000 : 0000000000000008 fffff803714c0000 0000000000000001 0000000000000000 : 0xffffc009e83f8080 ffff8502601d47b8 0000000000000008 : fffff803714c0000 0000000000000001 0000000000000000 0000000000002ae0 : vgk ffff8502601d47c0 fffff803714c0000 : 0000000000000001 0000000000000000 0000000000002ae0 ffff8502601d4840 : 0x8 ffff8502601d47c8 0000000000000001 : 0000000000000000 0000000000002ae0 ffff8502601d4840 fffff80371c04e1f : vgk ffff8502601d47d0 0000000000000000 : 0000000000002ae0 ffff8502601d4840 fffff80371c04e1f fffff803`60f60440 : 0x1


SYMBOL_NAME: nt!ExFreePool+9

IMAGE_NAME: Pool_Corruption

IMAGE_VERSION: 10.0.19041.1052

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
Can you tell me what i should do ?

 

[Colif]

vanguard caused the crash
vgk.sys - Vanguard anti cheat

which is funny, vanguard crashing valorant. Its meant to protect it

One thing I seen is vanguard seems to crash if you have other anti cheat programs on pc

could try reinstalling valorant/vanguard

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

 

[ahmansour]

vanguard caused the crash
vgk.sys - Vanguard anti cheat

which is funny, vanguard crashing valorant. Its meant to protect it

One thing I seen is vanguard seems to crash if you have other anti cheat programs on pc

could try reinstalling valorant/vanguard

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

Can it be for another reason from my hardware itself because i have just clean installed my windows for a week or its just a problem in thier anticheat
(Valorant is the only game i have on pc )

 

[Colif]

We can look

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

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 . . .

did you run memtest?

irq errors normally either drivers or ram, its why I suggested it

 

[ahmansour]

We can look

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

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 . . .

did you run memtest?

irq errors normally either drivers or ram, its why I suggested it

https://www.dropbox.com/s/jqxsxke5muylec6/070721-31703-01.zip?dl=0

 

[ahmansour]

We can look

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

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 . . .

did you run memtest?

irq errors normally either drivers or ram, its why I suggested it

i had run memtest before and had no errors

 

[Colif]

i will ask a friend to look at the dumps, he will reply later with a file I can read and see what it says. He may have an answer for you.

 

[ahmansour]

i will ask a friend to look at the dumps, he will reply later with a file I can read and see what it says. He may have an answer for you.

Ok i really appreciate your help

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/metpuq51/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:	070721-31703-01.dmp (Jul 7 2021 - 17:17:48)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:	*** WARNING: Unable to verify timestamp for vgk.sys
Probably caused by:	memory_corruption (Process: VALORANT-Win64-Shipping.exe)
Uptime:	0 Day(s), 3 Hour(s), 58 Min(s), and 48 Sec(s)

Crashing driver:

May 20 2021

vgk.sys

Vanguard Anti-Cheat driver

Possible Motherboard page: https://www.gigabyte.com/Motherboard/B450-AORUS-ELITE-rev-1x
You have the latest BIOS already installed, version F62c.

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]

well, we knew it was VGK.sys

how often does it happen?

you seem to have latest chipset drivers, or really close - https://www.amd.com/en/support/chipsets/amd-socket-am4/b450

Do you use wifi or Eitherner?

new Ethernet drivers are here under Windows header - Win10 Auto Installation Program (SId:1152921505693600553) - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

what WIFI card do you have?

this can cause errors

Dec 19 2018

idmwfp.sys

Internet Download Manager WFP driver (Tonec Inc.)

 

[ahmansour]

Thank you everyone i will try the solutions and let you know if there is anything new i just had this bsod 2 times so i hope it won't happen again