[GUIDE] DSDT override eGPU error 12 fix
 
Notifications
Clear all

[GUIDE] DSDT override eGPU error 12 fix  

 of  25
  RSS

Mikeal
(@mikeal)
Active Member
Joined: 3 years ago
 

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.  

2016 15" MacBook Pro (RP460) [6th,4C,H] + GTX 980 Ti @ 32Gbps-TB3 (Razer Core) + macOS 10.12 & Win10 [build link]  

ReplyQuote
Creativity
(@creativity)
Active Member
Joined: 3 years ago
 

Is it normal to have internal speakers not functioning after the override? Everything works for me, but the audio...

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

m3gefood liked
ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 4 years ago
 
Posted by: StevenOmg

 

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 itsage 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.

1483345772-MBPdsdtfix.png

Posted by: itsage

 

@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

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table

 
2015 15" Dell Precision 7510 (Q M1000M) [6th,4C,H] + GTX 1080 Ti @32Gbps-M2 (ADT-Link R43SG) + Win10 1803 [build link]  


ReplyQuote
Devaspark
(@devaspark)
New Member
Joined: 3 years ago
 

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.

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
StevenOmg
(@stevenomg)
New Member
Joined: 3 years ago
 

I follow all the steps but no thing happen. I can do all the steps except step 10, cuz I don't know choice which one to boot the system.  Should I boot with the clover and than chose the Microsoft from the EFI?  Thank you.Mikeal,nando4

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
ELLIOTTCABLE
(@ec)
New Member
Joined: 3 years ago
 

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? /=

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 4 years ago
 
Posted by: ELLIOTTCABLE

 

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/

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table

 
2015 15" Dell Precision 7510 (Q M1000M) [6th,4C,H] + GTX 1080 Ti @32Gbps-M2 (ADT-Link R43SG) + Win10 1803 [build link]  


ReplyQuote
ELLIOTTCABLE
(@ec)
New Member
Joined: 3 years ago
 
Posted by: nando4   

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.)

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
ELLIOTTCABLE
(@ec)
New Member
Joined: 3 years ago
 

Okay, WTF: I get completely different results with each Thunderbolt port on my machine.

  1. 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.

  2. Front-left: Against all expectations, this works! I get display output rendering from my card, and it shows up in the Display preferences!

  3. 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. 😛

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
StevenOmg
(@stevenomg)
New Member
Joined: 3 years ago
 

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. 

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

nando4 liked
ReplyQuote
 of  25