11 Replies Latest reply on Aug 4, 2016 5:20 AM by fxv300

    Radeon R9 380 no signal black screen crash

    getlogan

      When playing the System Shock demo for a few minutes the monitor will lose signal and display a black screen. A stuttering sound can be heard in the background on loop and the only way to recover from this crash is a hard reset of the computer. Upon restarting the computer and checking event viewer a log of the crash can be seen.

       

      EventID: 4101

      Source: Display

      Display driver amdkmdap stopped responding and has successfully recovered.

       

      I used to get the black screen crash on many other directx11 games (never had it on directx9 games), such as GTA5, Rainbow Six Siege, Satellite Reign, Unreal Tournament (the new one). However ever since a new driver released around April, at least for me, crashes in those games seem to be fixed as I have never encountered them again. System Shock is currently the only game I know of that still suffers from the same problem. I also get the same black screen issue with the Dolphin 5.0 emulator running with DX12 renderer and when playing movies in Media Player Classic using the MadVR renderer. Also graphics settings, resolution, windowed or fullscreen, refresh rate, FreeSync, tesselation, monitor, cable and port type, etc, does not matter as different combinations do not resolve the issue. Problem is a driver issue as it has been fixed in the past for other games.

       

      My specs:

      Core i7 6700k (stock, never been overclocked)

      Kingston HyperX Fury 16GB DDR4 (2x8GB)

      Asus Maximus VIII Hero (BIOS 1701, current latest)

      Seasonic XP-860 Platinum 860W Power Supply V2

      Sapphire Radeon R9 380 Nitro Dual-X 4GB (stock, never been overclocked)

      using Crimson 16.7.2 WHQL (shows as 16.7.3 in Radeon Settings Overview, installed after using DDU 16.1.0.1 in safe mode, Gaming Evolved NOT installed)

      Windows 10 Home 64-bit

       

      Monitor (single monitor tested individually, crashes occur on either):

      Benq XL2730Z using DisplayPort (2560x1440, 144hz, FreeSync)

      Benq V2400W using DVI (1920x1200, 60hz, non-FreeSync)

        • Re: Radeon R9 380 no signal black screen crash
          fogiatto

          Forget about this card, AMD is doing nothing to solve this...

          Instead of fix the problem, they are making us use a old driver, 15.11.

           

          try a DDU uninstall, then download and install the 15.11 driver.

          • Re: Radeon R9 380 no signal black screen crash
            getlogan

            Crimson driver 16.7.3 is an improvement for me.

             

            The System Shock demo still crashes. However, instead of getting the usual no signal black screen crash, now the game just crashes and I can continue using Windows without a hard reset.

             

            Same thing for Media Player Classic with madVR renderer. I still get a crash, but now I am able to alt-f4 to close the crashed Media Player Classic and continue using windows without a hard reset.

             

            Dolphin 5.0 emulator now seems to work without crashing using the DX12 renderer.

             

            Not sure if the crashes are a problem with the applications or display drivers, but I'm glad now the crashes don't stall the entire system.

            • Re: Radeon R9 380 no signal black screen crash
              fxv300

              This issue is seen with the RX480.

               

              Since the installation of Crimson WHL 16.7.3 I have started getting Total Black Screen also Total White Screen.

              Anyone else having the same issue?

               

              Does IE and HW acceleration have any adverse impact to this issue?

               

              Vid of my RX480

              • Re: Radeon R9 380 no signal black screen crash
                cnrom

                Mine is R9 380X 4G.

                Same, black screen on every Crimson drivers except the legacy version - 15.11 Crimson.

                AMD DO NOTHING ON SOLVING 380 SERIES PROBLEMS, THEY BUILT A PROBLEMATIC CARD AND NOW THEY GOT THE MONEY BUT DONT GIVE A SH*T TO THE USERS.

                Next time go green.

                  • Re: Radeon R9 380 no signal black screen crash
                    getlogan

                    Yeah this R9 380 ordeal has me disillusioned with AMD. For me at least, it looks like the no signal black screen crashes have all been finally fixed. Although, I thought the same thing back in April and then recently found more games and applications that still get the no signal black screen crash. So there may be many other games that still suffer from this crash that I haven't played yet.

                     

                    I don't like how long it has taken AMD to identify this issue. Do they not have enough beta testers or something? I suppose the customers could do it. Good ol' crowdsourcing.

                    I don't like how long it has taken AMD to fix this issue. It seems this black screen crash is a symptom of multiple issues and they are playing whack-a-mole, fixing some without noticing others.

                    I don't like how AMD has not acknowledged this issue in the driver release notes "known issues" section. It just makes the whole thing feel shady.

                     

                    I bought the R9 380 as an upgrade from a HD 5870. It was supposed to be a stepping stone until a high end Polaris card, but high end won't happen until Vega. Even though my troubles with the card seem to be getting resolved, the fact that I still see others (like yourself) reporting the same issue has me doubting this thing has been truly resolved. I want to be able to recommend AMD as a brand to friends and family, but after all this how can I honestly justify that as the right choice?

                     

                    I just ordered a GTX 1070. I will be keeping the R9 380 since I don't want to pass any potential misery onto anyone else. It will be a memento, to haunt me in case I forget.

                    2 of 3 people found this helpful