Windows 10: High definition audio controller giving me the code 10

I have a 13 year old ASUS laptop K73SV and a WD SSD. Whenever I try installing any sort of Windows OS onto the SSD in the laptop, the high definition audio controller always reports code 10. I have tried:Installing a Realtek audio driverInstalling an intel chipset from the official ASUS website for the modelUninstalling and re-installing the deviceAnd none of them worked. However, the windows 11 OS that I currently use has a working high definition audio controller and I have no idea why. Is there any way to fix this?

:)

 

Windows High Definition Audio Controller Code 10

Hi all, my High Definition Audio Controller shows up in Device Manager with a yellow exclamation mark and has code 10 in its Properties. I can't play any sound at all. I've tried:

-Uninstalling the High Definition Audio Controller and restarting my computer to no avail

-Using Windows Troubleshooter which couldn't identify the problem. It just said "High Definition Audio Controller has a driver problem".

I'm using Windows on a partition in my 2012 Macbook Pro running Mojave. The Windows partition was installed using a bootable USB.

 

Controller High Definition Audio Code 10

Motherboard: Asrock b450m pro4-f.

OS: Windows 10 Pro.

I have problems with audio. Everything worked well yesterday morning. Then I rewired the BIOS — and the audio was lost. Audio works only from the video card (speakers in the monitor) and via the USB port.

I tried to connect speakers and regular headphones — it was useless. Now in the device Manager I have, the controller High Definition Audio (Microsoft) - an error. Device state — "This device cannot be started. (Code 10) There are not enough system resources
to complete the API call.". I've already tried a lot of things, nothing helps.

I tried to install and reinstall Realtek (from Asrock website) — the apps have it, but I can't open the panel (and there is no Realtek device Manager either); Uninstalled and Reinstalled the High Definition Audio Controller...

I'd appreciate any help I could get.

 

Code 10 for High Definition Audio Controller

On an Asus N55SF, upgrading Windows 10 from version 1607 to 1709 (a reset install from USB, since numerous attempts through Windows update had failed to complete) caused havoc in that the High Definition Audio Controller (Device Manager – System devices)
subsequently refused to start; the dreaded Code 10 error. No such issues ever noted under version 1607.

Having then tried a host of suggestions posted online, and several combinations thereof, including Windows’ Troubleshoot – Playing Audio and Troubleshoot – Hardware and Devices, checking under Services if Windows Audio is running, removing and reinstalling
different versions of Realtek High Definition Audio drivers, Intel graphics and chipset drivers, modifying the registry (deleting UpperFilter values), all to no avail, the issue looked hopelessly deadlocked. An external USB DAC (Denon DA-10) was working fine
all the time.

However, one BIOS (ver. 207) setting on this Asus N55SF machine presents an apparently working work-around, if not a real solution: under the “Advanced” tab, when “Play POST Sound” is set to “Yes”, it enables the High Definition Audio Controller to start
when loading Windows, and the Realtek High Definiton Audio devices (both speakers and microphone) to work again. One then has to live with a sound being played at Windows startup and shut-down, but the “Speaker Volume” for this sound can be set to low (“1”)
in the BIOS settings.

The Realtek High Definiton Audio driver 6.0.1.7571 was automatically installed by Windows, but it did not work well; the best results so far on this machine with Windows 10 version 1709 have been with the Realtek High Definiton Audio driver 6.0.1.6413 (for
Windows 7) from Asus Support. It does, however, fail to install Asus Sonic Master. That does not matter much to me. The most recent driver versions 6.0.1.8219 and 6.0.1.8228 found at the excellent Asus driver resources site
https://ivanrf.com/en/blog/ install OK, but run less stably in this case than version 6.0.1.6413.