• TwitterFacebookGoogle PlusLinkedInRSS FeedEmail

Anthem Audio D2v Before Starting: Additional Instructions For Mac

15.02.2020 

The system was built using an Asus motherboard and uses both Intel processor and graphics and sound (on board) chips. When I contacted Asus they recommended going to their site, finding my motherboard, and updating with their suggested drivers. Did that but it didn't help. Going to the Intel site and pulling down and running the Intel Driver Update Utility, which asked me to downgrade my Intel Display Audio (the device I believe is having issues) and HD Graphics 4000.

Click on the following links for the driver package readme info./extract/Readme.txt This package supports the following driver models:CMD PCI-0640 IDE. Cmd pci-0649 ultra dma ide controller driver for mac. The Driver Update Tool – is a utility that contains more than 27 million official drivers for all hardware, including cmd pci-0649 ultra dma ide-controller driver.

So, I'm a bit baffed. With the current Asus recommended drivers things don't work.

Going to update the HD Graphics driver via Intel's utility would 'downgrade' the Intel Display audio and HD Graphics 4000 drivers. All indications are that the system must be changing things on reboot but I've no clue precisely what is being 'swapped' if it's drivers, or if something else is taking place. Win10 is not at all helpful in showing me what's going on. If there are tools or some means to find a log to search for changes, that would lead me in the direction of what is happening, I suppose. By the way, I did choose to allow the Intel update to the HD Graphics but not to alter the current Display Audio or HD Graphics 4000.

At least that way I've got the drivers Asus recommended as well as the updated one for HD Graphics that Intel recommended. Hi Steve, Thank you posting in Microsoft Community. Let’s try with the below methods and check if he issue resolves. Method 1: Run an inbuilt Sound troubleshooter. Press Windows + X keys and select the Control panel. Type troubleshooting and select it.

Left pane select view all and select the Playing audio. Run the troubleshooter and follow the instructions. Restart the system and check. If the issue doesn’t resolve then try with the next Method. Method 2: Reinstall the driver in Compatibility mode.

Anthem Audio D2v Before Starting: Additional Instructions For Mac Download

Refer to the below link to check how to install drivers in compatibility mode. Refer: Keep us posted to help you better. Thank you Sachin.V Microsoft Community. The first method was what I used to 'fix' the problem when it initially happened. And on boot sound did work. However on subsequent boots it failed again.

Method 2 doesn't apply since the device/driver are not foreign to Win10 but core (the device is Intel Display Audio (under Sound, Video and Game Controllers). I verified that this is the problem device by uninstalling the driver and testing local sound files like Asterisk. No sound until I reboot and the system finds and reinstalls the driver. By the way, it installs version 6.16.0.3154 from from Intel and signed by MS Win Hardware Compatibility Publisher. One other interesting bit: even if the system is working properly and I run the troubleshooter it says it found a problem and says it fixed it and asks me to reboot.

Anthem

So, either this is 'normal' or it's totally out of whack with respect to what it's reporting/doing in this regard. Again, in the absence of any logging/tracking, I've no way to know what's really happeing. So, I am unable to find the source of the problem, but it clearly seems to have something to do with either the driver or how it's deployed. I've checked the associated services and they all are up and listed as automatic. Any other ideas??? Hi Steve, Thank you for providing the details. Place the computer in clean boot state and check if the issue persists.

To disable all non-Microsoft services consult the article called Clean Boot. Refer: Note: After troubleshooting, refer to this section 'How to reset the computer to start normally after clean boot troubleshooting' Disclaimer: A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows. You may also troubleshoot or determine what conflict is causing the problem by performing a clean boot.

Keep us posted to help you better. Thank you Sachin.V Microsoft Community.

Hi Steve, Thank you keeping us updated. I would suggest you to refer the below link and check if it helps.

Refer: Note: After troubleshooting, refer to this section 'How to reset the computer to start normally after clean boot troubleshooting' Disclaimer: A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows.

You may also troubleshoot or determine what conflict is causing the problem by performing a clean boot. Keep us posted to help you better. Thank you Sachin.V Microsoft Community. So far so good. Seems all is working as it should. I do note that generally when I start up the system and attempt to send any sound to my outboard devices it takes a bit of time for everything in the chain to get 'synced' up. I'm going out of the PC to a Lumagen processor which passes the audio via HDMI to a Anthem D2V processor (again via HDMI) which finally send the analogue signal to the amp/speakers.

I'm guessing the EDID process itself gets in play to identify every component and establish the requisite source/destination behavior. So, for example, if I use Window's control to send the system sounds it usually takes a few tries before I get sound to the speakers.

So, can only surmise that this process is not a two-way street, but by persisting I eventually get the sound to occur.