2 Replies Latest reply on Oct 18, 2016 12:13 PM by manthepost

    "Radeon Settings: host application has stopped working".

    denik

      Guys, I already followed the steps described in this --> thread but since Catalyst became Crimson I couldn't event start it once.  While Windows is starting I get the "Radeon Settings: host application has stopped working" error.

       

      I'm using Windows 7 Ultimate x64 Service Pack 1.

      My card is a Sapphire Radeon HD 7870 Ghz Edition OC 2Gb DDR5 PCI-E.

       

      Regarding the thread mentioned before, I got the following results:

       

      • About DISM, the Microsoft KB in that post suggested me to install the patch "System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [October 2014]".  I did it but didn't work.

       

      • SFC didn't find anything wrong.

       

      • I tried with several versions of Crimson (16.7.3, 16.9.1 and 16.9.2) on a brand new Windows installation to avoid driver and software conflicts: I installed a completely clean copy of Windows, with no more drivers than Windows default drivers and no other software at all. But every time I try to start the utility or it runs at startup, I get the error mentioned before.

       

      I'm adding more details about the crash:

       

      Firma con problemas:

        Nombre del evento de problema: APPCRASH

        Nombre de la aplicación: RadeonSettings.exe

        Versión de la aplicación: 10.1.1.1648

        Marca de tiempo de la aplicación: 57dc524e

        Nombre del módulo con errores: atidxx64.dll

        Versión del módulo con errores: 21.19.137.1

        Marca de tiempo del módulo con errores: 57dc4d6f

        Código de excepción: c000001d

        Desplazamiento de excepción: 0000000000622571

        Versión del sistema operativo: 6.1.7600.2.0.0.256.1

        Id. de configuración regional: 11274

        Información adicional 1: b6d5

        Información adicional 2: b6d5f87691691173e01b5a88477c34f7

        Información adicional 3: 4a34

        Información adicional 4: 4a345f83155f928ec40ce2b31352ad9a

       

      I would really appreciate any kind of support to solve this issue.

       

      Thanks a lot, Denik.