Windows 11 BSOD

K

kvothe

Member
Joined
Dec 1, 2024
Posts
7
My PC has been blue screening multiple times per day. I have tried to look at the minidump files to identify an issue and haven't been able to. I have updated my drivers.

http://speccy.piriform.com/results/KI6hVHANnJJ4pvPlK5j0BiH

Specs:
I9 14900K
Nvidia GeForce RTX 4090
64gb of Kingston Fury Beast 6000Mhz
ASUS ROG Maximus Z790 Dark Hero

driver verifier disabled
 

Attachments

I9 14900K only supports DDR4 3200MHz and DDR5 5600 MHz of ram.
Yet you have 6000 MHz of ram, the sysnative file collection of ram information shows 4800 MHz.
 
Hello and welcome to the forum!

Taken as a group the dumps strongly suggest that bad RAM may be the cause here. It's not so much the configured speed, the RAM is clocked at its native (SPD) speed of 4800MHz which is fine. In any case, the 5600MHz that Intel quote is only the maximum guaranteed RAM speed, most CPUs can use RAM clocked higher than this.

It will take a long time to test that 64GB of RAM with a memory tester, it will be much easier for you to simply remove one RAM stick for a few days, or until you get a BSOD. Then swap the sticks over and run on just the other stick for a few days, or until you get a BSOD. If you get a BSOD on both sticks when run on their own then RAM is probably not the problem and we'll look elsewhere.

Do check with your motherboard manual that the single stick is in the correct slot (typically A2).

Let us know how that RAM testing goes.
 
ubuysa said:
Hello and welcome to the forum!

Taken as a group the dumps strongly suggest that bad RAM may be the cause here. It's not so much the configured speed, the RAM is clocked at its native (SPD) speed of 4800MHz which is fine. In any case, the 5600MHz that Intel quote is only the maximum guaranteed RAM speed, most CPUs can use RAM clocked higher than this.

It will take a long time to test that 64GB of RAM with a memory tester, it will be much easier for you to simply remove one RAM stick for a few days, or until you get a BSOD. Then swap the sticks over and run on just the other stick for a few days, or until you get a BSOD. If you get a BSOD on both sticks when run on their own then RAM is probably not the problem and we'll look elsewhere.

Do check with your motherboard manual that the single stick is in the correct slot (typically A2).

Let us know how that RAM testing goes.
Click to expand...
I ran Memtester86 and it was not able to find any issues.

I will try running with one stick at a time to see if that can narrow the issue down.
 
OK, try on a single stick for at least 24 hours, since you are getting multiple BSODs a day, and then swap sticks.

If it BSODs on both sticks on their own then we'll look somewhere else.
 
I have b
ubuysa said:
OK, try on a single stick for at least 24 hours, since you are getting multiple BSODs a day, and then swap sticks.

If it BSODs on both sticks on their own then we'll look somewhere else.
Click to expand...
I have had a BSOD on each stick now, so I don't think that is the issue.
 
Fair enough. In that case I suggest you enable Driver Verifier to see whether there is a rogue third-party driver causing these BSODs. Be sure to keep all dumps produced whilst Driver Verifier is enabled and upload them when you disable it please.
 
kvothe said:
I have b

I have had a BSOD on each stick now, so I don't think that is the issue.
Click to expand...
Please set the dump to complete dump mode
and then share with us the memory.dmp

From the System event log you have multi bugchecks
that point 1 of 2
1. memory corruption
2. Driver that causing it
enable Complete dump and when it, it should be under c:\windows\memory.dmp
zip the file and upload
 
NO!

Please DO NOT set the dump to complete dump mode. None of us are going to download a 64GB dump file when a 256kB minidump tells us all we need to know.

Just enable Driver Verifier as I advised and leave the dump type alone.
 
Sorry for the delay I have been very busy at work.

My computer has continued to BSOD roughly once or twice a day.

I have attached a new sysnative file dump. I would appreciate any help that you can offer.
 

Attachments

According to your System log you've had 24 BSODs since 17th Dec 2024, 13 of those dumps have been this year, yet the upload contains only 5 dumps; 4 from 7th Jan and one from 6th Jan. Not only that, but on 6th Jan you had two 0xC4 bugcheck BSODs, these are Driver Verifier caused BSODs and those two are the dumps I really needed to see. Where are they?

Rich (BB code): 
Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          06/01/2025 06:38:05
Event ID:      1001
Task Category: None
Level:         Error
Keywords:    
User:          SYSTEM
Computer:      Kvothes_Desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c4 (0x0000000000000062, 0xffffcf854c994da0, 0xffffcf854c9f9bb0, 0x0000000000000001). A dump was saved in: C:\WINDOWS\Minidump\010525-17234-01.dmp. Report Id: 67f66a28-ecea-43c5-b5dd-39778b880265.
Here a driver is unloading without freeing its pool allocations (parameter 1 is 0x52).

Code: 
Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          06/01/2025 06:56:16
Event ID:      1001
Task Category: None
Level:         Error
Keywords:    
User:          SYSTEM
Computer:      Kvothes_Desktop
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c4 (0x00000000000000e4, 0xfffff804684938d3, 0xffff9a003333ee78, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\010525-17750-01.dmp. Report Id: 25a416cd-0224-4d92-b4f6-aa626ab665a4.
Here a driver is making malformed kernel function calls (parameter 1 is E4).

Note that the timestamps in these reports are normalised to the time zone of the viewer and I'm 2 hours ahead of UTC (UTC+2).

It's possible that these two BSODs were caused by the same driver or by two different drivers, but without the dumps it's not possible to know. Whenever you enable Driver Verifier you MUST keep all the dumps! If you're running any kind of a garbage cleaner then please stop, at least until we've solved your problem.

For now, keep Driver Verifier enabled, keep using every app, feature, and device you have (to ensure that all third party drivers are loaded at some point) and KEEP ALL THE DUMPS.
 
Thanks for the info. Here are the two latest dumps. One happened without driver verifier, the other while it was enabled. I will keep driver verifier enabled until you are able to find more info.
 

Attachments

Neither of those BSODs were generated by Driver Verifier. Make sure that you follow the instructions at Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista to ensure that Driver Verifier is enabled correctly. The bugchecks we're looking for are these...
  • 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
  • 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
  • 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
  • 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
  • 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
  • 0xE6: DRIVER_VERIFIER_DMA_VIOLATION
If you can get a dump for a couple (or more) of those bugchecks we should be able to identify the rogue driver(s). BSODs with other bugchecks are unlikely to help much.
 
Is it possible for windows to blue screen with a different error while driver verifier is enabled?

I have had a couple KMODE_EXCEPTION_NOT_HANDLED BSODs while driver verifier has been enabled.
 
Last edited:
Yes it's common. Leave Driver Verifier enabled and make no changes to your system in that time. Do however, use every app you have, access every device you have, and use as many features of your apps as possible. The aim is to have every third-party driver that you have installed loaded at some point so that Driver Verifier can check it.

Because I can see that you have had Driver Verifier triggered BSODs (see my post #11) already I am confident that we will see them again. Only this time we'll keep the dumps.
 
Here is the only BSOD that has been caused by driver verifier. The majority have been the KMODE_EXCEPTION, or IRQL_LESS_THAN_EQUAL
 

Attachments

Many thanks. The problem driver in that dump is vgk.sys...
Code: 
FAILURE_BUCKET_ID:  0xc4_62_LEAKED_POOL_IMAGE_vgk.sys
It failed to properly free its memory pool allocations before unloading.

The vgk.sys driver is part of the Riot Vanguard anti-cheat system for the Valorant, and now, League Of Legends games and it's a very well-known and common cause of BSODs. All anti-cheat tools cause BSODs now and then, we see them often.

There is nothing you can do about this, other than not play Valorant/League Of Legends. You should contact Valorant/League Of Legends support and make this Driver Verifier dump available to them. Only Riot can fix this.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top