After going through trial and error, I've managed to overclock my 128MB Mobility Radeon 9700 card on my Dell Inspirion XPS laptop to 515.45/279.82 (stock: 445.25/263.25) with no visible artifacts in gaming. The problem is, however, whenever I put my computer into standby or hibernation from with these clocks, then return to the on state, the display comes back still visible, but extremely garbled. I do not understand why this happens when I don't get this problem at any other time.
Also, since I have another question on my mind, I might as well post it here also: As you can see, I've managed to get a decent clock out of the core, but I am rather disappointed with the memory clock; I've noticed that when I try to clock it to anything higher than 280MHz, I get extremely large artifacts all over the place when running 3dMark2k3. Why can I beef up the core so high but not the memory? 279.82MHz is rather low in my opinion considering that the older 64MB nVidia GEforce4 MX4000 card on my old computer has an around-350MHz clock.
/edit
Oh, on other question on my mind at the moment: when using ATItool (0.0.23 beta10), I get an error message telling me to disable Direct3S Debugging Runtimes, as well as telling me to disable Temporal Anti-Aliasing. I found the option to disable the Debugging Runtimes (the option was greyed-out tho but it was set to off), but I cannot seem to find the TAA option for the love of me. (My card's drivers are the Omega 2.5.97a, if that helps any.)
Also, since I have another question on my mind, I might as well post it here also: As you can see, I've managed to get a decent clock out of the core, but I am rather disappointed with the memory clock; I've noticed that when I try to clock it to anything higher than 280MHz, I get extremely large artifacts all over the place when running 3dMark2k3. Why can I beef up the core so high but not the memory? 279.82MHz is rather low in my opinion considering that the older 64MB nVidia GEforce4 MX4000 card on my old computer has an around-350MHz clock.
/edit
Oh, on other question on my mind at the moment: when using ATItool (0.0.23 beta10), I get an error message telling me to disable Direct3S Debugging Runtimes, as well as telling me to disable Temporal Anti-Aliasing. I found the option to disable the Debugging Runtimes (the option was greyed-out tho but it was set to off), but I cannot seem to find the TAA option for the love of me. (My card's drivers are the Omega 2.5.97a, if that helps any.)
Last edited: