Quad5Ny

bcavnaugh

Quad5Ny
Nooooo thats not a fix!!!  You're disabling pure UEFI mode, secure boot, full display resolution and it's not just a error, the card resets itself (if you have a FE card listen to its fans)... no just no.  The EFI GOP Display Driver (module thing,.. whatever) built into the ROM is at fault or the Display Driver is at fault.
You (We all) should be yelling at NVIDIA to fix this.

It is mine for now. 

I was really tired when I wrote that, it shouldn't have come out of my mouth so fast.  Sorry.
 
But it is true.  The UEFI video driver that loads during boot shouldn't cause a error (crash?) when passing control to the Windows driver.  I personally don't want to disable platform (chipset, firmware) features and be stuck in 1024x768 during boot just because NVIDIA hasn't fixed it.
 
Now on the flip side Windows takes control of things once loaded so you're only really missing Secure Boot and some minor other things.

This error is not only at boot time and the Driver Install but it also errors as soon as you install the NVIDIA Driver.
So IMO it is a Driver Issue and we just need to wait for NVIDIA to correct the Driver for the RTX Cards.
Then as well it could be a Graphics Card Bios that needs to be corrected. But only time will tell.
From what I understand this has nothing to do with "Secure Boot" I never changed any settings for the UEFI Boot as well.
I have CSM Disabled on all my rigs with Windows 10 and Enabled with Windows 7 Pre GTX 9xx Cards.
 
The Compatibility Support Module (CSM) is a component of the UEFI firmware that provides legacy BIOS compatibility by emulating a BIOS environment, allowing legacy operating systems and some option ROMs that do not support UEFI to still be used

CSM also provides required legacy System Management Mode (SMM) functionality, called CompatibilitySmm, as an addition to features provided by the UEFI SMM. This is optional, and highly chipset and platform specific. An example of such a legacy SMM functionality is providing USB legacy support for keyboard and mouse, by emulating their classic PS/2 counterparts.

Quad5Ny
I'm unsure of this (it's been such a long time, and I can't reboot to check) but with CSM enabled you can load unsigned code (Option ROM's).  Secure Boot should automatically disable itself.  I mean CSM is a BIOS emulation/compatibility layer.  By turning it on, it only makes sense you can load unsigned code. - Again, have not verified.
 
Now some fun stuff, SMM can also be used to run code that the operating system is unaware of.  Some people I uhh... well, just some people used it to emulate a hardware chip on Intel PC's running Aptio 4/5 firmware.  Of course this steals CPU cycles and there is no fault recovery if your code is bad.
 
UEFI Firmware is lot of fun to play with if you have a recovery method (and preferably not on your main PC).

Maybe a good Discussion Topic for another Thread.

Sajin

bcavnaugh
Getting this Error CMDre 00000001 00000200 00000000 00000005 00000006 on my new EVGA GeForce RTX 2080 Ti XC ULTRA GAMING, 11G-P4-2383-KR, 11GB GDDR6, Dual HDB Fans & RGB LED on my new X299 Dark and under Driver 416.81

No issues here.

Not really applies on your computer because you are not running Window 10 1809.
Can you even open Event Viewer with everything you disable in Windows 10?
And is CSM Disabled or Enabled in your Bios?

Sajin

bcavnaugh

Sajin

bcavnaugh
Getting this Error CMDre 00000001 00000200 00000000 00000005 00000006 on my new EVGA GeForce RTX 2080 Ti XC ULTRA GAMING, 11G-P4-2383-KR, 11GB GDDR6, Dual HDB Fans & RGB LED on my new X299 Dark and under Driver 416.81

No issues here.

Can you even open Event Viewer with everything you disable in Windows 10?
And is CSM Disabled or Enabled in the Bios?

Yes.
Disabled.

Good for you.
But you are also not running Windows 10 1809 
So in  your Event Logs you do not show this error "CMDre 00000001 00000200 00000000 00000005 00000006"

Sajin

bcavnaugh

Sajin

bcavnaugh

Sajin

bcavnaugh
Getting this Error CMDre 00000001 00000200 00000000 00000005 00000006 on my new EVGA GeForce RTX 2080 Ti XC ULTRA GAMING, 11G-P4-2383-KR, 11GB GDDR6, Dual HDB Fans & RGB LED on my new X299 Dark and under Driver 416.81

No issues here.

Can you even open Event Viewer with everything you disable in Windows 10?
And is CSM Disabled or Enabled in the Bios?

Yes.
Disabled.

Good for you.
So in  your Event Logs you do not show this error "CMDre 00000001 00000200 00000000 00000005 00000006"

Correct.

Thank you, But you are also not running 1809.

ManiXyZ
good news

"ManuelGuzmanNV"
The event ID I mentioned in the open bugs is specific to RTX 20 series cards as far as I can tell.  It is fixed and will be in our next driver.  

https://forums.geforce.co.../post/5914771/#5914771

Not seeing it.

ManiXyZ
The "next" driver isn't out yet, probably coming next 2-4 weeks.

OK Thanks, but that is Forever in terms of new drivers.

yes but not for all users, me and some others still have the Error
 
ASUS released also new BIOS for several mainboards( v. 1603 ) but isn't out yet for ASUS Prime-A.
It fixes device compatible issues but not sure yet is it RTX related

Same here with Auros Master w/ 9900K and 2080Ti.
 
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
CMDre 00000001 00000200 00000000 00000005 00000005
 
surprised the card hasn't gone dud yet, truly a christmas miracle you guys.

bcavnaugh

crouchgod
Same here with Auros Master w/ 9900K and 2080Ti.
 
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
CMDre 00000001 00000200 00000000 00000005 00000005
 
surprised the card hasn't gone dud yet, truly a christmas miracle you guys.

This was fix with a Driver, Post Above at the end of last November.

Doesn't seem to be the case.

Guy has an issue with his setup and gets a blue ribbon/money... Damn, you guys must really like this guy. 

chrisdglong
Guy has an issue with his setup and gets a blue ribbon/money... Damn, you guys must really like this guy. 

I still see you have issues, if you read the First Post it was Caused by NVIDIA's Driver and has been correct by the same.
https://forums.geforce.com/default/topic/1079837/geforce-drivers/official-416-94-game-ready-whql-display-driver-feedback-thread-released-11-13-18-/post/5914771/#5914771

Driver 419.xx should fixed this Error "2488424-RTX 20 series: Event ID 14 error in event viewer when Digital Vibrance setting is changed - 00000001 00000200 00000000 00000005 00000008"
and 417.01 should have fixed "Event ID 14 - 00000001 00000200 00000000 00000005 00000006"

Didn't help me with either setup-config.
 
Still seeing it as of now.(1803,1809,1703)
 
 
GPU usage drops to zero, resulting in a small hiccups/freeze.
can easily re-produce this hiccup/freeze in several games.
 
on my second card now, so this is something outside the "PC".
as the same behavior was exactly the same on my old machine(z370)