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

AMD "Never Settle" 12.11 Driver - benchmarks

LtMatt said:
Yeah you get the flicker because you didn't follow my guide, with my guide there is no flicker as its using AMD's powerplay tables correctly.

Let me know how you get on with trixx. :)
Click to expand...

Hi, no i did fix it with your guide but have done reformats since then and i didnt realy need my OC higher than AB goes stock, im just a bit bored today so just gonna mess with TRIXX as i heard thats good with 2d clocks as well if not im not to bothered just go back to AB at 1200/1650 which im fine with.
thanks
 
Last edited:
Scaling option is broken in CCC, won't let you move the slider. :(

Will send a report off.

BS Dave said:
Besty what's this about killing your card if you increase memory volts. Where's this come from?
Click to expand...

It comes from the fact that all it takes is one memory chip to crap out, rendering the whole lot gubbed.

He's right, it's probably the weakest link on the whole card and usually the first to break in general without even overclocking it.
 
Right 1st impression of TRIXX its good that clocks are fully open, ie core goes upto 1500 memory 2000. The bad it seems to have a lot less features than AB video cap,monitoring ect
It has a side gadget with spec but don't like it as it doesnt display in game so pointless so i ran AB for monitoing but then it uses AB clocks, well stock clocks anyway which i reset to in AB just in case there was a conflict.
But you said on here you could use AB to monitor through the G19 can you use it to monitor with out, otherwise i will have to uninstall AB to use my TRIXX clocks
Thanks
 
Last edited:
Well got AB monitering now, i uninstalled CCC,TRIXX and AB.
Then reinstalled Beta drivers without CCC, then installed TRIXX set OC then AB, the only thing i touched on AB were the monitoring tab and it seems to work using TRIXX clock and AB monitoring.
Is they a way to disable AB and just use the monitoring or disable AB so it doesn't use its clocks? i know its working now but wondered whether theres a deff answer.
Thanks
 
From extensive testing the only way i can get fps in battlefield 3 to go below 60fps now @1080p is only the most extreme explosions, or if you happened to be zoomed in looking at a large explosion.

I'm convinced large memory overclocks on the 7970 help with this. The core, not important really any more because of these drivers.
 
LtMatt said:
From extensive testing the only way i can get fps in battlefield 3 to go below 60fps now @1080p is only the most extreme explosions, or if you happened to be zoomed in looking at a large explosion.

I'm convinced large memory overclocks on the 7970 help with this. The core, not important really any more because of these drivers.
Click to expand...

Nice so whats you 24/7 clock now and voltage? what card do you have as well?
Thanks
 
borley said:
Nice so whats you 24/7 clock now and voltage? what card do you have as well?
Thanks
Click to expand...

Well since these drivers its changed, unless im benching ill run 1156/1823 @ 1.137 (stock 1.112)

That provides 350gb of memory bandwidth, which bf3 seems to love as does sleeping dogs.

But i can run the memory up to 1875 and higher which provides 360gb of bandwidth, pretty sure this is close to my limit now.

I see no reason to overclock the core much these days, but that can go up to 1225 core, (1.206) volts maximum. (1219 core {1.2 volts) is more likely for temps/voltage but i just dont need to run it anywhere near that high any more)
 
Last edited:
Well. I'm off to 12.10 WHQL.

Not a clue why, but some of the same bugs from the 'leaked' beta are now starting to show through to me in beta3, especially the one crippling my system and killing the driver as soon as it raises to 3d clock speeds.
 
pgi947 said:
Well. I'm off to 12.10 WHQL.

Not a clue why, but some of the same bugs from the 'leaked' beta are now starting to show through to me in beta3, especially the one crippling my system and killing the driver as soon as it raises to 3d clock speeds.
Click to expand...

Why aren't you using beta 4 Mr PG tips? :confused:
 
Thought that was only for some crossfire fixes??

I MAY have just found the issue, I had previously clocked for a 3dmark run, afterwards re-setting voltage and clocks via AB. Now I ALWAYS have AMD overdrive disabled, but out of interest I opened it to see what was happening before I removed the driver.

The clocks set in CCC were 1340/1900, trying to run at 1.175v!! may explain the crashes, just re-set and trying 3d clocks again...
Edit: Yep that seems to have fixed it. strange bug, means I'll have to keep an eye on overdrive as well as afterburner.
 
pgi947 said:
Thought that was only for some crossfire fixes??

I MAY have just found the issue, I had previously clocked for a 3dmark run, afterwards re-setting voltage and clocks via AB. Now I ALWAYS have AMD overdrive disabled, but out of interest I opened it to see what was happening before I removed the driver.

The clocks set in CCC were 1340/1900, trying to run at 1.175v!! may explain the crashes, just re-set and trying 3d clocks again...
Edit: Yep that seems to have fixed it. strange bug, means I'll have to keep an eye on overdrive as well as afterburner.
Click to expand...

That's what they say pg, but have you ever stopped and listened to what they say on a consistent basis? They being, i dont know who. :confused:
 
Anyone getting GPU spikes with Afterburner? I normally use GPU-z but just switched to AB and just sitting on desktop my GPU usage is spiking bad.
This a AB issue or driver? Gpu-z didn't show this.

56550741.jpg
 
You must log in or register to reply here.
Back
Top Bottom