6 Replies Latest reply on Oct 10, 2016 3:44 AM by amdmatt

    GFX Crashes - Crossfire RX 480

    jwshields

      Hello everybody,

       

      I just upgraded my graphics cards and since the upgrade I've been getting crashes while playing Forza Horizon 3. Playing the game on ultra in 1080p.

       

      The crashes are causing a BSOD for video_tfr_failure with regards to atikmpag.sys (according to the BSOD screen)

      Generally I'll just be playing the game, and it will lock up, screen will flash black a few times when the game quits, occasionally it will bring me back to my desktop, but more often than not, I'll get an odd screen on all my monitors with white noise/lines and boxes, gray/green/red colors all over. Sometimes Windows will do a crash screen, other times it won't.

       

      Any help would be appreciated.

       

      Specs:

      CPU: I7 4790k OC to 4.4ghz

      RAM: 32GB G.Skill Ripjaw (F3-1600C9D-16GXM)

      Mobo: ASUS Z97-Pro

      GFX: 2x MSI RX 480

      Drivers: AMD Crimson 16.9.2

      OS: Win10 (Build 14393.222)

      Display Devices: 1x ASUS VG248QE (DisplayPort), 2x ASUS VE248Q (HDMI)

      PSU: Corsair RM-850i 850W

       

       

       

      Here's a number of logs from event viewer from the time around my last crash:

      I couldn't find logs or memory dumps pointing at atikmpag.sys though.

       

      Faulting application name: forza_x64_release_final.exe, version: 0.0.0.0, time stamp: 0x57d31d7c

      Faulting module name: forza_x64_release_final.exe, version: 0.0.0.0, time stamp: 0x57d31d7c

      Exception code: 0xc0000005

      Fault offset: 0x0000000001c5f01c

      Faulting process id: 0x41d4

      Faulting application start time: 0x01d21e1552fa4e0e

      Faulting application path: C:\Program Files\WindowsApps\Microsoft.OpusPG_1.0.10.2_x64__8wekyb3d8bbwe\forza_x64_release_final.exe

      Faulting module path: C:\Program Files\WindowsApps\Microsoft.OpusPG_1.0.10.2_x64__8wekyb3d8bbwe\forza_x64_release_final.exe

      Report Id: 2ff9faf2-cf3c-41aa-83e3-92558feae07e

      Faulting package full name: Microsoft.OpusPG_1.0.10.2_x64__8wekyb3d8bbwe

      Faulting package-relative application ID: OpusReleaseFinal

      Fault bucket , type 0

      Event Name: BlueScreen

      Response: Not available

      Cab Id: 0

       

       

      Problem signature:

      P1: 116

      P2: ffffda0e148c2010

      P3: fffff8029290ed90

      P4: 0

      P5: d

      P6: 10_0_14393

      P7: 0_0

      P8: 256_1

      P9:

      P10:

       

       

      Attached files:

      \\?\C:\WINDOWS\Minidump\100316-11203-01.dmp

      \\?\C:\Windows\Temp\WER-11765-0.sysdata.xml

      \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CAF.tmp.WERInternalMetadata.xml

       

       

      These files may be available here:

      C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_11b2239fa4effbb88c25da2c5856fd5d12e1269_00000000_cab_03b83cba

       

       

      Analysis symbol:

      Rechecking for solution: 0

      Report Id: 71a79d4d-098a-40eb-b854-ac9d8ba5583b

      Report Status: 96

      Hashed bucket:

      The description for Event ID 16387 from source ATIeRecord cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

       

       

      If the event originated on another computer, the display information had to be saved with the event.

       

       

      The following information was included with the event:

       

       

       

       

      the message resource is present but the message is not found in the string/message table

      Faulting application name: dwm.exe, version: 10.0.14393.0, time stamp: 0x578999ab

      Faulting module name: dwmcore.dll, version: 10.0.14393.187, time stamp: 0x57cf99aa

      Exception code: 0x887a0005

      Fault offset: 0x0000000000120696

      Faulting process id: 0x4c0

      Faulting application start time: 0x01d21db5051ef9d1

      Faulting application path: C:\WINDOWS\system32\dwm.exe

      Faulting module path: C:\WINDOWS\system32\dwmcore.dll

      Report Id: 4d8f6dc4-f0ed-42e9-8434-85d37d830860

      Faulting package full name:

      Faulting package-relative application ID:

       

       

       

      From a crash where the desktop recovered and didn't BSOD:

      Display driver amdkmdap stopped responding and has successfully recovered.

        • Re: GFX Crashes - Crossfire RX 480
          amdmatt

          Thanks for the post. Please try updating to Crimson 16.10.1.

            • Re: GFX Crashes - Crossfire RX 480
              jwshields

              Looks like that helped. I updated to 16.10.1 running the Oct 4th update of Forza; things seem to be stable and not crashing anymore.

               

              Many thanks!

              1 of 1 people found this helpful
              • Re: GFX Crashes - Crossfire RX 480
                jwshields

                So I just ran into another crash. I unmarked the answer as fixed.

                This last crash was logged as being the same (video_tfr_failure with atikmpag.sys)

                 

                Faulting application name: forza_x64_release_final.exe, version: 0.0.0.0, time stamp: 0x57e7a1f4

                Faulting module name: forza_x64_release_final.exe, version: 0.0.0.0, time stamp: 0x57e7a1f4

                Exception code: 0xc0000005

                Fault offset: 0x0000000001c61a4c

                Faulting process id: 0x4c34

                Faulting application start time: 0x01d221edb421dd75

                Faulting application path: C:\Program Files\WindowsApps\Microsoft.OpusPG_1.0.14.2_x64__8wekyb3d8bbwe\forza_x64_release_final.exe

                Faulting module path: C:\Program Files\WindowsApps\Microsoft.OpusPG_1.0.14.2_x64__8wekyb3d8bbwe\forza_x64_release_final.exe

                Report Id: 62728285-238f-412f-8a71-54f7ef3cd49f

                Faulting package full name: Microsoft.OpusPG_1.0.14.2_x64__8wekyb3d8bbwe

                Faulting package-relative application ID: OpusReleaseFinal

                Fault bucket , type 0

                Event Name: APPCRASH

                Response: Not available

                Cab Id: 0

                 

                 

                Problem signature:

                P1: dwm.exe

                P2: 10.0.14393.0

                P3: 578999ab

                P4: dwmcore.dll

                P5: 10.0.14393.187

                P6: 57cf99aa

                P7: 887a0005

                P8: 0000000000120696

                P9:

                P10:

                 

                 

                Attached files:

                 

                 

                These files may be available here:

                C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_3048ecb25ed7bf23b22e9d6aa65955c632b7e85_e69b2600_4bc4392e

                 

                 

                Analysis symbol:

                Rechecking for solution: 0

                Report Id: 6853a03a-b4d3-41a7-bb3e-2b7d7830a43c

                Report Status: 96

                Hashed bucket:

                Fault bucket , type 0

                Event Name: MoAppCrash

                Response: Not available

                Cab Id: 0

                 

                 

                Problem signature:

                P1: Microsoft.OpusPG_1.0.10.2_x64__8wekyb3d8bbwe

                P2: praid:OpusReleaseFinal

                P3: 0.0.0.0

                P4: 57d31d7c

                P5: forza_x64_release_final.exe

                P6: 0.0.0.0

                P7: 57d31d7c

                P8: c0000005

                P9: 0000000001c5f01c

                P10:

                 

                 

                Attached files:

                 

                 

                These files may be available here:

                C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.OpusPG_88a3d2d33526e97a6da4d98f6690123536a730_0f0017e9_2c538f64

                 

                 

                Analysis symbol:

                Rechecking for solution: 0

                Report Id: 2ff9faf2-cf3c-41aa-83e3-92558feae07e

                Report Status: 96

                Hashed bucket:

                Fault bucket , type 0

                Event Name: BlueScreen

                Response: Not available

                Cab Id: 0

                 

                 

                Problem signature:

                P1: 124

                P2: 0

                P3: ffffb2032a92c028

                P4: bf800000

                P5: 124

                P6: 10_0_14393

                P7: 0_0

                P8: 256_1

                P9:

                P10:

                 

                 

                Attached files:

                \\?\C:\WINDOWS\Minidump\100316-10390-01.dmp

                \\?\C:\Windows\Temp\WER-10906-0.sysdata.xml

                \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3671.tmp.WERInternalMetadata.xml

                 

                 

                These files may be available here:

                C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_61405cb939b255ab1a126a5ee5641bd7c2b32e1_00000000_cab_03983690

                 

                 

                Analysis symbol:

                Rechecking for solution: 0

                Report Id: 5084968b-6aa6-4b8e-b47c-aa6706a59cd2

                Report Status: 96

                Hashed bucket: