Question dxgkrnl.sys BSOD

[Sir Tiffy Cashien]

I'd like to start off and apologize for this question since I am sure different BSOD questions come in every day.

I have been having BSOD issues the last few days, sometimes it doesn't happen for a month or so but it eventually comes back.
I downloaded WhoCrashed which I saw from another post, and these are my results

I am updated on Windows and have been for quite some time.
I just updated my GPU drivers as I made this post as well (outdated for 2 weeks, was having BSOD well before that)

I can't replicate the BSOD, it just happens when I'm playing video games or watching YouTube. My screen will kind of flicker and the program I'm using might freeze? for a second and THEN BAM BSOD!

Thank you for any help.

EDIT: Not the most computer savvy person so I don't really know the steps to take after reading the dump files. I apologize if the answer is right in front of me.

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 6/13/2022 1:26:04 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061322-13890-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF8072A2FD3C6)
Bugcheck code: 0x50 (0xFFFF9082A05DF000, 0x2, 0xFFFFF8072A2FD3C6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 6/13/2022 1:26:04 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF8072A2FD3C6)
Bugcheck code: 0x50 (0xFFFF9082A05DF000, 0x2, 0xFFFFF8072A2FD3C6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 6/11/2022 3:31:25 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061122-13750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F7D60)
Bugcheck code: 0xA (0xFFFFCC49C00003E8, 0x2, 0x0, 0xFFFFF80453A480F9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 5/18/2022 6:42:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051822-14406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F7D60)
Bugcheck code: 0xA (0xFFFFFF0000000000, 0x2, 0x0, 0xFFFFF8061F849FD6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 4/23/2022 2:26:03 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042322-15968-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF80674376EF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80674376EF2, 0xFFFFFA0424CC1930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you

EDIT 2: I followed a tutorial that a mod linked on how to use "Driver Verifier" on a similar post. I am here to say I will NEVER do that again since I was stuck in a constant BSOD loop because of it. Luckily I created a restore point right before I did all of this and I was able to restore successfully.

After getting back onto Windows and re-installing WhoCrashed, this is what Driver Verifier found:
Riot Vanguard is the anti-cheat for Valorant, so I just uninstalled it since I no longer play the game.
If anybody can confirm that was the issue I would appreciate it!!!

On Mon 6/13/2022 1:59:49 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061322-13500-01.dmp
This was probably caused by the following module: vgk.sys (0xFFFFF80F9039FD24)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80F9039FD24, 0x0, 0x656E6F4E)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Program Files\Riot Vanguard\vgk.sys
product: Vanguard Driver
company: Riot Games, Inc.
description: Vanguard kernel-mode driver.
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vgk.sys (Vanguard kernel-mode driver., Riot Games, Inc.).
Google query: vgk.sys Riot Games, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION



On Mon 6/13/2022 1:59:49 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: vgk.sys (0xFFFFF80F9039FD24)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF80F9039FD24, 0x0, 0x656E6F4E)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Program Files\Riot Vanguard\vgk.sys
product: Vanguard Driver
company: Riot Games, Inc.
description: Vanguard kernel-mode driver.
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vgk.sys (Vanguard kernel-mode driver., Riot Games, Inc.).
Google query: vgk.sys Riot Games, Inc. DRIVER_VERIFIER_DETECTED_VIOLATION

 

[johnbl]

change the memory dump type to kernel and provide the next memory.dmp file.
put the next memory.dmp file on a cloud server, share the file for public access and post a link.

the bugchecks were in the graphics subsystem, you will want to confirm that you are not running any overclock drivers. Update any motherboard sound driver.

go into bios, change any setting and change it back, save configuration and reboot.

when you run verifier you should know how to get into safe mode so you can turn it off via
verifier.exe /reset
or maybe use one of these safer options that turns it off automatically:
verifier.exe /bootmode disableafterfail
or
verifier.exe /bootmode oneboot