GOP Update Tool (Tuing)
Tool for updating graphics card firmware files or updating UEFI Graphics Output Protocol modules in packages.
Latest version
0.4.11
Supported models
NVIDIA Turing micro-architecture
Support platform
Windows 7 or later (some effects do not display properly in Windows 7)
*Requires PowerShell 2.0 or higher
Instructions
Use GPU-Z or NVFlash to extract the firmware file, or get the firmware update package from the official support page of the brand, drag the firmware file or update package to the GOP update tool icon and follow the prompts to use the GOP module stored in the inventory for update renew.
Precautions
Updating to the modified version will destroy the UEFI digital signature, please disable the Secure Boot function in the BIOS/UEFI settings before using it.
Q&A
- No file input detected, please drag and drop the firmware file to the batch.
Please re-drag the firmware file or update package to the GOP Update Tool icon.
Since the drag-and-drop function of the Windows platform does not support paths containing some special symbols, please move the file to a directory that does not contain special symbols or enter GOP Update Tool path space firmware file or update package path on the Windows Command Line and press Enter to execute operate.
E.g :
"C:\Users\Your Name\Desktop\GOP Tools\GOP Update Tool.bat" C:\Users\Your Name\Desktop\TU106.rom
-
Please check the file size and try again.
Please check your firmware file or update package size, GOP Update Tool supports size range from 500KB to 32MB.
If the firmware file is uncompressed and conforms to the architectural requirements, the size should not be smaller than 976KB, otherwise your firmware file may be incomplete or damaged. -
Missing available GOP module files, please confirm and try again.
Unable to find GOP module files from inventory directory, please keep files with .efi suffix and try again. -
Firmware read error, please check and try again.
Please close programs that may be using the firmware file or update package and check the file’s read permissions. -
Unsupported architectures (0x…) .
Firmware that does not support this architecture, for Ampere architectures (0x600…) and newer architectures Please consider using the GOP Tools (Ampere), and for AMD and earlier architectures, please consider using the GOP Updater . -
No GOP module detected.
Unable to detect the GOP module from the imported firmware file or update package, except that the file is compressed or encrypted, some mobile platforms (notebook or tablet) will use the integrated graphics chip built into the CPU for video output and initialization, so the graphics card is not configured GOP function. -
Which version should I choose?
Comparing versions, it’s evident that aside from certain specific versions undergoing program structure reconstructions, updated versions often include additional code supplements and modifications. From experience, we believe this represents functional fixes or stability improvements for the original program in certain scenarios. We recommend using the latest version on devices without compatibility issues to achieve a better user experience.
Furthermore, on certain devices, the available space for the GOP module is insufficient to accommodate the full version. Consequently, the tool offers modified versions with trimmed digital signatures to address space constraints. We advise prioritizing the use of unaltered versions on devices meeting space requirements.
*To use the Mod version, please disable the “Secure Boot” feature in the motherboard’s UEFI settings, some modern motherboards may fail device initialization due to a lack of digital signatures. -
Can I downgrade?
In theory, you’re free to change the version of the GOP module. However, considering the rarity of this requirement and factors such as device stability,This tool does not currently provide this feature. If you have such a need, please contact us. -
Why does the Device ID as 0000-0000？
Some firmware, especially OEM products, have not configured the GOP Device ID during compilation, and therefore use the default value of 0000-0000. -
The GOP module file suitable for version 0x500… update was not found.
Unable to find a newer GOP module file from inventory than this firmware file or update package, which may already have the latest known GOP version.
If you want to check for updates manually, you can check for the newly released firmware files or update packages for graphics cards with the same architecture from the official support page of the brand or TechPowerUp, and use the extraction and normalization tool to check whether there is a higher version. -
The required file was not found, please confirm and try again.
A required GOP module file was deleted, please close programs that may have deleted this file and try again. -
Cache verification failed, please close unnecessary programs and try again.
The temp\FW cache file created by the GOP Update Tool has been deleted, please close the program that may delete this file or folder and try again.
Also, do not run multiple instances at the same time. -
Firmware update failed due to unknown error.
The firmware file encountered an error during the update process and failed to validate, please check your Powershell platform version and environment configuration and retry.
If you are still experiencing this issue, please contact us.
.
Extraction and Normalization Tool (Tuing)
A tool for extracting and normalizing graphics card firmware files or UEFI Graphics Output Protocol modules in update packages.
Latest version
0.3.7
Supported models
NVIDIA Turing micro-architecture
Support platform
Windows 7 or later (some effects do not display properly in Windows 7)
*Requires PowerShell 2.0 or higher
Instructions
Drag a firmware file or update package to the Extract and Normalize Tool icon to extract and inventory new version GOP modules to the current directory for update use.
In addition, the Extraction and normalization tool also supports importing and normalizing the .efirom format files built into GOP Updater.
Q&A
- No file input detected, please drag and drop the firmware file to the batch.
Please re-drag the firmware file or update package to the Extraction and Normalization Tool icon.
Since the drag-and-drop function of the Windows platform does not support paths containing some special symbols, please move the file to a directory that does not contain special symbols or enter Extraction and Normalization Tool path space firmware file or update package path on the Windows Command Line and press Enter key to operate.
E.g :
"C:\Users\Your Name\Desktop\GOP Tools\Extraction and Normalization Tool.bat" C:\Users\Your Name\Desktop\TU106.rom
-
Please check the file size and try again.
Please check the size of the firmware file or update package you want to extract, Extraction and Normalization Tools support a size range from 50KB to 32MB.
If the imported file is uncompressed and meets the architectural requirements, the typical size should be no less than 67KB. -
Firmware read error, please check and try again.
Please close programs that may be using the firmware file or update package and check the file’s read permissions. -
Unsupported architecture.
Firmware that does not support this architecture, for Ampere architectures (0x600…) and newer architectures Please consider using the GOP Tools (Ampere), and for AMD and earlier architectures, please consider using the GOP Updater . -
No GOP module detected.
Unable to detect the GOP module from the imported firmware file or update package, except that the file is compressed or encrypted, some mobile platforms (notebook or tablet) will use the integrated graphics chip built into the CPU for video output and initialization, so the graphics card is not configured GOP function. -
GOP module file with the same or higher version already exists.
The inventory directory already has a GOP module file of the same or higher version as the imported firmware file or update package. -
Extraction failed due to unknown error.
During the process of extracting and normalizing the GOP module, an error was encountered and the verification failed. Please check your Powershell platform version and environment configuration and try again.
If you are still experiencing this issue, please contact us.