foothead
Omnicide now.
- Messages
- 10,027
- Location
- My own personal hell
Yep, radeon BIOS editor.
Make sure you flash it in DOS, not Windows.
Also, it's a good idea to leave the 2D clocks intact. This way, you will be able to reflash should you overdo it. Another thing I suggest is installing rivatuner and editing the parameters so you can test the clocks before making flashing. This way, all you have to do is reboot to revert.
Other overclocking tools I recommend are furmark, MSI afterburner, OCCT, and Crysis. OCCT usually stresses the GPU more than anything else out there, so it will catch most errors, however some issues do manage to get past the benchmarks and will only present themselves in specific games. I suggest finding the max that is stable with these three tests, then back off at least 20 MHz.
Also, if you need a vMod, I can help.
Swype is amazing. I couldn't stop laughing when it managed to pick up antidisestablishmentarianism.
Make sure you flash it in DOS, not Windows.
Also, it's a good idea to leave the 2D clocks intact. This way, you will be able to reflash should you overdo it. Another thing I suggest is installing rivatuner and editing the parameters so you can test the clocks before making flashing. This way, all you have to do is reboot to revert.
Other overclocking tools I recommend are furmark, MSI afterburner, OCCT, and Crysis. OCCT usually stresses the GPU more than anything else out there, so it will catch most errors, however some issues do manage to get past the benchmarks and will only present themselves in specific games. I suggest finding the max that is stable with these three tests, then back off at least 20 MHz.
Also, if you need a vMod, I can help.
Swype is amazing. I couldn't stop laughing when it managed to pick up antidisestablishmentarianism.
