Issues with Radeon 6350 in Windowx 7 x64 (Working REG Hacks Included)

Client and Mobile Solutions

Client and Mobile Solutions
Learn how to Deploy, Manage, Secure, and Virtualize Enterprise Client and Mobility solutions from experts and peers.

Issues with Radeon 6350 in Windowx 7 x64 (Working REG Hacks Included)

  • I'm having an issue where upon logon it wants to finish some sort of setup. As a normal user, I get a blocked error message stating newdev.exe was trying to run. When I logon with an administrative account, I get a UAC prompt asking me if I want to allow it to install hardware. If I say yes, it says it finished installing the video card.

    Things get even weirder after this. If I go into device manager and tell it to scan for hardware changes, its start evaluating the video card and ends up reinstalling video drivers and saying it is a Radeon 5450. No matter what I try to do after that I cannot get it to go back to a 6350. Removing the device and uninstalling the drivers doesn't help. I've even downloaded drivers directly from AMD and same deal. Anyone else having these issues? Otherwise, it is working well for me.

    One last thing, I am having the same issue in our Windows XP 32-bit environment with the 790. The card says it is a 6350. However, if I tell Windows to look for updated drivers, it will change it to a 5450. This is even after I installed the Catalyst control center seperately. I'm not sure what is going on, but there is definitely something not right with these drivers.
  • I just received an Optiplex 990 this week and had the same issue with the ATI Radeon 6350 being recognized as a 5450 by Windows 7 x64.
    Here's how I resolved the issue:
    1. Go to Device Manager
    2. Right click on AMD RADEON HD 5450, then choose "uninstall"
    3. Go to www.ati.com and install the ATI RADEON HD 6350 drivers
    4. Restart the system
    5. After Windows restarts and you log in, disable any auto-installation of the video driver (as it will likely try to re-install the 5450 driver) Tell it not to go to Windows Update.
    6. Go back into Device Manager, look for the display driver entry and select "Update Driver".
    7. Choose "Browse my computer for driver software", then select "Let me pick from a list of device drivers on my computer"
    8. If you don't already see "AMD RADEON HD 6350" in the Model list, then choose "All device drivers", then select Next.
    9. You should now be able to select AMD RADEON HD 6350.

    Hope that helps!
  • Thanks for the post. The more information the better. It appears to install properly at first but yeah updating devices makes it go wacky. I think they need to send out some sort of fix or update to the drivers. Also, hopefully they can address the UAC prompt when you first logon (Again this is if your environment has it enabled).
  • ArmitageID,

    Thanks for the post, I've seen these issues also. The elevation prompt has been an issue with NVidia/ATI/AMD drivers occasionally in recent years. I don't think I have a 6350 card on hand to test, but I'll forward this along to the dev teams.

    Thanks!
  • @Warren Do you have any updates on this?
  • The issue is being worked (had a call on the issue this morning), but a working driver is not available yet.
  • FYI - I am having the same UAC prompt issue with an Optiplex 990 and the Windows 7 (32-bit) drivers for the ATI Radeon HD 4650. (Works fine with the XP drivers) If I leave the drivers out of the plug and play pool and then run the full ATI installer after the build is complete it works without asking for the UAC prompt on lext login. Not where we want to be obviously though.. Hoping this is addressed soon!!
  • Thank you for the update Warren. Please keep us posted and update when something develops (hopefully soon).
  • I found a work around for my 6450 UAC prompt issue. Maybe this can help someone else out...
    (using SCCM btw) After mini setup runs and the driver is installed via plug and play, the machine boots back up into the "Install Software" phase. I added a task in my task sequence that imports the following registry keys.
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1002&DEV_6779&SUBSYS_21201028&REV_00\4&1f461cb9&0&0008]
    "Capabilities"=dword:00000000
    "ConfigFlags"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_PREPDRVR\0000]
    "Capabilities"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_1002&DEV_6779&SUBSYS_21201028&REV_00\4&1f461cb9&0&0008]
    "Capabilities"=dword:00000000
    "ConfigFlags"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PREPDRVR\0000]
    "ConfigFlags"=dword:00000000
    "Capabilities"=dword:00000000

    *This task only runs if the Radeon HD 6450 Adapter is present by putting a WMI Query "Condition" on the Task. The query I am using is:
    select * from Win32_VideoController where Name like "%Radeon HD 6450%"
    Since we have two Optiplex 990 standards, one with Intel and one with ATI I had to add the condition so it wouldn't apply the registry keys to my SFF 990 with Intel display.

    This removes the UAC prompt on first login. I found these keys by running a setup capture on the UAC prompt process. Still hoping for a fixed/updated driver set. ;-)
  • @wbracken Thank you for sharing your find. I've tried to use Process explorer but find it difficult to weed through everything. What did you use to pinpoint these keys. I haven't given this a try yet, but I will as soon as I get a chance. I do agree that an updated/fixed driver would be nice. I'll see how much tweaking is needed for a Radeon 6350.
  • Just as an update, I checked on a machine that I already hit ok to the UAC prompt. Looking in the registry areas my values are a little bit different. I don't have capabilities on the first LEGACY_PREPDRVR\0000 sections. The same goes for the ControlSet001 version. This is what I have for all those sections you listed above (minus a bunch of other stuff that is in those areas.)

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1002&DEV_68F9&SUBSYS_21261028&REV_00\4&1aa93dc8&0&0008]
    "Capabilities"=dword:00000000
    "ConfigFlags"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_1002&DEV_68F9&SUBSYS_21261028&REV_00\4&1aa93dc8&0&0008]
    "Capabilities"=dword:00000000
    "ConfigFlags"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_PREPDRVR\0000]
    "ConfigFlags"=dword:00000000

    Again, this is for a 6350.
  • I used Wise Install script and ran a setup capture. In most cases I find this easier that Proc Explorer as you are right it can get convoluted quickly and you spend half the day filtering out the junk to find what you are looking for. ;-)
  • I am happy to report that rolling the above setting swith the 6350 worked on the machine I re-imaged. I created a reg file and a new package in SCCM with that as its contents. Using a cmd /c reg import file.reg command line action to apply on machines that are an OptiPlex 790 with a Radeon 6350 video card. No UAC prompt! Thanks a bunch for your information wbracken. Again, hope an updated driver comes out soon so we don't have to do this reg hack any longer.
  • "I am happy to report that rolling the above setting swith the 6350 worked on the machine I re-imaged. I created a reg file and a new package in SCCM with that as its contents. Using a cmd /c reg import file.reg command line action to apply on machines that are an OptiPlex 790 with a Radeon 6350 video card. No UAC prompt! Thanks a bunch for your information wbracken. Again, hope an updated driver comes out soon so we don't have to do this reg hack any longer."
    My pleasure. Glad it helped someone else!
  • Same issues with BSOD added bonus.
    Optiplex 790 Windows 7 64bit with ATI 6350 Card
    Installed Dell 6350 driver, while installing windows decided it was a 5450 and installed those drivers. After a reboot, I get a BSOD pointing to atkmpag.sys part of the ati package. I downloaded the newest drivers from AMD and it sees the card as a 5450. Same atikmpag.sysy BSOD. I called Dell and they decided it was the video card and sent me a replacement. Installed the replacement and same BSOD. I booted into safe mode, uninstalled the 5450 driver and updated manually to the 6350 driver. So far no BSOD, Windows Update still sees it as a 5450 and I had to hide the update.