Need an updated Microsoft Unified Audio Architecture Driver for Intel Chipset C216\BD82C216\E208B284 RRS feed

  • Question

  • I have the Windows 8 x64 RTM installed on hardware using the Intel E208B284 Controller Hub. The hardware below is also listed as the C216 or BD82C216 chipset. Windows 8 runs well as an EFI booted OS, but I can't get the "High Definition Audio Controller" working. The error I get is:

    Device PCI\VEN_8086&DEV_1E20&SUBSYS_72708086&REV_04\3&11583659&0&D8 had a problem starting. Driver Name: hdaudbus.inf
    Driver Date: 7/25/2012
    Driver Version: 6.2.9200.16386 (win8_rtm120725-1247)

    My understanding is that this is the Microsoft UAA driver mentioned in this article (http://www.intel.com/design/chipsets/hdaudio.htm) "Microsoft* has chosen Intel HD Audio as the main architecture for their new Unified Audio Architecture* (UAA), which provides one driver that will support all Intel HD Audio controllers and codecs."

    The hardware in question is a 2012 retina MacBook Pro (model 10,1)

    Any chance of an updated driver?

    • Edited by Krash_ Thursday, August 23, 2012 2:16 PM
    Thursday, August 23, 2012 12:19 PM

All replies

  • Hi,

    If the built-in drivers cannot drive it. Maybe we need to contact Intel for an updated version.

    Juke Chou

    TechNet Community Support

    Friday, August 24, 2012 9:29 AM
  • Good idea Juke. What is the process to contact Intel?

    Keep in mind that the hdaudbus driver is signed by Microsoft.

    This problem is specific to the EFI install of x64 Windows 8. Under the BIOS install this hardware appears as a Cirrus Logic 4206B. So the hardware in question appears to be an Intel PCI Bridge of sorts that under EFI doesn't hand off to the Cirrus driver properly.

    It would be great to test a hotfix.

    Friday, August 24, 2012 8:53 PM
  • Hi,

    It's not the Cirrus chip, it's the High-Def Audio Controller, the Cirrus Logic chip is a separate device. So the High-Def Audio Controller is not properly managed because its driver is not loaded, and for that matter, the Cirus Logic audio chip is not even detected. The fault is in hdaudbus.sys, which is not loaded because its signature isn't valid (that is, in UEFI context ; because in MBR/BIOS context there is no problem whatsoever !)

    Sunday, November 17, 2019 8:56 PM