I bought a NUC5CPYH yesterday and installed 8GB RAM and a SSD I still had. Installed Windows 10 and updated it completely. And then installed Kodi. Some finetuning and everything was up and running. The NUC is intended to be used as a 2nd mediaplayer upstairs. The first use of the NUC went flawlessly.

But today the NUC appears to be completely dead; it refuses to power on. I took it downstairs and plugged it into the power adapter, hdmi- and networkcable of my 1st NUC but still nothing. Okay, the power adapter isn't to blame.

But it appears strange to me that a perfectly running NUC now gives no sign of live at all. What to do next? Any suggestions about what to try next?

English is not my native language; I'm sorry for any errors.

Hello,

3 months ago I purchased 3 Intel® NUC Kit NUC5i5RYK's for my small business and installed windows 7 on them. I have concerns about daily errors found in Event Viewer, here are screenshots https://drive.google.com/open?id=0B6qjwL9857-NRXpVcGhnck5aWkh5eWtjRXhuQWpJNk5WLTVr , https://drive.google.com/open?id=0B6qjwL9857-NQUJvc2FzRUJMUjR2QVpoQVFxdzlnY2w1VW1Z .

I would like to resolve them with your help thank you.

I plan to use Virtual Machines in NUC6i7KYK, using Hyper-V and Docker, and it seems Windows Server 2016 supports Docker better, from what I understand. And maybe VM's in general in Server have more performance and more features with Server 2016.

Is it safe to use Windows Server 2016 or should I stick with Windows 10?

Trying to update my NUC5i5RYH from 0354 to 0361. Initially tried Flash method and it returns error message mentioning "incompatibility to interim BIOS". Next, tried F7 method. Procedure proceeds as described, file selected, but the unit quickly reboots without doing the update. Next, tried sequentially updating the BIOS with next version above starting version (F7 method) - same results. On one version I got some cryptic message about "incompatible header". Searching, I see many have this problem. 1st time using this site - it's so difficult to register and I'm not sure where the response will even be sent.

I work with several NUCi3RYH's. I was using one of them to build a master Window 10 image using audit mode/sysprep. I have 2 USB flash drives and an external USB hard drive that I use in this setup. One flash drive is the Windows 10 installation media, the other flash drive is bootable media for the disk imaging software I use, and the external hard drive is where I store the images. My NUCs boot in UEFI mode. Last night while attempting to reinstall Windows I noticed that the my Windows install flash drive was being detected as the imaging flash drive. The Windows install drive normally shows up in the boot menu as "Lexar USB Flash Drive 8.07". But this time it showed up as "JetFlashTranscend 8GB 8.07" which is my imaging flash drive. No other USB devices were connected except my Windows install drive (Lexar) and my Logitech wireless keyboard/mouse dongle. If I try to boot from it anyway the screen flashes black for a split second like it fails to boot and then comes right back to the boot menu.

It might seem like it is a problem with the Lexar flash drive but I can take it to my other NUC's or other computers and it is detected with the correct ID and boots as expected. Even more strange is that if I boot with both flash drives connected the Transcend will appear as normal but the Lexar will then be detected as my WD Passport which is the external HDD that I use to store my images. If I try booting with all three drives connected then The WD Passport shows in the menu and two instances of the Transcend show up as well. One of them will boot with the imaging software, the other one (clearly the misidentified Lexar) will cause the screen to flicker and come back to the menu. If I boot in legacy mode the drive will show up with the right label but it can't boot because the drive is setup only for booting in UEFI mode. If I boot in mixed mode the drive will be listed twice, one in legacy mode with the correct lablel and one as UEFI with the incorrect Transcend label. If I boot into Windows all devices are detected properly. This issue occurs regardless of which USB port I connect the drive to. This issue seems isolated to UEFI mode on this particular NUC.

I have tried restoring to the BIOS to factory defaults and I have updated the BIOS to the latest version (0361). Nothing changes. Previously it was running BIOS version 0356 when the trouble started.

Can anyone help me figure out what is going on here?

Environment: NUC6i7KYK "Skull Canyon", BIOS v 42, Win10 Pro x64, current with Windows Update, all current drivers from intel.com as of Friday, Dell U2410 display connected via DisplayPort. No firmware updates available from Dell for the display. Cable is Monoprice 13373 Select Series mini DisplayPort 1.2 to DisplayPort 1.2 cable.

Description: When Win10 shuts down the display via "Power & sleep, turn screen off after x minutes" setting, the display and NUC get in some kind of race condition where the display keeps changing from sleep to wake to sleep in a several second cycle. Mouse/keyboard activity does not change this condition. If the computer goes to sleep, then it comes back up fine. If I turn the display off/on from the power button, Windows audio bings a bunch of device state bings, and the display comes back up fine. Tried changing from DP to HDMI and HDMI seems to work as expected. Same monitor, different PC/different graphics card/driver, but also via DP and Win10 Pro x64, successfully powered down and up for years. All other functions, this monitor/cable/system seem to work exactly as expected.

Any suggestions/path to solution? Thanks in advance!

Hello all,

I am not able install chipset driver 10.1.1.38 the latest available for Windows 7. The install is failing with 1603 error. Upon further looking into the MSI log I spotted the below log which spells out the trouble. Do any of you know how to rectify this problem?

FYI: I am trying to install using SetupChipset.exe from the chipset package. I was also looking into a way that I could extract the msi file, but was not able to.

Is this a problem with WIX packaging or the custom action code? Appreciate your help.

Thanks,

Raj

MSI (s) (E0:B4) [17:58:21:762]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI53B5.tmp, Entrypoint: InstallDrivers

SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI53B5.tmp-\

SFXCA: Binding to CLR version v4.0.30319

Calling custom action ChipsetWiX.CustomAction!Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers

12/2/2016 5:58:21 PM  ** InstallDrivers **  ----------> Action Begin

12/2/2016 5:58:21 PM  ** InstallDrivers **  Installing driver to device: 'PCI\VEN_8086&DEV_9D14' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystem.inf'

12/2/2016 5:58:21 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:21 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Installing driver to device: 'PCI\VEN_8086&DEV_9D21' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystem.inf'

12/2/2016 5:58:21 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:21 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Installing driver to device: 'PCI\VEN_8086&DEV_9D23' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystem.inf'

12/2/2016 5:58:21 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:21 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Installing driver to device: 'PCI\VEN_8086&DEV_9D48' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystem.inf'

12/2/2016 5:58:21 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:21 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Installing driver to device: 'PCI\VEN_8086&DEV_9D27' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystemLPSS.inf'

12/2/2016 5:58:21 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:21 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:21 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:21 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Installing driver to device: 'ACPI\INT344B' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystemLPSS.inf'

12/2/2016 5:58:21 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:21 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:22 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:22 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:22 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:22 PM  ** InstallDrivers **  Installing driver to device: 'PCI\VEN_8086&DEV_9D31' 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}\Drivers\SunrisePoint-LP\SunrisePoint-LPSystemThermal.inf'

12/2/2016 5:58:22 PM  ** InstallDrivers **  UpdateDriverForPlugAndPlayDevices return code: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:22 PM  ** InstallDrivers **  Exception occurred: System.Exception

12/2/2016 5:58:22 PM  ** InstallDrivers **             Message: An error occurred when calling DriverPackageInstall.

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.CheckReturnCode_UpdateDriverForPlugAndPlayDevices(Int32 returnCode)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Tools.DeviceManager.Driver.Install(String hwID, String infFile, Boolean& needsReboot, String& driverStorePath)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:22 PM  ** InstallDrivers **  -Exception occurred: System.ComponentModel.Win32Exception

12/2/2016 5:58:22 PM  ** InstallDrivers **  -           Message: 0x00000002 The system cannot find the file specified

12/2/2016 5:58:22 PM  ** InstallDrivers **  Deleting directory recursively: C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}

12/2/2016 5:58:22 PM  ** InstallDrivers **  Exception occurred: System.IO.DirectoryNotFoundException

12/2/2016 5:58:22 PM  ** InstallDrivers **             Message: Could not find a part of the path 'C:\Windows\Installer\MSI4C72.tmp-\%HOMED~1\Temp\{81520FC5-3518-40E9-9803-70CE8A801D07}'.

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.DeleteTemporaryFolder(Session session)

12/2/2016 5:58:22 PM  ** InstallDrivers **         Stack Trace:    at Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers(Session session)

12/2/2016 5:58:22 PM  ** InstallDrivers **  ----------> Action Fail

CustomAction InstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (E0:64) [17:58:22:017]: User policy value 'DisableRollback' is 0

MSI (s) (E0:64) [17:58:22:017]: Machine policy value 'DisableRollback' is 0

Action ended 17:58:22: InstallFinalize. Return value 3.

I have a NUC 6i7KYK and the visual bios has some cool monitoring gadgets for the temperature and fan monitors... But how can I view all that info from Windows 10?

//Brew

I am experiencing  crashes/freezes on certain websites that contain embedded video. The NUC involved is model NUC5i7RYH running windows 10 64 bit. The freeze is total when it happens. Everything just stops working. There is no blue screen just a complete freeze. I have to power down to get the NUC working again. After much investigation I discovered that the culprit is the Iris 6100 graphics driver. I am using the latest version 20.19.15.4300 but the problem also occurred on previous version. When I change the driver to the Microsoft basic display driver the problem disappears. However, video and text with the microsoft basic display driver does not appear to be quite as good video as with the intel driver (and Windows 10 constantly "updates" the driver to the problem intel version). Hence, this is only a temporary fix or workaround.

I've  noted that this problem can be recreated by launching the Iris Graphics Control Center, selecting Video, then selecting Color Enhancement on the left side (the default) and  then under Preview selecting FilmModeDetection. As soon as I select FilmModeDetection the computer freezes. If I change the driver settings on this page to Full Range the FilmModeDetection option will sometimes run and some problem websites will load without crashing the computer immediately but they do eventually cause a crash so selecting the "Full Range" option does not appear to be a fix.

It would be nice if Intel could solve this issue. I expect others must be experiencing it as well. In fact, my searches have indicated a variety of problems with intel video (not just Iris) and windows 10.

I have an INTEL NUC model NUC5i5RYH that losses connectivity to the M.2 SATA. I have upgraded the BIOS to the latest. I tried a new unit and i have tried different M.2 SATA cards. Does anyone have the solution or had this issue

Bekomme seit gestern weder in der Taskliste noch im Gerätemanager das Bluetoothicon angezeigt.

Es ist kein Gerät nutzbar, trotz dass ich den aktuellen Treiber installiert habe (ohne Fehlermeldung).

Wie kann ich Bluetooth wieder "einschalten"??

Environment: NUC6i7KYK "Skull Canyon", BIOS v 42, Win10 Pro x64, current with Windows Update, all current drivers from intel.com as of Friday. No devices, TB or otherwise, connected to TB port.

Desciption: Intel "Thunderbolt-3-Firmware-Update-Tool.zip" updater says "No active Thunderbolt controller found in the system or Thunderbolt software is not present in the system" when run. The Thunderbolt Settings Device Connection Details also shows no Thunderbolt controller box. Device Manager Show Hidden Devices also doesn't seem to show a TB controller. I have confirmed that Thunderbolt is enabled in the BIOS Devices->Onboard Devices->Thunderbolt Controller setting.

I don't (yet?) have any Thunderbolt device. Is there no way to see/set/update Thunderbolt firmware without a Thunderbolt device present and connected?!? My Skylake Dell XPS13 has no such restrictions and can update without TB device(s) present and shows controller details in the Thunderbolt Settings Device Connection Details box, and the TB controller cn be seen in Device Manager Show Hidden Devices.

I am trying to install Windows 7 X64 on the nuc.   When I do however I have no mouse / keyboard to complete the install.

I have created a usb boot / install from Rufus and ran the Windows 7 usb3.0 support image tool from Intel (on every search you do with Nuc windows 7 usb 3.0)

Bios is the latest version.

Ram  16gb

disk is a intel m2 180gb and a 256gb samsun evo 750 ssd.

I have also tried using the using the dism tools  for Windows 7 usb 3.0 creator utility

So I'm thinking the something is wrong with what I'm doing or the driver package.   However on another model of nuc the image does work  (nuc 6i5syk ) 

Does anyone have any ideas?

Hi there

Issue:

• when I switch to my Samsung Series 9 75 inch KS9005 4K SUHD through the HDMI port, the TV keeps auto detecting it as HDMI/DVI and not as PC. I can manually change it to PC but I have to keep doing this each time. My old PC setup with NVidia 960GT was always detected as PC.
• Then when I try to enable YCbCr, the colours are all pink or green. If I then flick back to pc monitor and then back to TV it usually fixes the colour.
• With YCbCr enabled, half the time when I switch to TV I get the same colour issue, then have to switch back and forward to get it right.

I have UHD enabled in TV as well as using the HDMI/PC input. Had absolutely no issues with old PC with Nvidia 960GT with YCbCr 4:4:4 enabled. Using same HDMI cable which is supposed to be 2.0 compliant. I tried another cable (which was same brand) but same issue.

Skull Canyon is brand new and installed with Win10 64bit, latest 0042 bios, latest 4542 graphic divers. I also did the HDMI firmware update when connected to my TV. It already had the latest version but updated again.

TV running at 4K 3840 × 2160 at 60Hz.

Does this NUC support YCbCr at 4:4:4, because even with YCbCr enabled I seem to be getting a bit of black crush compared to nvidia?

Any thoughts on the weird colour as well? I've attached a couple of pics which illustrate the problem?

Paul

Its all

Hello everyone,

There are already several discussions about this issue and I wonder if there happens to be a solution by now.

Anyway, I have just bought a NUC 6I3SYK and connected it to my 4K TV which is connected to my surround system via optical cable. My NUC however, simply does not want to output the audio in more than 2 channels. In the Windows 10 speaker setup I have no other choice but "Stereo".

I have tried absolutely every driver I could find for my system, but none of them worked. I have tried wiping the audio/graphics drivers and reinstalling the newest version - nothing.

Kinda love this little box, but no Surround sound on a Mediacenter PC is pretty much unforgivable. There has to be a solution for this, right? After all this is Intel...

Intel BOXNUC6i7KYK1  with Crucial Ballistix Sport LT 32GB Kit (2 x 16GB) DDR4-2400 SODIMM

Everything installed and worked fine…but after about 5 minutes, the NUC6i7KYK turns off then re-starts.  After it turns back on by itself, it asks to edit the BIOS.  Answering NO, the system re-boots and is stable with no issues.

Same result with Crucial 32GB Kit (2 x 16GB) DDR4-2133 SODIMM, part #CT2K16G4SFD8213, DDR4 PC4-17000 • CL=15 • Dual Ranked • x8 based • Unbuffered • NON-ECC • DDR4-2133 • 1.2V • 2048Meg x 64

Same thing happens with DDR4-2133 memory, which is completely compliant with the NUC6i7KYK memory specification.  The NUC6i7KYK shuts down after the first 5 minutes then restarts.

Please advise on how to get the Intel NUC6i7KYK to operate without the very annoying automatic restarts!

Thank you very much!

Message was edited by: lonzo54

I bought a NUC5CPYH yesterday and installed 8GB RAM and a SSD I still had. Installed Windows 10 and updated it completely. And then installed Kodi. Some finetuning and everything was up and running. The NUC is intended to be used as a 2nd mediaplayer upstairs. The first use of the NUC went flawlessly.

But today the NUC appears to be completely dead; it refuses to power on. I took it downstairs and plugged it into the power adapter, hdmi- and networkcable of my 1st NUC but still nothing. Okay, the power adapter isn't to blame.

But it appears strange to me that a perfectly running NUC now gives no sign of live at all. What to do next? Any suggestions about what to try next?

English is not my native language; I'm sorry for any errors.

Hello,

Could you please tell me from which manufacturer is the front panel header on the NUC5i7 and NUC7i7 ?

Thank you very much.

YG

Audio output is still bugged through hdmi under Ubuntu 16.10.

it is distorted, and crakeling!

latest drivers are installed!

when will you fix this!!