Starting with a baseline of 50.6 MHz and 0% usage on both cards, I started AIDA64 and opened the System Stability Test GUI. I opened two instances of GPU-Z 0.5.8 (one for each card) to monitor the frequency and usage. PS - I repeated these tests several times to make sure the results were always the same. I'm still using the GeForce version 275.33. Why does quitting AIDA64 allow the clocks to return to 2D? I immediately started AID64 back up before the clocks got all the way back down and the clocks remained declining to 2D speeds. But as soon as I quit AIDA64 the clocks immediately started coming down as observed with GPU-Z. I then quit the test and the clocks never came down.
The usage went down but the clocks stayed up and never came down. I then unchecked the GPU test and noticed that the log said GPU1 finished. GPU usage went up as expected and the temperature went much higher to 65 degrees C. I then selected and ran the GPU test along with the CPU test. Also the GPU temperature never went higher than about 50 degrees C. However, I was surprised to see the clocks revert back to 2D when the CPU test was cancelled. I watched the GPU usage and it never showed any activity so I know the GPU test doesn't run until it's selected to run. Switching that on or off seems to have no effect at all. The preference for "Stability: Change to 3D profile on nVIDIA video adapters" has absolutely no effect on this condition. But is this normal?Īfter more testing I have more detailed observations.Īctivating the CPU/FPU stress test (with the GPU test UNCHECKED) increases the GPU clocks to 3D speeds and they never come back down during the test. I went back to version 2.00 because I don't want the GPU test running with the CPU test even if it's not really running but just increasing the GPU clocks. I did this several times to make sure but it always happens. I ran the Stability test again with the GPU test unselected and the GPU test ran anyway or at least the clocks speeds all maxed out and temperature started going up. I rebooted and started AIDA64 and everything looked normal. So I thought maybe that was making me think the GPU test was running. Then I noticed that the GPU clocks (GPU, Shader & Memory) do not return to idle speeds until AIDA64 is shut down. I then unchecked the GPU test to run only the CPU & FPU tests and the GPU test still runs. GPU Clock, Shader Clock & Memory Clock on my EVGA GTX580 maxed out as expected. In the System Stability Test I checked the new GPU test and ran it. I don't know if these are bugs or intended features but I tried the new version this morning and this is what happened.