Please help, I don’t know what’s wrong with my PC. For the past two days, it’s been acting strangely. At first, I noticed that my PC makes a connect/disconnect sound after playing Valorant or Wuwa for a while. Then, I found out that it was my Bluetooth disconnects completely — it’s like it disappears from the system entirely. I can’t turn it back on, and the toggle to enable it is gone. (restart pc bring it back tho) I thought it might be a loose connection, so I re-plugged my Bluetooth adapter, but it didn’t help.
I then tried troubleshooting by uninstalling and reinstalling the Bluetooth driver, tweaking a couple of settings, but out of nowhere, my screen went black while playing Valorant. It wasn’t completely off; it was just displaying a black screen. There was stuttering sound, like sound when program freezes, and it stayed like that for 2-3 minutes before the PC shut down and rebooted itself.
So, I reinstalled Windows, wiping all drives and reinstalling everything fresh, including drivers, but the problem persisted. I updated the BIOS to the latest version, but that didn’t fix it either.
After some digging and trying to troubleshoot for 1-2 days, I was advised by GPT to use Driver Verifier to check for conflicting drivers. After enabling Driver Verifier, my PC restarted immediately when I launched Valorant.
The Driver Verifier report pointed to “vgk” something (probably Vanguard), so I thought Vanguard might be conflicting with other drivers. I reinstalled Windows again, but this time only installed Wuwa. However, the issue still occurred, though this time, the crash was related to something else — a Win32kfull.sys error.
I also suspected undervolting might be the issue, so I disabled it, but it didn’t fix the problem. I tried disabling XMP for my RAM as well, but that didn’t help either.
Here’s the thing: If I disable Driver Verifier, I can play both Valorant and Wuwa without crashing. (it crashed one time tho the first time I tried installing bluetooth driver) However, after playing for a while, the Bluetooth will disconnect again. But if I’m actively connected to Bluetooth (e.g., using headphones), it won’t disappear.
Lastly, the screen freeze/blackout I mentioned earlier (while playing Valorant) didn’t happen with Driver Verifier disabled. I’m really confused about what’s causing all of this. could it be gpu??? Any advice would be greatly appreciated.
My spec
Ryzen 5 7500f (2month old)
RTX4060 (4m old)
Asrock B650M pg lighting (2m old)
PSU 650W Corsair 80 plus bronze (1M old)
ram 4800 xmp 5200 16gb
This is what I see in Windbg from minidump of Driver verifier btw
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.156 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\OctusMF\Desktop\011925-21968-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff80035005000 PsLoadedModuleList = 0xfffff80035c2f810
Debug session time: Sun Jan 19 06:33:24.386 2025 (UTC + 7:00)
System Uptime: 0 days 0:03:29.008
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
PEB is paged out (Peb.Ldr = 000000000026f018). Type ".hh dbgerr001" for details Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800354038f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9309`c218e020=00000000000000c4
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000029d0, Handle value being referenced.
Arg3: ffffc00154178100, Address of the current process.
Arg4: ffff851f44934784, Address inside the driver that is performing the incorrect reference.
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 859
Key : Analysis.Elapsed.mSec
Value: 891
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: 234
Key : Analysis.Init.Elapsed.mSec
Value: 51354
Key : Analysis.Memory.CommitPeak.Mb
Value: 101
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0xc4
Key : Bugcheck.Code.TargetModel
Value: 0xc4
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0xc4\_f6\_win32kfull!xxxCreateWindowStation
Key : Failure.Hash
Value: {590a44da-142a-f32d-b873-1cef51d5069a}
BUGCHECK_CODE: c4
BUGCHECK_P1: f6
BUGCHECK_P2: 29d0
BUGCHECK_P3: ffffc00154178100
BUGCHECK_P4: ffff851f44934784
FILE_IN_CAB: 011925-21968-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
FAULTING_THREAD: ffffc00145295080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Client-Win64-S
STACK_TEXT:
ffff9309c218e018 fffff800359d9e34 : 00000000000000c4 00000000000000f6 00000000000029d0 ffffc00154178100 : nt!KeBugCheckEx
ffff9309c218e020 fffff800359e336f : ffffc00154178100 ffff9908af8faa20 ffff851f44934700 0000000000000005 : nt!VerifierBugCheckIfAppropriate+0xe0
ffff9309c218e060 fffff80035803f23 : 0000000000000000 0000000000000000 ffff9309c218e2e0 00000000000029d0 : nt!VfCheckUserHandle+0x1eb
ffff9309c218e150 fffff8003563b965 : ffffc00154178100 0000000000000000 0000000000000000 ffff9309c218e300 : nt!ObpReferenceObjectByHandleWithTag+0x1cbb63
ffff9309c218e1e0 fffff80035619db1 : ffffc00160706200 ffffc00142603a68 00000000000000c0 ffffc00ff9997c40 : nt!ObpLookupObjectName+0x285
ffff9309c218e3b0 fffff8003563e6b9 : ffffc00142603a80 ffff9309c218e6b0 0000000000000000 ffff9309c218e860 : nt!ObpInsertOrLocateNamedObject+0x141
ffff9309c218e590 fffff80035612a38 : 0000000000000000 ffff9309c218e8a0 ffffc001607062d0 0000000000000008 : nt!ObpCreateHandle+0x9a9
ffff9309c218e7a0 fffff80035676092 : ffff851f4480a950 ffff851f4469f37f ffff9908edd118b0 ffff851f44c18fc8 : nt!ObInsertObjectEx+0x488
ffff9309c218ea30 ffff851f44934784 : 0000000000000000 000000000000c019 ffff9309c218eb79 fffff800359dd5d0 : nt!ObInsertObject+0x22
ffff9309c218ea80 ffff851f44934453 : 0000000000000000 0000000000000000 ffff854400000008 00000000000029f8 : win32kfull!xxxCreateWindowStation+0x18c
ffff9309c218ebc0 ffff851f446991bc : ffff9309c218f328 ffff9309c218f3d0 ffff9309c218f310 beaa025100000018 : win32kfull!EditionCreateWindowStationEntryPoint+0x7b3
ffff9309c218f2f0 ffff851f44699103 : 0000000000000008 ffff9309c218f500 000000000a8bf228 ffff9309c218f428 : win32kbase!ApiSetEditionCreateWindowStationEntryPoint+0xac
ffff9309c218f360 ffff851f44e7e503 : 000000000a8bf880 0000000000000001 000000000a8bf278 fffff80035644b7c : win32kbase!NtUserCreateWindowStation+0x33
ffff9309c218f3b0 fffff80035417908 : 0000000000000000 fffff800357019fc 000000000a8bf270 ffff9309c218f500 : win32k!NtUserCreateWindowStation+0x53
ffff9309c218f410 00007ffefafa8844 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000000a8bf208 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe`fafa8844
SYMBOL_NAME: win32kfull!xxxCreateWindowStation+18c
MODULE_NAME: win32kfull
IMAGE_NAME: win32kfull.sys
IMAGE_VERSION: 10.0.19041.5247
STACK_COMMAND: .process /r /p 0xffffc00154178100; .thread 0xffffc00145295080 ; kb
BUCKET_ID_FUNC_OFFSET: 18c
FAILURE_BUCKET_ID: 0xc4_f6_win32kfull!xxxCreateWindowStation
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {590a44da-142a-f32d-b873-1cef51d5069a}
Followup: MachineOwner
7: kd> lmvm win32kfull
Browse full module list
start end module name
ffff851f448e0000 ffff851f44c94000 win32kfull (pdb symbols) C:\ProgramData\Dbg\sym\win32kfull.pdb\0EF87F5C2CB44B71C1C0316FDD062CFB1\win32kfull.pdb
Loaded symbol image file: win32kfull.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\win32kfull.sys\575458943b4000\win32kfull.sys
Image path: win32kfull.sys
Image name: win32kfull.sys
Browse all global symbols functions data Symbol Reload
Image was built with /Brepro flag.
Timestamp: 57545894 (This is a reproducible build file hash, not a timestamp)
CheckSum: 003A908C
ImageSize: 003B4000
File version: 10.0.19041.5247
Product version: 10.0.19041.5247
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: win32kfull.sys
OriginalFilename: win32kfull.sys
ProductVersion: 10.0.19041.5247
FileVersion: 10.0.19041.5247 (WinBuild.160101.0800)
FileDescription: Full/Desktop Win32k Kernel Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
