I was using AB last night to find my max memory overclock and after getting a checkered screen, the display driver went haywire. The screen kept flashing on and off and the keyboard and mouse quit responding. Rebooted (which generally solves the issue when I'm unstable) and as soon as Windows loads up I get the same flashing non-responsive computer. Tried uninstalling AB (choosing to NOT save settings) and get the same issue. Finally booted into Windows using the DVI port on my motherboard, uninstalled all traces of AMD software (again choosing NOT to save any settings), rebooted using my 7970, and reinstalled the drivers. Everything was working at that point. So I reinstalled AB, put in the EULA info to unlock the overclocking, used the -xcl extension to extend the clocks, and rebooted. Got the same endless loop of flashing and then blank screen with warning messages that the display driver had quit working. This was without touching any of the clocks. As soon as I got into Windows everything went haywire again. Tried deleting all the entries in the registry relating to AB but that didn't seem to help. I'm thinking there must be something left over from AB that is raising clocks to the unstable setting when it originally crashed so when I reinstall AB it picks up those settings and causes the display driver to wig out. When I first install AB I can open it up and everything seems ok, but once I reboot same looping cycle. Any ideas how to fix AB without a complete re-installation of Windows?