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!

I hate that NUM LOCK is turned off by default at bootup.  Is there a fix for this?

I also hate that there is not HDD/SSD light on the unit.  Can anyone recommend an application that will at least show disk activity in the Windows system tray, etc.?

Thanks.

Hello. On my SSD is Windows 10 installed and sometimes the NUC will boot without Problems. But often comes a "no bootable device detected" error. The same Intel 600p SSD works and boot in my NUC5i5 without any problems. So, i tested a Samsung M.2 850 Evo in the NUC7i3, no Boot Problems. Any Ideas? Thanks!

Greetings

Nachricht geändert durch Benjamin Schoch

I have this Intel NUC6i5syh that currently runs Windows 10 Pro 1607 x64, that is also fully updated with the latest cumulative update. In addition, VMware Workstation Pro 12.5.2 is installed on the unit and is hosting 5 VMs with 1 core each and 2GB of RAM. The OS currently is running off a samsung 850 evo drive with 32GB of crucial RAM.

Within 6-18 hours of the NUC's uptime, the NUC will "freeze" at the Windows Login screen. When I try to move the mouse or interact with it using the keyboard, no input is registered onscreen. The only way that I have been recovering from this is to hard reset the device from the physical power button.

There are no blue screens, no information in reliability monitor, chkdsk reports no issues, sfc /scannow reports no issues and no errors explaining why Windows is freezing in Event viewer. I have also tested my RAM using memtest86+ and it completed three passes with zero errors. This is a replacement NUC unit that I received from a previous NUC that exhibited this same problem.

Does anyone else have a NUC like mine and experience similar problems? What can I do to fix this?

Though I have tried to find out why this is being reported as a fault, not every shutdown (in Windows 10) produces the error. I see it every day. and Power is not disconnected or switched off.

Any ideas?

Have installed fedora on disk drive but at start firmware goes looking for usb to boot from.

I have ticked optical box for disk drive on bios setup screen without success.  Other changes to bios setup.

Not familiar with configuring bios.

NUC7I3BNH with a msata intel 525 120gb drive. Thinking about using a msata to m.2 adapter. Also using a 4tb WD in the 2.5". Think it will work?

I'm running Windows 10, Anniversary Edition with the latest updates.

It only has been two weeks I have had a NUC Skull, I can hear the its fan noise whenever I turn it on. Even on the first day one I turned it on. Sometimes it can be so loud and that makes me want to cry.

The noise gets loud sometimes when I just browse websites, copying files or just do nothing.

Is it normal that the fan should be running all the time when it is on?

If so, I can accept that but the loud noise is really unacceptable.

I have used a couple of laptops from Dell, I never had such experience. The fan quality in Dell seems a lot better. It is almost silent. It gets loud occasionally. While Skull is often!

Why does it have such a bad quality fan built in a expensive machine?

How can I reduce the fan noise? How can I know that whether it is damaged or not?

I hope this will start a discussion on the use of NUC6i5/NUC6i3 with Linux distributions (i.e. Debian, Ubuntu, Mint, and others)

For some time I was reluctant to buy a NUC since all feedback I found was about bugs and unsupported devices.  For many years I used Intel semiconductors in my projects and PC platforms.  So I really was sad about the lack of interest of Intel staff to support the Linux community, after all we also buy lots of motherboards and CPUs and devices from Intel.

Then I found a project called Opensource 01.org | Intel Open Source Technology Center  that turn on a light for the my quest, so I decided this new year to invest in a new NUC kit the NUC6i5SYH which I installed 2x4GBytes of RAM, a 250GByte SSD/M2 and a 500GB HDD/SATA to test and be able to retire my Gigabyte desktop tower, if all goes well.  The power efficiency was the first point that caught my attention, which is my area of interest since college.  I have tested many low power units, of many brands, for business development, and this NUC really did look promising.

So this is my test log with the mighty, greener, smaller footprint desktop killer that Intel is developing and the work around solution I have to share with our great GPL/GNU community of enthusiasts and professional IT experts that do not take for granted closed black box systems.  Go were no one has gone before.

The first week with my NUC6i5 was very strait forward.  I downloaded the best version (by my research)  http://releases.ubuntu.com/14.04/ubuntu-14.04.5-desktop-amd64.iso.torrent that could bundle support for most of the hardware devices included and used the mkusb to create a USB live ubuntu installation device.  You can use a USB stick or a SD card.  I used a microSD with a USB adapter.  Since the ISO image is less than 2Gbytes usually today any SD or USB drive is fine.

I decided to make the first install on the HDD, since I am not comfortable, yet, with SSD's limitations, (ie.  SSD vs. HDD ), since I could need to reinstall the system many time on this first test, and last, but not least, 10 second or 1 second boot time is not a problem for my applications and use of the NUC.

My partition strategy is using the advantages of EFI:

NAME   MAJ:MIN RM     SIZE  RO TYPE        MOUNTPOINT

sda      8:0    0   465,8G  0  disk

├─sda1   8:1    0     243M  0  part FAT32  /boot/efi*   bootloader/grub

├─sda2   8:2    0    47,7G  0  part Ext4   /

├─sda3   8:3    0   114,5G  0  part Ext4   /home

└─sda4   8:4    0     3,8G  0  part        [SWAP]

        Notice there is free space left for other uses, and /dev/sdb not in use.

OK, so after the install and boot, most devices worked: boot screen, system screen (then logging screen), network (ie. wifi) just connected and ask for the password, Bluetooth was on (had to disable it manually), and I noticed a heat issue, compared to the Live USB test with just the SSD installed, prior to installing the HDD.  I rebooted and tweaked the cooling configuration of the UEFI GUI and ajusted the threshold temperatures and the fan started to be more present (ie. I could now hear it working more often) and the temperature was under control again (notice: I keep air conditioning off at my SOHO for lower carbon footprint).  I then installed lm-sensors, gkrellm, acpi packages and did some google search to fine tune the configuration files.  The probing of the sensors (ie. using sensors-detect command) shows Found unknown chip with ID 0x8607

I would suggest this git project Support for IT8607E  for the tip on using the:

sudo modprobe --verbose it87 force_id=0x8603

this did really work around the lack of a module for the used chip in the NUC (hope Intel helps us here to fine tune measurements ).

This is the output I get with sensors command:

NUC-John:~$ sensors

acpitz-virtual-0

Adapter: Virtual device

temp1:        +27.8°C  (crit = +105.0°C)

temp2:        +29.8°C  (crit = +105.0°C)

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +45.0°C  (high = +100.0°C, crit = +100.0°C)

Core 0:         +44.0°C  (high = +100.0°C, crit = +100.0°C)

Core 1:         +43.0°C  (high = +100.0°C, crit = +100.0°C)

it8603-isa-0a40

Adapter: ISA adapter

Vcore:                     +0.62 V  (min =  +0.55 V, max =  +1.52 V)

SDRAM:                     +1.21 V  (min =  +1.14 V, max =  +1.26 V)

3VSB:                      +3.29 V  (min =  +3.14 V, max =  +3.46 V)

Vbat:                      +2.93 V 

+3.3V:                     +3.31 V 

System Fan:               5000 RPM  (min = 1997 RPM)

Memory Temp:               +45.0°C  (low  =  +0.0°C, high = +95.0°C)  sensor = thermal diode

Motherboard Ambient Temp:  +43.0°C  (low  = +15.0°C, high = +90.0°C)  sensor = thermal diode

PCH Temp:                  +47.0°C  (low  = +35.0°C, high = +100.0°C)  sensor = disabled

As you can see, still needs some fixes of the sensors configuration file, but we are on the right track.

That is all for now.  Hope to get some feedback.  Long Live Linux!

Hi There

I am getting very frustrated with my NUC. I am running the NUC6i7KYK on Windows 10 with a Samsung 960 Pro 512GB and 2 x 8GB HyperX Impact DDR-4 RAM (2133 MHz). I have all the newest drivers intalled and I am running on the newest BIOS version. I have already reinstalled Windows, without success.

The problem I am experiencing are frequent freezes. However, I have never experienced this kind of freezes on any system before. Often, a certain program starts freezing at first while I can still more or less operate many of the others. However, if I open the task manager I can neither kill any program nor can I shutdown the system. If I do the latter, there is simply nothing happing. Generally, the issue becomes more severe the longer I try to enter other programs. More and more programs become unresponsive until none is working anymore. The only thing that always works up to the point of forced restart is the mouse. Anybody know what to do here? Or is the NUC simply broken?

Cheers,

Patrick

hi, have a nuc 5i5ryk with a transcend MTS600, SSD Solid state drive 256Gb, turning it on, only the powerbutton shows flashing blue light, doesn't show anything thoughout the hdmi or displayport. What can the problem be?

Hi.

I struggling w/ a power-up issue w/ my just recently bought (actually kinda brand new) Skull Canyon: while it worked PERFECTLY for ~a week it suddenly (during a video conf. call — thought I doubt it is related) powered off. Since then, I can not power it up again.

My Status: the NUC is powering for roughly 2-3 seconds then shuts down (powers off).

My Setup:

- OS: Arch Linux

- BIOS: KY0041

- RAM: HyperX Impact HX424S14IBK2/32 32GB (2 x 16GB) RAM Kit (2400MHz DDR4 CL14 SODIMM, 1.2V, 260-pin

- HDD:  Samsung SSD 960 Pro Series NVMe 512GB ML

My analysis so far:

1. w/ removed RAM (and HDD) the NUC is powering up until LED flashing 3 blinks (3 beeps) sequence — indicating a RAM issue (well, yes, because there is no ram, right?). Testing w/ one RAM module or even completely different RAM, see next bullet, doesn't help.

2. Replacing RAM... following some pointers in the forum, speaking about RAM being the root cause of rather strange issues w/ the Skull, I've tried w/ a Crucial 32GB Kit (16GBx2) DDR4 2400 MT/s (PC4-192000) SODIMM 260-Pin Memory - CT2K16G4SFD824A — unfort. w/ out success.

3. Trying a BIOS reset (via jumper) does not work because the NUC is either not powering "long enough" (w/ RAM installed) or not at all (flashing 3 blinks (3 beeps) sequence).

Is there anything - apart from returning this otherwise wonderful piece of tech - that I could try? Some sort of reset, maybe...?

Thanks a lot, any feedback highly appreciated.

M.

Hi,

I recently picked up a NUC6i7KYK which looks like an awesome little box, but I'm have some issues with the video coming out from it. Initially I simply couldn't get HDMI and DP-mini to work together - the HDMI monitor would just tell me there was no signal after getting past the bootloader. So I got a USB-C to DP cable, and now have that and the DP-mini connected to two LG 4K monitors. Both work and look great.

However, they flicker something awful. Every now and then one of them will cut out completely, go black and then coming back a few seconds later. That happens perhaps once every ten minutes. On top of that I see a fast flicker, either over the whole of one monitor, or just a horizontal part of it. I've not seen both monitors flicker at exactly the same time yet.

I'm using Ubuntu 16.04 (actually its KDE Neon, which is based on 16.04) which I've updated to Kernel 4.9. I've also got the latest BiOS installed (045 I think it was). Internally there is 1x1TB Samsung 960 and 1x256GB ADATA XPG SX8000 NVMe. In the RAM slots there are 2x Crucial 16GB (CT16G4SFD8213).

I've read the other threads on this topic (which are closed now, which is why I am posting here rather than in those threads), and tried the trick of removing one of the RAM sticks, which made no difference.

I'd be happy to provide an SSU dump, but it looks like it is only for Windows, and I've not got a Windows install on this machine. Is there a Linux equiv.?

Thanks,

Allan

It appears that the maximum size of the X11 virtual screen (randr) with the NUC6i7KYK is 8192 square. From `xrandr` output:

     ~$ xrandr

     Screen 0: minimum 320 x 200, current 7680 x 2160, maximum 8192 x 8192

This means that it isn't possible to use three 4k monitors side by side. Is there a reason that the max is set lower than that value? Can it be modified?

Thanks,

Allan

Hi guys,

One year ago I bought a NUC6i3SYH.

I mated it with a HyperX 8gb, ddr4 2133mhz 1.2v module, because the guys around here wrote that it was compatible with the NUC.

Also I bought a Kingston V300 120gb sata III SSD.

Peripheral I used a Microsoft All in One Media keyboard.

Operating system Windows 10 Pro.

Usual apps: Chrome browser, Plex Media Server, uTorrent.

All went well for 1 year, until a week ago. From then on, I got so many Blue Screens (BSOD) I can't even count them. Every time another error message.

I have tried the following with NO success:

Update to latest BIOS

Clean install of Windows 10 with latest updates

Installed the latest drivers

Changed the RAM module with a Micron module, approved by the Intel site

Disabled Bluetooth, LAN

Ran stress tests and no BSOD appeared. Ran memory, hdd checks and no BSOD or errors.

It seems that I almost always get a BSOD while running Chrome or Edge, or being connected to the internet LAN or Wi-Fi

In Chrome I get the "Aw Snap" error first then in 4-5 mins BSOD.

In Edge - error loading page, then in 4-5 mins BSOD

If I leave it with no Internet connection and loop a movie in mpc-hc  + heavyload stress test, there is no problem.

Should I send it in for waranty? I don't know if they will have the patience to tinker and replicate the errors, because the seem almost random.

Please help!

LE: I also got a BSOD right before finishing a Windows install, so that put me off

Message was edited by: Codrin Havrici

Hello;

While a little accident my NUC D54250WYKH fell from the rack and as I failed to tighten the bottom screws firmly it dissolved into parts.

Fortunately to high intel quality it still works - but the two SATA cables are defective.

I'am now searching for fitting replacement cables but was not able to find this very special ones which apply to the D54240WYB daughterboard anywhere - even not at microsatacables.

Any Idea where I can get these special cables to make my NUC whole again?

Thank you in advance;

Gerd

Hello everyone,

Today, the bluetooth drivers on my NUC crashed. I went to the device manager, deinstalled them, downloaded the newest ones from the NUC support page and installed those. Bluetooth didn't start working again, though. When I open up the device manager, the screen flickers/refreshes every second. Tried to repair the driver, deinstall/reinstall the driver, nothing helped. The only way I got rid of the constant refreshing in the device manager is deactivating bluetooth in the BIOS. Could this be a hardware problem? WiFi still works fine.

Greetings

I have this Intel NUC6i5syh that currently runs Windows 10 Pro 1607 x64, that is also fully updated with the latest cumulative update. In addition, VMware Workstation Pro 12.5.2 is installed on the unit and is hosting 5 VMs with 1 core each and 2GB of RAM. The OS currently is running off a samsung 850 evo drive with 32GB of crucial RAM.

Within 6-18 hours of the NUC's uptime, the NUC will "freeze" at the Windows Login screen. When I try to move the mouse or interact with it using the keyboard, no input is registered onscreen. The only way that I have been recovering from this is to hard reset the device from the physical power button.

There are no blue screens, no information in reliability monitor, chkdsk reports no issues, sfc /scannow reports no issues and no errors explaining why Windows is freezing in Event viewer. I have also tested my RAM using memtest86+ and it completed three passes with zero errors. This is a replacement NUC unit that I received from a previous NUC that exhibited this same problem.

Does anyone else have a NUC like mine and experience similar problems? What can I do to fix this?

Is it normal that, when I have a SD Card inserted in my nuc I can not acces the Bios anymore ? Maybe some weird bug ? I already got the latest Bios installed. When i pull the SD card out everything works fine.