Repository navigation
GPU Auto Optimizer v0.4.5
Pre-release
Pre-release
This is a pre-release for testing. The app does not offer it as an update. It is 0.4.4 with one addition, made to find out why the memory-bandwidth measurement fails on some cards.
New
gao --bandwidthshows what the measurement looked like: every run with its reading, or that it was thrown away because the clock changed under it. With--after-load <seconds>it measures right after that many seconds of full load, as a run does. It changes no setting.- A measurement that never settled says why in
run.log: how many runs gave a reading, between which values, and how many were thrown away.
If the app finds no memory overclock on your card
Since 0.4.4 a bandwidth measurement that does not work leaves the memory at stock. To help find out why it does not work, run the measurement by itself and send what it prints:
- Unzip, open the folder, and open a terminal there (right-click in the folder, Open in Terminal).
- Run
.\gao.exe --bandwidth --after-load 30and wait about 40 seconds. The fans may speed up. - Copy everything it printed into an issue or a message.
Before a run
- Close MSI Afterburner completely, also its icon in the notification area, and RivaTuner if you have it.
- NVIDIA app, System, Performance: switch Automatic Tuning off.
- Keep the NVIDIA overlay (Alt+Z) closed during the run.
- Close games and other programs that use the graphics card.
Known
- On a card where the bandwidth measurement does not work, no memory overclock is found. On the reference card a lowered power limit was ruled out as the cause; what it is on other cards is not known yet.
- A card that is hotter at stock than a profile allows gets its power limit lowered to meet the profile's temperature, which can make "Best of my GPU" slower than stock. Not solved in this version.
- The NVIDIA overlay is not detected; keeping it closed is up to you.
- The executables are not signed. Windows SmartScreen may warn at the first start, and a detection by an antivirus program cannot be ruled out; if you see one, please open an issue.
- Tested on one PC: an RTX 4070 with driver 617.42.