The AMD Driver Thread

humbug · 9 Jun 2015 at 16:11

BS Dave said:
17.5% clock increase in CPU limited game = 15% frame increase shocker!!

I think the overhead gains are currently only on the win10 branch - though I will be playing around tonight with gta v

Something is different

its not the only thing i have noticed a difference in, PS2 always seems to be permanently pegged on the V-sync these days and i don't think that was ever true for me.

pete910 · 9 Jun 2015 at 16:24

LoadsaMoney said:
Look at the state of that brick wall on the bottom shot, compared to the top.

Don't notice any difference on the shots here tbh. png issue?

thebennyboy · 9 Jun 2015 at 17:11

Anyone know what could cause this? It does it randomly, but only when 2 displays are connected.

fs123 · 9 Jun 2015 at 17:15

thebennyboy said:
Anyone know what could cause this? It does it randomly, but only when 2 displays are connected.

Usually gpu memory when overclocked too much. Are you overclocking or at stock? Try lowering memory clock.

shankly1985 · 9 Jun 2015 at 17:16

McShave said:
Anyone here used the Windows 10 Engineering sample drivers lately? I've been avoiding them like the plague. Today I've had four blue screens browsing Chrome (Driver stuck in thread).

Just to check if it was the Intel driver I went to disable that and realised some how the Win 10 drivers sneaked on today without me noticing. Last time I used DDU I ticked the option to not install new drivers. I wasn't allowing 10 to update. Bit confused today how they were installed.

Guess it's time to uninstall then reinstall the 15.5s again!....this is getting stupid now.

Might not be your issue but before new year ocuk replaced my gpu for same issue..
thread stuck in device driver 0x10000ea

thebennyboy · 9 Jun 2015 at 17:19

fs123 said:
Usually gpu memory when overclocked too much. Are you overclocking or at stock? Try lowering memory clock.

It is at it's stock memory clock of 1550Mhz.

Combat squirrel · 9 Jun 2015 at 17:31

AMDMatt said:
Going to send you a trust message, stand by.

Thanks sir, much obliged

LoadsaMoney · 9 Jun 2015 at 17:44

pete910 said:
Don't notice any difference on the shots here tbh. png issue?

Yeah strange, it looks alright now, before, the bottom shot, textures were all blury, not as sharp compared to the top shot, like the top shot was on high, and the bottom was on low.

pete910 · 9 Jun 2015 at 20:14

LoadsaMoney said:
Yeah strange, it looks alright now, before, the bottom shot, textures were all blury, not as sharp compared to the top shot, like the top shot was on high, and the bottom was on low.

I have a confession, I re uploaded to make sure it want a corruption issue

McShave · 10 Jun 2015 at 10:19

shankly1985 said:
Might not be your issue but before new year ocuk replaced my gpu for same issue..
thread stuck in device driver 0x10000ea

thebennyboy said:
Anyone know what could cause this? It does it randomly, but only when 2 displays are connected.

Interesting. A few days before I started getting the driver thread bluescreen I began to get that graphics corruption exactly the same as thebennyboys. After rebooting the main screen had some serious flicker on the desktop. No setting or reboot would make it go away. (this was with no sort of over clock). The only thing that made it go away was to up the GPU clock, mem clock and voltage using CCC (don't know which one made the difference). The flicker instantly went away.

After lowering the settings again everything was fine till these bluescreens.

Devrij · 10 Jun 2015 at 12:35

I used to get that with dual displays because the driver was dropping the clocks too low to drive both displays (single display clocks). If you forced higher clocks for your 2d profile it would fix it.

McShave · 10 Jun 2015 at 13:05

Devrij said:
I used to get that with dual displays because the driver was dropping the clocks too low to drive both displays (single display clocks). If you forced higher clocks for your 2d profile it would fix it.

Thanks I'll have to look that up later on, damn work.

Type_R · 10 Jun 2015 at 14:54

Dygaza said:
Modded - W7

http://forums.guru3d.com/showthread.php?t=399691 - that version.
If people really wanna try modded driver, don't blame AMD if they cause problems.

Just tried this in Win 7 x64.

Absolutely awesome! Installed it as per instructions, although in Win7 you need to disable driver signature using other methods (I just googled it!).
Whilst installing it seemed like the driver has 'stopped responding' so just be patient and eventually it installed fine.

Fired up pcars...able to turn SMAA to Ultra and anti-aliasing up one notch from 2X to 4X with no drop in fps reported by fraps

Now why can't AMD just release drivers like this instead of messing us all about!

mmj_uk · 10 Jun 2015 at 15:18

Flanos said:
AMDMatt do you have any indicator or a really rough idea of where progress is with CrossFireX enabled FreeSync ?

It's starting to look like there is a hardware flaw preventing it from working properly and they're delaying until the new cards tbh.

StrongSad · 10 Jun 2015 at 16:16

Hello AMD Bods!

Thought you GTA V peeps might be interested in this from the release notes from R*

Fixed an issue where certain combinations of anti-aliasing settings on CrossFire systems could cause graphical corruption

Happy Wednesday!

LtMatt · 10 Jun 2015 at 16:17

Strudders said:
Hello AMD Bods!

Thought you GTA V peeps might be interested in this from the release nots from R*

Fixed an issue where certain combinations of anti-aliasing settings on CrossFire systems could cause graphical corruption

Happy Wednesday!

Good news, no need for a Catalyst Driver update folks.

As for Flickering seen in The Witcher 3 with MSAA enabled, no further update. It will be fixed in a future game update or an updated Catalyst Driver.

flopper · 10 Jun 2015 at 16:33

AMDMatt said:
Good news, no need for a Catalyst Driver update folks.

As for Flickering seen in The Witcher 3 with MSAA enabled, no further update. It will be fixed in a future game update or an updated Catalyst Driver.

Nice, busy before the 16?

Dygaza · 10 Jun 2015 at 17:07

Type_R said:
Just tried this in Win 7 x64.

Absolutely awesome! Installed it as per instructions, although in Win7 you need to disable driver signature using other methods (I just googled it!).
Whilst installing it seemed like the driver has 'stopped responding' so just be patient and eventually it installed fine.

Fired up pcars...able to turn SMAA to Ultra and anti-aliasing up one notch from 2X to 4X with no drop in fps reported by fraps

Now why can't AMD just release drivers like this instead of messing us all about!

I'm sure they release them soon when they feel they're stable enough. Remember there have been people who are using 15.5 drivers even under win 10. That tells that there is some instability there, which is holding them from releasing them.

But yeah, difference is quite huge compared to 15.5 drivers.

BS Dave · 10 Jun 2015 at 18:58

mmj_uk said:
It's starting to look like there is a hardware flaw preventing it from working properly and they're delaying until the new cards tbh.

Same one that's stopping dsr, g-sync and sli maybe?

Matson · 10 Jun 2015 at 21:25

AMDMatt said:
Good news, no need for a Catalyst Driver update folks.

As for Flickering seen in The Witcher 3 with MSAA enabled, no further update. It will be fixed in a future game update or an updated Catalyst Driver.

When most of us will have probably completed the game and not care anymore