This message was posted on behalf of Intel Corporation
Thank you for joining the Intel® NUC community.
In order to have a better look of your case, please respond to the following;
- When you say that "it does work"; what do you mean? Do you mean that you do not have video from the dock?
- Can you please confirm if this Acer Graphics Dock brings external GPU support for notebooks - NotebookCheck.net News is the dock model you have?
- I would like to gather more information in regard to your system, so please provide me with the following report Download Intel® System Support Utility. Once done attach the report, to attach a file, you must click "Use Advanced Editor" in the top right corner of the response box, then the "attach" option will appear in the bottom right corner of the response box.
- Can you please test the NUC without the dock? This is just for testing purposes.
Hello and thank you for your time.
1) I mean that I do not have video output from the dock's display port, and also, I see a yellow triangle in device manager for NVIDIA GTX960m (in device properties I see error code 43).
2) Yes this is the correct dock.
3) I am attaching the system report run with and without the dock.
4) What do you want me to test. Please clarify.
The nuc works perfectly without the dock (I am using it to type this very message).
3dmark with only the integrated card is running fine. Video playback is fine (using VLC and PLEX). Sound from the display port is fine.
Also, please find attached the screenshot from thunderbolt manager from this NUC and one from my XPS 13 (9350)-the one that the dock works fine with.
1 of 1 people found this helpful
Same issue here with latest TB3 firmware (18), latest bios (41) and all drivers up to date.
The error i see in the log is:
Fehler bei der Treiberinstallation. Ergebnis = 0x8007045B für devnode "PCI\VEN_10DE&DEV_139B&SUBSYS_104A1025&REV_A2\8&82E3B93&0&0008000800E4".
I disabled fast startup, did reset the bios to defaults, uninstalled all nvidia drivers and re-installed the latest version 22.214.171.12470.
I disabled the usb energy saving options and even tried to play with TdrDdiDelay and TdrDelay under
without any success.
As the Acer Graphics Dock is working properly with the DELL XPS 13 under TB3 Firmware V16, i think the problem is related to some timing or energy based issues.
it would be interesting to test if older thunderbolt firmwares like version 16 would work with the graphics dock.
are there bin files available for the nuc with older firmwares than version 18 (KYK_TBT_FW_0018.bin) ?
dell is still using firmware version 16 with the latest controller drivers (126.96.36.1995) for the xps 13:
man it would be great if somebody from intel would join this discussion and help to solve this issue ;-)
the acer graphics dock is the only available eGPU product which is available in europe and it would be really cool if it would work with the nuc ;-)
1 of 1 people found this helpful
Yesterday evening i played with the bios settings and enabled "Native ACPI OS PCIe Support" under the Power-Tab.
After a reboot, the device manager structure changed and all the "PCI to PCI Bridges" changed to "PCI Express Up- and Downstream switch ports".
I re-installed the NVIDIA Drivers, then reconnected the Graphics Dock and for the first time, the GTX 960M was recognized without error 43 in the device manager.
But the NVIDIA Control Panel didn't start and also in GPU-Z and AIDA, the GTX 960M was listed with 1GB of memory and without any clock or memory rate.
Also after another restart nothing changed and the dock still couldn't be used.
I don't know if enabling "Native ACPI OS PCIe Support" is a good idea at all and what this means or if the device should work with those "PCI to PCI Bridges".
If it is necessary to enable "Native ACPI OS PCIe Support", then something else still seems to be missing to make the Dock working properly.
The glossary for the bios and google didn't gave any real explanation of what this option really does and when it should be enabled or disabled.
I really don't have any other ideas what else could be done to make this thing work.
Could be drivers, could be firmware, could be hardware, who knows?