late-2016 13" Macbo...
 
Share:

late-2016 13" Macbook Pro + [email protected] + Win10 [ultraman982]^  

  RSS

ultraman982
(@ultraman982)
Active Member
Joined: 2 years ago
Posts: 5
January 14, 2017 8:34 am  

Hello!

I've been lurking for a while but finally got my Razer Core in the mail! As in the title I have the emoji bar 13'' and a 1060.

Setup for me was as follows:

  1. Simply connected Razer Core when in Bootcamp (Windows 10)
  2. Installed Nvidia drivers
  3. Works...sort of.

I've noticed some strange issues which I haven't seen reported (despite seeing similar setups), and am curious if others have seen them or have solutions to them.

  1. I can't seem to get hot plugging to work. The only way the setup works is if I boot into Windows with the core connected. Connecting the core while in Windows cause an occasional bluescreen, but a guaranteed reboot.
  2. My internal display is useless. I've seen people extend or mirror their displays, but this has never worked for me. My internal screen is either fully black or has a windows logo. There seems to be no guaranteed state, which is odd. To make things worse--I've had a crash where the windows logo was burned into my LCD (in OSX even) and needed to run my screensaver overnight to fix.

For the most part I'm happy with the setup though. I haven't done any benchmarks but have run Witcher 2 and 3 at high/max settings @ 1440p. If anyone has a free benchmark I can use I would be happy to install and post scores.

Anyone have any ideas here re: my issues? I didn't do DSDT, but don't think its necessary (only a 3GB card). Hot plugging is not a big deal, though I've seen it reported working. I'm most curious about the useless internal display--which I haven't seen any other cases of online. Any help is much appreciated.

Obligatory setup pic:
IMG 2271
Useless internal display (stuck Windows logo):
IMG 2274
Burn in on OSX (scariest moment when you think you've broken a $2000 laptop):
IMG 2269

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


Quote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1870
January 14, 2017 9:09 am  

Looking like a sweet eGPU implementation there 🙂

For your black internal LCD issue in Windows, pls work through this thread: https://egpu.io/forums/mac-setup/how-to-keep-mbps-irisiris-pro-activated-when-booting-into-windows-boot-camp/

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
ultraman982
(@ultraman982)
Active Member
Joined: 2 years ago
Posts: 5
January 15, 2017 1:51 am  

So the instructions above worked, in that when I boot into Windows 10--I see the Intel Integrated Graphics as my display device (when the core is connected). But despite my Razer core being connected / active--it doesn't show up in device manager. 

Because hot plugging crashes Windows--it looks like the key to getting the internal display working is figuring out hot plugging, that way I can boot with apple_set_os.efi then hot plug to have 2 display devices. (Similar to how eGPU on the 15'' MBP shows the dedicated graphics along with the external in the device manager).

Going to try doing DSDT since those who have hot plugging working seem to have done this--will update with more details.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
ultraman982
(@ultraman982)
Active Member
Joined: 2 years ago
Posts: 5
January 15, 2017 3:18 am  

Update: I ended up doing the DSDT and can see the newly added "Large Memory" ... this didn't seem to help any of the issues though.

Strangely enough the Large Memory never shows as allocated for the eGPU or Intel Iris for that matter. Doing a .efi boot will give me Iris, but hot plugging still leaves me with a lovely BSOD.

State of device manager post .efi boot, hotplugging renders crash--I can see two display devices for 3-4 seconds before BSOD:
post efi boot

Unallocated Large memory. Never allocated, even when eGPU is connected or Integrated Graphics are in use:
unallocated large memory

BSOD which occurs after any hot plugging no matter what. Including .efi boot, even with DSDT:
IMG 2282

Anyone have any ideas here? Maybe it's easier to eGPU on the 15'' in Windows because of the dGPU. @nando4...I saw your eGPU setup tool, could it help my usecase in anyway?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Trajans Row
(@trajans-row)
Active Member
Joined: 2 years ago
Posts: 18
January 16, 2017 2:53 pm  

I have a similar config with an EVGA 6GB GTX 1060 in a Razer Core connected to a 13" tMBP.

 
To use the internal LCD, I've always needed to connect the Core immediately after the Windows logo appears during boot. I've not had any issues with that (aside from the inconvenience. I might try that fix nando4 linked to.). Does hot-plugging during boot work for your setup?

 
Interestingly, that blue screen corruption is exactly the same thing that I see if I plug in my thunderbolt display while using the Core. I'm probably going to need to ditch that thing in favor of something with displayport. 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
blackdoo996
(@blackdoo996)
Active Member
Joined: 2 years ago
Posts: 13
January 25, 2017 6:08 am  
Posted by: Trajans Row

 

I have a similar config with an EVGA 6GB GTX 1060 in a Razer Core connected to a 13" tMBP.

 
To use the internal LCD, I've always needed to connect the Core immediately after the Windows logo appears during boot. I've not had any issues with that (aside from the inconvenience. I might try that fix nando4 linked to.). Does hot-plugging during boot work for your setup?

 
Interestingly, that blue screen corruption is exactly the same thing that I see if I plug in my thunderbolt display while using the Core. I'm probably going to need to ditch that thing in favor of something with displayport. 

   

My problem with you, with your method I successfully entered the windows. But the sound driven out of the question, need to prohibit the use, and then enable, after a sound. You have encountered such a situation?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1870
January 25, 2017 9:52 am  
Posted by: blackdoo996

 

My problem with you, with your method I successfully entered the windows. But the sound driven out of the question, need to prohibit the use, and then enable, after a sound. You have encountered such a situation?

 

Are you saying sound is not working, requiring disabling then re-enabling in Device Manager to fix? That can be automated:

1. Download and install  Windows 10 WDK
2.  Then run commands in bold like below to disable then re-enable your AUDIO devices:

cd \Program Files (x86)\Windows Kits\10\Tools\x64

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon disable *audio*

SWD\MMDEVAPI\{0.0.0.00000000}.{3B11890E-048A-45E7-BFB4-0B8D5A211327}: Disabled
SWD\MMDEVAPI\{0.0.1.00000000}.{87E01770-2F5C-4F53-A6DF-B013046945AF}: Disabled
HDAUDIO\FUNC_01&VEN_10EC&DEV_0292&SUBSYS_102805BE&REV_1000\4&B62E94A&0&0001: Disabled on reboot
SWD\MMDEVAPI\{0.0.0.00000000}.{393BEF20-CDE3-49A9-BE7A-774FC0A67348}: Disabled
The 4 device(s) are ready to be disabled. To disable the devices, restart the
devices or reboot the system .

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon enable *audio*

SWD\MMDEVAPI\{0.0.0.00000000}.{3B11890E-048A-45E7-BFB4-0B8D5A211327}: Enabled
SWD\MMDEVAPI\{0.0.1.00000000}.{87E01770-2F5C-4F53-A6DF-B013046945AF}: Enabled
HDAUDIO\FUNC_01&VEN_10EC&DEV_0292&SUBSYS_102805BE&REV_1000\4&B62E94A&0&0001: Enabled on reboot
SWD\MMDEVAPI\{0.0.0.00000000}.{393BEF20-CDE3-49A9-BE7A-774FC0A67348}: Enabled
The 4 device(s) are ready to be enabled. To enable the devices, restart the devices or
reboot the system .

 

If happy with results, create a batch file that does this, copy it to C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup and check it run through OK with  Group Policy Editor (win+r, gpedit.msc) -> Computer configuration->Windows Settings->Scripts->Startup

 

If using Win10 Home, which doesn't have group policy startup/shutdown directories don't exist, then use the task scheduler instead to auto-start your batch file: http://www.thewindowsclub.com/autostart-programs-windows-10-make

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


3RYL liked
ReplyQuote
blackdoo996
(@blackdoo996)
Active Member
Joined: 2 years ago
Posts: 13
January 26, 2017 6:45 am  
Posted by: blackdoo996

 

What should i do?。。。。。

   

Successful, I use the cmd administrator

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon disable *audio*

HDAUDIO\FUNC_01&VEN_10DE&DEV_0083&SUBSYS_10DE119D&REV_1001\9&26CDBEAB&0&0001: Disabled

HDAUDIO\FUNC_01&VEN_1013&DEV_8409&SUBSYS_106B3600&REV_1001\4&A4C0FCF&0&0001: Disabled

HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101&REV_1000\4&A4C0FCF&0&0201: Disabled

SWD\MMDEVAPI\{0.0.1.00000000}.{07FB55ED-BDED-4E83-B85C-F49152427F54}: Disable failed

SWD\MMDEVAPI\{0.0.0.00000000}.{DAE993C9-4A7F-446D-A601-1837CA42833C}: Disable failed

3 device(s) disabled.

 

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon enable *audio*

HDAUDIO\FUNC_01&VEN_10DE&DEV_0083&SUBSYS_10DE119D&REV_1001\9&26CDBEAB&0&0001: Enabled

HDAUDIO\FUNC_01&VEN_1013&DEV_8409&SUBSYS_106B3600&REV_1001\4&A4C0FCF&0&0001: Enabled

HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101&REV_1000\4&A4C0FCF&0&0201: Enabled

3 device(s) are enabled.

 

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
blackdoo996
(@blackdoo996)
Active Member
Joined: 2 years ago
Posts: 13
January 26, 2017 7:17 am  
Posted by: nando4

 

Posted by: blackdoo996

 

My problem with you, with your method I successfully entered the windows. But the sound driven out of the question, need to prohibit the use, and then enable, after a sound. You have encountered such a situation?

 

Are you saying sound is not working, requiring re-enabling? That can be automated:

1. Download and install  Windows 10 WDK
2.  Then run commands in bold like below to disable then re-enable your AUDIO devices:

cd \Program Files (x86)\Windows Kits\10\Tools\x64

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon disable *audio*

SWD\MMDEVAPI\{0.0.0.00000000}.{3B11890E-048A-45E7-BFB4-0B8D5A211327}: Disabled
SWD\MMDEVAPI\{0.0.1.00000000}.{87E01770-2F5C-4F53-A6DF-B013046945AF}: Disabled
HDAUDIO\FUNC_01&VEN_10EC&DEV_0292&SUBSYS_102805BE&REV_1000\4&B62E94A&0&0001: Disabled on reboot
SWD\MMDEVAPI\{0.0.0.00000000}.{393BEF20-CDE3-49A9-BE7A-774FC0A67348}: Disabled
The 4 device(s) are ready to be disabled. To disable the devices, restart the
devices or reboot the system .

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon enable *audio*

SWD\MMDEVAPI\{0.0.0.00000000}.{3B11890E-048A-45E7-BFB4-0B8D5A211327}: Enabled
SWD\MMDEVAPI\{0.0.1.00000000}.{87E01770-2F5C-4F53-A6DF-B013046945AF}: Enabled
HDAUDIO\FUNC_01&VEN_10EC&DEV_0292&SUBSYS_102805BE&REV_1000\4&B62E94A&0&0001: Enabled on reboot
SWD\MMDEVAPI\{0.0.0.00000000}.{393BEF20-CDE3-49A9-BE7A-774FC0A67348}: Enabled
The 4 device(s) are ready to be enabled. To enable the devices, restart the devices or
reboot the system .

 

If happy with results, create a batch file that does this, copy it to C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup and check it run through OK with  Group Policy Editor (win+r, gpedit.msc) -> Computer configuration->Windows Settings->Scripts->Startup

   

thank you so so so so much!!!

Successful, after the resumption of normal can hear the sound..

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
haruhiku
(@haruhiku)
Active Member
Joined: 2 years ago
Posts: 6
March 2, 2017 10:05 pm  

Thanks for the information! I am very curious about the problem you mentioned that "I've had a crash where the windows logo was burned into my LCD (in OSX even) and needed to run my screensaver overnight to fix.". Is this problem fixable? How exactly did you fix it? I am going to try a similar egpu implementation with my MBP 13 2016 so I am also worried about this burn in issue...Thanks in advance.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Luminair
(@luminair)
Active Member
Joined: 2 years ago
Posts: 5
March 8, 2017 4:42 am  
Posted by: nando4

 

Posted by: blackdoo996

 

My problem with you, with your method I successfully entered the windows. But the sound driven out of the question, need to prohibit the use, and then enable, after a sound. You have encountered such a situation?

 

Are you saying sound is not working, requiring disabling then re-enabling in Device Manager to fix? That can be automated:

1. Download and install  Windows 10 WDK
2.  Then run commands in bold like below to disable then re-enable your AUDIO devices:

cd \Program Files (x86)\Windows Kits\10\Tools\x64

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon disable *audio*

SWD\MMDEVAPI\{0.0.0.00000000}.{3B11890E-048A-45E7-BFB4-0B8D5A211327}: Disabled
SWD\MMDEVAPI\{0.0.1.00000000}.{87E01770-2F5C-4F53-A6DF-B013046945AF}: Disabled
HDAUDIO\FUNC_01&VEN_10EC&DEV_0292&SUBSYS_102805BE&REV_1000\4&B62E94A&0&0001: Disabled on reboot
SWD\MMDEVAPI\{0.0.0.00000000}.{393BEF20-CDE3-49A9-BE7A-774FC0A67348}: Disabled
The 4 device(s) are ready to be disabled. To disable the devices, restart the
devices or reboot the system .

C:\Program Files (x86)\Windows Kits\10\Tools\x64>devcon enable *audio*

SWD\MMDEVAPI\{0.0.0.00000000}.{3B11890E-048A-45E7-BFB4-0B8D5A211327}: Enabled
SWD\MMDEVAPI\{0.0.1.00000000}.{87E01770-2F5C-4F53-A6DF-B013046945AF}: Enabled
HDAUDIO\FUNC_01&VEN_10EC&DEV_0292&SUBSYS_102805BE&REV_1000\4&B62E94A&0&0001: Enabled on reboot
SWD\MMDEVAPI\{0.0.0.00000000}.{393BEF20-CDE3-49A9-BE7A-774FC0A67348}: Enabled
The 4 device(s) are ready to be enabled. To enable the devices, restart the devices or
reboot the system .

 

If happy with results, create a batch file that does this, copy it to C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup and check it run through OK with  Group Policy Editor (win+r, gpedit.msc) -> Computer configuration->Windows Settings->Scripts->Startup

 

If using Win10 Home, which doesn't have group policy startup/shutdown directories don't exist, then use the task scheduler instead to auto-start your batch file: http://www.thewindowsclub.com/autostart-programs-windows-10-make

   

Unfortunately this process didn't enable my sound.  Do you have any other ideas?  I have an Akitio Thunder3 with a GTX 1060 plugged into a 13in 2016 Macbook Pro.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1870
March 8, 2017 5:29 am  
Posted by: Luminair

 

Unfortunately this process didn't enable my sound.  Do you have any other ideas?  I have an Akitio Thunder3 with a GTX 1060 plugged into a 13in 2016 Macbook Pro.   

The important point is whether enabling/disabling the sound device in Device Manager re-enables sound. If it does, then can automated that process via a script:  https://egpu.io/forums/builds/2016-macbook-13-tb-akitio-thunder3-evga-gtx-1060-6gb/#post-2614

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote