Upgrading from AMD to Nvidia, Code 39 .. driver corrupted trying to have a better oculus DK2 experience

I bought a new video card to make my oculus rift DK2 experience better… oddly enough pulling out my HD 7770 ghz edition radeon card and replacing it with the GTX 660 OC went fine … well it did .. but a couple of reboots later, things went afoul… my display dropped resolution and device manager was reporting that the driver was corrupted or missing ( code 39 ) …

I spent a good 2 hours trying various things like driver removal tools in safe mode and many other things others have tried, but the most common fix I found was “do a clean reinstall of windows” …. NO THANK YOU

So here’s what I did… but I think the last step is the kicker..

1. Ran the driver cleanup tool to remove the old AMD drivers in safe mode AFTER I ran the uninstall in normal mode
2. Ran the driver cleanup tool to temove the nvidia drivers in safe… blah blah same as above
3. Edited my registery…

#3 is the big one.. you need to find the guid of your card, hint… it’s in the device manager for your display adapter on the details tab with the “device class guid” tab… I believe all video cards share the same class guid .. so.. {4d36e968-e325-11ce-bfc1-08002be10318} is what you’re looking for..

Open your registry editor and search for that string… exactly that string… the FIRST entry should contain an UpperFilters string … if it does, nuke that puppy.. delete it! send it to internet hell … you probably have some kind of other video device that is causing issues … that key is making you pay for it .. in my case it was my oculus rift messing with my video card change 🙂 …

SO .. after I cleaned all remnants of my old drivers AND made that registry tweak, then rebooted… everything worked perfectly.. I reinstalled my nvidia drivers, I reinstalled the latest DK2 SDK run time and everything was perfect.. no reinstall of windows required..

Literally in everything I’ve read online, when you run into a code 39 … finding the device GUID as described above, then editing the registry to delete the UpperFilters key seems to do the job… sometimes apparently there’s a lowerfilters key as well ..

I hope this helps someone..

– Lon

Leave a Reply

Your email address will not be published. Required fields are marked *