Hehe, I think that title should read “don’t install that UNSIGNED driver”. It’s too bad Microsoft doesn’t have the concept of a user-space driver model… soo much more stable to run crapple drivers like those.

http://www.linuxjournal.com/article/7466

There are a few things that you should know about windows that may or may not help in this instance (it really depends on what files gets overwritten, but it’s worth a shot). One is that windows keeps multiple copies of system driver settings in the registry. Pop open regedit and traverse to:
HKEY_LOCAL_MACHINE\SYSTEM\Select

You’ll see current, default, failed, and lastknowngood. By changing the default to one of your other “control sets” you can revive your computer back to pre-loaded crappy driver state. Note that this can also be done by hitting F5 during the beginning of windows boot process. Now that you’ve already done a bit of futzing around with the device drivers after the fact, this may not work, but it’s good to know for any future occurance.

One thing I haven’t tried but think should also work is to set a system restore point before loading the driver and then revert to that state in case something bad happens:
%systemroot%\system32\restore\rstrui.exe

Btw, you may be interested in this trick to show ALL devices, not just detected ones:
Start, Run…, compmgmt.msc
click on Device Manager
right click on Device Manager, View, Show Hidden Devices

Also, did you know that all registry entries have time stamps?
Note the last parameter: lpftLastWriteTime
http://msdn2.microsoft.com/en-us/library/ms724862.aspx

Wouldn’t it be nice if there was a registry editor that exposed this? One could do a search and replace in files AND registry for recent writes and zero in on these types of problems.