• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Unable to switch to UEFI due to GOP problem

0Nameduser

New Member
Joined
Aug 5, 2024
Messages
6 (0.02/day)
There's a program I'd like to use called RTCV (Real Time Corruptor), but for being able to use RTCV requires Vanguard to connect (hence the "V"). Attempting to use RTCV shows "Waiting for Vanguard client to connect" but stays like that forever. Searched up the problem, one from reddit said to "Enable Secure Boot" to a guy that had a similar problem like me.
Attempting to enable said secure boot, requires UEFI. Attempting to switch to UEFI, the PC restarts to switch. It goes on, suddenly it shuts down. Restarts again,

"There is no GOP (Graphics Output Protocol) support detected in this card.
'BIOS CSM/UEFI Mode' settings in BIOS will be changed to 'CSM'.

Press F1 to run setup.
Press F2 to load default values and continue.
"

All while there's a bright white light shining from where it says "VGA" below it.

Searched up the GOP problem, returns "Find a switch for the GPU or flash a new VBIOS on it".
No switch found, and flashing the VBIOS didn't help at all, same GOP message.

GPU-Z says the GPU supports UEFI, in other words there's a checkbox checked where it says "UEFI".

+ I have a UEFI-Compatible Intenso 1TB USB Hard Disk on GPT (GUID Partition Table) to boot on with UEFI (Windows not installed yet).
I also attempted to update the Motherboard BIOS to vAE but downloading it returns to "Not Found".
What I find weird is that first time switching to UEFI, it booted to the UEFI USB Drive. Switching to UEFI again, same GOP message.
Please help, nothing I searched did anything.

OS: Windows 10 Pro 64-Bit, reinstalled a few weeks ago
Motherboard: MPG Z490 GAMING PLUS, BIOS Version: MS-7C75vAD
CPU: Intel(R) Core(TM) i3-10100F 3.60GHz, Quad Core
GPU: Nvidia GeForce GTX 770, Subvendor: ASUS, VBIOS Version: 80.04.C3.00.02, Driver Version: 30.0.14.7514
 
There's a program I'd like to use called RTCV (Real Time Corruptor), but for being able to use RTCV requires Vanguard to connect (hence the "V"). Attempting to use RTCV shows "Waiting for Vanguard client to connect" but stays like that forever. Searched up the problem, one from reddit said to "Enable Secure Boot" to a guy that had a similar problem like me.
Attempting to enable said secure boot, requires UEFI. Attempting to switch to UEFI, the PC restarts to switch. It goes on, suddenly it shuts down. Restarts again,

"There is no GOP (Graphics Output Protocol) support detected in this card.
'BIOS CSM/UEFI Mode' settings in BIOS will be changed to 'CSM'.

Press F1 to run setup.
Press F2 to load default values and continue.
"

All while there's a bright white light shining from where it says "VGA" below it.

Searched up the GOP problem, returns "Find a switch for the GPU or flash a new VBIOS on it".
No switch found, and flashing the VBIOS didn't help at all, same GOP message.

GPU-Z says the GPU supports UEFI, in other words there's a checkbox checked where it says "UEFI".

+ I have a UEFI-Compatible Intenso 1TB USB Hard Disk on GPT (GUID Partition Table) to boot on with UEFI (Windows not installed yet).
I also attempted to update the Motherboard BIOS to vAE but downloading it returns to "Not Found".
What I find weird is that first time switching to UEFI, it booted to the UEFI USB Drive. Switching to UEFI again, same GOP message.
Please help, nothing I searched did anything.

OS: Windows 10 Pro 64-Bit, reinstalled a few weeks ago
Motherboard: MPG Z490 GAMING PLUS, BIOS Version: MS-7C75vAD
CPU: Intel(R) Core(TM) i3-10100F 3.60GHz, Quad Core
GPU: Nvidia GeForce GTX 770, Subvendor: ASUS, VBIOS Version: 80.04.C3.00.02, Driver Version: 30.0.14.7514
Gpu-z screenshot is needed
 
Maybe the GOP in the yours VBIOS is one of the earliest versions having some compatibility bugs with your newer motherboard.

There are several methods for updating GOP in Kepler GPUs VBIOS, but as a starting point I'd suggest just updating entire VBIOS to 80.04.EB.00.2A https://www.techpowerup.com/vgabios/159157/asus-gtx770-2048-140408

Also, at first try enabling the UEFI without switching to Secure boot (one-change-at-a-time)

Edit: I assume you have DirectCU II Asus variant (from your original VBIOS version)

This series has some caveats in VBIOS flashing.

Some samples requires running nvflash with
--protectoff
argument, some others crash some nvflash versions.

So make sure that VBIOS version really updated after flashing
 
Last edited:
Maybe the GOP in the yours VBIOS is one of the earliest versions having some compatibility bugs with your newer motherboard.

There are several methods for updating GOP in Kepler GPUs VBIOS, but as a starting point I'd suggest just updating entire VBIOS to 80.04.EB.00.2A https://www.techpowerup.com/vgabios/159157/asus-gtx770-2048-140408

Also, at first try enabling the UEFI without switching to Secure boot (one-change-at-a-time)

Edit: I assume you have DirectCU II Asus variant (from your original VBIOS version)

This series has some caveats in VBIOS flashing.

Some samples requires running nvflash with
--protectoff
argument, some others crash some nvflash versions.

So make sure that VBIOS version really updated after flashing
No secure boot, still GOP message. Maybe it's because of "Fast Boot" that gets enabled when switching to UEFI?
Also, is nvflash supposed to stop at "Reading EEPROM"?
And yes, I have a DirectCU II ASUS variant.

Original ASUS GTX 770 VBIOS file and nvflash CMD log are in the attachments.
 

Attachments

  • cmdlognv.png
    cmdlognv.png
    50.2 KB · Views: 63
  • GK104.rom
    GK104.rom
    163.5 KB · Views: 56
Thats nvflash bug specific to Kepler-era Asus GPUs. It supposed going further with messages about actual flashing process - so your VBIOS actually stayed unchanged.
Asus GPUs have something special in their VBIOS inforom part that causes nvflash to crash while it analyses existing VBIOS before doing the flash.

From my experience this can be fixed by rolling back to quite old nvflash (not sure which version) or using modern nvflash with --force_preserve_inforom option instructing it to avoid any adjustments in the inforom part
nvflash64 --force_preserve_inforom -6 vbios_file_to_flash.rom
 
Thats nvflash bug specific to Kepler-era Asus GPUs. It supposed going further with messages about actual flashing process - so your VBIOS actually stayed unchanged.
Asus GPUs have something special in their VBIOS inforom part that causes nvflash to crash while it analyses existing VBIOS before doing the flash.

From my experience this can be fixed by rolling back to quite old nvflash (not sure which version) or using modern nvflash with --force_preserve_inforom option instructing it to avoid any adjustments in the inforom part
nvflash64 --force_preserve_inforom -6 vbios_file_to_flash.rom
Rolling back to an older version of nvflash helped (5.558.0), I flashed the VBIOS successfully and it actually booted with UEFI and secure boot to the UEFI USB disk (still windows not installed yet), ...but I went to BIOS again to check everything then restarted the PC, and the grueling GOP message returned. I don't know what now.
 
Rolling back to an older version of nvflash helped (5.558.0), I flashed the VBIOS successfully and it actually booted with UEFI and secure boot to the UEFI USB disk (still windows not installed yet), ...but I went to BIOS again to check everything then restarted the PC, and the grueling GOP message returned. I don't know what now.
Update the motherboard bios
 
Latest bios for gpu


All others below

If it still doesnt work you might need a newer gpu.

Good luck
 
Back
Top