Guide: DSDT override eGPU error 12 fix (Windows only) [started 2012@NBR ]
here ◄ Mac owners please work through this thread to solve error 12 before doing a DSDT override
here ◄ pre-compiled DSDT overrides – load or use as reference when making your own
| Introduction |
A Windows system’s DSDT table root bridge definition (ACPI PNP0A08 or PNP0A03) is usually confined to a reserved 32-bit space (under 4GB) budgetted 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.
When retrofitting a eGPU, an error 12 (This device cannot find enough free resources that it can use) can occur against an eGPU in Windows’ device manager making it inoperable. This can indicate there is insufficient 32-bit addressing space available to host the eGPU. An eGPU requires a relatively large PCIe config space to allocate into. Decreasing TOLUD by reducing RAM to 2GB offers a somewhat impractical workaround. Rather, the definitive solution is below.
This three step solution removes Window’s 32-bit PCIe allocation constraint in order to resolve the eGPU error 12:
Step 1. Create a dsdt-modified.aml DSDT file with a 36-bit root bridge
Step 2. Load your dsdt-modified.aml as registry override or in-memory substitution
Step 3. Confirm success with a ‘Large Memory’ area in Device Manager
macOS users: refer instead to Mikeal’s post that covers these steps titled Windows 10 – Clover DSDT memory override [UEFI Windows on Macbooks only].
| Step 1. Create a dsdt-modified.aml DSDT file with a 36-bit root bridge |
i. Download and install required tools:
- Windows Binary Tools (WBT – Dec 2016) extracted to c:\dsdt directory. [ newer WBT has parsing errors]
- Windows Driver Kit (WDK), which contains the Windows ASL Compiler (asl.exe)
- Notepad++ text editor with Search->Goto (line) menu for fast line editting if asl or iasl compilation fails below
ii. Copy WDK’s ASL compiler into the c:\dsdt directory. Do this by opening Command Prompt (run as administrator) and then copy-and-paste the commands below.
mkdir c:\dsdt c: & cd \dsdt set 64bit_OS_asl="C:\Program Files (x86)\Windows Kits\10\Tools\x64\ACPIVerify\asl.exe" set 32bit_OS_asl="C:\Program Files (x86)\Windows Kits\10\Tools\x86\ACPIVerify\asl.exe" copy /y %32bit_OS_asl% c:\dsdt > nul & copy /y %64bit_OS_asl% c:\dsdt > nul if not exist c:\dsdt\asl.exe echo ERROR: Failed to copy asl.exe to c:\dsdt
iii. Dump your ACPI tables to disk files (dsdt.asl and dsdt.dat) with these commands at Command Prompt (run as administrator). The created dsdt.asl is copied here as dsdt-modified.asl which is used later on to make our required modifications.
c: & cd \dsdt acpidump -b -z asl /u dsdt.dat copy dsdt.asl dsdt-modified.asl
iv. You now can choose either the Intel method or Microsoft method (with blue dsdt-modified.dsl or magenta dsdt-modified.asl work file respectively) to generate a dsdt-modified.aml file, even trying both to maximize success. Consider:
– For systems other than Lenovo, use the Intel method as their DSDT usually has an Intel creation signature.
– Lenovo Thinkpad X220, T420, W530, T540P and likely other 2nd-4th gen i-core Lenovo Thinkpad systems are known to require the Microsoft method . The Intel method causes a “ACPI BIOS ERROR” on Windows bootup there.
OPTION 1: Use the Intel method
i. Save this >> refs.txt file << to your c:\dsdt folder. What is it used for? From tonymacx86: The iasl disassembler will attempt to guess the number of arguments [for unresolved symbols not defined in any file] but often guesses poorly. You can correct it by providing the external declarations in a refs.txt text file. It contains some common (and not so common) missing symbols . . .
ii. From the Command Prompt (admin), decompile dsdt.dat as dsdt.dsl . The refs.txt file is used here. dsdt.dsl is then copied as dsdt-modified.dsl on which we’ll make the required changes on.
c: & cd \dsdt iasl -da -dl -fe refs.txt dsdt.dat copy dsdt.dsl dsdt-modified.dsl
iii. With Notepad++, open the resultant c:\dsdt\dsdt-modified.dsl file and search for ResourceProducer. Beneath it will be a series of “DWordMemory” resource entries. Under the last DWordMemory entry in that area, typically above the _CRS method, add a ‘QWordMemory’ (64-bit) entry as shown in red below. The range chosen is in the 36-bit range (< 64GB) to maintain compatibility with PAE-capable 32-bit Windows. A location above 48GB was chosen to alleviate issues with 32GB equipped systems. Here we use between 48.5GB to 56.25GB. Once systems start shipping with 64GB of RAM, this will need to be revised to use a 64-bit address.
DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, // Granularity 0x000A0000, // Range Minimum 0x000BFFFF, // Range Maximum 0x00000000, // Translation Offset 0x00020000, // Length ,, , AddressRangeMemory, TypeStatic) QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x0000000000000000, // Granularity 0x0000000C20000000, // Range Minimum, set it to 48.5GB 0x0000000E0FFFFFFF, // Range Maximum, set it to 56.25GB 0x0000000000000000, // Translation Offset 0x00000001F0000000, // Length calculated by Range Max - Range Min. ,, , AddressRangeMemory, TypeStatic) }) Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings
iv. Create a dsdt-modified.aml file . The ‘-ve’ disables warning messages.
c: & cd \dsdt iasl -ve dsdt-modified.dsl
It is unlikely this will succeed first time as the compiler is very strict. Errors reported will need to be looked at with Notepad++ on the line they occur on. Search for a unique error keyword from your dsdt-modified.dsl error line within dsdt-modified.asl (it may look a bit different) and the just swap the lines above/below into your dsdt-modified.dsl file and compile. This was sufficient to get a Dell XPS 9350, Dell E6540, 2016 15″ Macbook Pro DSDT override all done perfectly.
If stuck then see eGPU.io’s public pre-compiled DSDT repository for various systems. If one exists for your system then can download it along with Winmerge to merge the file changes into your dsdt-modified.dsl work file. There are also other fixes like described at [Guide] Patching LAPTOP DSDT/SSDTs (tonymacx86). Consider also asking for guidance at the DSDT-centric tonymacx86.com DSDT forums . Then try compiling your DSDT again.
v . Proceed to Step 2 to load your dsdt-modified.aml file.
OPTION 2: Use the Microsoft method
i. With Notepad++, find the working area in your c:\dsdt\dsdt-modified.asl file as shown in screenshots below. In that area, make the following two edits. These are annonated in those screenshots.
EDIT 1: use Windows’ calc in programmers mode to add hexidecimal 2E (46 decimal) to your “Buffer(value)” line. Examples:
- “Buffer(0x1C0)” becomes “Buffer(0x1EE)”
- “Buffer(0x1D4)” becomes “Buffer(0x202)”
EDIT 2: replace “0x79, 0x00” in the hex table end with the following 46 hex values, also ending with “0x79, 0x00”. This adds the same 36-bit QWordMemory resource entry shown in the Intel method but as a hex table.
[ copy-and-paste this table ]
0x8a, 0x2b, 0x00, 0x00, 0x0c, 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x20, 0x0c, 0x00, 0x00, 0x00, 0xff, 0xff, 0xff, 0x0f, 0x0e, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xf0, 0x01, 0x00, 0x00, 0x00, 0x79, 0x00
For Lenovo Systems [ CLICK on images to zoom ]
 |
|
For other systems [ CLICK on images to zoom ]
 |
|
ii. At the Command Prompt (admin), compile your dsdt-modified.asl file to generate a dsdt-modified.aml file:
c: & cd \dsdt asl /Fo=dsdt-modified.aml dsdt-modified.asl
This will almost certainly fail to generate a dsdt-modified.aml on your first compile attempt due to to error lines requiring further editting of your dsdt-modified.asl file, like the ones below (further example here), followed by another compile attempt. A successful compilation with many warnings is OK.
– ATMC() – error: ATMC is not a method -> swap ATMC with \_SB_.PCI0.LPC_.EC__.ATMC()
– Zero – error: unexpected ASL term type -> add ‘Zero’ as bracketted argument to line above it, eg: GLIS (Zero)
– Arg0 – error: unexpected ASL term type -> add ‘Argo0’ as bracketted argument to line above it, eg: GDCK (Arg0)
iii. Open c:\dsdt with Windows explorer. Compare the size of your created dsdt-modified.aml file against the memory dumped dsdt.dat. They should be within +/- 10% of each other in size. If not, repeat the above process to make sure no mistakes were made.
A HP Elitebook 8440P saw the generated dsdt-modified.aml being only 15% the size of the memory dumped dsdt.dat. There this process simply did not work. For such cases use the Intel method instead.
iv . Proceed to Step 2 to load your dsdt-modified.aml file.
| Step 2. Load your dsdt-modified.aml as a registry override or in-memory substitution |
OPTION 1: Load your dsdt-modified.aml as a registry override with Windows test signing mode enabled
Here we load your dsdt-modified.aml as Windows registry DSDT override. Do note that an invalid dsdt-modified.aml loaded in this way can cause a BSOD on bootup. Furthermore, Windows test signing mode can be problematic for app compatibility. Both these issues can be avoided by using OPTION 2: Load your dsdt-modified.aml as an in-memory DSDT substitution.
i. At Command Prompt (admin) type the following. WDK containing asl.exe must be installed per Step 1 (i) and (ii) for this to work.
c: & cd \dsdt asl /loadtable dsdt-modified.aml
ii. Enable TESTSIGNING mode for the registry override to apply. At the Command Prompt (admin) type:
bcdedit -set TESTSIGNING ON
If get an error like below when do this, then disable SECURE BOOT in your BIOS.
An error has occurred setting the element data
The value is protected by Secure Boot policy and cannot be modified or deleted
iii. Reboot your system and check for ‘large memory’ in step 3.
OPTION 2: Load your dsdt-modified.aml as an in memory DSDT substitution
Here we avoid the problematic registry override & test signing mode altogether by loading the DSDT as an in-memory substitution before Windows loads with these steps:
i. Disable the previous registry DSDT override and test signing mode.
bcdedit -set TESTSIGNING OFF
ii. check whether you are using a MBR or UEFI Windows installation by viewing Device Manager->Disk Drives->[double-click boot drive]->Volumes->Populate->Partition Style. If it says “MBR”, then it’s a MBR install. If it says “GPT” then it’s a UEFI install. This will determine which next step to apply.
iii. [ MBR mode ] Load the dsdt-modified.aml as an in-memory substitution via DIY eGPU Setup 1.35 in the next post.
iv. [ UEFI mode] Load the dsdt-modified.aml as an in-memory substitution via Clover bootloader as follows:
BIG WARNING by nando4 >> @Goalque has correctly identified that Clover loads a DSDT table in firmware volume and as such can brick a Macbook as this user found. If you proceed with using Clover to do a DSDT override the you do so at your own risk!! For risk-adverse users it is suggested to simply do a DSDT registry override and persevere with Windows’ test signing mode until other solutions are found and presented.
– Mount your EFI volume as s: drive and backup your existing \EFI\BOOT\BOOTX64.efi file. At Command Prompt (admin) type:
mountvol s: /s
copy s:\EFI\BOOT\BOOTX64.efi s:\EFI\BOOT\BOOTX64.win
– Download the Clover ISO file and install it by extracting with 7-zip (64-bit only) the clover.tar.lzma->clover.tar->clover.pkg->\EFI folder to s:\EFI. Be sure to use the the 7-zip interface to extract to s: drive as Windows explorer refuses to allow viewing of the s: EFI volume.
– Copy your dsdt-modified.aml file as dsdt.aml to s:\EFI\CLOVER\ACPI\Windows, the directory Clover uses to preload it. If your source dsdt-modified.aml file is not in c:\dsdt then use this workaround to copy-and-paste it. Locate your dsdt-modified.aml file with Explorer, right-click, rename to dsdt.aml, right-click, copy. Then hit CTRL+ALT+DEL, task manager, File->New task. Explore the s:\EFI\CLOVER\ACPI\WINDOWS directory and paste it there.
Otherwise at the Command Prompt (admin) type:
copy c:\dsdt\dsdt-modified.aml s:\EFI\CLOVER\ACPI\WINDOWS\dsdt.aml
– Reboot via Clover -> Windows EFI menu and proceed to step 3 to confirm it worked.
| Step 3. Confirm success with a ‘large memory’ area in Device Manager |
Check you now have a new Large Memory entry in Device Manager as shown below to confirm your dsdt-modified.aml was a success:
| Success stories |
nando4 – HP ZBook 17 G2 + AKiTiO Thunder2 + GTX970. SUCCESS! Allocated the eGPU into 36-bit space.
Mikeal – 2016 15″ Macbook Pro + Razer Core + GTX1070. SUCCESS! Allocated the eGPU into 36-bit space.
theitsage – 2016 13″ Macbook Pro + AKiTiO Thunder3 + GTX980Ti. SUCCESS! Allocated the eGPU into 36-bit space.
batist – 2013 15″ Lenovo T540 + EXP GDC + GTX680. SUCCESS! Allocated the eGPU into 36-bit space.
| FAQ |
1. I still have an error 12 with the ‘large memory’ area present. How can I fix it?
i. [MBR only] Force allocate the eGPU into 36-bit PCI space before booting Windows with DIY eGPU Setup 1.35 software:
- At Windows boot menu, select Setup 1.35
- Boot Setup 1.35 -> menu-based
- Select PCI compaction->Endpoint=56.25GB (36-bit)
- Select PCI compaction->Run compact. When prompted for the scope select eGPU.
- Select Chainloader->Test Run
- At Windows boot menu, select Windows.
Your result will be then be like shown in step 3 above, but you’ll have the eGPU rather then the (example) HD8790M dGPU allocated into 36-bit PCI space.
ii. Use the bcdedit forcedisable option to override the advanced PCI Express features and use legacy PCI Express behavior as explained by Microsoft. madjester confirmed this fixed error 12 on 2015 13″ MBP after doing a DSDT override here (thank you!)
bcdedit.exe -set PCIEXPRESS FORCEDISABLE
iii. Re plug’n’play the devices. Go into Device Manager -> Video cards, delete the eGPU. Also go into Device Manager -> System devices and delete the PCI Express Root Port x entries.
Window should now be clever enough to re-allocate the eGPU into 36-bit space upon realizing there is insufficient 32-bit space to host it.
Can go one step further and delete your eGPU NVidia/ATiAMD driver, restart the system and reload it. That may help as well.
iv. From here:
- remove all of the devices in Device Manager – Resources using the large memory space (All of the ones with a blue icon – not the USB icon one!)
- Hot Plug the eGPU (Within a few minutes the eGPU will be usable without error 12 and the other devices will also come back and start working again)
- Everything should work
2. How do I disable the registry DSDT override?
The easiest method is to disable TESTSIGNING. If your system fails to boot with the DSDT override in place then boot in Safe Mode and disable TEST SIGNING.
bcdedit -set TESTSIGNING OFF
Remove the DSDT override from the registry:
c: & cd\dsdt asl /loadtable -d dsdt-modified.aml
.. or remove this DSDT key in the registry. Windows will create a new one derived from your system bootup ACPI DSDT table upon restart:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\services\ACPI\Parameters\DSDT
* where XXX are 001, 002, 003 & so on.
and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ACPI\Parameters\DSDTfcho
GUIDE: an in-memory DSDT override using DIY eGPU Setup 1.35 [MBR partitions only]
Windows 10 or 8 enumerates the DSDT table from the in-memory copy on every boot. The only way to change that is to either:
– perform a registry DSDT override with test signing enabled as described in the above post. Do not that some apps are either problematic or refuse to run with test signing enabled.
– perform an in-memory DSDT table substitution using the DIY eGPU Setup 1.35 pre-boot environment which eliminates the need to alter your registry or enable test signing as explained in this post.
| How to do a in-memory DSDT override using DIY eGPU Setup 1.35? |
Pre-requisite requirements
|
How to load your dsdt-modified.aml via DIY eGPU Setup 1.35
1. Copy your dsdt-modified.aml file as dsdt.aml into Setup 1.35’s v:\config directory
:: Mount the Setup 1.35 disk image as V: drive c:\eGPU\eGPU-setup-mount copy c:\dsdt\dsdt-modified.aml v:\config\dsdt.aml
2. Boot DIY eGPU Setup 1.35 -> automated startup via startup.bat (default).
It will automatically load this dsdt.aml file and present the Windows bootloader where you then select Windows. Check for the ‘Large Memory’ area to indicate a successful in-memory DSDT override like shown below in View->Devices By Connection. Then check for error 12 against your eGPU..
3. If there is an error 12. then force allocate the eGPU into the DSDT override’s 36-bit PCI space:
- At Windows boot menu, select Setup 1.35
- Boot Setup 1.35 -> menu-based
- Select PCI compaction->Endpoint=56.25GB (36-bit)
- Select PCI compaction->Run compact. When prompted for the scope select eGPU, force 32-bit=none.
- Select startup.bat->Test Run.
- Select Chainloader->Test Run
- At Windows boot menu, select Windows.
| Does this work? |
Yes. Below we see the new ‘Large Memory Area’ indicating the PCI BUS now extends into 36-bit PCI space with the iGPU (didn’t have an eGPU at hand) relocated into that 36-bit space.
Hello there! 🙂 no problem.
@nando4 I still have the same problem.. the eGpu insists to connect to other Pci root port, instead the one created under the large memory… What should I do?
I already unistall all the ports, the eGPU and the nvidia drivers, but it still not connect to the large memory..
Posted by: Yukikaze
Samuel, I think that Setup 1.35 should be able to fix that, because I believe you can force it to allocate the eGPU to the large/high memory area. I am not sure if there is a way to do it without Setup 1.35, but nando might know how to.
If the eGPU won’t auto-allocate to the ‘Large Memory’ area, then revert to using eGPU Setup 1.35 software to hard allocate it in a pre-boot environment.
@everyone, the opening post is presented with an up-to-date DSDT override example using a 4th gen i-core Dell E6540. Unfortunately previous discussion was deleted along with the thread due to an offsite issue. Sincerest apologies there.
Thank you Nando4! I was able to solve Error 12 on the 2016 15″ MacBook Pro following your DSDT Override instructions. No BSOD and Large Memory shows up in Device Manager.
Thanks @nando4, that did the trick It wouldn’t run without setup 1.35 and compacting. After 2 days of tinkering with DSDT. I needed to cut “If (COND) FPED” statement and paste to where OS’s are listed. Also added QWORD. Now that I know what I’m doing it’s 2 min.
For reference my config is HP 2570p (i5 3360m) – Win 10 x64 + Asus GTX 1060 6GB Turbo + EXP GDC V8 ExpressCard PCIe x2 + 8GB 1600Mhz. Witcher 3 on Ultra Avg 40-50FPS 1080p.
Many thanks
Sobi
In my experience with my X230 and an Expresscard eGPU, the latest Lenovo X230 BIOS has no TOLUD problems. My HD7950 worked with it without any DSDT overrides or any Setup1.3x remapping of the eGPU. As far as I know, though, the X220 never got such a BIOS update.
"Dire Wolf II" - HP ZBook 15 G4: Core i7-7820HQ, 32GB, M1200 dGPU, R9 Fury@32Gbps-TB3 (Mantiz Venus) eGPU, HP Z27q (5K) + Dell P2715Q (4K).
"Stormcrow" - Lenovo T430s: Core i7-3520M, 8GB, GTX1050Ti@10Gbps-TB1 (AKiTiO Thunder2) eGPU, Sony 4K TV.
Always listen to experts. They'll tell you what can't be done, and why. Then do it.- Robert A. Heinlein, "Time Enough for Love."
GUIDE: an in-memory DSDT override using MaciASL+ Clover [UEFI Windows on Macbooks only]
here ◄ is Mikeal’s updated second revision of this article
BIG WARNING by nando4 >> @Goalque has correctly identified that Clover loads a DSDT table in firmware volume and as such can brick a Macbook as this user found. If you proceed with using Clover to do a DSDT override the you do so at your own risk!! For risk-adverse users it is suggested to simply do a DSDT registry override and persevere with Windows’ test signing mode until other solutions are found and presented.
I have this working on a 2016 15″ Macbook Pro MBP w/touch RX460 1TB with Clover loading a modified DSDT and the problematic Win10 test signing disabled. Thank you to nando4 for pointing out using Clover for DSDT link for UEFI installations, instructions in the opening post and formatting this post.
1. Boot into Windows and disable test mode if enabled using Command Prompt (admin)
bcdedit -set TESTSIGNING OFF
2. Reboot into macOS. Install / Load MaciASL. We will use MaciASL in MacOS to extract, edit, and compile the DSDT table.
3. Make the QWordMemory modification as detailed in opening thread post, copied here:
Search for “ResourceProducer”. Beneath it will be a series of “DWordMemory” resource entries. Under the last DWordMemory entry in that area, typically above the _CRS method, add a ‘QWordMemory’ (64-bit) entry as shown in red below. The range chosen is in the 36-bit range (< 64GB) to maintain compatibility with the PAE-capable 32-bit Windows. A location above 48GB was chosen to alleviate issues with 32GB equipped systems. Here we use between 48.5GB to 56.25GB. Once systems start shipping with 64GB, this will need to be revised to 64-bit space.
DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, // Granularity 0x000A0000, // Range Minimum 0x000BFFFF, // Range Maximum 0x00000000, // Translation Offset 0x00020000, // Length ,, , AddressRangeMemory, TypeStatic) QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x0000000000000000, // Granularity 0x0000000C20000000, // Range Minimum, set it to 48.5GB 0x0000000E0FFFFFFF, // Range Maximum, set it to 56.25GB 0x0000000000000000, // Translation Offset 0x00000001F0000000, // Length calculated by Range Max - Range Min. ,, , AddressRangeMemory, TypeStatic) }) Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings
Save as DSDT.aml
5. Insert / automount a usb drive
6. Run the Clover package installer, and select the USB drive as the destination drive
7. Open Terminal:
sudo bash mkdir /Volumes/EFI mount -t msdos /dev/disk0s1 /Volumes/EFI
leave this window open
8. Open Finder
Look for the usb device, go into the EFI folder, copy the CLOVER folder
Paste CLOVER folder into /Volumes/EFI/EFI/
9. Go back to the elevated terminal window and copy your DSDL.aml file to /Volumes/EFI/EFI/CLOVER/ACPI/WINDOWS. Alternatively, use Finder to copy-and-paste your dsdt.aml file there.
cp ~/Documents/DSDT.aml /Volumes/EFI/EFI/CLOVER/ACPI/WINDOWS
The final file structure looking like this:
10. Reboot into Clover, select Windows, /clap && open beer to celebrate full Windows (no test signing mode) & eGPU functionality with ‘large memory’ area in Device Manager to indicate DSDT override was a success.
[ click to zoom ]
Update: I still have an error 12 with the ‘large memory’ area present. How can I fix it?
i. Use the bcdedit forcedisable option to override the advanced PCI Express features and use legacy PCI Express behavior as explained by Microsoft. madjester confirmed this fixed error 12 on 2015 13″ MBP after doing a DSDT override here (thank you!)
bcdedit.exe -set PCIEXPRESS FORCEDISABLE
ii. Work through https://egpu.io/forums/mac-setup/2016-macbook-pro-solving-egpu-error-12-in-windows-10/
Update: my internal soundcard doesn’t work after applying this fix. What can I do?
See solution at https://egpu.io/forums/implementation-guides/2016-macbook-13-tb-akitio-thunder3-evga-gtx-1060-6gb/#post-2614
Just wanted to let you know how it went for me. I also have the late 2016 MacBook Pro 460. I tried Mikeal’s method and it worked perfectly.
However, one issue/side effect. If I boot up with both the Razer Core and the USB-C to USB adapter, it would give me the Code 12 Error. Only when I disconnected it and boot up with the RC, does it work. (to be clear, adapter with an usb device attached such as mouse or keyboard)
After booting up, you can connect the adapter normally.
It’s kinda weird or maybe something wrong with my system allocation but the adapter somehow screws up the reallocation.
Hope this helps.
Hi Devaspark,
Are you using the USB adapter on the same side the core is connected? I stopped using that one because I was having issues and thought it was because they shared the thunderbolt controller. I switched to a cheap ankar USB-C to 4 port USB 3.1 adapter on the other side. Even if the core side 2nd adapter was working for me, it got bad performance(Oculus complained about tracking). I have no problem running all 3 sensors and the Rift off the other side though.
Hi，Devaspark @ Devaspark
I have the Macbook pro 450 and I also use Mikeal’s way to deal with the problem of the Code 12 Error. However, I have the issue of the DSDT compilation. Do you have this error: code 4096, unexpected PARSEOP_IF, expecting“,”or”)”
If you have fixed the same errors, would you like to tell me how to do? Thank you.
Hi Steven
Are you using MaciASL as the editor? I had issues with other editors I used introducing errors, but MaciASL didn’t show any. If you’re following the reddit post for the guy that used the java client, he gave up and used MaciASL too he just didn’t post about it.
Is it normal to have internal speakers not functioning after the override? Everything works for me, but the audio…
Hi，Devaspark @ Devaspark
I have the Macbook pro 450 and I also use Mikeal’s way to deal with the problem of the Code 12 Error. However, I have the issue of the DSDT compilation. Do you have this error: code 4096, unexpected PARSEOP_IF, expecting“,”or”)”
If you have fixed the same errors, would you like to tell me how to do? Thank you.
I just moved the offending if statement on it’s own separate line as shown below. It compiled OK and theitsage confirmed (earlier) that loading the resultant dsdt.aml file as a registry override did result in the ‘large memory’ area appearing in Device Manager -> View -> Resources By Type, confirming it was a success.
Posted by: theitsage
@nando4 I’m trying this DSDT override on a 2016 15″ MBP but got 4 errors in Step 1. Can you give me a hand?
Compiler aborting due to parser-detected syntax error(s) dsdt.dsl 9794: 0x01020015, Zero), If (((Arg0 == 0x03) || (Arg0 == 0x04))) Error 6126 - ^ syntax error, unexpected PARSEOP_IF, expecting PARSEOP_CLOSE_PAREN or ',' dsdt.dsl 9795: { Error 6126 - ^ syntax error, unexpected '{' dsdt.dsl 9798: }) Error 6126 - ^ syntax error, unexpected PARSEOP_CLOSE_PAREN dsdt.dsl 9814: Error 6126 - syntax error, unexpected PARSEOP_METHOD, expecting $end and premature End-Of-File ASL Input: dsdt.dsl - 9814 lines, 313616 bytes, 3565 keywords Compilation complete. 4 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
I tried doing the windows way of modifying the dsdt and got roughly the same errors as other people reported. However, even when I fixed the error and and loaded it via windows method, I never could get rid of the error 12.
The only way way I was able to get it working was via the Maciasl way, which, when I extracted and modified it, did not have any errors.
i assume you did the windows way using the windows kit and all that?
If so, I recommend doing via Mac OS side via maciasl and save some of the trouble I had to go through. Hope that helps. It does take some time to install and get maciasl working but it’s a wayyyy smoother process.
Okay; so I finally got Clover installed (the method I had to follow was not described in any of the above posts; so I’m not sure how you guys did it — I had to exercise some of my own knowledge of the UEFI boot-process, and re-arrange 1. the pre-existing Apple EFI programs, and 2. the Clover EFI program). The DSDT patch took, and I’ve got the aforementioned “Large Memory” area in the Device Manager.
Unfortunately, this has changed nothing: the GTX 1080 is still Code 12’ing. I’ve tried the other above suggestions (right-click → ‘uninstall device’, checked the ‘uninstall drivers’ box, rebooted). No luck — after the drivers re-install, it’s still Code 12’ing. Nothing appears to have been allocated to the “Large Memory” area.
Is there any other ways to force Windows to allocate the graphics card to the newly-allocated 36-bit address-space? /=
The DSDT patch took, and I’ve got the aforementioned “Large Memory” area in the Device Manager.
Unfortunately, this has changed nothing: the GTX 1080 is still Code 12’ing. I’ve tried the other above suggestions (right-click → ‘uninstall device’, checked the ‘uninstall drivers’ box, rebooted). No luck — after the drivers re-install, it’s still Code 12’ing. Nothing appears to have been allocated to the “Large Memory” area.
Is there any other ways to force Windows to allocate the graphics card to the newly-allocated 36-bit address-space? /=
Some additional techniques for solving error 12 on Apple systems are given below:
1. https://egpu.io/forums/mac-setup/2016-macbook-pro-solving-egpu-error-12-in-windows-10/
2. Certain Macbooks, listed in the link, running MBR Windows can have error 12 solved with https://egpu.io/egpu-setup-13x/
Some additional techniques for solving error 12 on Apple systems are given below:
1. https://egpu.io/forums/mac-setup/2016-macbook-pro-solving-egpu-error-12-in-windows-10/
2. Certain Macbooks, listed in the link, running MBR Windows can have error 12 solved with https://egpu.io/egpu-setup-13x/
Unfortunately, most of those tricks seem to be for MBR-formatted MacBooks? On new hardware like the Mac Pro and the 2016 Macbook Pro (like mine), Bootcamp doesn’t create a hybrid-MBR; it sets up a UEFI boot of Windows.
As for the ‘uninstall the root-bridge’ one … like I said, just tried that one (although there’s nothing called a “root bridge,” nor any “downstream ports” like in the screenshot, on the 15″ Macbook Pro — I just tried to emulate the same process on the “PCI-to-PCI Bridge” entries that show up on my installation.)
I’m running out of things to try!
(If anyone else is trying to do this over the next few days, feel free to come chat in realtime on Freenode: http://ell.io/IRC . Name there is the same as here — if I don’t respond immediately, leave the window open, and I’ll reply when I’m at the computer.)
Okay, WTF: I get completely different results with each Thunderbolt port on my machine.
-
Rear-left: The behaviour I’ve been describing thus far — the Razer Core is recognized, and my “NVIDIA GeForce GTX 1080” shows up, but Code 12’s.
-
Front-left: Against all expectations, this works! I get display output rendering from my card, and it shows up in the Display preferences!
-
Rear-right, front-right: I just see a generic “Video Controller (VGA Compatible)”; Windows claims there are no drivers installed for it.
Worse, when the Core is plugged into the right-hand ports, my system becomes extremely unstable: the Windows install goes black and reboots, without any warning, a few moments after logging in. (I think it’s trying to install a driver and failing?)
So, it’s a great step forward that it renders, at least from one port; unfortunately, that port isn’t reachable from the final install location of my Core (damned short Thunderbolt 3 active cabling!) … so I gotta figure out why the right-hand ports are crashing Windows.
My next step is probably a reinstall from scratch, I suspect. If I do get this working, I’m going to write my own tutorial, including actual instructions for installing Clover. 😛
Hi nando4 and Mikeal，thank you for your guys’ help and I can use my razer core now.
And after many times tries, I want to say that the method of Mikeal is good and it is very easy to success. However, I still have the issue of the Step 9 which I followed first time but the error 12 still have and there was no large memory.
So, after the step 9, I did one more step: copy the DSDT.aml from the Documents and paste it directly to the USB driver–EFI–CLOVER–ACPI–WINDOWS
I hope this can be helpful for some people.
@ElliottCable I’ve had mixed results with the ports as well. The right side seems to work best for me, and running nothing else off that thunderbolt controller. That is where I originally had it plugged in. Using the other side gives me the VGA device showing as you had.
Also the boot issue with clover might be because I previously had refind installed.
Hey Nando4,
I managed to do it! The large memory is there and all! Which is great. But it still doesn’t work :/ unsure why
Current setup: Late 2016 Razer Blade Stealth, Powercolour devil box + gtx 1060
Prev setup: 2016 13" MBP (no touchbar)
Powercolor Devil Box + GTX 1060/GTX 980(succeeded somewhat), RX480 Nitro+ 4GB(attempted but failed)
Another potential Code 12 fix. For my uncooporative 2015 13″ MBP, running “bcdedit.exe -set PCIEXPRESS FORCEDISABLE” (with the Graphics Card totally uninstalled) then installing the card fixed allocation (after a DSDT override.)
(Someone knowledgable should probably try this, discover pitfalls, explain why it works, all that.)
Another potential Code 12 fix. For my uncooporative 2015 13″ MBP, running “bcdedit.exe -set PCIEXPRESS FORCEDISABLE” (with the Graphics Card totally uninstalled) then installing the card fixed allocation (after a DSDT override.)
(Someone knowledgable should probably try this, discover pitfalls, explain why it works, all that.)
Nice work figuring that out. I’ve added it to the opening post linking your finding. Would you mind including your eGPU + notebook specs in your sig? I’m curious if it was with an AMD or NVidia card that this worked with.
Will do, full post on the Mac side with details. Edit though, this is with the startup.nsh script also!
I got this working successfully after some finagling. Each port appears to act different. My back left port even allows for hot plugging! My only issue, which I’m hoping someone can help with, is I need to use the USB to access Clover every time. The large memory disappears if I skip booting through Clover on the USB (which makes sense if I follow how this works correctly), but it looked like 7-9 were supposed to enable Clover without the USB.
If I didn’t explain this clearly, I’d be happy to provide more explanation. To summarize, the Clover edit still requires the USB. Thank you for the help! Also, if there are any questions about how I got mine working, I’d be happy to provide information!
Hitting OPTION before booting would presumably give the Macbook several EFI items you can choose. Just work through them one at a time until same Clover screen appears instead of Windows. It’s unmistakeable when Clover boots.
I am sorry for not explaining this better. When the USB is plugged in, Clover is a boot option when viewing the EFI items. However, when the USB is removed, the option disappears, and the only other option is the “vanilla” Windows option.
I just checked, and the /Volumes/EFI directory gets deleted on reboot, which explains why Clover is not an option on boot. I do not, however, know what is causing macOS to decide to remove this directory. To be clear, after performing the steps there is a /Volumes/EFI folder, then, after reboot, there is no longer a /Volumes/EFI folder.
Edit: diskutil list is showing EFI as present. Now to just figure out how to get this to show up in the boot menu.. I will trouble shoot
@JasonConig, the /Volumes/EFI directory is only deleted because you were using it as a mount point. If you remake the directory, and remount it, all the same information will be in it.
I copied the clover folder from the USB, into /Volumes/EFI/EFI/Clover. After you make the DSDT related changes copy that folder into /Volumes/EFI/EFI/boot. This will give you the clover boot loader option every time you reboot. If I want to go into OS X and I was last in windows, I reboot and hold the option key then select the macox drive (which is my only selection in that menu now).
I subscribed to the thread now didn’t realize I wasn’t getting notified.
Hi, I’m new here and I followed the steps and could successfully run the Akitio Node on my MacBook pro 13″ early 2015 and could run games with no problems. But I found that after I had restarted my laptop, I received errors like IRQL_NOT_LESS_OR_EQUAL when starting up and had no luck getting it back to work ever since. Any ideas?
Hi, I’m new here and I followed the steps and could successfully run the Akitio Node on my MacBook pro 13″ early 2015 and could run games with no problems. But I found that after I had restarted my laptop, I received errors like IRQL_NOT_LESS_OR_EQUAL when starting up and had no luck getting it back to work ever since. Any ideas?
If there is a mismatch between the DSDT override and your current system bootup state then this could occur. So.. reset NVRAM, disable the DSDT override and re-create it.
Here’s where it is useful to have the Clover method working as don’t need to wrestle with recovering Windows back into a working state.
Working