Hello guys

a few days ago I bought my first NUC ( NUC7i3BNH ) and everything works great but only 1 thing is strange.

In my use case I have a plex server running on win10 and when no plex client is connected to the plex server through my network, he will change to sleep mode (theoretically) but when no display is attached via HDMI the sleep mode seems to have no effect. I tried to set the NUC in sleep mode by hand via rdp connection (selected the sleep mode in shutdown settings - not working).

Strange thing is

When I connect the NUC to my tv and make the same settings via connected keyboard, the NUC is moved to sleep mode (blinking blue power led) and hes waking up again when I use the keyboard (wake on via lan is also working)

Does this behavior mean that a HDMI connected display is forced to have so the sleep mode works correctly? or do I have to change some major settings in UEFI setup or in windows?

thanks for help

Im using a NUC6CAYH primarily as a 24/7 media server. I've set the power options under Win 10 as appropriate and even installed the mouse jiggler program. I can get it to stay awake for about three days maximum but then it crashes, sometimes less, requiring me to unplug and reboot.

Any suggestions?

Hi all,

We are aware of this issue and a bug was opened a couple weeks ago.  The developers/engineers are working on finding a solution and I will post any updates and/or solutions here.

Thank you for your patience.

NUC6i3RYHK with dual displays and the screen keeps blanking out when it comes back the desktop reverts back to a single display

I have a very strange audio issue that I'd like advice on.

I recently replaced my NUC DC3217BY with the NUC6i7KYK. The computer sits under my TV for media playback, video calling, and gaming.

My TV is a Panasonic plasma from 2008 with Full HD resolution. The surround amp is a Marantz NR1601 (HDMI1.4a) with 7.1 surround.

Windows is set up to output 7.1 with 24-bit audio @ 96kHz. This setting is common between the two NUCs.

For media, I stream YouTube or Netflix, play video files using VLC, and play DVDs/Blu-Rays using WinDVDPro.

With my DC3217BY I used WinDVDPro11, on the NUC6i7KYK I use WinDVDPro12. The drive is a Pioneer BDR-XU03 connected to one of the rear USB3.0 ports of the NUC.

The DC3217BY setup was flawless. It is only nearly flawless with the NUC6i7KYK.

I can play everything, but when I open WinDVDPro12 to play a DVD or  Blu-Ray, I notice the PCM indicator on my amp blinks off for about half a second every 10-20 seconds with an accompanying break in audio from the speakers. There is no issue with the video playback at all.

If I close WinDVDPro, the audio glitch continues on the same cadence regardless of what programs I open or what media I play.

The only way to get it to stop is either to put the computer into and out of standby or select a different audio playback device from the Windows 10 volume dialogue and then switch back to HDMI.

While WinDVDPro is open, if I change audio output to the headset jack or my Bluetooth headphones, there is no glitching on those outputs. When I revert to HDMI, the glitching resumes.

I have downloaded the Intel Driver Update Utility. However, when it scans my computer it keeps throwing up the same software and drivers as out-of-date. Attempts to install recommended versions fail. The graphics driver and the audio driver, however, are up-to-date. The chipset, Thunderbolt and a couple of others (including CIR) are flagged as wrong (I am not using the Thunderbolt port yet, the CIR seems to work without issue).

I have tried to run the HDMI v2.0 firmware update, but it will not install until I connect a HDMI v2.0 compliant device, which I do not have.

I don't believe I can blame WinDVDPro for the glitching as all it has to do is decode the audio and video from any disc that is playing, which it does correctly with all my other audio devices and there is no issue with the video at any point.

The fact that the issue starts when WinDVDPro starts is suspicious, but closing WinDVDPro does not fix it (I have to adjust audio output or put the computer to sleep).

The HDMI cables are all 1.4 high-speed and are 3' or 4' in length, so signal distortion does not seem likely (and anyway, audio is fine with every program except WinDVDPro).

My Marantz receiver is compatible with the audio settings I have.

Are there any known incompatibilities with HDMI audio that I can investigate?

Why doesn't the driver update utility work correctly to update all the drivers it says are outdated?

I have tried altering the settings for audio in Windows, but no sample rate or dynamic range bit-depth has any different effect. I have tried changing the way WinDVDPro works with audio from the DVD/Blu-Ray discs, but again no change.

Coming from Intel NUC DN2820 I was able to play 3D MVC with Kodi with new Intel Media SDK, I just purchased Intel NUC NUC7i3BNK and 3D playback doesn't work.

On the Intel NUC DN2820, the resolution was set 1920X1080p 3D and everything works great

On the Intel NUC NUC7i3BNK either I set the 1920X1080p 3D or  3820X2160p 3D doesn't work

The Intel Media SDK was supposed to allow 3D MVC to work, I did some testing and found the HDMI 2.0 connection is the one causing the issue and any NUC with HDMI 2.0 doesn't work/

Intel HD Graphics Driver for Windows 7* , 8.1*, and  Windows• 10 for Intel NUC Kit NUC6i7KYK  won't install on my Windows 10 Pro system

Error is:

DSAService.exe Information: 0 : 29/08/2017 8:10:17 PM: InstallationController: Starting installer

DSAService.exe Information: 0 : 29/08/2017 8:10:18 PM: InstallationController: Beginning install of file GFX_WIN7_8.1_10_64_15.45.19.4678_KY.zip

DSAService.exe Error: 0 : 29/08/2017 8:10:22 PM: InstallationController: Installation failed with exception: System.ArgumentException: Process with an Id of -1 is not running.

Hello Everyone,

There is anyone there, who knows or has information about the compatibilities of:

-PCoIP for VMware

-HDX for Citrix

-RDSH for Windows Server (remoteFX)

With Intel® NUC Kit NUC7i7BNH

Intel® NUC Kit NUC7i5BNK

Intel® NUC Kit NUC7i3BNK

Thank you in advance for your help.

Best regards,

Sidiki

Hi,

I made an installation with three video-wall displays and Intel NUC-machine.

The Intel Graphics finds the monitors and an extended display can be used with all of them.

As the installation topology is 1x3 (ie. wanted resolution is 1920x3240px) collage mode is needed.

When entering the collage -mode settings, the Intel Graphics finds only 2 displays at the time.

How can I use all of the three displays in collage mode?

As per the Dell's link below, it is said the third (last) monitor needs to be set to DP1.1.

Can anyone confirm this?

*EDIT* We tried this (last screen in DP1.1 and that didn't work either.

Machine:

INTEL NUC BOXNUC7i7BNH Core i7-7567U

With Windows 10 HP

Displays:

Display connection via Targus USB-C - Display Port -adapter.

Found this: How to Configure U2415 Monitor Daisy Chaining on Intel HD Graphics | Dell Suomi

Just finished bringing up my NUC7i5BNH with a clean install of Windows 10.

When the generic Windows driver was in charge before I installed the Intel Graphics driver, I had the native 2560 x 1440 displayed on my monitor over the HDMI cable. As soon as I installed the iGFX driver (GFX_WIN10_64_15.46.2.1.4729) the display dropped to 1920 x 1080 and I cannot for the life of me find a way to return to the display's native resolution.

I tried a custom setting in the Intel Graphics Setting application and it says that the requested setting is outside the bandwidth limitations for the device (which it shouldn't be).

Under the "Options and Support" section of the Intel Graphics Setting application, the application does see that 2560 x 1440 @ 60p Hz is a supported monitor mode. The monitor is from Monoprice and it's a 27" display.

The Intel Driver Update Utility doesn't register a version number for the graphics driver and reports it as "Unknown".

I don't know if it's related, but the system also doesn't recognize the audio capabilities of the monitor either.

More information from the Iris Graphics Control Panel:

----

Intel(R) Iris(TM) Plus Graphics 640

Report Date: Saturday, August 26, 2017
Report Time [hh:mm:ss]: 1:21:03 AM
Driver Version: 22.20.16.4729
Operating System: Windows* 10 Home (10.0.15063)
Physical Memory: 32659 MB
Vendor ID: 8086
Device ID: 5926
Device Revision: 06
Graphics Output Protocol (GOP) Version: 9.0.1066
Current Resolution: 1920 x 1080

Processor: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz
Processor Speed: 2208 MHz
Processor Graphics in Use: Intel(R) Iris(TM) Plus Graphics 640
Shader Version: 5.1
OpenGL* Version: 4.5
OpenCL* Version: 2.1
Vulkan* Version: 1.0.38

* Microsoft DirectX* *
Runtime Version: 12.0
Hardware-Supported Version: 12.0

* Devices connected to the Graphics Accelerator *

Active Displays: 1

* Digital Display *

Display Type: Digital
Serial Number: YSP12310001
DDC2 Protocol: Supported
Gamma: 2.2
Connector Type: DisplayPort
Device Type: Digital Display

Maximum Image Size
Horizontal Size: 23.62 inches
Vertical Size: 13.39 inches

Supported Modes
640 x 480 (60p Hz)
640 x 480 (75p Hz)
720 x 400 (70p Hz)
720 x 480 (60i Hz)
720 x 480 (60p Hz)
720 x 576 (50p Hz)
720 x 576 (50i Hz)
800 x 600 (60p Hz)
800 x 600 (72p Hz)
800 x 600 (75p Hz)
1024 x 768 (60p Hz)
1024 x 768 (75p Hz)
1152 x 864 (75p Hz)
1280 x 720 (50p Hz)
1280 x 720 (60p Hz)
1280 x 1024 (60p Hz)
1280 x 1024 (75p Hz)
1440 x 900 (60p Hz)
1680 x 1050 (60p Hz)
1920 x 1080 (60p Hz)
1920 x 1080 (60i Hz)
1920 x 1080 (50i Hz)
1920 x 1080 (50p Hz)
2560 x 1440 (60p Hz)

Power Management Support
Standby Mode: Supported
Suspend Mode: Supported
Active Off Mode: Supported

Raw EDID:
00 FF FF FF FF FF FF 00 66 70 60 27 00 00 00 00
0F 17 01 04 80 3C 22 78 FE EE 95 A3 54 4C 99 26
0F 50 54 A5 CB 00 71 4F 81 C0 81 80 95 00 B3 00
D1 C0 01 01 01 01 56 5E 00 A0 A0 A0 29 50 30 20
35 00 55 50 21 00 00 1A 00 00 00 FF 00 59 53 50
31 32 33 31 30 30 30 31 0A 20 00 00 00 FD 00 17
4C 0F 63 19 00 0A 20 20 20 20 20 20 00 00 00 FC
00 32 37 69 6E 63 68 20 48 44 4D 49 0A 20 01 5B

02 03 1F F1 4C 01 02 03 04 05 07 90 12 13 14 16
1F 23 09 07 07 83 01 00 00 65 03 0C 00 10 00 02
3A 80 18 71 38 2D 40 58 2C 45 00 FE 1F 11 00 00
1E 01 1D 80 18 71 1C 16 20 58 2C 25 00 FE 1F 11
00 00 9E 01 1D 00 72 51 D0 1E 20 6E 28 55 00 FE
1F 11 00 00 1E 8C 0A D0 8A 20 E0 2D 10 10 3E 96
00 FE 1F 11 00 00 18 01 1D 00 BC 52 D0 1E 20 B8
28 55 40 E8 12 11 00 00 1E 00 00 00 00 00 00 07

* Other names and brands are the property of their respective owners.

In a nutshell, the only issue I have with the NUC system is, the CPU fan would left turned on after ESXi shutdown while the NUC power button would be turned off. To turn the system back on with the power button, I would need to first pressing the power button for 5 seconds or so until the fan is turned off (the system is then forcefully powered off), only then I can turn the system back on again by pressing the power button normally. This annoys me as if I forgot to force the units to go down completely, I'd find the units are warm in the next morning and I don't have air conditioning running all the time. I had done a bit of research and did try a few things and unfortunately I had not found a solution to this, yet. I have two NUC units with the same parts and EXSi, both have the same experience.

Would appreciate your advise on what I should try.

And as much as I'd like to get some support regarding the above subject, I'd like share on this thread my experience of running ESXi 6.5 on the NUC units.

Hardware and firmware

Important hardware and firmware remarks

• For those planning to run ESXi 6.5 or similar, and for those planning to run Linux operating system on the NUC with Intel SSD 600P, I highly recommend that the SSD is updated with firmware version 121C (or better if available)
• There were issues reported running Linux on the Intel SSD 600P, at the time I'm writing this only Microsoft Windows versions listed on the 600P product page are 'officially' supported
• Having said, I had see reports on this forum and others that firmware version 121C works good for certain Linux flavors, and for me, ESXi - see also important notes on the NVMe driver for ESXi

BIOS configuration - configured according to article here by William Lam and article here by Erik Bussink - in summary, I have the following BIOS settings. I'm listing them for reference, not that I know what each of the settings meant

VMware ESXi

• Installed on the USB boot drive
• Updated to ESXi 6.5.0 Update 01 Build 5969303 here
• Two data store on each NUC, each data store fully occupy each 600P

Very important remarks

• Replace the stock NVMe driver that came with ESXi with the one built specifically for Intel SSD here
  • After the update, it showed intel-nvme instead of nvme as the driver for the storage adapter
  • You'll see on the driver page that the model 600P isn't listed, but the driver worked well for me so far
• I did the driver update after I had applied the ESXi 6.5.0 Update 01
• And prior to that, I had both of the 600P low-level formatted with HDAT2 (by verify/write/verify), the tool is listed here here

The catch was, without the intel-nvme adapter driver, I had painful experience working on the ESXi platform with the NUC system - obviously the system or its parts are not ESXi HCL listed

• Copying virtual machine folders from one ESXi data store to another ESXi data store that was created on another 600P on the same NUC would usually fail before 20% completion
  • ESXi would lose connectivity to the data store that it was writing after the error
  • I had to reboot to recover from the situation
• Or, similarly, copying virtual machine folders to/from the same data store would also result in similar experience
• Or, deploying virtual machines with thick disk mode (-diskmode eagerZeroedThick) with the VMware ovftool would also result in similar experience
  • Having said that, I didn't get any issue deploying virtual machines with thin disk mode

Post updating ESXi with the intel-nvme driver, I had tested the system to PASS the above test cases which failed 100% previously

Edits: there are 3 items attached to each NUC units

• The DC power plug
• The USB boot drive
• Cat5e network cable

No other items are connected other than the items above. Specifically I don't have any type of displays attached to the units.

Message was edited by: scene (added items attached to the NUC units)

Hi!

My boss told me to buy three PCs for a customer project that is based on "Red Hat Enterprise Linux 7.3". The system does nothing more than issuing some X.509 certificates per day. So, instead of buying three over-sized tower PCs I'd like to use a tiny device for this application.

But I am unsure if RHEL7.3 will work an a NUC7. I have no need of high 3D fps oder Wifi. I will only need the LAN port and the USB-ports. The NUC will be connected to a FullHD monitor via an HDMI->DVI adapter. That's it. But the desktop should not be sluggish.

I guess that RHEL7.3's kernel is too old (3.10) to support the 7th generation of Intel chipsets, isn't it?

If so, is there a really simple way to solve this? With "simply" I mean not to self compile a kernel, a display driver and so on. The solution should overcome normal system updates.

Thank you very much!!

It looks like iTCO_wdt won't properly setup a /dev/watchdog device on Intel recent Celeron NUCs (NUC6CAYS).

```
# uname -a
Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
```

Modules are properly loaded (but looks like it is not used)

```
# lsmod | grep -e dog -e wdt
iTCO_wdt 16384 0
iTCO_vendor_support 16384 1 iTCO_wdt
```

No device found in kernel.log:
```
Aug 28 18:49:56 player-ef15 kernel: [ 14.192689] iTCO_vendor_support: vendor-support=0
Aug 28 18:49:56 player-ef15 kernel: [ 14.198585] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
```

No device found by the service:

```
# service watchdog status
● watchdog.service - watchdog daemon
   Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled)
   Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
  Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
  Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, status=0/SUCCESS)
Main PID: 2768 (watchdog)
    Tasks: 1
   Memory: 732.0K
      CPU: 13ms
   CGroup: /system.slice/watchdog.service
           └─2768 /usr/sbin/watchdog

août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no soft=no mla=0 mem=0
août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to check
août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno = 2 = 'No such file or directory')
```

This driver is listed under downloads for a NUC6i5SYH, as for Windows 7*, 8.1*, and Windows® 10* for Intel® NUC Kit NUC6i3SY and NUC6i5SY. However it does not install on a NUC6i5SYH running Windows 7 Professional 64 bit and the release notes advise that it is [only] for Microsoft Windows* 10-64.

Also, installing this driver in a NUC7i5BNH running Microsoft Windows* 10-64 has led to some apparently intractable issues with audio in MPC-HC. I haven't seen any other reference to this driver update in recent discussions, but is it possible that the audio issues might be resolved with application of the latest bios version to the NUC7i5BNH? I am currently running bios version 46 and have no intention of updating it until I am confident that other issues raised in discussions here relating to bios version 48 have been resolved.

Hello,

I've recently purchased a Skull Canyon NUC and found out my USB multimedia keyboard does not work with it when no operating system is loaded.

I've borrowed a USB 2 hub and a USB keyboard to try and the borrowed keyboard and my mouse were detected by BIOS when connected by the hub to the nuc. Good news as I plan to waste at most 1 USB port for keyboard and mouse as the nuc has very few usb ports and I have many USB peripherals.

Now I need to buy another keyboard and a hub but I cannot tell before trying if they would be recognised by the bios.

Is there a way to know which hubs and keyboards are working in BIOS without trying them ?

My multimedia keyboard is a USB composite device with keyboard, mouse and multimedia buttons. I've used it for 10 years without any issues with a 10 year old computer. It works in my old computer BIOS. It also worked 2 times with the nuc, which is strange.

Thank you.

Im using a NUC6CAYH primarily as a 24/7 media server. I've set the power options under Win 10 as appropriate and even installed the mouse jiggler program. I can get it to stay awake for about three days maximum but then it crashes, sometimes less, requiring me to unplug and reboot.

Any suggestions?

I've been usuing my NUC Skull Canyon since last January without any problem. In fact, I was quite satisfied with it.

About three weeks ago, I started experiencing freezes (the video output, either HDMI or DisplayPort, was frozen and the system didn't respond to any keyboard or mouse input) or Windows' blue screens of death.

Sometimes these issues are related to device drivers, so I decided to update all the drivers to the last version available at the Drivers & Software section for this computer. The last one was the BIOS update 049, which was downloaded at Download BIOS Update [KYSKLi70.86A]. The update method I selected was Express BIOS update [KYSKLi70.86A.0049.EB.EXE].

The express update process rebooted my PC, updated the BIOS and booted into Windows again. After logon, I was notified that the update process was successful.

However, even though the system seemed much more stable, it became frozen after using it for an hour or so (before, it didn't take more than 5 minutes to block). Since that happened, I haven't been able to boot the system again. The boot screen with the Intel NUC logo does not even appear, and the system just keeps rebooting every half minute approximately. The power-on LED stais static and only powers off during these reboots.

I've tried to perform a BIOS recovery using BIOS Recovery Update Instructions for Intel® NUC. However, the system keeps boot-looping as I've just described before, no matter what recovery option I use (tried both Power Button Menu and Security Jumper alternatives). I tried changing the video output (both HDMI and Display Port), changing the display monitor, and introducing my USB flash drive in different USB ports, but the flash drive light never indicated any activity.

Is there any other option I can try?

PS: I've installed the following components:

- Crucial 32GB (2 x16GB) DDR4 KIT. I tried using both modules and using either of the two (pluging the other out of the motherboard), but made no difference.

- Intel 600p series SSD 512GB. I tried booting without, but neither made any difference.

I have just purchased my first NUC Skull Canyon and I have connected it to my Samsung S27B971D WQHD monitor. However, 2560x1440 is not listed in the available resolutions. I have also tried to add it manually through Intel Iris Graphics Control Panel but I am getting "The custom resolution exceeds the maximum bandwidth capacity". 3 different HDMI cables I have tried with no success. I am pretty sure that I can get this resolution through DisplayPort but currently I do not have one. I am pretty sure I can get it through HDMI as well, as I have read that 4K is supported through HDMI on this machine.

NUC6i3RYHK with dual displays and the screen keeps blanking out when it comes back the desktop reverts back to a single display

Hello.

I'm a new proud owner of a nuc7i3bnh.

Bios version 86A (49).

Windows 10 home 64bit.

I will be using the nuc as a media device connected to my tv (lg webos 2014).

When I turn on my tv I want the nuc to start (works fine as specified in nuc bios).

When I turn off my tv I want the nuc to shutdown (does not work, see below).

HDMI cec signals are working great using the lg tv remote. I have a pulse eight adapter inside the nuc. Navigating the windows 10 kodi app works as expected.

This is what happens when I turn my tv off:

Everything is running fine, tv on and nuc also.

I press the tv remote red button.

Tv turns off.

Nuc stays on.

I then start tv again to see what happened by pressing tv remote red button.

Tv turns on.

When I see the windows desktop it only takes a few seconds then the computer automatically shuts down.

It's as if the "shutdown" windows signal is not sent the first time due to timing.

The reason I say this is because if i instead set Kodi to sleep instead of shutdown (when tv turns off) it actually does sleep. But funny enough when I turn the tv back on windows still shuts down.

There are hdmi cec settings in the bios (set to turn on nuc when tv starts, other settings are turned off).

There are hdmi cec settings in kodi (what to do when tv is turned off, set to shutdown windows/pc).

And finally my lg tv has hdmi cec settings (SimpLink, auto-sync power is on).

If I disable the auto-sync power feature of SimpLink the nuc stays on, doesn't sleep or power down.

Due to a lot of cec settings involved perhaps there is a conflict. Hope you guys have some ideas.

Thanks for reading.

Best regards,

Eriksson