• 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.

5850 Bios that works OC without glitching

Soldato
Joined
27 Dec 2006
Posts
2,916
Location
Northampton
Current I have an MSI 5850 thats factory overclocked. There is a known glitch that when using dual screen one of the screen can flicker and become annoying.

I over come this problem by flashing the bios to an stock ASUS 5850 and I've noticed in games that its struggles to handle the normal stuff. If i attempt to overclock it, I go back to my original problem of the dual screen flicker.

Anyone know any good bios that is overclocked and the voltage tweaked so it doesn't flicker?
 
Hasn't this been ongoing for ages now? I've had my 5850 since October and when getting dual screen its given me the glitch. Initially before my rebuilt I downclock my MSI and it stopped the glitches but didn't effect performance too much.

Now I just get a big hit on performance.
 
Anyone know any good bios that is overclocked and the voltage tweaked so it doesn't flicker?

There is a user made bios linked on this thread. Though it appears hes set the memory to remain at 1200 constantly, which, as shown near the bottom of the thread, increased idle power usage noticeably. There is a suggestion that a 400/800 setting would sort it. I only ever use dual monitors whilst gaming, so havent been bothered looking for a solution to this, but have been keeping an eye out here for a fix. Nothing on the 10.4a driver thread I saw mentioned this, but I'll stand corrected, as havent been fully following.

http://forums.techpowerup.com/showthread.php?t=117230
 
Last edited:
Doesn't need a new bios, go into the drivers, make a new profile, find the profile in users. app data/local/ati/ace/profiles, edit, adjust the lower 2d idle speed(the first one listed, its obvious where) to 400, and adjust the memory to 1000mhz for all speeds).

After that it won't idle below 400/1000, you get no flickering at those speeds, this has been covered time and time and time again in so many threads lately its getting silly.

Theres other ways to do this, use msi afterburner to control 2d/3d speeds itself and set 400/1000 for 2d, or use gpu clock tool to set full 3d speed which also disables powerplay so will stop it idling too low.

Using the drivers/profiles method allows for the lowest possible voltage in idle as it will allow the 0.95v setting to be used, lowest MSI afterburner can use is 1v, it makes a difference, though not power bill destroying.
 
I had the flicker issue on a 5870 and made a custom profile which keep the memory clock up which fixes it.

However does anyone else find that profiles need to be applied twice in some cases to make all the settings apply? I've set up batch files to do this with a short interval in between applying settings but wondered if this is normal for ATI CCC (I've had Nvidia cards for the last few years).
 
10.5 beta driver fixes the problem, all gddr5 cards seem to have the problem that it won't work with dual screens at a low frequency, only fix is to up the memory speeds which this driver does I'm afraid, nvidia has the same problem, that's why with dual screens the 4x0 cards have such high idle temps with dual screens.
 
Question all, i'm testing the 10.5 leaked drivers but when i up any of my Core clock or Mem Clock it begins to glitch like normal.

How do i actually it my 5850 to overclock only on 3d mode? I've tried using MSI afterburner and made two profiles 2d and 3d. But when i do a benchmark I dont see the 3D settings kick in.
 
Doesn't need a new bios, go into the drivers, make a new profile, find the profile in users. app data/local/ati/ace/profiles, edit, adjust the lower 2d idle speed(the first one listed, its obvious where) to 400, and adjust the memory to 1000mhz for all speeds).

After that it won't idle below 400/1000, you get no flickering at those speeds, this has been covered time and time and time again in so many threads lately its getting silly.

Theres other ways to do this, use msi afterburner to control 2d/3d speeds itself and set 400/1000 for 2d, or use gpu clock tool to set full 3d speed which also disables powerplay so will stop it idling too low.

Using the drivers/profiles method allows for the lowest possible voltage in idle as it will allow the 0.95v setting to be used, lowest MSI afterburner can use is 1v, it makes a difference, though not power bill destroying.

I want to revisit this issue i'm still getting.

Like you mentioned I can edit the cfg on my ATI but the numbers do not match up.

MSI and Ati CC are telling me what my current values are and on my cfg file these do not reflect these. Anyone want to explain this to me please?

atiy.jpg
 
I've said in many threads, and I can't say why it does, but once you overclock it seems to bypass the current drivers and revert to the I assume bios clocks.

Its hard to explain and that wasn't good :p

Basically when I first install a system, all is completely hunky dory, any driver(from about 9.12/10.1 up) will default a dual screen system to 400/900 (though personally I get flickering up to 400/1000 in some instances so those are the clocks I set myself).

That works fine for me, I reinstalled windows today as it happens, dual screen, not a flicker in sight, same happened last time.

Now the SECOND I overclock, it seems to override something in the drivers, the "fix" as it were and after I overclock the OLD idle speeds come back into play, the 137/300 speeds as in your config file.

I really don't know why, only that it does. Without overclocking the drivers would appear to have a fix that when default clocks are enabled, and it finds a dual screen setup, it over rides those clocks, but anything outside of default clocks and the fix doesn't work.

So for me, in that config file you posted, I'd change the core clock settings to 400/400/775 (775 is max it will go on a 5850 in the CCC< you can put in 9.2Ghz there, it will only go to 775 with normal bios), in the memory I put 1000/1000/1100.

I actually seem to get away stability wise, with the lowest voltage setting while still at 400Mhz so I keep both the first two settings at 950, largely because afterburner only allows 1v as the lowest setting and 0.95v you can set here, drops temps and power a little.

Even worse though is, now and then, it did a few days ago, out of no where it started enabling itself to 137/300 clocks again. I may well have overclocked something different to usual, I hit a few profiles in afterburner and everything was back to normal. I'm not really sure at that stage, what had changed.

The safest, completely fullproof method is to run stock or overclocked 3d speeds all the time, either using gpu clock tool, or msi afterburner, gpu clock tool will disabled powerplay full stop, at any speed you set. Afterburner will only stop powerplay working completely if you set clocks above the CCC limits. For a 5850 thats 775Mhz, if you set afterburner to run at 775Mhz, it will still drop to idle clocks, set it to 776Mhz and it will stay at whatever speed you set it too. Usefully, if you reset the speed to 775Mhz, it will re-enable powerplay, while gpu clock tool won't.

SO what I tend to do for gaming, is set a higher overclock with higher voltage, around 950/1.25v and it stays there in games no matter what. Then for idle stuff i'll have a profile at 775Mhz, set that and powerplay will kick in idle speeds for me. I then use the config file with the AMD profiles to make sure those don't go too low.

Cainer, if AMD made this a sticky on THEIR forums, it would solve almost everyones problems. I've remarked on that repeatedly aswell, AMD, Intel, Nvidia, just about everyone should have one page updated with these kinds of fixes, a page EVERYONE knows about and everyone will check first. They are all morons for not doing that.
 
Have we got an ETA for a permanent fix from ATI on this? Was planning on buying a 5850 for my uncle who won't have a clue / be arsed with having to tweak new hardware just to get it to do what it's supposed to do!
 
So can you explain to me why my clocks in the profile does not match up in the CCC overdrive tab or in MSI Afterburner?

Code:
 <Group name="Overdrive5">
        <Feature name="TimeUnlocked" />
        <Feature name="OverclockEnabled">
          <Property name="OverclockEnabledProperty" value="True" />
        </Feature>
        <Feature name="AutoTuneSupport" />
        <Feature name="CoreClockTarget_0">
          <Property name="Want_0" value="15700" />
          <Property name="Want_1" value="55000" />
          <Property name="Want_2" value="76500" />
        </Feature>
        <Feature name="MemoryClockTarget_0">
          <Property name="Want_0" value="30000" />
          <Property name="Want_1" value="90000" />
          <Property name="Want_2" value="112500" />
        </Feature>
        <Feature name="CoreVoltageTarget_0">
          <Property name="Want_0" value="950" />
          <Property name="Want_1" value="1038" />
          <Property name="Want_2" value="1088" />
        </Feature>
        <Feature name="MemoryVoltageTarget_0">
          <Property name="Want_0" value="0" />
          <Property name="Want_1" value="0" />
          <Property name="Want_2" value="0" />
        </Feature>

Autotune support reflects what exactly? want 0,1,2 are indicating what figures exactly, because I can't see what these figures mean to me even though you constantly tell about the glitch and talking about your experiences and it means nothing to me:(
 
Want 0 is your 2D clock
Want 1 is some midway clock that is rarely used
Want 2 is your 3D clock

I've just done this with m7 5870:

<Feature name="CoreClockTarget_0">
<Property name="Want_0" value="40000" />
<Property name="Want_1" value="40000" />
<Property name="Want_2" value="90000" />
</Feature>
<Feature name="MemoryClockTarget_0">
<Property name="Want_0" value="60000" />
<Property name="Want_1" value="60000" />
<Property name="Want_2" value="130000" />
</Feature>
<Feature name="CoreVoltageTarget_0">
<Property name="Want_0" value="1063" />
<Property name="Want_1" value="1063" />
<Property name="Want_2" value="1163" />

That eliminates all but an odd flicker when changing from 2D->3D and tries to keep power usage down.

So in 2D I run at 400/600 with the GP voltage bumped down to 1.063V.

Setting Want 0 and Want 1 to the same values helps eliminate flicker greatly.
 
Back
Top Bottom