The last time I saw something similar it turned out to be the HD audio device on the video card for HDMI.
Updating AMD/ATI cards, 'drivers only'.
- Thread starter satrow
- Start date
Hmmm - interesting. I had not thought of that. Certainly makes sense and explains why there were two entries for the card. Is there anyway I can tell for sure? And does anyone have any suggestions as to what I should do about it?
Many thanks
Yes, pretty sure it's the sound part of the HD(MI) card. Try the install as before, if it fails, don't worry, use it for a while and see if there are any real issues that occur.
It could be that a full CCC, warts and all install is the only way to clean up Device Manager.
It could be that a full CCC, warts and all install is the only way to clean up Device Manager.
In the first instance, I have just tried Disabling it in Device Manager. Everything is running fine with it disabled and no wizard on reboot. So can I just leave it disabled for good now and move on?
Many thanks - you guys are great!
PS - I have disabled the ATI Hotkey Poller/ati2evxx.exe service as from what I can see that won't be needed for my install.
Many thanks - you guys are great!
PS - I have disabled the ATI Hotkey Poller/ati2evxx.exe service as from what I can see that won't be needed for my install.
Disabling it should be fine - but upsetting for the purists 
I've never used the hotkey switching either, the main reason I mentioned it was to alert you that it would be visible at some point - isn't there a similar .dll (atiacm64.dll here on W7x64, was loading from HKCR\CLSID\{5E2121EE-0300-11D4-8D3B-444553540000}) that loads onto the right-click on the Desktop too? Autoruns is the tool to disable that, if it installs on XP: https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
I've never used the hotkey switching either, the main reason I mentioned it was to alert you that it would be visible at some point - isn't there a similar .dll (atiacm64.dll here on W7x64, was loading from HKCR\CLSID\{5E2121EE-0300-11D4-8D3B-444553540000}) that loads onto the right-click on the Desktop too? Autoruns is the tool to disable that, if it installs on XP: https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
Disabling it should be fine - but upsetting for the purists
Oh dear! Hopefully they'll get over it!
I am not too sure what hotkey switching even is/what it allows you to do. But I'm thinking it might need CCC and if so it would not be relevant to me. Likewise the other .dll you mention. I think that might be a CCC thing. As it is now, no other services/processes are running. And I get nothing AMD related in the menu when I right click the desktop.
Cheers
Hotkey switching, as far as I recall, just sets a keyboard combo (like Ctrl+S) that allows you to toggle between monitors or screen resolutions - it might be an enabler for the right-click on the Desktop ATI menu as well - not sure that there's any documentation on it, probably a relic from Win9x/NT4.
I'll put it on my list for testing when I'm bored or my Internet is down
I'll put it on my list for testing when I'm bored or my Internet is down
This drivers only procedure still applies to the new, non-CCC, Crimson AMD/ATI installer (Download Drivers).
I use W7 still, the auto-detected driver package downloaded from AMD (Radeon-Crimson-15.11-Without-DOTNet45-Win7-64Bit - the name will vary) was executed and then cancelled after the initial file extraction, then point the Device Manager updater to C:\AMD\Radeon-Crimson-15.11-Without-DOTNet45-Win7-64Bit\Packages\Drivers\Display\W76A_INF
On the games I tested all worked as normal, nothing unusual seen in Windows or other programs either.
If you use HDMI, you're probably still stuck with having the use the full Crimson/CCC package install.
I use W7 still, the auto-detected driver package downloaded from AMD (Radeon-Crimson-15.11-Without-DOTNet45-Win7-64Bit - the name will vary) was executed and then cancelled after the initial file extraction, then point the Device Manager updater to C:\AMD\Radeon-Crimson-15.11-Without-DOTNet45-Win7-64Bit\Packages\Drivers\Display\W76A_INF
On the games I tested all worked as normal, nothing unusual seen in Windows or other programs either.
If you use HDMI, you're probably still stuck with having the use the full Crimson/CCC package install.
Hotkey switching, as far as I recall, just sets a keyboard combo (like Ctrl+S) that allows you to toggle between monitors or screen resolutions - it might be an enabler for the right-click on the Desktop ATI menu as well - not sure that there's any documentation on it, probably a relic from Win9x/NT4.
I'll put it on my list for testing when I'm bored or my Internet is down
Did you ever get bored enough to try this?!?!
:huh: So there might be a new driver available for my HD5450? Or is it only for newer GCs? I'll check when I get a mo, but if you know the answer off the top of your head and don't mind letting me know = great!
I'm on XP still and followed the procedure and it worked fine with my HD5450 use the both ports (one of which is HDMI). Was I lucky? Or am I misunderstanding?
Cheers
Not running hotkey switching doesn't affect the Desktop ATI menu, it just enables a keyboard method of switching between display resolutions.
No Crimson support for that 'relic', I'm afraid, the latest CCC might still support it but I very much doubt that it will improve anything.
Sorry, I should have stated full HDMI (video + sound), video will work fine but the HDMI sound will, as far as I can tell, require a full CCC/Crimson package install.
No Crimson support for that 'relic', I'm afraid, the latest CCC might still support it but I very much doubt that it will improve anything.
Sorry, I should have stated full HDMI (video + sound), video will work fine but the HDMI sound will, as far as I can tell, require a full CCC/Crimson package install.
Maybe time for an update on the Nvidia article, esp. as there's more bloat to avoid now?
Same initial procedure, the folder to point (File) Explorer/DevMan at (Step #3 and #9) is:
(W10 x64) C:\NVIDIA\DisplayDriver\*378.66*\Win10_64\International\Display.Driver
(W7/8 x64) C:\NVIDIA\DisplayDriver\*382.05*\Win8_Win7_64\International\Display.Driver
*_* Replace these numbers with those that correspond to your driver version.
Non-English International driver versions and x86 drivers will also have a slightly different subfolder structure, modify to suit your own language version and OS 'bitness'.
Sorry ATI fans, I no longer have an ATI build to test with, contributions are welcome.
Same initial procedure, the folder to point (File) Explorer/DevMan at (Step #3 and #9) is:
(W10 x64) C:\NVIDIA\DisplayDriver\*378.66*\Win10_64\International\Display.Driver
(W7/8 x64) C:\NVIDIA\DisplayDriver\*382.05*\Win8_Win7_64\International\Display.Driver
*_* Replace these numbers with those that correspond to your driver version.
Non-English International driver versions and x86 drivers will also have a slightly different subfolder structure, modify to suit your own language version and OS 'bitness'.
Sorry ATI fans, I no longer have an ATI build to test with, contributions are welcome.
Has Sysnative Forums helped you? Please consider donating to help us support the site!