Question [Hang/Freeze/Crash] - Event ID 14 nvlddmkm, AMD+NVIDIA

Page 4 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Apr 17, 2020
3
4
15
This thread is for if your issue occurs sporadically and randomly (from once every week(s) to once every month(s)). If you are having the same event ID repeatedly and consistently you do not have the same issue.

PLEASE DO NOT COMMENT IF YOU DO NOT HAVE QUESTIONS, A FIX OR RELEVANT ADDITIONAL INFO as this will otherwise flood the thread is it did with the previous one. Use the poll instead to add your +1.


Introduction:
This has been a long going thread from Reddit which I was the owner of.
The thread is almost 6 months old, meaning it will most likely archive and I am getting notifications from other people having the issue almost every other day. I decided to compile (300+ comments) the info from that thread and post it here.

Issue Description:
As stated above, this issue occurs sporadically: you can be gaming, editing, or watching a Youtube video, it doesn’t seem to have correlation. On average it will happen once every 3 weeks for me.
When the error occurs, the computer will begin to stutter, your inputs will be extremely jerky/delayed and sometimes the screen will go black with only the cursor displaying. This makes it impossible to use the computer while it occurs.
The issue will sometimes resolve itself (can take from 1 to 15 minutes) and sometimes last too long for it to be worth waiting, meaning I will manually crash my computer.

There seems to be a correlation between having a NVIDIA GPU and an AMD Ryzen CPU, however, (very) few have described the issue happening on a different configuration.

Last time I had the issue: [2020-03-07]
(YYYY,MM,DD).

Event Viewer Error:
Event ID 14 - nvlddmkm
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3
0cec(3098) 00000000 00000000

The message resource is present but the message was not found in the message table

Contacts:
Others and I have attempted contacting both AMD & NVIDIA here is each of their answers (broadly):
AMD: Ensure that you have updated the BIOS and chipset drivers for your motherboard and are using stock settings. They think it's mostly an issue related to the graphic's card. It should be on NVIDIA's side to fix this. It could also be related to this link: https://support.microsoft.com/en-us/help/2665946/display-driver-stopped-responding-and-has-recovered-error-in-windows-7 (which is related to windows 10 as well).
NVIDIA (info from Reddit user u/faildude7): “[...] I contacted with NVIDIA and they told me that is an incompatibility issue that they're aware of it and it's more common with RTX series but it's gonna be hard to fix since it's on AMD's part and should be resolved with a BIOS fix from their part, they told me that it's because the use of virtual threads on multi-threading in Ryzen that doesn't link well with NVIDIA processes.” + “he told me that and it's pretty bad since this error seems like it's 6 years old at least so I don't see them fixing it any time soon, this just was more popular with the RTX series since he told me that it's more common with these graphics but if you search info you can see people complaining for years.”

Fixes
This is a list of attempted and not attempted fixes mentioned by some users from the thread mentioned above. The problem with this issue is also not knowing when the issue will happen. Someone can declare a fix but we don't truly know about whether it works or not after a few months of waiting (as the issue occurs so sporadically). Running generic stress tests will also not make the issue occur.

Attempted Fixes:
  1. RMA (Replace) with the same GPU model. This does not fix the issue. (Generic fix)
  2. Update drivers. This does not fix the issue. (Generic fix)
  3. Use stock settings. This does not fix the issue. (from AMD)
  4. Disabling XMP on the BIOS. This does not fix the issue. (from u/3feetHair)
  5. Enabling XMP on the BIOS. This does not fix the issue. (Generic fix)
  6. Setting your Power Plan to AMD’s “High Performance” (from u/Injuis)
  7. Setting Memory Frequency to the correct frequency through BIOS (from u/NovalAcanthocephala6)
  8. Change your GPU power mode to “Maximum Performance”. NVIDIA Control Panel -> Manage 3D Settings -> Global Settings -> Power Management mode. Many users have mentioned this working (from u/eatwritelaugh) [fix personally attempted on 2020/04/16]
  9. DDUd and reinstall drivers. This does not fix the issue. (from u/Aravind92)
Potential Fixes:
  1. Update BIOS for Chipset & Motherboard. (This has been attempted by some and didn’t fix the issue, however it could still be a potential fix in the future.)
  2. Reset Windows Power Options (from u/Aravind92)
  3. Disable HW Acceleration in Firefox (from u/Aravind92)
  4. RMA (replacing) with a different PSU. This has apparently fixed the issue for one user, however the user had an intel CPU. (from u/Speedfreakz)
  5. Replacing every component in your computer seems to work (which admittedly is not a fix).
  6. Set your RAM to “Power Down Enabled/mode” to disable and “Gear Down Mode” enabled. (from u/Gigakv)
Other Info compiled from user comments on the previous thread:
  • u/sprousaTM has mentioned this only occurring when the PC is idle.
  • u/ponybeu5 has mentioned changing from a 1080 Strix to a 2080 Super EVGA and then starting getting the issue (with AMD 3900X).
  • u/RafaMarioFan has said the following: Started with this setup: GT1030+ used A320+ ryzen3600 + 500W psu (that doesn't have 80plus), changed to a Galax 1660 and started having the error. Replaced PSU for a Corssair CX 550 (80p bronze) which didn’t fix the error. Went back to the GT1030. Bought a RTX 2060S which caused the issue again. Then changed from A320 to a B450 which didn’t fix the issue.
  • A few users have mentioned the issue only occurring a few months after having their PC built. (I personally don’t remember)
  • u/Civil_Specter has mentioned a fix, however it seems like their issue was occurring consistently when gaming, which is different from what a majority of people are getting and most likely a different issue:
    • Use AMD Ryzen Master to disable SMT (Simultaneous Multi threading)
    • Downloaded a program called Project Lasso to improve gaming performance.
    • Used EVGA Precision X1 software to make a custom GPU profile with “Boost Lock” enabled. Which keeps your GPU from idle.
  • u/Gigakv has provided the following info: Can confirm it's still an issue with Ryzen 3000 + Turing
    • Ryzen 2600 + RTX 2060 - no problem
    • Ryzen 3600X + GTX 1070 TI - no problem
    • Ryzen 3600X + RTX 2060 that worked fine with the Ryzen 2600 - GPU crashing when using hardware acceleration \ idle. No issues during gaming or stress testing.
  • A few users mention that it probably has a link with hardware acceleration.
  • A few users mention that it probably has a link with the GPU switching from idle to performance mode.
  • u/MBDdk mentioned that the issue might’ve been fixed in the AMD driver update 20-2-2: “Performing a task switch with some Radeon Software features enabled or some third-party applications with hardware acceleration running in the background may cause a system hang or black screen.”
My Full Computer Specs:
GPU: NVIDIA GeForce RTX 2080 Ti
CPU: AMD Ryzen 9 3900X
CPU Cooler: NZXT Kraken x62
Motherboard: GIGABYTE X570 Aorus Master
RAM: G.Skill Ripjaws V Series 64GB DDR4-3200 [16GB x 4]
PSU: Corsair HX Platinum 750 W80
Case: NZXT H700i ATX Mid Tower
SSD [Windows 10]: Samsung 970 Pro 1TB
HDD: Seagate BarraCuda Pro 4TB 3.5” 7200 RPM

List of a portion of reported setups with the issue from the reddit thread:
  • u/faildude7: Ryzen 9 3950X + RTX 2080Ti + G.Skill Trident Z Neo 32GB (2x16GB) 3600MHz + Gigabyte X570 AORUS Pro
  • u/rimokonman: Ryzen 3700X + NVIDIA 2070S
  • u/eatwritelaugh: Ryzen 5 3600 + RTX 2070 Super + Adata 3200mhz 8x2 + MSI B450 Carbon
  • u/sprousaTM: Ryzen 3800X + RTX 2080 + 16GB Trident RAM + 1200watt corsair power supply (+custom watercooling)
  • u/Aravind92: Ryzen 3600x + MSI Tomohawk B450 Max + gtx 1660 ti + Corsair Vengeance LPX 8 x 2 3000 mhz + cm mwe v2 550w + Acer VG240YP.
  • u/QueBugCheckEx: Ryzen 9 3950x + RTX 2080ti
  • u/PentaChicken: Ryzen 5 3600X and RTX 2070 Super
  • u/Skastrike09: Ryzen 3600 + NVidia 2060
  • u/iksargodzilla: ryzen 3700x + rtx 2060 super + tuf gaming x570-plus (wifi) motherboard + 2x8gb ram
  • u/OOO639: 3700x and a 2080 super
  • u/clockwork000: 3900X + 2070S
  • u/ Dyeneks: RTX 2070 Super + Ryzen 7 3700X
  • u/TheChozoKnight: RTX 2080 + Ryzen 7 3700X + Asus X570F Mobo
  • u/impmallet: 2080ti + 3700x + Gigabyte x570 Aurus Elite
  • u/fluidzreddit: Msi trio 2080ti @ stock + 3700x + Gigabyte x570 master (f11 bios). Ram - Crucial ballistix sport 3200 cas 16 @ xmp
  • u/kaimenlau: Ryzen 3950x + rtx 2080 ti
  • u/NovelAcanthocephala6: 3950x + 2080 super
  • u/MBDdk: Ryzen 5 3600 + NVIDIA RTX 1660S
  • u/Speedfreakz: Asus TUF Z270 MARK 1 + Intel® Core™ i7-7700K CPU @ 4.20GHz + NVIDIA GeForce RTX 2080 SUPER (TU104-450) @ 300 MHz + Samsung SSD 970 EVO Plus 1TBCougar STX 750 power supply.+ 2x 16gb HyperX Predator Rgb memory
  • u/yanboz: 3950X + 2080Ti
  • u/Tounushi: Asus GeForce RTX 2070 Super Dual Evo OC + Asus Prime x370-Pro mobo (BIOS v.4801) + 750W power source + AMD R7 3700X + 16GB DDR4 2666MHz (running 2400) + M.2 SSD OS drive + SSD and HDD gaming and storage drives, respectively
  • u/Skastrike09: RTX 2060, Ryzen 5 3600, and X570 AORUS ELITE
  • u/Oren1: Ryzen 5 3600 + Rtx 2060 super
  • u/rickgolds: Ryzen 5 3600 + RTX 2080 + RAM Trident Z with Samsung B-Die
  • u/Aravind92: Ryzen 3600x, MSI Tomohawk B450 Max, gtx 1660 ti, Corsair Vengence LPX 8 x 2 3000 mhz, cm mwe v2 550w, Acer VG240YP.
  • u/MrSheep_: 1660ti + Ryzen 5 3600.
  • u/KM1k92: R9 3900x + RTX 2060 SUPER
  • u/Sanastro: i9 9900k + Zotac 2080ti
  • u/Flush535: 3700X + 2070S
  • u/3feetHair: Ryzen 2700 + GTX 1660
  • u/Sp0KI: 3700x + x470 + 2070
  • u/ThatOneCrazyFriend: 3900X + 2070 Super
  • u/calscks: 3900X + RTX 2080
  • u/hop-limit: 3800x + rtx 2070s
  • And many others…
Reddit thread: View: https://www.reddit.com/r/techsupport/comments/dnm7pt/event_id_14_nvlddmkm_computer_stutters_2080_ti/
 

AlHouine

Commendable
May 26, 2020
8
0
1,510
I went through the links, while I am not an expert to understand eveyrthing said, I get it a little bit, Even I was surprised a little bit by how few the reports are of this issue compared to the ryzen 3rd gen processor sales. I shrugged it off and still to an extent beleive that lots of people are not reporting it as it only rarely happens, I assume they just restart the pc and get on with it.

If the cpu indeed is at fault, I wonder how anyone is ever going to convince AMD to RMA the cpus(seeing as you can't even tell if its fixed even with a new cpu as it happesn very rarely(I personally had a gap of 3 months between two instances and in the instance after the 3 months gap I was able to fix by closing MSI afterburner(however the behaviour(mouse movement stuteering with anything taking forever to open) was same a before) if they had been working fine on previous gen cards. From reading the comments on the links you provdided, it looks like all communication busses have errors(mostly not relevant enough to cause an issue) , in that case, shouldn't a BIOS fix be possible across the range of hardwares if that is indeed the defect you are refering to. And also, how are we ever going to know if a hardware is faulty or not if a BIOS update can fix it at seemingly no cost to the end user in terms of performance and usability.

I've linked a video I shot of the issue when it happened, check and tell me if this is the issue you are refering to as well. The behaviour seen in the video is exactly the issue people with 3rd gen ryzen and turing are facing, after restart you can find the error in event viewer, only the nvlddmkm, not any other error like the intel user mentioned in your thread, maybe we are talking about entirely different issues. Like, I said closing MSI afterburner solved it once(although I did not try this the preivous two times this issue happened) and opening it again in the same session(without restarting) triggered an nvidia driver restart(however all was fine in the interim period in the same session when msi afterburner was closed).

In the 7 months I've been using the pc it has only happened thrice and I pretty much do the same things(browsing, youtube and games) on my pc.

View: https://www.youtube.com/watch?v=zszRpGy-dVI


that's exactly what happens when trouble comes.
And I get the error id 14 nvlddmkm in the event handler after rebooting the computer.
 

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
i just had another driver crash, while scrolling through reddit and having a youtube video open in the background. But this time it was different. i got no stutter>freeze, but a blackscreen for like 2 seconds and then everything went back to normal. maybe 455.38 fixed something? i mean its still a crash, but its better than before.
Hi, this same thing happened to me sometime back, 2 second black screen without any driver crash or errors,but this happened only after I updated to the chipset driver that was released before the recent one, I was also on Agesa 1.0.0.4b at that time, everything sorted itself out after the 1.0.0.5 update, atleast I think it did.

Also try updating to the June chipset drivers.
 

tomsliwowski

Prominent
May 13, 2020
12
0
510
Hi, this same thing happened to me sometime back, 2 second black screen without any driver crash or errors,but this happened only after I updated to the chipset driver that was released before the recent one, I was also on Agesa 1.0.0.4b at that time, everything sorted itself out after the 1.0.0.5 update, atleast I think it did.

Also try updating to the June chipset drivers.
What June drivers? The latest Ryzen Master drivers I see are from May.
 

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
Guys, A quick update, I was checking event viewer just now and found I had another event 14 on the 3rd June albiet not accompanied by the usual behaviour.
I was using the pc at that time, nothing wierd happened. I was surprised to see the error but this time the code was a little different, see below.

\Device\00000077
CMDre 00000049 00000200 ffffffff 00000001 ffffffff

So, I am not sure whats going on.

Edit : just spoke with another guy on reddit who has the same issue and he has done some extensive testing as well, he actually brought to my notice that AGESA 1.0.0.5 fixed the issue and he also seems to have had the error after the BIOS update, just like me without any system instabilities.

And he has now now updated saying AGESA 1.0.0.6 is actually stopping the error messages as well, looks like AMD is aware and fixing it.

I also read somewhere that many board partners are skipping 1.0.0.5 and going to 1.0.0.6 directly. Check all your boards' support pages, you guys could perhaps go to the most stable one straight away.
 
Last edited:

Diceman_2037

Distinguished
Dec 19, 2011
56
3
18,535
If the cpu indeed is at fault, I wonder how anyone is ever going to convince AMD to RMA the cpus(seeing as you can't even tell if its fixed even with a new cpu as it happesn very rarely

There is no convincing required, you just open an RMA and AMD will grant you the exchange, its up to AMD to determine the condition of the processor in their diagnostic labs, new chip is sent as soon as they receive shipping info from you as long as the replacement is in stock

Intel is the same, if a cpu is not in stock both will generally refund you the original cost of the chip.

Unlike mainboard/gpu vendors that run their tests before shipping the replacement (or the defective product back if they half arsed them and couldn't reproduce the issue) its a fair bit harder to identify every single cause of an issue in a cpu, but more readily reproduce the symptoms of those issues, hence why Errata lists are updated over the life of a product and revisions are made.
 
May 18, 2020
19
0
10
Hi all, so I've just built a new PC with a evag 2070 super and ryzen 3600 (x570 aorus i pro wifi mobo) (all chipset and mobo and gpu drivers up to date)
Had a couple of crashes but only just clocked the nvlddmkm in the event viewer.

I've set my power management to maximum in nvidia.

I'm fortunate enough that it only occurs during gaming rarely. It happened during terraria last night as I was fighting skeleton. It started to stutter and get increasingly worse until it fully froze.

Same with Detroit becoming human, bit of stuttering (I chalked it up to being a graphically intensive map) then the stutter got horrendous and lockup.

Will update if I can be of assistance.
 

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
Hi all, so I've just built a new PC with a evag 2070 super and ryzen 3600 (x570 aorus i pro wifi mobo) (all chipset and mobo and gpu drivers up to date)
Had a couple of crashes but only just clocked the nvlddmkm in the event viewer.

I've set my power management to maximum in nvidia.

I'm fortunate enough that it only occurs during gaming rarely. It happened during terraria last night as I was fighting skeleton. It started to stutter and get increasingly worse until it fully froze.

Same with Detroit becoming human, bit of stuttering (I chalked it up to being a graphically intensive map) then the stutter got horrendous and lockup.

Will update if I can be of assistance.

Just to confirm, there was a BIOS released on 16th June 2020, you've updated to that as well?
 
May 18, 2020
19
0
10
Just to confirm, there was a BIOS released on 16th June 2020, you've updated to that as well?

Oh! I had the one before this. It's jumped from f12f to f20a.

f20a update Description - Update AMD AGESA ComboV2 1.0.0.2 for 3rd Gen AMD Ryzen XT series processors and New Gen AMD Ryzen with Radeon Graphics processors support

Thanks, I'll install this now.
 
Jun 18, 2020
1
0
10
Hi everyone,

I had the same issue but it got worst over time for me, with a freeze happening consistently after one/two hour of gaming (which is why I'm not sure if it's the same issue).
Thanksfully, this worked for me so far : swapping my GPU from the PCIe 4.0/3.0 slot to the PCIe 3.0 slot.
Just contacted MSI to know if there would be some issues with PCIe 4.0 compatible slots (may just be my motherboard though).
I thought that might help some people who stumble upon this thread.

-------
Build:
Motherboard : MSI MPG X570 GAMING EDGE WIFI (MS-7C37)
CPU : AMD Ryzen 5 3600
GPU : MSI RTX 2070 SUPER Ventus OC
RAM : Crucial Ballistix Sport LT BLS8G4D30AESCK 3000 MHz 2x8Go
OS : Microsoft Windows 10 1909
 

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
Hi everyone,

I had the same issue but it got worst over time for me, with a freeze happening consistently after one/two hour of gaming (which is why I'm not sure if it's the same issue).
Thanksfully, this worked for me so far : swapping my GPU from the PCIe 4.0/3.0 slot to the PCIe 3.0 slot.
Just contacted MSI to know if there would be some issues with PCIe 4.0 compatible slots (may just be my motherboard though).
I thought that might help some people who stumble upon this thread.

-------
Build:
Motherboard : MSI MPG X570 GAMING EDGE WIFI (MS-7C37)
CPU : AMD Ryzen 5 3600
GPU : MSI RTX 2070 SUPER Ventus OC
RAM : Crucial Ballistix Sport LT BLS8G4D30AESCK 3000 MHz 2x8Go
OS : Microsoft Windows 10 1909

Now that kinda confirms the other guy's finding from reddit if its the same issue.

he claimed the issue weas caused by GPU switching between idle/power states on PCIE 4 compatible boards, on 400 series boards as well because initally 400 series supported PCIE 4 biut was later blocked by AMD as it wasn't stable enough, this blocking seems to have been half arsed causing the issues. Have you installed the recent BIOS from MSI, check and see if that helps.
 

Diceman_2037

Distinguished
Dec 19, 2011
56
3
18,535
Now that kinda confirms the other guy's finding from reddit if its the same issue.

he claimed the issue weas caused by GPU switching between idle/power states on PCIE 4 compatible boards, on 400 series boards as well because initally 400 series supported PCIE 4 biut was later blocked by AMD as it wasn't stable enough, this blocking seems to have been half arsed causing the issues. Have you installed the recent BIOS from MSI, check and see if that helps.

the same pcie controller is used, there is no such thing as a pcie 4.0 vs 3.0 slot, the controller is 4.0 and all lanes provided from the IO die and x570 are Gen 4,

Even on where used on 400 and 300 series motherboards, the slot is agnostic to pcie version but these are firmware locked to Gen 3 due to noise and signal levels and will use Gen 3 no matter what you put in it.

Gen 3 graphics cards establish a Gen 3 link regardless of the controller supporting Gen 4, any issues being experienced are faults with the pcie controller.

Note: A hanging system might even be hanging only when a m.2 or 2 gpu's are installed because of this case
 
Last edited:

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
the same pcie controller is used, there is no such thing as a pcie 4.0 vs 3.0 slot, the controller is 4.0 and all lanes provided from the IO die and x570 are Gen 4,

Even on where used on 400 and 300 series motherboards, the slot is agnostic to pcie version but these are firmware locked to Gen 3 due to noise and signal levels and will use Gen 3 no matter what you put in it.

Gen 3 graphics cards establish a Gen 3 link regardless of the controller supporting Gen 4, any issues being experienced are faults with the pcie controller.

Note: A hanging system might even be hanging only when a m.2 or 2 gpu's are installed because of this case

ok, Did you watch the video I posted, like I said the system isn't hanging, I could still use the pc everytime, just everything was moving slow, once closing MSI afterburner even solved the issue. Two, things, if its a hardware defect, why am I able to constantly stress bnoth the gpu and cpu and not have an issue and why did it get resolved by closing MSI AB.

Also, I did not experience any issues at all the last time nvlddmkm crashed on June 3rd, just found the error in event viewer. That leads me to beleive it is a firmware issuebeing addressed through AGESA. 1.0.0.5 solves the issue but the error still appears, 1.0.0.6 completely stoops the errors as well apparently.

Wouldn't a hardware defect with the controller be more apparent, like often causing instabilities rather than once is few weeks to months.
 
May 28, 2020
5
0
10
Well I'm back because it has happened again. It was about to be a month since the error in 2 days and it happens again. I had installed the 436.48 driver on the 27th of May when it occurred and assumed it was fixed.

Jaw1caj.png
 
Last edited:

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
Well I'm back because it has happened again. It was about to be a month since the error in 2 days and it happens again. I had installed the 436.48 driver on the 27th of May when it occurred and assumed it was fixed.

Jaw1caj.png

Just checked and found asrock released AGESA 1.0.0.6 for B450 steel legend, perhaps you can contact the support and see whats up with the m version.

Like I mentioned earlier a lot of board partners skipped 1.0.0.5 and decided to go for 1.0.0.6 directly. From what I am reading, looks like it should drop any day now for you board, shouldn't hurt to pester them tho.
 

Aravind92

Distinguished
Apr 1, 2014
699
9
19,065
New nvidia gpu driver update
451.48

says

- Supports hardware-accelerated GPU Scheduling.

May fix the issue?

I am afraid hardware accelerated gpu scheduling is an entirely different matter, it has to do with the OS letting the GPU itself handle the video memory unlike before when it was done by the OS.

Did you update the BIOS, hopefully that will resolve the issue.
 
May 28, 2020
5
0
10
Just checked and found asrock released AGESA 1.0.0.6 for B450 steel legend, perhaps you can contact the support and see whats up with the m version.

Like I mentioned earlier a lot of board partners skipped 1.0.0.5 and decided to go for 1.0.0.6 directly. From what I am reading, looks like it should drop any day now for you board, shouldn't hurt to pester them tho.

Yeah I actually sent them a message a few hours ago on this exact reason. Hopefully they get back to me soon. If I get an update from them I'll let you all know here in case someone here has the same board.
 
Jun 26, 2020
2
0
10
Hey,

I've now been randomly getting this issue, it has been working fine a ages now its been doing it consistently

Intel 9900k
2x2080ti EVGA XC Ultra
Aorus z390 ultra
1600w PSU EVGA

i;ve updated bios, re-seated ram, did a memtest no errors. DDU but the crash keeps coming back
Tried all the things mentioned here like set max power mode etc too. Out of ideas at this point :(
 

Calamity James

Prominent
Jun 30, 2020
1
0
510
Hey all, found this thread after coping with the crashes for the last 2 months (built the system in April, been having the issues since about a week after install).

Just updated the chipset drivers, changed power management for the GPU to "prefer max performance" and ensured the PCIE link state management power saving option was off.

Will update if it happens again.

Specs:
  • ASRock B450 Pro4 (Latest BIOS - 4.1 (May 2020), AGESA 1.0.0.4 "Patch B")
  • AMD Ryzen 5 3600X
  • Gigabyte NVIDIA RTX 2060 6GB (currently on 445.87 but about to install 451.48)
  • Corsair Vengeance LPX 32 GB (16x2) 3200 MHz
  • Windows 10 Enterprise 1909
Edited to add Event Viewer log to show number of occurrences:
FU1fq0x.png
 

AlHouine

Commendable
May 26, 2020
8
0
1,510
HI everyone, do you know if with the 451.48 driver you still have problems with nvlbbmkm errors?

I had more problems with the 436.48 driver except on modded minecraft (but I had an open GL error with it) and since uninstalling minecraft no more crashes with the 436.48 driver.

With recent games, the 436.48 driver shows graphic weaknesses and I really need to update nvidia.

So people with driver 451.48, do you still encounter nvlldmkm errors?
 
May 18, 2020
19
0
10
HI everyone, do you know if with the 451.48 driver you still have problems with nvlbbmkm errors?

I had more problems with the 436.48 driver except on modded minecraft (but I had an open GL error with it) and since uninstalling minecraft no more crashes with the 436.48 driver.

With recent games, the 436.48 driver shows graphic weaknesses and I really need to update nvidia.

So people with driver 451.48, do you still encounter nvlldmkm errors?


Yes but....I had one freeze and the nvlldmkm was no longer in the event viewer. But I then turned PCIE link state management power saving off and no crashes since.
 
Status
Not open for further replies.