Showing results for 
Search instead for 
Did you mean: 

ROG-STRIX-RTX3080-O10G-GAMING: nvlddmkm.sys BSOD

Level 7

GPU: ROG-STRIX-RTX3080-O10G-GAMING. This is in an 10900X / Strix X299-E II system.

I have been having issues with a random Windows 11 BSOD naming "nvlddmkm.sys" as the culprit.
- occurs when using windows 11, no pattern
- occurs in gaming, only tested with WZ so far.

I have not been able to spot a pattern yet. Fresh install of W11, latest nVidia drivers etc. No software overclock application installed for GPU.

The problem appears to go away when I run the card in "normal" mode (i.e. the physical overclock switch on the card is "Off").

Is anyone else out there getting BSODs with this card?

Does anyone have any thoughts on why the physical OC would induce a BSOD?

PipJones wrote:
That's great, thanks for doing this. I will DM you my e-mail address.

I think all the overclocking tools work the same way. My preference is NVI (nVidia Inspector) because it does not need installing.

In AIDA do:

File -> Preferences

And then select the "Logging" option, should be 5th one from the bottom.

This will activate the panel on the right hand side. You select a location to save the logs to and what you want logging. Please select CSV, not HTML.

Try and log all the "interesting" stuff, like clock speeds, utilization etc. Plus everything you can related to GPU.

Launch AIDA just before you launch FH5, close it when done. This will keep the log files tidy.

AIDA will generate a summary and a detail log, It would be cool if you can send both.

If you really fancy going for it, try and grab some "clean" logs (no crashes) and if / when BSODs.

Ok. I will send you some logs tomorrow when i have the time

Level 7
no worries, no hurry

Level 7
Firstly, many thanks to all those involved - and sorry for the delay in posting an update.

I think I finally have stability. I've had about 5+ hours in both FH and WZ without crashing.

The short answer is the v511.09 SD (studio driver) appear to yield stability on my system.

The longer ansewr and methodology.


The OC scan in ASUS GPU Tweak was used to retrieve the driver "profile" for the card when running the ASUS v472.12 driver downloaded from the ASUS website. This profile shows an expected voltage and frequency chart. The assumption is that these are the "last known good" values for voltage and frequency.

AIDA64 was used to grab logs while running the FH5 benchmark tool. These logs were analysed to find voltages and frequencies hit during the benchmark run. These benchmark runs were repeated many times using the drivers mentioned below.

This is what has been learnt:

1. Using data from my 3080, the more recent v497.xx nVidia GR (game ready) drivers are pushing too high frequency on too low voltage in comparison to the v472.12 drivers supplied by ASUS.

2. Using data from Nikos 3070, we can see the same pattern. I need access to the "profile" for the 3070 using v472.12 to confirm what the expected values should be.

3. Just like a CPU overclock, this "too high frequency on too little voltage" is introducing the instability that yields a CTD (crash to desktop) and/or BSOD (Windows Blue Screen Of Death). This "too high frequency" is the "maximum boost" that is being attempted by settings within the driver.

4. When using these more recent GR drivers it appears to be possible to regain stability by forcing the cards to NOT boost too high. A decrease of 30 Mhz and increase of "Power and Temperature target" to 110% brought my voltages and frequencies in line with "last known good" values.

5. The new v511.09 SD (studio drivers) from nVidia use a voltage range that is simillar to the v472.12 drivers from ASUS and this driver appears to be stable.

More testing will be required when the next GR driver is released. For now, I am sticking with the SD driver with no overclock or underclock in place and I will feedback later.

Other things I would like to test:

@Ribellu: ROG-STRIX-RTX3080TI-O12G-GAMING and the 120 / 144 Hz issue.

"I have this error when I play in 4K by setting my screen to native 144Hz."

Can you try the SD driver? If you still get the BSOD / CTD crashes, can you generate the logs for 120 and 144 Hz for investigation?