5 Replies Latest reply on Aug 23, 2016 4:17 AM by amdmatt

    Blue screen out of nowhere.

    casinan

      Hello. After trying everything I know about solving the issue, things went bad, so I decided to come here. The machine in cause is a Dell Inspiron 3537 laptop, which I own for about two years. I had problems with the AMD video card since I bought it, but I managed to solve them (which may be the issue at hand right now). Without any warning, one morning I received a blue screen, with the codes clearly pointing out a display driver issue. But I didn't know that at the time, so I went and checked the memory, hard drive and CPU, all working fine. Then it hit me that, of course, the dedicated video card was the issue. After countless driver installations, and so on, I can barely use the laptop because only the Intel integrated card works. I can't use Aero, editing software (which is basically my only income until I get out of college) doesn't run so well, and features are missing, and basically I can't even think about games. The funny thing is, I don't even know what the video card is, it constantly switches between an HD 8850M, R9 200X (which makes NO sense) and an HD 8870M. When it was time to clean up the laptop, which I do every month or so, I removed the battery, and, when I started it once again, the Aero theme worked and I had access to the Catalyst. It lasted about 30 seconds, when I got a pop up in the bottom right corner (Windows 7). Unable to read the whole thing, I vaguely remember something about the word "snap-in", which I didn't find a lot of stuff about. I am not able to recreate the situation, even by removing the battery like I did. I tried literally everything from system restores, to old drivers, to the latest drivers, using DDU to clean everything up, drivers from the official Dell website, and I am still at a loss. I kindly ask for some advice.

        • Re: Blue screen out of nowhere.
          amdmatt

          Regardless of what name the GPU has, its performance will not change so you can disregard that.

           

          What you have described could be caused by software or hardware. Initially i would recommend a system clean up and a fresh installation of our latest driver. If this does not resolve the issue, then you might need to try a clean installation of Windows. I will list some troubleshooting steps which will hopefully prevent the need for this.

           

          Run the Windows Deployment Image Servicing and Management (DISM) and System File Check (SFC) tools as Administrator. The DISM and SFC tools scan the integrity of the Windows image and all protected system files replaces corrupted, damaged and incorrect versions with correct Microsoft versions.

           

          To run the DISM command do the following:

          • Use the Windows key + X keyboard shortcut to open the Power User menu and select Command Prompt (Admin).

          Type the following command DISM /Online /Cleanup-Image /RestoreHealth and press enter:Note: While running DISM you will notice the process will pause at 20%. After a few minutes the operation will complete successfully. To run the SFC command, please refer to this Microsoft knowledge base article

          • Use the Windows key + X keyboard shortcut to open the Power User menu and select Command Prompt (Admin).

          Type the following command SFC /SCANNOW and press enter:

          For more information on using SFC on Windows 7, 8, 8.1 and Windows 10, please refer to this Microsoft KB:

           

          AMD driver software package requires the latest updates for Microsoft Net Framework and Windows to be installed. Please run Windows Update and install all available critical and recommended updates. In order to minimise the risk of installation errors, Windows should be fully updated before installing AMD driver software package.

           

          Use DDU to sweep the system of AMD drivers in safe mode.

           

          Install the latest Crimson 16.8.2 drivers once the above is completed and check to see if the issue is resolved.