MBP UEFI WINDOWS SOUND FIXED!!!!

Question

Level 1

23 points

MBP UEFI WINDOWS SOUND FIXED!!!!

If anyone is still interested I have found the solution for audio on MBP 2011 Windows 10 UEFI installs - it has taken me 4 years to figure out. I was given the answer from a tutorial only adjacently related -here:

https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/

essentially what we knew was that windows didn't 'see' the correct audio devices when booted in pure efi-

The part that was frustrating to me was that many users like myself have lots of UEFI installs on their 2011 MBP and those OS's have no problem 'seeing' the HD audio controller -

So what was windows doing different?

I had messed around with mm commands in a UEFI shell (The shell provided in the rEFIt package) to no avail*

I had tried to pass SETPCI commands from grub into Windows 10- no luck*

A quote from the link above got my brain spinning

"A Windows system's DSDT table root bridge definition (ACPI PNP0A08 or PNP0A03) is usually confined to a reserved 32-bit space (under 4GB) budgeted to be large enough to host the notebook's PCIe devices. A watermark TOLUD value is then set and locked in the system firmware. Windows OS honors the root bridge definition and will allocate PCIe devices within it. macOS ignores the root bridge constraints as too does Linux when booted with the 'pci=noCRS' parameter. Neither of those OS require a DSDT override and can allocate freely in the huge 64-bit PCIe address space"

So Windows 'honors' the root bridge and OSX and linux disregard it --hmmm interesting.

As someone who also deals in hackintoshes I am very aware of DSDT's and how editing them can help get OSX running on home brew PC hardware- I had played around with installing Clover (the UEFI bootloader almost synonymous with Hackintoshes) on USB thumb drives and putting the DSDT from my MBP 2011 in the /Clover/ACPI/Windows folder - still nothing-- I thought that pointing windows to a DSDT would be enough.......

A side note is that there are people who have 'bricked' their real Macs when using clover, I have never had that issue personally (a sub-link in the link above describes such a situation)*

If you follow the guide and make a modified DSDT (one that add 'qwords' to the dwords section) you can test it in two ways-

I used Maciasl to extract and edit my DSDT to add a 'Qword' section - I placed the DSDT in two locations /EFI/Clover/ACPI/Patched [not sure if that one matters] & /EFI/Clover/ACPI/Windows

holding ALT/option during bootup I selected "EFI Boot" from the USB clover and booted into Clover

for the exact Clover configuration send me a message

After booting into windows the sound card was immediately working (this was because I had installed the cirrus logic drivers from bootcamp 4) - the display audio driver in device manager had an exclamation point but I was able to install the display audio driver from intel's driver support for the i7 2470m CPU in this machine-

I also looked at device manager via 'by resources' and saw that a new entry 'Large memory with an address range appeared

And low and behold the address range for the 'large memory section' contained the range for the hd audio controller

I then wanted to see if the method described in the initial link posted above where you force that memory map into the registry and turn on 'test signing' worked --

it did, which allowed me to boot directly into windows without the help of clover --

*NOTE: when I tested the registry method I skipped the first few steps since I already had a modified DSDT- I did need to create the 'C:\dsdt folder and extract the windows binaries to that folder - but I did not use their acpi dump nor compiler (I check for errors and compiled my dsdt in Maciasl in OSX)

I would gladly go more in depth but I doubt there are many more who need this information- just glad to have figured it out without the BIOS emulation of bootcamp- going to test this method on other 'pre 2013' Macs with non complient UEFI bios'

MacBook Pro

Posted on Feb 3, 2019 11:57 AM

Reply

Answer 1

Jun 29, 2020 10:46 PM in response to TGIK

Hi, my name is Tanveer

I was using my macbook mid 2012 on windows only without sound. I have another MBP18 running on Catalina. so i installed windows on my MBP12.

Your reply encouraged me to seek help that how can i install audio driver on my MBP12.

I am just a user not a professional like you but could understand few steps.

Could you please help me on how can i correct my MBP12 audio drivers that is only running on Windows 10.

I tried to installed windows on legacy boot system but failed. Windows can only be installed on MBP12 in UEFI GPT mode.

I would appreciate your advice and help in this regard.

Reply

Answer 2

Loner T

Level 9

59,513 points

Jul 1, 2020 10:01 AM in response to tanveersadiq

tanveersadiq wrote:

I tried to installed windows on legacy boot system but failed. Windows can only be installed on MBP12 in UEFI GPT mode.

What was the failure? If you need help with legacy mode installation on your 2012 MBP, start a new discussion.

Reply

Answer 3

Loner T

Level 9

59,513 points

Jul 3, 2020 11:04 AM in response to tanveersadiq

tanveersadiq wrote:

When i start up the mac and hold alt key, i cannot find usb that is made bootable in MBR format. USB is only visible at bootscreen when UEFI GPT bootable format is set to make it bootable in RUFUS.

Please start a new discussion.

Reply

Answer 4

Jul 15, 2020 7:13 PM in response to TGIK

By the way, I have my Windows fixed with your instructions, sound working fine, but I screwed up everything by installing a drivers package for Windows 7 in a Mac Min instead of Windows 10 for MacBookPro :@ I picked up the wrong pen drive!!! I spent a week trying to fix it, I removed all I could see, I got no return point, the reinstaller didn't work, I install the right drivers so might overwrite the wrong ones, tried everything... if wasn't by the sound fix I was already reinstalled Windows. Now I am hoping there is a way to save these modifications I made to have my sound working and just to overwrite it in a new fresh install... is there a way?

Reply

Answer 5

Jul 19, 2020 3:23 PM in response to TGIK

Alright, after some reinstalls, it seems I got a stable Windows 10 2004. I got no time to go further on this, but Windows 10 2004 with bootcamp package won't run at all, blue screen all the time. Now I just install Windows and the drivers manually, one by one, instead of just run the setup. Some features as keyboard backlight won't work, but I hope not heaving blue screens anymore, at list not all the time.

Also I saved my dstd-modified.aml in the desktop already, so I am ready to walk when you are.

Reply

Answer 6

Jul 19, 2020 6:31 PM in response to GustavoPi

Did you try Valor, I updated the boot camp drivers within the iso. Http://www.howeitworks.com/valor It should help you with your MacHalt.sys driver issue that you got going on. If you want to send me your DSDT file I can make your own copy of Valor.

Reply

Answer 7

BetoCN

Level 1

4 points

Aug 14, 2020 2:42 PM in response to TGIK

Hi TGIK, first of all, thanks for your work, I fixed my audio problem months ago, but I still have a problem, my Intel HD3000 don't install drivers and it use the Microsoft's Legacy Drivers, when I install Bootcamp, crash occurs during HD3000 driver's installation, any idea???

I have an 15' 2011 Early Macbook Pro with a defective dedicated GPU.

Reply

Answer 8

Sep 11, 2020 3:24 PM in response to jdscada

Yes, I did with my own MacBook Pro 2012 and worked perfectly... than I screwed it all trying to update some drivers! As my tests shown, there is nothing to do with this hack, it seems the drivers we download thought Bootcamp won't work with last version of Windows 10.

Reply

Answer 9

BetoCN

Level 1

4 points

Sep 13, 2020 3:30 PM in response to xAndrewH1993x

Hi Andrew... I reinstalled windows and used VALOR and It works great, thanks... But I'm still had an issue with my Intel HD 3000, if i try to install driver, BSOD's happen... I need to remove this driver from BootCamp driver's folder and ok, it install Microsoft Legacy Driver... after I tried to update the driver on Windows Device Manager and now it has a exclamation sign, the driver doesn't work. You know what could I do to resolve this? I had a 2011 MacBook Pro 15" with a defective dedicated GPU, in MacOS HD3000 works fine.

Reply

Answer 10

m.marcel

Level 1

4 points

Sep 15, 2020 12:41 AM in response to m.marcel

I just did some research and it seems to be a common issue with the multi GPU Systems and the driver file of intel igdkmd64.sys under Windows 10. I found multiple Websites describing this issue like: https://appuals.com/how-to-fix-igdkmd64-sys-bsod-on-windows-10/

It seems the best solution for this issue is to disable the Intel Graphic Card in the Windows Device Manager and just using the AMD Radeon HD Graphic Card only instead of both. This should be fine for me because the AMD Radeon HD is the better one. The only drawback may be the Power usage in Battery mode. I will try this solution later today when I am at home. I will reply here if it worked.

Reply

Answer 11

TGIK Author

Level 1

23 points

Sep 15, 2020 2:44 PM in response to BetoCN

Been a minute since I have chimed in - sorry to those who have reached out to me - I am swamped as a parent and I am doing an unrelenting IT related job since July -- in terms of those of you who have dual gpu systems, especially those who have a defective/broken AMD GPU we have to dig into finding the right efi script to disable that AMD gpu -

look at these kind of youtube videos https://www.youtube.com/watch?v=4WdJQjDiRwM&ab_channel=RealMacMods

This would solve the issue when installed the hd3000 driver in Windows etc....

Reply

Answer 12

m.marcel

Level 1

4 points

Sep 15, 2020 11:00 PM in response to TGIK

Hi, wouldn't it make more sense to disable the Intel HD3000 GPU in EFI if this is possible? instead of the AMD . Because the AMD GPU is not broken and has the better performance I guess. But I just found articles about disabling the AMD GPU instead of the intel GPU. Everyone is disabling the ADM GPU, I guess because of the issue that it breaks at some time.

BTW to disable the Intel HD3000 GPU in device Manager prevent the system to get the Bluescreens. But I still couldn't install the AMD Driver correctly. So it seems without the working AMD or Intel Driver the Graphic is working but not in the full acceleration. Videos don't play smooth.

@xAndrewH1993x in Valor light I found a small issue.

In the File: "Valor (DOUBLE-CLICK-TO-START)" and iaStorA_Installer.bat (Valor_Lite-(Dont-Delete-Backup)\Resources\Drivers\Pre_Downloaded\BootCamp\Drivers\Apple\iaStorA)

@echo iaStorA (IDE ATA ATAPI Drivers Update (BSOD FIX) Installer

chdir %SYSTEMDRIVE%\Users\%USERNAME%\Downloads\Valor-(Dont-Delete-Backup)\Resources\Drivers\Pre_Downloaded\BootCamp\Drivers\Apple\iaStorA

start README2.txt

call iaStorA_Installer.bat



@echo iaStorA Installer

start "" "%SYSTEMDRIVE%\Users\%USERNAME%\Downloads\Valor-(Dont-Delete-Backup)\Resources\Drivers\Pre_Downloaded\BootCamp\Drivers\Apple\iaStorA\dpinst.exe" /a /path %SYSTEMDRIVE%\Users\%USERNAME%\Downloads\Valor-(Dont-Delete-Backup)\Resources\Drivers\Pre_Downloaded\BootCamp\Drivers\Apple\iaStorA\

Pause:

should be: Valor_Lite-(Dont-Delete-Backup) instead of Valor-(Dont-Delete-Backup)

Reply

Answer 13

Sep 15, 2020 11:05 PM in response to m.marcel

Thank you I'll fix it first thing in the morning and re-upload. Hope you have a good night! I apologize for the reason to support 2012 models. It is because I'm limited to early 2011 hardware and don't have 2012 models to build Valor on.

Reply

Answer 14

TGIK Author

Level 1

23 points

Sep 16, 2020 5:50 AM in response to m.marcel

My response was pointed to a poster who had a broken AMD gpu - which clearly seems to be a pretty common issue with these macbook's. I am sure there is a way to also do it for the HD3000 but as you found there isn't much documentation on it -- It needs to be done on either the EFI firmware level or perhaps I need to look at my original DSDT edits and see if I can make the device invisible via the DSDT -

Reply

Answer 15

DPK101

Level 1

12 points

Sep 23, 2020 8:14 AM in response to BetoCN

Can your Mac even boot into macOS? If you can, you could try installing gfxCardStatus and gSwitch, and have them set up to default to the integrated Intel graphics.

I say that because I’ve accidentally got my win 10 boot camp running successfully using only the Intel HD 3000 igpu on my late 2011 17 inch MacBook Pro (macbook pro 8,3).

Although the discreet AMD card IS still working on my machine, I have gfxCardStatus and gSwitch installed on El Capitan set to use the intel igpu only, and I believe they kick in as soon as I boot up the machine - even when I boot directly into my Win 10 EFI partition. The apps seem to force the machine to use the Intel igpu only, which is what I want!

In fact, Win 10 device manager and the AMD catalyst software show an error symbol for the AMD card, and state that Intel is the only video card. So if you can get into macOS, try set both apps to integrated and then boot into your Win 10 EFI to see if it works, it might be as simple as that...

Unfortunately I am not technical enough to understand how this may have worked, why I haven’t had to set up the integrated.bat as on igpu.io, or if it would work for a machine with a broken AMD gpu, but for me this setup enables faultless Win 10 usage on only the intel graphics!

Quick rundown on how I created the Win 10 EFI in case it helps: In El Capitan I used disk utility to create a guid partition for the windows install, did the boot camp info.plist trick (instructions from 1:37 - 4:40) and then downloaded the newest boot camp drivers for my Mac using boot camp assistant, downloaded a Win 10.iso from microsoft’s site, put that and the bootcamp drivers onto a FAT-32 formatted USB and then used bootcamp assistant to create the Windows installer from the .so. I then restarted and booted to the USB EFI boot (by holding down ALT), followed the installation to create the Win 10 EFI boot partition, then followed Andrew and Derek Riddle’s instructions - which includes installing a big Microsoft drivers package that might help with the Intel graphics situation (thanks so much to you guys for all of your work) - to fix the audio.

I can confirm that Windows' system information shows the BIOS mode is 'UEFI' Now the only things that don't work are the screen brightness controls in Win 10 (the screen is stuck at 100% brightness) and presumably the thunderbolt display port.

I have a Startech USB to HDMI/VGA adapter, so the intel igpu is also driving an external FHD display by HDMI (instead of the disabled AMD thunderbolt port), and again there are no issues with that in macOS or Win 10. I recommend similar USB to HDMI/VGA/Display Port adapters to anyone who needs to use an external display on a macbook with deactivated discreet graphics. They're essentially egpu's that connect to your laptop by USB.

Hope this helps someone as much as this thread helped me, thanks again!

Reply