RT2.20 multi-GPU support major RED FLAG
Commenta 
26th November , 2008|
OK i just traced this down to RivaTuner 2.20. this past weekend i tried out the 180.60 drivers and RT 2.20. after attempting to adjust my second GPU’s clocks with RT and rebooting my system my second GPU was permanently locked to 198/1188/396. GPU-Z reported everything as 0MHz and the performance in SLI in any game or benchmark showed a huge decline from before and after. as for steps to solve this i did everything i could think of. i tried dropping back to 180.48, trying 180.60 again and falling back to 178.24 without solution (and yes i used the current Driver Sweeper every time). even went as far to flashing the bios. i formatted my machine last night and installed 180.60 and RT 2.20. in and out of SLI both RT and GPU-Z saw the same and correct clocks for my second GPU. i just tried the same changes in RT with my second GPU and rebooted. the same problem has returned and my second GPU is once again running at 198/1188/396.. now i get to reinstall a second time but i am going to post this same block of info in a thread to alert Unwinder. oh and Hybrid –> my 3DMark06 score in SLI for Mother Nature @ 1680×1050 with 2AA/16AF went from 170+FPS on avg to 70 in both instances of this problem occuring… |
FYI i also, on the first occurrence, went through my Registry and stripped everything to do with RivaTuner from version 2.09 to 2.20 after about the fourth driver/RT uninstall/reinstall attempt without resolution.
- Robert (PmR)DeathInJune
Original post by pmrdij