Display Driver Uninstaller Thread

Happy holidays! Please relax now and get better for next year! ;P

 

Thanks for the update Wagnard.

Happy Christmas to you and yours.

 

Display Driver Uninstaller 13.5.5.0 (12-30-2014)

Display Driver Uninstaller 13.5.5.0 (12-30-2014)

Changelog:
-nVidia 347.09 support.
-Microsoft Surface Pro 3 tested.
-Fixed a possible bug when detecting the GPU details at launch.
-Fixes/enhancements on the Cleanup engine (clsidleftover part).
-Additional Intel/AMD notebook service cleanUP.

http://www.wagnardmobile.com/DDU/downloads.html

 

Happy New Year, DDU's team!

 

Thank you, man! I too wish you a very happy new year 2015

Sweet, this is the best way to end the current year!
Happy holidays, DDU Team!

 

Thanks for everything guys, Happy New Year!

Thanks! Very much Appreciated!

 

With the combination of AMD's driver uninstaller, followed by TWL's 5.01 cleaner, and DDU to finish up in safe mode, you can be sure everything driver related is nuked to the level of what a fresh OS install would be.

You can test out drivers, and rule out any driver conflicts at the same time as many times as you want without having to worry about AMD's uninstallers not cleaning up after themselves properly or leaving odd CCC settings behind, and/or borking your system because when I use this triple method this always gives me a clean slate with just VGA and no driver related files to be found.

I always use this triple whammy cocktail for cleaning out ALL the driver junk and registry/video entries even OpenCL and it works brilliantly each and every time.

Can't fault DDU and nice to have in your arsenal. Appreciated work.

 

Twl?

Just out of pure curiosity, what driver cleaner utility does TWL refer to?

 

http://forums.guru3d.com/showthread.php?t=322616

To everyone, I think it's unnecessary to use multiple cleanUp tool.
DDU should be able to remove most if not all of them.
If there is still left-overs, please feel free to tell me about them so I can take care of them in a future update.

 

Hi wagnard,

I used your other nice program "TDR-manipulator".
Is there any new version after 1.1 ?

tanx

 

No,
Is there something that need to be fixed?

 

well, just curious.

still have TDR 141

 

Not sure that TDR manipulator affect TDR based on this error (STOP 0x00000141: VIDEO_ENGINE_TIMEOUT_DETECTED)

From the title, seems related to the video decoding.

 

It is for me on legacy....they all still complement each other well.

But if AMD did package installs/uninstalls like Carlsberg, none of these cleaners would exist at all, and I wouldn't be here posting this...

I'd love to use DDU exclusively as a catch all one size fits all total removal but...there are still a few "orphans" in my travels installing/uninstalling drivers.

It misses sweeping the old (namechanged for 2 drivers) amdcal's from 8.12 & 9.1 that may still be floating around on system which can conflict with newer aticalxx (ATI stream) when both are installed when launching AIDA.

Also AtiHdmi.sys from System32/Drivers is never removed even though the device is, is that by design because I always tick HDMI device removal in options?

Maybe also the 10.2/10.3 atipmdag.sys driver .inf created proxies that only appeared in those 2 drv's only that could still be floating around.

There were also some more stuff from old drivers from down into the 8.xx/9xx series that I don't remember right now not taken care of by DDU, that was hoovered out by TWL's cleaner & this is exactly why I still prefer to use all 3 for a good scrub.

Because like most AMD users, I change drivers often surprise surprise, haha...

And the potential for screw ups is geometrically proportional to the amount of installing/uninstalling done without any cleaner "assists".

3 months of installing/uninstalling drivers without "cleaners" inbetween on AMD's installers alone, and you be guranteed to be re-installing Windows for sure matey. The registry will be as corrupt as Jimmy Saville.

I'll keep you informed what they exactly the rest are as I find them all (without it being off the top of my head), because for now I'm back on more "modern" drivers and don't feel like playing anymore today.

It's still a superior clean out util nonetheless, better than that trojaned ATIMan crap that is just a plain rip off of renamed TwL's scripts with a virus added.

But even better still if it catches everything orphaned from the old drivers as well, not only the new ones where these files don't exist anymore but could still be on system from changing h/ware etc, and still have the potential to cause conflicts in some way referenced by the code etc...

I'm on legacy 4870x2/Win7 x64. The old 8.xx/9xx drivers I force install on Win7 as Vista or just use Orca to create my own custom installs.

Not everybody is as crazy as me to be even using such old drivers, or even bother to notice the things from out of them that still get left behind today. :infinity:

I guess I need to get out more...

 

Thanks for the post, i'll be looking at this.

From what Cat version to you get a AtiHdmi.sys ? Usually that driver file is named atihdwb6.sys

Edit: after a little research, I think it belongs to some older drivers.
Ill add it to the cleaning along with theses :
amdcalcl.dll
amdcalcl64.dll
amdcaldd.dll
amdcaldd64.dll
amdcalrt.dll
amdcalrt64.dll
atipmdag.sys (including service removal)
atipmdag.dll

If you can wait to test, you can manually add those to the .cfg files without any need to recompile the app.

If you find anything else feel free to tell me.

 

Yes AtiHdmi.sys is from older 9.xx/8.xx releases.

I figured already you can add your own stuff for deletion in the DDU cfg's if you're brave enough, but it's nice to have it done by default as standard in the util for everybody for any old stuff floating around on the system so the tool can be used universally for all, not just mantle stuff and any new drivers.

For legacy cards, it's better that this old stuff is cleaned out other than not, as you don't know what if any problems anything left behind might cause down the line.

atipmdag is probably from 10.1-10.5 and is created by proxying atikmdag in the driver .inf itself. It doesn't actually exist as a file in the driver folders, but copied by namechange from atikmdag.sys when the driver .inf runs.

Don't ask me what for because I don't know..

Cheers, K.

 

DDU webpage could be down for a couple hours. (renewing stuff/ server changes)

Sorry for any inconvenience it may cause.

 

Here you go, decided to play around some more Ton8 for the benefit of all to find the odd ones out still escaping the "scrub"...

I found some more not covered by DDU but covered by Twl. Hard to do this with running only VGA driver to test squinting at the screen folders w/o cleartype but anyway...

Ati2evxx.dll
Ati2evxx

(ATI External events Utility process/service needs to be killed before they will delete from \System32\ or the files are LOCKED for deletion)

atibrtmon
atiumd6a.dat
atiumdva.dat

(one in System32 and one in SysWOW64, the .dat's are pre Cat 9.2)

ativcaxx.cpa
ativcaxx.vp
ativdkxx.vp
ativokxx.vp
ativpkxx.vp
ativpkxx.vp

Twl cleaner/Von Dach deletes these...

Located in Windows\System32\Drivers\ for atikmdag.sys for pre-CAT 9.2.

Also possibly an atiapfxx useless profile log file in SysWOW64 although I can't confirm which driver does that or why...

Give me a reason not to use TwL cleaner anymore...

 

Ill add them too.
For atikmdag.sys, atiumd6a.dat,atiumdva.dat , DDU already remove them.

There is chances i'll make a release today, ill credit you for the time you took.

 

Display Driver Uninstaller 13.6.0.0 (01-11-2015)

Changelog:
-DDU will now log some of the deleted registry key. (work in progress)
-New extended log window that show the log progress in realtime.
-Additional AMD assembly cleanUP
-Additional AMD cleanUP for older CAT version (Thanks to kevsamiga1974 help on this)

Download