BernardP, thanks for the reply. Yes, it seems 197.13 carries the same problematic code branch as the 196.75 drivers. Absolutely nothing I do can get rid of the bug - even when I uninstall the driver, reboot to safe mode, run Drive Sweeper, then restart. Not even when Windows reverts back to...