How to Fix ATT beta Black Screen errors

Discussion in 'ATI Tray Tools Public Beta Section' started by berni2k, Apr 4, 2007.

  1. berni2k

    berni2k Member

    Messages:
    32
    Likes Received:
    0
    GPU:
    X1800XT 256 + HD4850 512
    1
    find a way to reboot your sys (e.g. Alt-F4, enter or windows key, right arrow, enter or pressing the reset/power button)

    2
    while booting up hit F8 after the BIOS initialiastion

    3
    in the upcomming menu select boot windows in save mode with networking (so you can download some software you will need to fix this)

    4
    now windows will _not_ load the catalyst 7.2 dispay drivers and therefor you will finally see the GUI again
    -> 4.1
    unistalling ATT will not be enough to fix this error because ATT changed some setting inside the display drivers itself
    -> 4.2
    now you say ok so lets just uninstall catalyst then .. well sorry catalyst drivers are such a **** they wont unisall inside windows safe mode because the install/uninstall setup routine bundeled together with catalyst wont let you

    5
    download driver cleaner pro 1.5, a new version of catalyst maybe 7.3, and a new version of ATT beta maybe 018 or newer

    6
    uninstall ATT

    7
    install and run driver cleaner pro 1.5 (select the ATI settings and clean)
    http://www.pcwelt.de/downloads/tools_utilities/treiber-tools/106370/index.html

    8
    restart and install catalyst again and the new ATT version
     
    Last edited: Apr 4, 2007
  2. berni2k

    berni2k Member

    Messages:
    32
    Likes Received:
    0
    GPU:
    X1800XT 256 + HD4850 512
    and found that at the inquirer, maybe it helps someone:

    *Start the PC in Safe Mode
    *Go to Start > Run
    *Run Services.Msc
    *Find the ATI External Event Utility Service
    *Right click > Properties
    *Change it to Startup Type = Disabled
    *Apply, then click OK
    *Reboot.

    If you do that correctly, you should be able to use your computer normally. However, your system won't detect if you plug in or unplug a display whilst Windows is running, since the External Event service that you just disabled is designed to do just that. It seems that this module must be where the problem is, but quite why it would go bonkers, not even ATI knows at the moment.
     

Share This Page