Display Driver Uninstaller Thread

Discussion in 'Videocards - AMD Radeon Drivers Section' started by Wagnard, Jul 14, 2013.

Thread Status:
Not open for further replies.
  1. doge4life

    doge4life New Member

    Messages:
    1
    Likes Received:
    0
    GPU:
    Sapphire Tri X R9 290X OC
    Does anybody know why a second GPU would be recognized in Display Driver Uninstaller but not in device manager?
     
  2. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    because its a hidden device. Either a removed card or a leftover of older driver.
    Its 1 of the major point of using DDU, getting rid of thoses.
     
  3. Jackalito

    Jackalito Master Guru

    Messages:
    583
    Likes Received:
    100
    GPU:
    Radeon RX 5700 XT
    I installed the new AMD beta drivers today. Used DDU frist to uninstall the previous one, and everything went flawlessly ;)

    @Wagnard, are there any new additions (files or reg entries) you need to add for these latest AMD drivers, or can I just use DDU 12.3 in case I decide to roll back to Catalyst 13.12?

    Thanks! :)
     
  4. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    I didnt test on my side but I guess its all ok. The driver are not that different from 1 to another. but ill sure give a test run when I have the time.
     

  5. Jackalito

    Jackalito Master Guru

    Messages:
    583
    Likes Received:
    100
    GPU:
    Radeon RX 5700 XT
    Ok, I'd guessed that much so far ;)

    Thank you! :)
     
  6. SlackerITGuy

    SlackerITGuy Master Guru

    Messages:
    393
    Likes Received:
    1
    GPU:
    SAPPHIRE Radeon R9 Fury
    Hey Wagnard, been meaning to write this post for a couple of days now (extremely busy), I used DDU 12.3 when 14.2 was released by AMD on the 25th, and after performing the uninstall (under safe mode, Windows 8.1 Pro), an error message appeared right before the restart saying "Unknown hard error", then Windows restarted itself.

    Everything seems fine at the moment (already using 14.2).

    But I'm curious, what caused the error message?

    I will upload the log file once I get home later tonight.

    Thanks.
     
  7. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    The hard error was from DDU? I mean DDU crashed with a hard error?
     
  8. SlackerITGuy

    SlackerITGuy Master Guru

    Messages:
    393
    Likes Received:
    1
    GPU:
    SAPPHIRE Radeon R9 Fury
    The "unknown hard error" message appeared just after DDU closed (seconds before restarting), on this screen:

    [​IMG]
     
  9. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    weird, cold be anything.
    If you find out in the log or in windows event viewer what may have gone worng just tell me.
    COuld be the system restart that ended DDU too fast.
     
  10. SlackerITGuy

    SlackerITGuy Master Guru

    Messages:
    393
    Likes Received:
    1
    GPU:
    SAPPHIRE Radeon R9 Fury
    I really don't know mate, this is the 1st time I've had that message pop up, and I've been using DDU from very early on.

    Here's the log:

    2/26/2014 12:02:06 AM >> DDU Version: 12.3
    2/26/2014 12:02:06 AM >> OS: Windows 8.1
    2/26/2014 12:02:06 AM >> Architecture: x64
    2/26/2014 12:02:06 AM >> PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1CDA0A78&0&0008: AMD Radeon HD 7900 Series
    1 matching device(s) found.

    2/26/2014 12:02:06 AM >> Driver Version : 13.350.1005.0
    2/26/2014 12:02:06 AM >> User Account Name : David Chramcow
    2/26/2014 12:02:32 AM >> Uninstalling AMD driver ...
    2/26/2014 12:02:32 AM >> Executing ddudr Remove
    2/26/2014 12:02:32 AM >> Found an AMD audio controller bus !
    2/26/2014 12:02:32 AM >> PCI\VEN_1002&DEV_AAA0&SUBSYS_AAA01002&REV_00\4&1CDA0A78&0&0108: Removed
    1 device(s) were removed.

    2/26/2014 12:02:32 AM >> PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1CDA0A78&0&0008: Removed
    1 device(s) were removed.

    2/26/2014 12:02:32 AM >> ddudr Remove Display Complete
    2/26/2014 12:02:32 AM >> HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1003\5&DB445ED&0&0001: Removed
    1 device(s) were removed.

    2/26/2014 12:02:32 AM >> ddudr Remove Audio/HDMI Complete
    2/26/2014 12:02:33 AM >> ddudr Remove Monitor started
    2/26/2014 12:02:33 AM >> -DISPLAY\BNQ7F10\5&210C8E76&0&UID0- Monitor id found
    2/26/2014 12:02:33 AM >> DISPLAY\BNQ7F10\5&210C8E76&0&UID0 : Removed
    1 device(s) were removed.

    2/26/2014 12:02:33 AM >> -DISPLAY\DEFAULT_MONITOR\1&8713BCA&0&UID0- Monitor id found
    2/26/2014 12:02:33 AM >> DISPLAY\DEFAULT_MONITOR\1&8713BCA&0&UID0 : Removed
    1 device(s) were removed.

    2/26/2014 12:02:33 AM >> -DISPLAY\BNQ7F10\5&210C8E76&0&UID263- Monitor id found
    2/26/2014 12:02:33 AM >> DISPLAY\BNQ7F10\5&210C8E76&0&UID263 : Removed
    1 device(s) were removed.

    2/26/2014 12:02:33 AM >> -DISPLAY\BNQ7F10\1&8713BCA&0&UID0- Monitor id found
    2/26/2014 12:02:33 AM >> DISPLAY\BNQ7F10\1&8713BCA&0&UID0 : Removed
    1 device(s) were removed.

    2/26/2014 12:02:33 AM >> -DISPLAY\DEFAULT_MONITOR\5&210C8E76&0&UID0- Monitor id found
    2/26/2014 12:02:33 AM >> DISPLAY\DEFAULT_MONITOR\5&210C8E76&0&UID0 : Removed
    1 device(s) were removed.

    2/26/2014 12:02:37 AM >> Cleaning known Regkeys
    2/26/2014 12:02:37 AM >> Starting dcom/clsid/appid/typelib cleanup
    2/26/2014 12:02:37 AM >> Interface CleanUP
    2/26/2014 12:02:38 AM >> ActiveMovie Filter Class Manager cleanUP
    2/26/2014 12:02:38 AM >> AppID and clsidleftover cleanUP
    2/26/2014 12:02:39 AM >> Record CleanUP
    2/26/2014 12:02:39 AM >> Assembly CleanUP
    2/26/2014 12:02:39 AM >> ngenservice Clean
    2/26/2014 12:02:39 AM >> Pnplockdownfiles region cleanUP
    2/26/2014 12:02:47 AM >> System environement cleanUP
    2/26/2014 12:02:47 AM >> Remove eventviewer stuff
    2/26/2014 12:02:47 AM >> No value exists with that name. HydraVisionDesktopManager
    2/26/2014 12:02:47 AM >> No value exists with that name. GRID
    2/26/2014 12:02:47 AM >> No value exists with that name. HydraVisionMDEngine
    2/26/2014 12:02:47 AM >> Removing known Packages
    2/26/2014 12:02:47 AM >> Debug : Starting S-1-5-xx region cleanUP
    2/26/2014 12:02:48 AM >> Debug : End of S-1-5-xx region cleanUP
    2/26/2014 12:02:48 AM >> No value exists with that name. StartCCC
    2/26/2014 12:02:48 AM >> No value exists with that name. AMD AVT
    2/26/2014 12:02:48 AM >> SharedDLLs CleanUP
    2/26/2014 12:02:49 AM >> Killing Explorer.exe
    2/26/2014 12:02:49 AM >> Cleaning Directory (Please Wait...)
    2/26/2014 12:02:49 AM >> Could not find directory 'C:\AMD'.
    2/26/2014 12:02:49 AM >> Could not find directory 'C:\Program Files (x86)\AMD AVT'.
    2/26/2014 12:02:50 AM >> Could not find directory 'C:\Program Files (x86)\AMD APP'.
    2/26/2014 12:02:50 AM >> Deleting some specials folders, it could take some times...
    2/26/2014 12:02:50 AM >> Method failed with unexpected error code 3.SteadyVideo testdelete
    2/26/2014 12:02:50 AM >> Executing Driver Store cleanUP(Find OEM)...
    2/26/2014 12:02:50 AM >> ddudr DP_ENUM RESULT BELOW
    2/26/2014 12:02:50 AM >> The following third-party driver packages are installed on this computer:
    oem0.inf
    Provider: Intel
    Class: IDE ATA/ATAPI controllers
    oem1.inf
    Provider: Intel
    Class: System devices
    oem10.inf
    Provider: Advanced Micro Devices, Inc.
    Class: Display adapters
    oem2.inf
    Provider: Intel
    Class: System devices
    oem3.inf
    Provider: Intel
    Class: Universal Serial Bus controllers
    oem4.inf
    Provider: Intel
    Class: System devices
    oem5.inf
    Provider: Intel
    Class: System devices
    oem6.inf
    Provider: Intel Corporation
    Class: IDE ATA/ATAPI controllers
    oem7.inf
    Provider: Broadcom
    Class: Network adapters
    oem8.inf
    Provider: ASUSTeK
    Class: Sound, video and game controllers
    oem9.inf
    Provider: AMD
    Class: System devices

    2/26/2014 12:02:50 AM >> oem10 Found
    2/26/2014 12:02:50 AM >> -f dp_delete "oem10.inf"
    2/26/2014 12:02:50 AM >> Executing Driver Store CleanUP(delete OEM)...
    2/26/2014 12:02:51 AM >> Driver package 'oem10.inf' deleted.

    2/26/2014 12:02:51 AM >> oem9 Found
    2/26/2014 12:02:51 AM >> dp_delete "oem9.inf"
    2/26/2014 12:02:51 AM >> Executing Driver Store CleanUP(delete OEM)...
    2/26/2014 12:02:51 AM >> Driver package 'oem9.inf' deleted.

    2/26/2014 12:02:51 AM >> Driver Store CleanUP Complete.
    2/26/2014 12:02:51 AM >> Cleaning Process/Services...
    2/26/2014 12:02:51 AM >> Restarting Computer
     

  11. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    Display Driver Uninstaller 12.4 (03-01-2014)

    DDU should be considered as beta software.
    Changelog:
    -Fixed a bug introduced recently that could have prevented the cleanUP of the pnplockdownfiles section. (Nvidia only)
    -made a packages.cfg file to give further DDU CleanUp power to the users. (AMD Only)
    -Spanish language update from Jackalito ! Thanks.

    http://wagnardmobile.com/DDU
     
  12. Elite3540

    Elite3540 Master Guru

    Messages:
    668
    Likes Received:
    1
    GPU:
    MSI GTX 970 GAMING 4G OC
    Great!

    Thanks for your fully support man, WE really appreciate it!
     
  13. CrazY_Milojko

    CrazY_Milojko Ancient Guru

    Messages:
    2,611
    Likes Received:
    1,442
    GPU:
    Asus STRIX 1070 OC
    Wagnard, can I send you PM here (or to e-mail) with ziped DDU translation on Serbian (Latin)? I was using files from DDU 12.4 version, just did a triple check of my translation...

    edit:
    If you want I could also make translation to Serbian (Cyrilic).
     
    Last edited: Mar 2, 2014
  14. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    Yeah of course !
     
  15. CrazY_Milojko

    CrazY_Milojko Ancient Guru

    Messages:
    2,611
    Likes Received:
    1,442
    GPU:
    Asus STRIX 1070 OC
    Give me a hour or two to make and check a Serbian (Cyrilic) translation.

    edit
    I've send download link for Serbian (Latin) and Serbian (Cyrilic) translation for DDU by PM and to your e-mail
     
    Last edited: Mar 2, 2014

  16. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    Hi guys,
    I need a general opinion on the auto reboot into safemode.
    Do you guys want to keep it or not?

    I was thinking of removing it because some users have problem with their computer denying them to go into safemode.

    So I want to know if you guys want to keep this feature or not.
     
  17. Extraordinary

    Extraordinary Ancient Guru

    Messages:
    19,562
    Likes Received:
    1,634
    GPU:
    ROG Strix 1080 OC
    Might be handy to keep for people running 8.x

    Not as easy to get into safemode running 8.x

    Maybe make running the program as Admin a must ? Would that sort the permission out ?
     
  18. 7stars

    7stars Member Guru

    Messages:
    107
    Likes Received:
    0
    GPU:
    Sapphire R9 290 Tri-x OC
    maybe let the user choose what to do ? :)
    IF that's more useful and effective, i would not remove it completely...
     
  19. Wagnard

    Wagnard Ancient Guru

    Messages:
    2,686
    Likes Received:
    384
    GPU:
    MSI Geforce GTX 1080
    Its already a must to be Admin.

    The problem encountered by some user is a bug from a backup software from "Easeus" recently. (probably on one of their latest update)

    They had a driver that fail to load in safemode and because DDU is adding with BCDEDIT the value to boot into safemode with networking, it result that the system will always tries to go into safemode and by so always fail.

    This is one of the issue encountered. I'm sure many users have different reason why their system doesn't work into safemode.

    It's already a choice. But some users never go into safemode and by so they dont even know their safemode is not working or will hang or crash.
    And if this happen, the computer is stuck in a safemode boot loop because it cannot enter safemode and DDU cannot remove the bcdedit change it did.

    It is possible to remove it manually with the windows cd and selecting the repair option with command prompt then BCDEDIT our-self, but when a "not so techy user" encounter this problem, it required me to explain the procedure every time.
     
    Last edited: Mar 4, 2014
  20. Mott

    Mott Master Guru

    Messages:
    984
    Likes Received:
    271
    GPU:
    6800XT / 6800M
    Definitely keep the option to boot into safemode as most of us use it and really like the feature. Just put a warning that it might not work for everyone. If it does not work for someone have some simple instructions maybe on how to boot into safe mode. Just because it doesn't work for some people does not mean you should pull a feature that most of us really appreciate from the program.

    Keep it in there and keep up the great work I really like this program and now have all of my friends using it.
     
Thread Status:
Not open for further replies.

Share This Page