After installing new drivers for an old ATI All-In-Wonder, every time the system booted up, atievxx.exe would crash. Annoying, but not tragic, and I lived with it for a while. Cleaning out the old drivers didn’t help, nor did reinstalling the OS. On the chance that it was a hardware problem with the card, I went ahead and replaced it with a newer model, new drivers and everything… and still, that atievxx.exe crash.
I finally tracked it down to a conflict with UltraVNC’s “video hook” driver. Who knew? Curiously, without its video hook driver, UltraVNC is a bit of a slug, so I replaced it with RealVNC, which I’ve been using on other systems with dual-monitor setups for a while.
On another system, I installed the operating system from scratch, and the next step was to install the drivers… But the installation program locked up the system. After trying permutations of everything (there weren’t many permutations of software to try) I resorted to ATI support — who mostly sent me form letters about where to find the latest drivers and asked if my power supply was adequate. Intriguingly, the drivers worked fine if I let Windows install them with the “found new hardware” wizard, but the ATI installer choked no matter what I did.
The problem? A Lucent winmodem sitting in one of the PCI slots. As far as I know, it works perfectly well, but it’s been disconnected for a long time, and god knows why the ATI installer doesn’t like it (or vice versa) but there it is.