1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

OCing HD6850

Discussion in 'AMD / ATI' started by Richard Shepherdson, Jan 16, 2013.

  1. Richard Shepherdson New Member

    Joined:
    Jul 12, 2006
    Messages:
    109 (0.04/day)
    Thanks Received:
    5
    Question guys,

    Had no problem OCing HD6850 in past, stock 830/1100 been running at 950/1150 for gaming.

    OCing with afterburner, though the problem seems to happen in TRIXX as well.

    Noticed flickering when reseting back to default values, or running with powerplay enabled, though I was getting artefacting, though realised last night that what is happening is the mem speed is no longer locked after reset, and is dropping to 150/100 and I guess switching with powerplay, hence flicker everytime there is a change in mem speed. Reset machine, and everything fine i.e powerplay running fine with 300/1100 600/1100 and 830/1100. Soon as I OC then mem starts switching again.

    Any advice.
     
  2. RCoon

    RCoon Gaming Moderator Staff Member

    Joined:
    Apr 19, 2012
    Messages:
    7,473 (8.08/day)
    Thanks Received:
    3,615
    Location:
    Gypsyland, UK
    MOAR POWAH. I got my old MSI Cyclone Power Edition 6850 to 1Ghz with a minor memory clock and plenty of juice.
    After all that clocking the card may have become power hungry. Try notch it up a bit. If that doesnt work, bake it in the oven for a couple minutes, might be a solder issue (I've done this and repaired artifacting cards this way, 375 deg Fahrenheit for 5-7 mins, remove all plastic)
     
  3. Richard Shepherdson New Member

    Joined:
    Jul 12, 2006
    Messages:
    109 (0.04/day)
    Thanks Received:
    5
    The problem does not seem to be a card fault issue, its the behavior of the mem after afterburner is used to reset to default settings, its changing the mem speed, I'm pretty sure this should be locked at 1100 not changing up and down.
     
  4. RCoon

    RCoon Gaming Moderator Staff Member

    Joined:
    Apr 19, 2012
    Messages:
    7,473 (8.08/day)
    Thanks Received:
    3,615
    Location:
    Gypsyland, UK
    Browsed the interwebs quickly, recommendations are to uninstall afterburner and reinstall drivers. Then install afterburner back on, apply overclock at startup etc and start your OC again.
     
    Richard Shepherdson says thanks.
  5. HossHuge

    HossHuge

    Joined:
    Jun 26, 2008
    Messages:
    2,048 (0.88/day)
    Thanks Received:
    503
    Location:
    EDM, AB, CAN
    Which 6850?

    My Asus would only do 900mhz/core but my Sapphire Toxic would go over 1G.
     
  6. Richard Shepherdson New Member

    Joined:
    Jul 12, 2006
    Messages:
    109 (0.04/day)
    Thanks Received:
    5
    Toxic also, what voltage did you run at, never gone past 1.2 on mine.
     
  7. HossHuge

    HossHuge

    Joined:
    Jun 26, 2008
    Messages:
    2,048 (0.88/day)
    Thanks Received:
    503
    Location:
    EDM, AB, CAN
    I replaced the stock TIM and would set the fan at 60% with voltage at 1.3ish (If I remember correctly). I use a headset so I don't really care about noise too much. My temps would max at around 71 to 75ish C.

    I had the same type of problem. For some reason when I started my computer my memory would stay at the 1200 OC but my core would go back to 830. I always had to reset everything in Trixx and then apply my OC profile again.
     
  8. Richard Shepherdson New Member

    Joined:
    Jul 12, 2006
    Messages:
    109 (0.04/day)
    Thanks Received:
    5
    Well really annoying, uninstalled 12.10s driver swept, the works. removed trixx afterburner, reinstalled everything.

    Soon as I try to overclock, powerplay, I think, drops speeds to 150/150 with screen flicker as mem speed changes.

    Its got to be driver induced.

    See what 13.1s bring I guess.
     
  9. Richard Shepherdson New Member

    Joined:
    Jul 12, 2006
    Messages:
    109 (0.04/day)
    Thanks Received:
    5
    Problem solved, it is indeed driver related.

    No change for 13.1s but a drop back to the 12.8 after reading of similar problems in the 13.1 topic has cured it.

    :toast:
     

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page