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

The AMD Driver Thread

Done a google search for "Max Payne 3 crossfire" and all that came up were problems and how poor the scaling was compared to SLI.

Not holding my breath for GTA
 
Anything on my DX12 issue, Matt?

Sent you another email as i don't have any information of what the problem is other than the driver does not work too well.

Done a google search for "Max Payne 3 crossfire" and all that came up were problems and how poor the scaling was compared to SLI.

Not holding my breath for GTA

Are you sure? QuadFire works well in this game which means Crossfire and TriFire will work just as well, if not better.
 
That must be old information then, because I played it recently (February) and was saying how well it scaled at 4k across my 295x2/290x.

It looked good still as well, and GTA V uses an updated (Albeit, open world) version of the same RAGE engine.
 
@Matt - Any news on the Dying Light CF issue matey? Couple of my mates have now bought and we're fancying some action... don't fancy turning off my cards just to get it running without flickers etc...

Important Note:
The AMD CrossFire™ profile for Dying Light is currently disabled in this driver while AMD works with Techland to investigate an issue where AMD CrossFire configurations are not performing as intended. An update is expected on this issue in the near future through an updated game patch or an AMD driver posting.

No update from the release notes yet.

The game contains surfaces which are unfriendly towards Crossfire, this is why you see flickering. Unfortunately there is nothing we can do until the issue is corrected in a game patch, at this point we'll enable the profile in our drivers.
 
Probably going to be another crappy port then.

Where can i download Win10 drivers Matt? The ones i got through windows update don't want to work with DX12.

These are the ones it downloaded:
f050b768c94f47960e11123d48ea667b.png
9e7910c751ccc9c4c35832b3ba52739c.png

Is yours the ntl world email? Seems to have ended up in spam. Sent you an email.

Hi Ben,

DX12 is not yet supported on CrossFire in the API overhead test with the 15.20.1012.2 driver. It should work with CrossFire disabled or one GPU only though. :)
 
It now works, thank you Matt. I am having another issue though.

On Part 2 of the DX12 test it gets to the end then my PC completely freezes. Have to force restart my PC. Tried multiple times and it freezes in the exact same spot.
 
It now works, thank you Matt. I am having another issue though.

On Part 2 of the DX12 test it gets to the end then my PC completely freezes. Have to force restart my PC. Tried multiple times and it freezes in the exact same spot.

Glad to hear it Ben. :)

Does it occur with everything (cpu, memory and gpu's) at stock clocks? Head into the bios, F5 reset to optimised defaults, save and retest please.

Maybe disable afterburner if you have it running as well.
 
Glad to hear it Ben. :)

Does it occur with everything (cpu, memory and gpu's) at stock clocks? Head into the bios, F5 reset to optimised defaults, save and retest please.

Maybe disable afterburner if you have it running as well.

Still doing it with Trixx disabled. Everything is at stock.

CCC seems to be crashing too, this is in event viewer:

Faulting application name: CCC.exe, version: 4.5.0.0, time stamp: 0x54d3e116
Faulting module name: KERNELBASE.dll, version: 10.0.10041.0, time stamp: 0x5503b2d5
Exception code: 0xe0434352
Fault offset: 0x000000000002ecc8
Faulting process ID: 0xe64
Faulting application start time: 0x01d06af60ed15a10
Faulting application path: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report ID: 8818a030-d6e9-11e4-ab4e-40167eb28f6f
Faulting package full name:
Faulting package-relative application ID:

Does the 15.3 BETA driver work with DX12 on Windows 10? According to Microsoft that error usually signifies an incompatibility between a 32/64-bit application.

It also includes a .net error:

Application: CCC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
Stack:
at MS.Internal.TextFormatting.TextMetrics+FullTextLine.FormatLine(MS.Internal.TextFormatting.FullTextState, Int32, Int32, Int32, Int32, Int32, MS.Internal.TextFormatting.LineFlags, MS.Internal.TextFormatting.FormattedTextSymbols)
at MS.Internal.TextFormatting.TextFormatterImp.FormatLineInternal(System.Windows.Media.TextFormatting.TextSource, Int32, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)
at MS.Internal.TextFormatting.TextFormatterImp.FormatLine(System.Windows.Media.TextFormatting.TextSource, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)
at System.Windows.Controls.TextBlock.OnRender(System.Windows.Media.DrawingContext)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.Controls.Grid.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.Controls.Control.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.Controls.StackPanel.StackArrangeHelper(System.Windows.Controls.IStackMeasure, System.Windows.Controls.IStackMeasureScrollData, System.Windows.Size)
at System.Windows.Controls.StackPanel.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at MS.Internal.Helper.ArrangeElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)
at System.Windows.Controls.ContentPresenter.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.Controls.Border.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.Controls.Control.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at MS.Internal.Helper.ArrangeElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)
at System.Windows.Controls.ContentPresenter.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.Controls.StackPanel.StackArrangeHelper(System.Windows.Controls.IStackMeasure, System.Windows.Controls.IStackMeasureScrollData, System.Windows.Size)
at System.Windows.Controls.StackPanel.ArrangeOverride(System.Windows.Size)
at System.Windows.FrameworkElement.ArrangeCore(System.Windows.Rect)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.Interop.HwndSource.Process_WM_SIZE(System.Windows.UIElement, IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
at System.Windows.Interop.HwndSource.LayoutFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.ShowWindow(System.Runtime.InteropServices.HandleRef, Int32)
at MS.Win32.UnsafeNativeMethods.ShowWindow(System.Runtime.InteropServices.HandleRef, Int32)
at System.Windows.Window.ShowHelper(System.Object)
at System.Windows.Window.ShowDialog()
at ATI.ACE.CLI.Component.Dashboard.Dashboard.DerivedRun()
at ATI.ACE.CLI.Component.Client.Shared.Private.ClientUIComponent.DoRun()
at ATI.ACE.CCC.Implementation.CCC_Main.CCCNewThreadBegin(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)
 
Last edited:
Still doing it with Trixx disabled.

CCC seems to be crashing too, this is in event viewer:



Does the 15.3 BETA driver work with DX12 on Windows 10?

With your system at stock clocks?

We've not been seeing many similar reports though, and i noticed you said Sniper Elite V3 was crashing too previously upon loading up. Just wondering if something on your system could be causing the crashing of this, Sniper Elite V3 and CCC?

I'll inform our team anyway and see if we get the same problem, thanks.
 
With your system at stock clocks?

We've not been seeing many similar reports though, and i noticed you said Sniper Elite V3 was crashing too previously upon loading up. Just wondering if something on your system could be causing the crashing of this, Sniper Elite V3 and CCC?

I'll inform our team anyway and see if we get the same problem, thanks.

Yes, CPU, GPU and Memory are all at stock clocks and it's still doing it.

Does 15.3 BETA work with DX12 on Win10?
 
I doubt it.

I've relayed the info to my team and will see what they say, thanks Ben.

I might go back to 15.3 BETA as they seemed to work pretty well on Win10. I guess DX12 is currently a very early release, more likely just teething issues.

Is there any way to download the R9 200 series 15.2 driver? I know it's a long shot but it may narrow things down. Cheers for helping Matt, i do appreciate it.
 
Last edited:
No update from the release notes yet.

The game contains surfaces which are unfriendly towards Crossfire, this is why you see flickering. Unfortunately there is nothing we can do until the issue is corrected in a game patch, at this point we'll enable the profile in our drivers.

Matt have you seen my post about BF4 in the Mantle patch - i seem to be getting flickering on the oil spills around c on operation firestorm.

if you're talking to DICE about quadfire etc in BF4 already can you let them know about that? Not sure if it's been introduced in the latest patch or what, but it's only a crossfire problem.

Matt I'm having trouble with mantle in 2 card crossfire in bf4. I get texture flicker on the oil patches around the petrol tankers at c in operation firestorm and if I look at any fire fps just tanks into the 20s or less. With a single card I only get drops into the 40s albeit at lesser settings. Also when the helicopter lands with the sweary female soldier st the end of the penultimate mission in single player again fps just totally tanks. Again single card is much better. I'm running win 8.1, omegas, 16gigs samsung green, 2 x290s at stock, 3930k at 4.5(down clocked a bit to insure stability).

It is worth me upgrading to the betas, or are there things I can to in bf4 to try to sort it? I've verified and repaired game files already... Might clearing the cache help??
 
Back
Top Bottom