• 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

These drivers have stopped my upgrade itch.

I was going to upgrade my i7 920 as I thought it was bottlenecking my 7970s :D

I'm going to put the money towards a new car instead.
 
chief barker said:
These drivers have stopped my upgrade itch.

I was going to upgrade my i7 920 as I thought it was bottlenecking my 7970s :D

I'm going to put the money towards a new car instead.
Click to expand...

I know someone who has 7970 xfire, since the release of these drivers hes put one up for sale as he no longer needs the other one due to the performance increase. :eek:
 
ACEOWNER said:
Anyone think there might still be more to come from driver optimizations?
Click to expand...

You ain't nothing yet with GCN in my opinion, I still think there still even more performance waiting to be unleashed, wouldn't be surprised to see 384bit or even 512bit memory interface with the next AMD graphic cards.

Just look at AMD’s FirePro W-series cards which use GCN, gives you some idea of what can be achieved, just takes time for it to mature & for the 78xx, 79xx cards to hit their full potential.
 
Last edited:
Solution if you use AB to overclock...

Enable AMD overdrive and manually drag the the memory clock to its lowest setting and apply

Memory now downlclocks automatically when in 2d mode, and ramps up automatically in 3d apps.
 
Heads up, atiumdva.dll was deleted by my av, could be handy to exclude it or check in case you missed it getting quarantined.



I still think there is more power waiting to be unleashed, hopefully the longer it takes the 8's to release, the more Amd will get out of it...

...although they should try and get rid of the 'humbug' vertical stripe screen of doom.

It's not constant, it can go a week or so 24/7, totally fine, then 3 or 4 times in an hour, when my boys playing Minecraft(kids crack cocaine:eek:, be warned if your kid asks for it anyone) and watching youtube Minecraft vids.

Come to think of it, it hasn't done it on the GHz bios, yet anyway.

@Matt,

NP, pity it didn't work, but I didn't install the driver until I flicked to the GHz bios-whether that makes a difference, at least you got something sorted.

Must be a software conflict somewhere as the cards are identical and there's not much difference between our systems.

@JD,

go for it, and the Asus monitor looks the part, reading that review, it looks like the Nvidia used the same format as Samsung with lightboost, so I guess I'm getting similar results as lightboost, which must explain the good 3D.

@Marine,

I'l start a thread when I get some free time, been so busy the last week or so, not had much time to do anything recently.:(
 
Last edited:
Nightglow said:
Totally forgot that:o, but they needed to move to 384bit from 256bit, as it held the previous generation cards back I feel.
But, I still think AMD might go with a 512bit memory interface.
Click to expand...

Long way to go before they are bandwidth limited on 384bit.
next gen will be 384bit also as speed memory gets faster and faster.

cost vs performance is also a big factor.
 
dave_beast said:
Solution if you use AB to overclock...

Enable AMD overdrive and manually drag the the memory clock to its lowest setting and apply

Memory now downlclocks automatically when in 2d mode, and ramps up automatically in 3d apps.
Click to expand...

Doesn't work for me, as soon as you apply an overclock if goes back to 500/1375 in ccc/afterburner. Using that preset method each time is the only working method ive found yet.
 
flopper said:
Long way to go before they are bandwidth limited on 384bit.
next gen will be 384bit also as speed memory gets faster and faster.

cost vs performance is also a big factor.
Click to expand...

Totally agree with this. The cost of 512-bit PCB's may be much more expensive than 384-bit PCB's. We will probably see 384-bit and 3GB ram for the top end of the next generation. Nvidia may also move to this configuration, which would be significant looking at the currently bandwidth constrained Keplers.

Also a jump to 512-bit would almost certainly mean a minimum of 4GB onboard, which is unnecessary and a needless expense for most users.
 
LtMatt said:
Doesn't work for me, as soon as you apply an overclock if goes back to 500/1375 in ccc/afterburner. Using that preset method each time is the only working method ive found yet.
Click to expand...

Disable afterburner then, set clocks in CCC to your desired core 1100mhz etc and memory to 150mhz. When Windows boots before CCC loads clocks show as 500/1500, but when it loads clocks return to 300/150.
 
dave_beast said:
Disable afterburner then, set clocks in CCC to your desired core 1100mhz etc and memory to 150mhz. When Windows boots before CCC loads clocks show as 500/1500, but when it loads clocks return to 300/150.
Click to expand...

I use afterburner for more vcore and clock overclocks though so thats not really an option. I think ill just stick to applying the preset as and when i need to by pressing Alt+F5.
 
From AMD rep

"We are pushing out a new beta, beta 4, some time today. It will be packaged under the same executable as driver revision 9.01.08, probably around 2 PM EST. This beta is primarily designed to fix a crash in MOH:WF on CrossFire configs.

It will not include the Tahiti idle clock fix, as we are still investigating the cause."
 
LtMatt said:
From AMD rep

"We are pushing out a new beta, beta 4, some time today. It will be packaged under the same executable as driver revision 9.01.08, probably around 2 PM EST. This beta is primarily designed to fix a crash in MOH:WF on CrossFire configs.

It will not include the Tahiti idle clock fix, as we are still investigating the cause."
Click to expand...

Pointless driver update is pointless :p
 
dave_beast said:
Pointless driver update is pointless :p
Click to expand...

Yeah i really want this fixed as well dave but the solution i have will do for now.

I just posted this elsewhere but ill post it here as well.

I've figured out what causes the (idle clock bug) problem. Its the memory.

Once windows loads start up ccc go to overdrive and set the memory clock down at 150.

Now the 2d clock is working, correct voltage core and memory clocks set.

Now in ccc put the memory clock at 1205, suddenly the card gets stuck in a different mode where the voltage increases to 0.9 the core gets bumped to 500 and the memory stays at 1375.

The card voltage and core clock will never clock down unless you manually set the memory down below 1205. The memory will stay clocked up though unless you put it back down to 150.
 
You must log in or register to reply here.
Back
Top Bottom