Friday, August 31, 2012 2:32 PM
Friday, August 31, 2012 9:48 PMTurns out the problem was a configuration issue with the vendor's driver settings. A clean install did not have any errors. Upgrading from the 2.3.x driver to the 2.4.x driver left an entry that caused the problem.
Remove this registry key:
Tuesday, September 04, 2012 2:16 AMModerator