Question Getting BSODs in games ? WinDbg results below

[rodrigojkrs]

I'm only having these problems in games, games crash and then blue screen.

DMP Files: Google Drive DMP

---------------------------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Rodrigo\Desktop\DMP\052523-12890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff806`27e00000 PsLoadedModuleList = 0xfffff806`28a2a2d0
Debug session time: Thu May 25 18:14:32.839 2023 (UTC - 3:00)
System Uptime: 0 days 0:14:37.447
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`281fbfc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd38b`49aa76c0=000000000000000a
6: 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: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff806280e09ff, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1999

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3245

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0xa

Key : Bugcheck.Code.Register
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 052523-12890-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: a

BUGCHECK_P1: 3

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff806280e09ff

WRITE_ADDRESS: fffff80628afb390: 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
0000000000000003

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MsMpEng.exe

TRAP_FRAME: ffffd38b49aa7800 -- (.trap 0xffffd38b49aa7800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffbf8e148d8d50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806280e09ff rsp=ffffd38b49aa7990 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=ffffbf8df7156b00
r11=ffffd6039fd86040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiAcquireKobjectLockSafe+0xf:
fffff806`280e09ff f00fba2907 lock bts dword ptr [rcx],7 ds:00000000`00000003=????????
Resetting default scope

STACK_TEXT:
ffffd38b`49aa76b8 fffff806`28210029 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd38b`49aa76c0 fffff806`2820bbe3 : ffffbf8e`0a7b2080 ffffbf8e`0c015d20 ffffbf8e`0cbf5e58 fffff806`28007682 : nt!KiBugCheckDispatch+0x69
ffffd38b`49aa7800 fffff806`280e09ff : 00000000`00000000 00000178`ff2b9d48 ffffd38b`49aa7aa8 00000000`00000000 : nt!KiPageFault+0x463
ffffd38b`49aa7990 fffff806`2809522e : 00000000`00000003 00000178`ff210d48 ffffbf8e`0a7b2080 fffff806`28411bbe : nt!KiAcquireKobjectLockSafe+0xf
ffffd38b`49aa79c0 fffff806`28246f7e : 00000000`00000000 ffffbf8e`148d8d50 00000000`00000002 00000000`00000000 : nt!KeInsertQueueEx+0x9e
ffffd38b`49aa7a30 fffff806`2820f7f8 : ffffbf8e`0a7b2080 ffffbf8e`00000000 ffffbf8e`0ac9aab0 ffffd38b`49aa7b40 : nt!NtReleaseWorkerFactoryWorker+0x1ba94e
ffffd38b`49aa7ac0 00007ffa`099efec4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000004f`4458f3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`099efec4


SYMBOL_NAME: nt!KiAcquireKobjectLockSafe+f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3031

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: f

FAILURE_BUCKET_ID: AV_nt!KiAcquireKobjectLockSafe

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {87978629-0a82-b7ad-caa7-eb2c5ba684a3}

Followup: MachineOwner
---------

 

[Colif]

Specs of pc could help

MsMpEng.exe

that is part of defender. Without looking at dumps I could guess you might need to update LAN drivers.

But if I look at dumps... i might see more...

Conversion of dump files

report - click run as fiddle to read


File: 052723-12312-01.dmp (May 28 2023 - 04:11:36)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
Probably caused by: vgk.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 06 Sec(s)

File: 052623-54843-01.dmp (May 27 2023 - 04:14:26)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: WerFault.exe)
Uptime: 0 Day(s), 0 Hour(s), 08 Min(s), and 08 Sec(s)

File: 052623-12921-01.dmp (May 26 2023 - 23:59:49)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: Pool_Corruption (Process: explorer.exe)
Uptime: 0 Day(s), 0 Hour(s), 16 Min(s), and 49 Sec(s)

File: 052623-12812-01.dmp (May 27 2023 - 08:50:28)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: LeagueCrashHan)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 36 Sec(s)

File: 052523-12890-01.dmp (May 26 2023 - 07:14:32)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: MsMpEng.exe)
Uptime: 0 Day(s), 0 Hour(s), 14 Min(s), and 37 Sec(s)

Processes named are victims


You most recent BSOD caused by Vanguard - Valorants anti cheat. Try updating it.

I have seen this cause BSOD before

Jun 13 2019

cfosspeed6.sys

cFosSpeed driver (cFos Software)

Do you use Ethernet cable or WIFI?
if ethernet, download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

crash 2 & 3 look like they could be GPU driver related

try running DDU in safe mode, uninstall Nvidia drivers, boot back into normal mode and reinstall Nvidia drivers

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

 

[ubuysa]

Has someone advised you to enable Driver Verifier? If so, what settings did you use?

One of the dumps is a Driver Verifier generated dump which very clearly shows vgk.sys (Valorant anti-cheat) failing to free it's pool allocations before closing. I've seen vgk.sys cause countless BSODs before. The version of vgk.sys that you have is pretty current (May 3rd 2023), so there's unlikely to be an update. I would suggest you turn it off as shown here. and see whether the BSODs stop and/or see whether Valorant Support have any advice.

That said, the other BSODs look much more like having a hardware cause, so it's worth testing your RAM thoroughly.

 

[rodrigojkrs]

Thank you for helping guys, here are the specs:


CPU: AMD Ryzen 9 5900x
MOBO: TUF GAMING B550M-PLUS WIFI II
RAM: 2X8GB HyperX Fury Black 8 GB CL15 DIMM DDR4 2400
GPU: NVIDIA GeForce RTX 2060 SUPER
PS: COUGAR SL 500 500W 80 PLUS

I'm using Ethernet cable, I'll try to update the driver. About DDU, I did this process before creating this post and it didn't solve the problem, I'll uninstall Valorant and see if this continues. Today I was playing an io game in the browser and then I got a new dmp, here it is: DMP FILE

About Driver Verifier, yes I tried to use it that way, "Create Standard Settings> Automatically select all drivers installed on this computer" and then I had to restart, after 2 loops it showed this message: DRIVER VERIFIER IOMANAGER VIOLATION

 

[rodrigojkrs]

I did everything suggested above and nothing fixed the problem, I got 2 new DMP on Spotify and Driver Easy: NEW DMP Files

 

[ubuysa]

Third-party driver install tools like Driver Easy are NOT recommended - at all. You have no idea whether the tool is selecting the correct driver, nor from where the driver has come. Drivers should only ever be sourced from the PC vendor's website, the motherboard vendor's website, Windows Update, or the specific hardware device vendor's website.

Those three dumps look very much like hardware, so I really would test your RAM. Download Memtest86, use the extracted tool to make a bootable USB drive, then boot that USB drive. Memtest will start running as soon as it boots.

If no errors are found after the four iterations of the 13 different tests, then restart Memtest and do another 4 iterations (for a total of 8). Even a single bit error is a failure.

If Memtest finds no RAM errors let us know and I'll show you have to run Driver Verifier with the best options.

 

[rodrigojkrs]

Third-party driver install tools like Driver Easy are NOT recommended - at all. You have no idea whether the tool is selecting the correct driver, nor from where the driver has come. Drivers should only ever be sourced from the PC vendor's website, the motherboard vendor's website, Windows Update, or the specific hardware device vendor's website.

Those three dumps look very much like hardware, so I really would test your RAM. Download Memtest86, use the extracted tool to make a bootable USB drive, then boot that USB drive. Memtest will start running as soon as it boots.

If no errors are found after the four iterations of the 13 different tests, then restart Memtest and do another 4 iterations (for a total of 8). Even a single bit error is a failure.

If Memtest finds no RAM errors let us know and I'll show you have to run Driver Verifier with the best options.

I had installed the drivers from the motherboard website, Driver Easy was just a try.
I did tests with Memtest86 and it showed me several errors, maybe we found my problem? IMG ERRORS

 

[ubuysa]

Yep, your RAM is faulty and that will be your problem. You could run Memtest on each stick to find the flaky one, but TBH you're better off buying another pack of 2 x 8GB RAM sticks to be sure of getting a matched pair.

 

[rodrigojkrs]

Ok, I bought new RAMs and a power supply and the problem is solved, thanks everyone for your help guys