• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

RV7XX Software Overclocking is HERE!!

What did you use to test stability? Never go off the CCC test. Use something a lot more punishing like 3DMark Vantage/06 or ATI Tool.

You may have damaged your card, I did the exact same thing ears ago on an Nvidia card. And ever since, it was never as good at OC'ing, and gradually just got worse.

Meh, used ATI CCC's autotune and that got it straight back up to 700/1155, didn't bother pushing it further.
 
Running vista x64 on the abit ip35pro

4870 is @ 815 core 925 mem

Running lightsmark on a 24" DGM mon with test set to 1280-1024

With the mobo not being pcie2 is a score of around 205.5fps average sounding about right ??

Cheers
 
I don't know if anyone else has noticed this, but you can also use this app to make 48xx cards idle at lower clocks without having to flash with modified bios.

By default, with a modified profile xml, CCC doesn't allow you to set the idle speed for a 4850 to less than 450/675.

However, if you first underclock the card to 160/500 with the GPU clock tool, then start CCC, you can create a profile that works with that as the idle speed.

For example:

Code:
<Profile>
  <Caste name="Graphics">
    <Groups>
      <Group name="Overdrive5">
        <Feature name="TimeUnlocked" />
        <Feature name="OverclockEnabled">
          <Property name="OverclockEnabledProperty" value="True" />
        </Feature>
        <Feature name="CoreClockTarget_0">
          <Property name="Want_0" value="16000" />
          <Property name="Want_1" value="16000" />
          <Property name="Want_2" value="62500" />
        </Feature>
        <Feature name="MemoryClockTarget_0">
          <Property name="Want_0" value="50000" />
          <Property name="Want_1" value="50000" />
          <Property name="Want_2" value="99300" />
        </Feature>
        <Feature name="CoreVoltageTarget_0">
          <Property name="Want_0" value="1046" />
          <Property name="Want_1" value="1046" />
          <Property name="Want_2" value="1123" />
        </Feature>
        <Feature name="MemoryVoltageTarget_0">
          <Property name="Want_0" value="0" />
          <Property name="Want_1" value="0" />
          <Property name="Want_2" value="0" />
        </Feature>
        <Feature name="FanSpeedProtocol_0">
          <Property name="FanSpeedProtocolProperty" value="Percent" />
        </Feature>
        <Feature name="FanSpeedAlgorithm_0">
          <Property name="FanSpeedAlgorithm" value="Automatic" />
        </Feature>
        <Feature name="FanSpeedRPMTarget_0">
          <Property name="Want" value="0" />
        </Feature>
        <Feature name="FanSpeedPercentTarget_0">
          <Property name="Want" value="0" />
        </Feature>
      </Group>
    </Groups>
    <Adapter name="PCI_VEN_1002&amp;DEV_9442&amp;SUBSYS_05021002&amp;REV_00_4&amp;239521B6&amp;0&amp;0008A">
      <Aspect name="Overdrive5" />
    </Adapter>
  </Caste>
</Profile>
 
Last edited:
^useful info...but with the BIOS you can also lower idle voltage which has a real impact on temps and power drain.
 
^useful info...but with the BIOS you can also lower idle voltage which has a real impact on temps and power drain.

You can with CCC too, by changing the 'CoreVoltageTarget_0' lines. I'm running my idle voltage at 1.000v in CCC, which makes a small difference to temps but it is only 0.045v lower than default. I tried 0.95v but was getting artifacts in windows.

The big advantage of the modified bios is the improved automatic fan control settings. But, a lot of people would rather not take the risk of a bios flash.
 
Last edited:
Back
Top Bottom