Re: NVflash 5.427.0 error. Not sure what it is doing.
2018/02/26 06:03:10
(permalink)
NVFlash is always changing..Versions have changed, commands have change, supported cards have changed, supported operating systems (32 vs 64-bit) have changed..Can be a little bit of a hassle/trial and error to find a version and the supported commands that works right.
The NVFlash.exe in the download packages for the proper 32/64-bit OS (nvflash/nvflash64) and --protectoff (or -r) commands are the neccessary essentials in newer versions, as well as using versions with certificate checks bypassed (JoeDirt at OCN got that pretty much handled) on some cards..The --protectoff (or -r) command is essential for all versions of NVFlash, far as I know..Uninstalling the NVIDIA graphics driver or disabling the graphics card in Device Manager (which just disables the NVIDIA graphics driver) and rebooting is recommended, if not essential too, and is part of the EVGA recommended flash procedure.
I just gave the command line example in my post #7 as to how I do it with my card and older cards..Older versions of NVFlash don't include the nvflash64.exe that is neccessary with newer OS's and cards..NVFlash for Windows 5.165 (that doesn't include nvflash64) never gave me a problem in Win7 and 10 64-bit, but 5.427.0 coughs up an error unless nvflash64 is used, and all version refuse to flash and error out if the --protectoff (or -r) command is not used first.
* Corsair Obsidian 450D Mid-Tower - Airflow Edition * ASUS ROG Maximus X Hero (Wi-Fi AC) * Intel i7-8700K @ 5.0 GHz * 16GB G.SKILL Trident Z 4133MHz * Sabrent Rocket 1TB M.2 SSD * WD Black 500 GB HDD * Seasonic M12 II 750W * Corsair H115i Elite Capellix 280mm * EVGA GTX 760 SC * Win7 Home/Win10 Home * "Whatever it takes, as long as it works" - Me