BTW-The old video card I was using in the prior machine never gave me this error. All hardware was the same except for the change to the EVGA 2080 Ti.

Yea. I had a Titan Xp and never had an issue until this upgrade to the 2080 Ti. I had used that hardware (In my old machine) about 1 year with no problems. The only difference was the 2080 Ti. Very unlikely to be anything else.
 
I did see this error reported with SLI setups which does not apply to me, but I see you're running 2 cards.

I'll try that. Thanks.

Any New Bios for your Motherboards?
Anyone ask ASUS about this on there Motherboard Support Site? 

Iceman2733

bcavnaugh
Any New Bios for your Motherboards?
Anyone ask ASUS about this on there Motherboard Support Site? 

I am on the latest BIOS, I made a post but it seems like that site is very dead with very limited support.  I called Asus support and you can imagine how that went, Asus is becoming bad about not giving any support for products after a year.  I mean buy a $649 motherboard and give it a year worth of updates kind of upsets me.  I have thought about picking up an X299 Dark and trying it out. 

The X299 Dark is on Sale for only $299 ATM & FREE Standard Shipping on this item for a Limited Time
I got this with my 3rd X299 Dark MB  Fun Game and the Best Motherboard I have ever had and from EVGA to Boot.
EVGA X299 DARK, 151-SX-E299-KR, LGA 2066, Intel X299, SATA 6Gb/s, USB 3.1, USB 3.0, EATX, Intel Motherboard

bcavnaugh

Iceman2733

bcavnaugh
Any New Bios for your Motherboards?
Anyone ask ASUS about this on there Motherboard Support Site? 

I am on the latest BIOS, I made a post but it seems like that site is very dead with very limited support.  I called Asus support and you can imagine how that went, Asus is becoming bad about not giving any support for products after a year.  I mean buy a $649 motherboard and give it a year worth of updates kind of upsets me.  I have thought about picking up an X299 Dark and trying it out. 

The X299 Dark is on Sale for only $299 ATM & FREE Standard Shipping on this item for a Limited Time
I got this with my 3rd X299 Dark MB  Fun Game and the Best Motherboard I have ever had and from EVGA to Boot.
EVGA X299 DARK, 151-SX-E299-KR, LGA 2066, Intel X299, SATA 6Gb/s, USB 3.1, USB 3.0, EATX, Intel Motherboard

I have read quite a bit of positive stuff about the board also, if it wasn't for my whole system being hardlined water cooled I would have already bought it and given it a try.  I still might buy it, Amazon had it for $248 ships and sold by them it lookslike it went up a bit

Hopper64
I’m on the latest bios too for the R6EOmega. Flashed it yesterday without any problems.

Well I ordered the X299 dark I will let you know if it fixes  issues.  If you go to Asus forum I have a thread there you can comment on maybe it  will gain notice 

$291.99  Sold by: Amazon.com (This is what you should buy on Amazon) Link
Ships from and sold by Amazon.com is what you want for 100% Support from EVGA.
$248.98 Sold by 21k Elite Publishing and Fulfilled by Amazon. This is a 3rd Party Seller and you should not buy from them.
Maybe the price is so low because they cannot sale them.

I did RMA on entire pc expect cpu and same error (also same motherboard as Iceman2733 ASUS ROG RAMPAGE VI Extreme). I reported this problem when i received 2080ti FTW3 from evga with nvlink bridge. Asus need to update BIOS for SLI setups (20 series). Old sli setup 1080 ti ftw3 boot without problems. Also this happens totally random. If asus have no plans to update bios i will need to buy new motherboard. Asus support is biggest cancer ive seen in my life no comment about that.
 
https://rog.asus.com/forum/showthread.php?105105-Code-0E-Load-VGA-Bios/page2&highlight=bios
 
I called Asus support the night before last and the agent told me they were receiving many escalations regarding this 2080 issue and their engineering team is currently working on resolution. The only information they could provide me was it is indeed related to nvlink interface incompatibility with current BIOS/board, and users of the 20xx series GPU's, whether multipgpu or single gpu may face issues and instability until BIOS update is released.

They also stated there is other issues related to the 20xx series GPU's and screens going black prior to login screen in windows/drive instability with boards at the moment, and this is affecting other boards as well (not just the ZE) and they are working on BIOS updates for these issues too. 

They said to expect BIOS updates "soon" and their L2 teams will keep in touch. 

Seems the NVlink interface, regardless of multigpu or single, is causing issues with ASUS mobos in general for many. I suspect they never really added support for it since it was technically outside the scope of the market these boards were intended for (well, until now).

Iceman2733

kacan22
I did RMA on entire pc expect cpu and same error (also same motherboard as Iceman2733 ASUS ROG RAMPAGE VI Extreme). I reported this problem when i received 2080ti FTW3 from evga with nvlink bridge. Asus need to update BIOS for SLI setups (20 series). Old sli setup 1080 ti ftw3 boot without problems. Also this happens totally random. If asus have no plans to update bios i will need to buy new motherboard. Asus support is biggest cancer ive seen in my life no comment about that.
 
https://rog.asus.com/forum/showthread.php?105105-Code-0E-Load-VGA-Bios/page2&highlight=bios
 
I called Asus support the night before last and the agent told me they were receiving many escalations regarding this 2080 issue and their engineering team is currently working on resolution. The only information they could provide me was it is indeed related to nvlink interface incompatibility with current BIOS/board, and users of the 20xx series GPU's, whether multipgpu or single gpu may face issues and instability until BIOS update is released.

They also stated there is other issues related to the 20xx series GPU's and screens going black prior to login screen in windows/drive instability with boards at the moment, and this is affecting other boards as well (not just the ZE) and they are working on BIOS updates for these issues too. 

They said to expect BIOS updates "soon" and their L2 teams will keep in touch. 

Seems the NVlink interface, regardless of multigpu or single, is causing issues with ASUS mobos in general for many. I suspect they never really added support for it since it was technically outside the scope of the market these boards were intended for (well, until now).

I am really glad I am not the only person who was having these issues, don't get me wrong I am sorry you are having them also but glad to know it isn't just me. 
 
I know your pain about Asus support I went ahead and cut my losses and picked up a x299 Dark board which seems to doing ok.  But that is a pathetic fix for a company like Asus it isn't like they don't make 2080Ti that they should be doing testing with. 
 
I swear this whole 2080/Ti Release really makes you wonder if anyone tested these things before they released them.  This has by far been the worse release I can remember, from all the hardware related issues to software.  Its like nothing is correct about these cards.  Even when looking at overclocking software that is still buggy as all get out and doesn't work correctly. 

I think that evga cards have problem with asus motherboard ( I just looked at this random video https://www.youtube.com/watch?v=MnZ51GqdgN4). Maybe EVGA should do some tests on same motherboard with FTW3 cards. I dont know what to do. I have to options fight with asus or evga to do something or buy evga dark x299 or msi creation x299

Do you think this will help? (If i disable secure boot do i need to reinstall window?)
I have fast boot disable and launch csm enable but secure boot enable.
 
Dear Asus Valued Customer,
 
Thank you for contacting Asus, my name is Evangelia and I will try my best to assist you with your current situation.
 
Regarding the below described case, please check if the problem persists with the below settings at BIOS >> Boot

Secure Boot >> disable
Fast Boot >> disable
Launch CSM >> enable
 
In case you are not satisfied by our reply above, please inform us accordingly before filling the satisfaction form.
In case you are satisfied by our reply above, we invite you to select 9 or 10 as a positive evaluation.
 
 
Should you have any further questions, please do not hesitate to get back in touch with us.
 
Kind regards,
Evangelia P.

Iceman2733

kacan22
Do you think this will help? (If i disable secure boot do i need to reinstall window?)
I have fast boot disable and launch csm enable but secure boot enable.
 
Dear Asus Valued Customer,

Thank you for contacting Asus, my name is Evangelia and I will try my best to assist you with your current situation.

Regarding the below described case, please check if the problem persists with the below settings at BIOS >> Boot

Secure Boot >> disable
Fast Boot >> disable
Launch CSM >> enable

In case you are not satisfied by our reply above, please inform us accordingly before filling the satisfaction form.
In case you are satisfied by our reply above, we invite you to select 9 or 10 as a positive evaluation.


Should you have any further questions, please do not hesitate to get back in touch with us.

Kind regards,
Evangelia P.

I did a few combinations of the above except never turned off fast boot. Not sure how that would affect the GPUs during post. I ended up picking up a set of Asus 2080ti OC models, I hate I already changed out boards but going to see if I have similar issues with these cards that might tell us if this is a evga bios issue or a 2080ti issue

I gave up im getting meg x299 creation from MSI

kacan22

Iceman2733

kacan22
Do you think this will help? (If i disable secure boot do i need to reinstall window?)
I have fast boot disable and launch csm enable but secure boot enable.

Dear Asus Valued Customer,

Thank you for contacting Asus, my name is Evangelia and I will try my best to assist you with your current situation.

Regarding the below described case, please check if the problem persists with the below settings at BIOS >> Boot

Secure Boot >> disable
Fast Boot >> disable
Launch CSM >> enable

In case you are not satisfied by our reply above, please inform us accordingly before filling the satisfaction form.
In case you are satisfied by our reply above, we invite you to select 9 or 10 as a positive evaluation.


Should you have any further questions, please do not hesitate to get back in touch with us.

Kind regards,
Evangelia P.

I did a few combinations of the above except never turned off fast boot. Not sure how that would affect the GPUs during post. I ended up picking up a set of Asus 2080ti OC models, I hate I already changed out boards but going to see if I have similar issues with these cards that might tell us if this is a evga bios issue or a 2080ti issue

Hey,
 
So guys in caseking.de tested my EVGA 2080TI FTW3 (i bought cards from them) in sli on ASUS Rampage VI EXTREME they came to conclusion that evga FTW3 (sli) cards are not supported on asus rampage vi extreme motherboard that i need to wait for future bios updates. They also tried other cards from msi and aorus (there is no LOAD VGA BIOS). I bought new motherboard and fixed my problems with this. I will probably ask for refund on ASUS Rampage VI EXTREME. Only affected models are FTW3 because other model like EVGA BLACK work without problems . Single ftw3 is working fine but when you add 2 ftw3 cards with nvlink problems start to happen. They tested this for almost 1 month. This is so retarded but my problem is fixed (buying new motherboard).

Interesting.

I managed to solve "9C Load VGA BIOS" error code for my setup. I have  "ASUS ROG Maximus XII Extreme Z490" motherboard and "VGA GeForce RTX 2080 FTW3" graphics card.
 
Before you turn your PC on make sure that ALL your USB devices are unplugged. This should get you passed the error and into the BIOS. Once there, just plug in a plain old school keyboard. I used a USB3 port. Now you can set your boot device. In my case, I switched from default to windows (sorry for not being specific, I cannot recall the exact wording).
After I restarted the PC, it successfully booted into Windows. After further restarts, I did not see this error anymore.
 
Good luck.