CG miner AND msi can nolonger drop my memclocks (low enough)

[Fiyasko]

So for months i was running 1000core and 400mem, Getting a happy 320mh/s per 6870, I have two, And they are in a gaming rig.
After a clusterfuck of driver changing.
MSI 2.1 gave 0's when "readingout" my gpu stats,
So i upgraded to 2.2, And i got proper readings.
With the mimimum memclock being 575<-normal
So, As usual i enabled the unofficial overclocking... I dragged the slider to 400, Hit OK, It said "OK" but the mem clock Always goes to 575, Regardless of what i select.
So i went "great, MSI 2.2, And Cat 12.3= no 400mhz memclock"
I decided to use CGminer to control the clocks, But to no avail...
I got the standard "GPU something reports OK for clock change, Check clocks to make sure"
So i check the clocks, And 1000core, 575mem....

Im wondering why i cannot bring my 6870's memory clock down anymore... before the driver cluster fuck i was using msi 2.1, cat 12.3

[drakahn]

I've run into this, i just deleted them from device manager and let it reinstall the drivers on restart

i use sapphire trixx instead of msi afterburner, but i imagine its the same thing

[Fiyasko]

I've run into this, i just deleted them from device manager and let it reinstall the drivers on restart

i use sapphire trixx instead of msi afterburner, but i imagine its the same thing

Hmm, I tried what you said, No luck

[Fiyasko]

BUMP!

[bitlane]

Go to the Afterburner folder in Program Files...then into the Profiles folder. Delete everything.

[billington.mark]

I had a weird memclock\gpuclock issue a while ago and it ended up being high temps... worth checking.

[Fiyasko]

Go to the Afterburner folder in Program Files...then into the Profiles folder. Delete everything.

This just seems like it would cause me to have a clean install of msia
W/e, Shouldnt hurt

I had a weird memclock\gpuclock issue a while ago and it ended up being high temps... worth checking.

Naw, It's nothing like that, Ever since the new amd drivers and msia, I've lost the ability to go lower

[-ck]

Various catalyst versions introduce different buggy underclocking issues. I believe 12.3 was one of them. Roll back or forwards on catalyst.

[sadpandatech]

Various catalyst versions introduce different buggy underclocking issues. I believe 12.3 was one of them. Roll back or forwards on catalyst.

this. I had the same issue when I allowed windows 7 to auto download and install drivers when it finds new hardware. Even though cat 11.8 and sdk 2.4 were already installed, when I switched one of the cards, win7 downloaded a later version of the dirvers and I had the same issue as OP.

reverting back to the previous driver/sdk combo fixed it.

[Fiyasko]

Various catalyst versions introduce different buggy underclocking issues. I believe 12.3 was one of them. Roll back or forwards on catalyst.

FACT!
And Gosh it annoys me, I really liked having low memclocks on my gaming rig when i wanted to mine with it.

Various catalyst versions introduce different buggy underclocking issues. I believe 12.3 was one of them. Roll back or forwards on catalyst.

this. I had the same issue when I allowed windows 7 to auto download and install drivers when it finds new hardware. Even though cat 11.8 and sdk 2.4 were already installed, when I switched one of the cards, win7 downloaded a later version of the dirvers and I had the same issue as OP.

reverting back to the previous driver/sdk combo fixed it.

Naw, I would never have windows on auto update.

[Fiyasko]

So for months i was running 1000core and 400mem, Getting a happy 320mh/s per 6870, I have two, And they are in a gaming rig.
After a clusterfuck of driver changing.
MSI 2.1 gave 0's when "readingout" my gpu stats,
So i upgraded to 2.2, And i got proper readings.
With the mimimum memclock being 575<-normal
So, As usual i enabled the unofficial overclocking... I dragged the slider to 400, Hit OK, It said "OK" but the mem clock Always goes to 575, Regardless of what i select.
So i went "great, MSI 2.2, And Cat 12.3= no 400mhz memclock"
I decided to use CGminer to control the clocks, But to no avail...
I got the standard "GPU something reports OK for clock change, Check clocks to make sure"
So i check the clocks, And 1000core, 575mem....

Im wondering why i cannot bring my 6870's memory clock down anymore... before the driver cluster fuck i was using msi 2.1, cat 12.3

I Have figured out the error!
Turns out one of the cores on the 6990 was defective, And was crashing and Halting, But not inturrupting much of anything other than readouts and anything that attempted to use the "crashed" core would cause a bsod, (I had not installed anyform of auto restart)

Why was CGminer failing on my desktop?
Well that one was high OC+heat related and is totally solved with a can of air now. For whatever reason CGminer's interface likes to lockup when instead it should flag a HW error.

Why the hell was GUIminer working on the "crashing" 6990 and CGminer was not?
I cant really answer that since i dont know... But perhaps gui miners poclbm has someform of crash reduction, Or like a "less harsh" mining style, Or a auto restart, Etc.