No problems here with any of amd drivers tbh since I got this msi gaming 290 (less said about the 2 stock 290x's I owned the better :s) But you are right both company's have issues. I had months of bad drivers for bf3 when I had my 680 disco textures and broken msaa for 3 months plus :/

Not updating drivers untill they make major performance enhancements or fix the heat "thing" that was introduced in 14.6. Still no word as to WHY every single card runs 5-10c hotter with 14.6 compared to drivers earlier than 14.4

5-10c HOTTER!?? WTF? Not noticed that at all with any 14.x drivers. All clean installed using DDU and not a single issue with any of them. I maybe noticed around a 1-3c increase in temps over the past couple weeks mainly due to the hot weather.

No problems here with any of amd drivers tbh since I got this msi gaming 290 (less said about the 2 stock 290x's I owned the better :s) But you are right both company's have issues. I had months of bad drivers for bf3 when I had my 680 disco textures and broken msaa for 3 months plus :/

A much as people moan and complain each side has issues. I remember for 5 straight months of drivers on my old 4870x2 it had the 2D clock bug where in any 3D game the 2nd GPU would stay at 2D clocks and not work at all. Not even disabling ULPS helped. I had to use TwL's drivers which improved performance in crossfire MASSIVELY compared to AMD's drivers and crossfire actually worked!

Yeah, They don't even change number...It's still says its 14.6 RC in CCC for me.

Same here... I checked the file versions, it's all OK, but, CCC says 14.6.

Same here... I checked the file versions, it's all OK, but, CCC says 14.6.

Yep same here, I think this is just going to become a WHQL driver soon. Basically with all the 14.x improvements so far just with WHQL stamp and a few new crossfire profiles.

My temps only went up a couple of degrees when i used the 14.6s, but noticed frames were up as well, so put it down to the GPU being utilised more.

For me too.. Say 14.6 RC in CCC and GPU-Z. :3eyes: Thank you asder00

Jesus #$@&*( ............. Not this bug again. I have enough trouble tracking AMD driver/component versions as it is.

I was testing if these fixed the black screens or BSODs with my card and... NO... Back to the fixed 2D clocks "fix" again...

intel graphics? :d

nevarrrr!!! Lol

youtube is running smoothly again and no display driver crashes.

Did they fix BSODs with this version? Those were from HW acceleration, I think or whenever I tried to play BF3 or CIV5 with my browser open. Launch the game and get a BSOD -> reboot and launch the game again -> game starts fine. Started from 14.6, I've seen some similar posts about this issue so I had to roll back to 14.4

I got blue screens in Planetside 2 as well. I guess I'm forced to stick with 13.12...

Thanks

Yeah, They don't even change number...It's still says its 14.6 RC in CCC for me.

1st uninstall the 14.6 reboot then install the 14.7 and it will show 14.7

Is freezing/hangs in Dragon Age: Origins fixed yet? How about other DX9 games?

Stutter on AMD GPU today equals: - unstable (throttling) CPU overclock - graduating turbo OC per number of threads used like 45/42/39/37 (1/2/3/4 threads used) instead of (44/44/44/44) - unstable (throttling) GPU overclock - bad case airflow again causing thermal throttling - unrealistic user pumping details to Ultra+++ while having mainstream HW - slow HDD (not even cheapest ssd for system + cheap raid 0 for data/games + no defrag) - 60Hz screen + standard V-Sync while playing at 60fps edge going from 60 to 30fps displayed and back - not using RadeonPRO or not using it properly (if things above are handled properly RadeonPRO is not even remotely needed for DVC/DFC) Other than that it is kind of weird that there are so few improvements/fixes in last month released. My guess is that driver team is working on release of new HW as they have to do this next launch right as they had bad launch with HD7970 (low performance) & R9-290x (black screens) killing their initial sales to certain degree.

Regarding "graduating turbo OC per number of threads used like 45/42/39/37 (1/2/3/4 threads used) instead of (44/44/44/44)" -- I'm assuming you suggest disabling turbo altogether to prevent this (I've personally had turbo disabled forever)? I didn't know that turbo dynamically adapts according to # of threads being run. And regarding the RadeonPro suggestion -- how do you use RadeonPro "properly"? I've used it for years, but I'm curious if perhaps there are things that I should/shouldn't be doing for better performance.

i guess this is it AMD, bye2 for good. i had better luck when with Nvidia drivers rather than AMD drivers, 3870 = poor performance, even my old 9600GT beat that thing into oblivion. the 7850 that i currently had is quite good, but the issue is the driver, but too bad i'm gonna have to wait a while, since it seems Nvidia is about to release a new series. which meant good things, because old series probably gonna have some reduced price, probably gonna pick up 750ti or 760. next PC back to Intel + Nvidia again. i wanted new driver to fix openGL, because openGL Games(brink, wolfenstein, Doom 3) on AMD sucks badly.

Uninstalled 14.6 Rebooted Booted in to Safe mode, used DDU and uninstalled leftovers Rebooted Booted in to system Installed 14.7 RC Rebooted Says 14.6 RC :3eyes:

Same situation here...:3eyes:

Yes, CPUs have basic turbo frequency not based on TDP or temperature (smart way), but number of cores where currently runs some workload even very small (stupid way). And then there is thermal throttling to protect CPU from damage if temperature is too high.

Thanks. So is disabling turbo in BIOS sufficient? I've had both turbo + speedstep disabled for some time, however, HWinfo's continued to show the core clocks bouncing around, cutting in half when there's no load, then bouncing up to 4200 when there is. I've wondered if maybe this is a "side effect" of hyper-threading (which I have enabled), where it's basically splitting a physical core in half for its virtual core. And how about C-states? What do you use, as far as turbo/Speedstep/Hyperthreading/C-states/core-parking? Currently, I use: Turbo: disabled Speedstep: disabled Hyper-threading: enabled Virtualization: enabled C-states: C1E Core-parking: disabled I'm overclocked at 4.25GHz on an i7 930. Would you propose changing any of the above? I've wondered if it's useful to have C-states enabled or not, if there's very much power savings, and if it may cause stuttering.

RadeonPRO will not give you higher performance in most of cases. But can prevent stutter. Since you have profiles per game you can set each in way it works best: Like if you have only 60Hz screen it is reasonable to try to avoid v-sync if your fps goes under 60. But then to partially limit tearing and have nicer "frame pacing" you can limit fps to 60/59fps with DFC (this is my preferred method on 120Hz). Then if you use Triple Buffering in RP it is different than usual TB in most of games (It's the way it should be). And if you happen to use v-sync DVC (dynamic) is reasonable as nVidias Adaptive VSync.

So do you recommend using DFC for every game, always, setting it to the monitor's refresh rate? (I use a 60Hz plasma HDTV) Do you recommend also using DVC with DFC? Or would it be better to enable DFC but then set vsync manually? I've heard some suggest setting vsync for -1 frame below the refresh rate (so 59Hz instead of 60). Why is that? Should this always be done? I always use RP's triple buffering for every game. Do you suggest using it always, or are there times when it would be better not to? What about game-native functions vs. RadeonPro vs. CCC -- would one work better than another? For example, if a game has its own "triple buffering" + "V-sync" settings, would it be better to use the game's instead of RP's? Or would you suggest always using RP's? What about RP vs. CCC?

My universal approach which is stutter free is: - CPU runs with all 4 cores @4.5 as long as there is any even small load which prevents random loss of performance for main (or any other) game thread. - I lower game details to have fps over 100 at all times where possible 120fps+ - then I use DFC to limit 120fps in most cases. In few where it causes heavy tearing I go to 119fps (on 120Hz screen)

Thanks. So do you only use DFC, but no vsync? I thought that limiting the frame rate but not using vsync would still cause tearing, because the monitor's refresh isn't in-sync with the frame buffer. Is it possible to only use DFC with no vsync and not get any tearing?

- not doing heavy OC on graphics VRAM even at 1500MHz it eats like 60+W -> in short AMD method to TDP limit is: VRAM runs on frequency you set and eat what it eats, if something has to throttle it is GPU, because VRAM is not capable to save power. And that is one of problems which r9-290x has (additional memory chips eating power which GPU needs).

Is there much benefit to OC'ing VRAM? I've modded my reference 7950 BIOS with improved memory timings + a force 1675MHz memory clock across all states always -- because I hate the flickering whenever the memory clock changes! And I've modded my 3D state to 1140/1675MHz. But if there isn't much benefit between VRAM 1500MHz vs 1675MHz, maybe I should just use 1500? What do you think?

Weird enough, I never had major problems with AMD drivers and if I had some trouble with the drivers, it never was enough to turn my back to the card and run to nvidia. My brother had a nvidia card and he has as many issues as I'm having with drivers. It seems like most people think that Nvidia have wonderdrivers never producing any problems, but my experience tell that both have problems fixing bugs... Also, when there's a bug or something, it's never something you really need to worry about. You're kind of a luxury baby when some little bugs may turn you to buy a new GPU.

i never said Nvidia drivers doesn't have issues, i said i had more luck with Nvidia drivers rather than AMD drivers, no need to insult people, when i decided that i had enough with AMD drivers. besides buying an old series, when new series came, because it gonna have a price cut = luxury baby ? good luck with your AMD card, that after 14.4 can't play DX9 games anymore. besides what's wrong with me changing side because i want to be able to play my newly bought Wolfenstein TNO ? since it ran badly on my 7850.

...

According to RadeonPro settings. I'm preferring Flip Queue Size value set to "1" also.