When will Intel Visual BIOS be updated to access the embedded SKYLAKE PTT and AES Encryption coprocessor with TPM 2.0 capabilities to allow for the Skylake NUC systems to be secured and hardened?  Is there a fix or workaround possible?  If not, I have to return NUC to Newegg before my 30 days are up.  A reply would be appreciated.   

System Tested:  NUC6i3SYK

Manufactured: 12/2015

Intel Visual BIOS Version:  SYSKLi35.86A.0028.2015.1112.1822

M.2 SSD: SAMSUNG 950 PRO 256GB

Intel Visual BIOS Settings:

Boot Settings:

Boot Priority:

UEFI Boot selected;

Legacy Boot deselected.

UEFI Install Verified in MSW 10 Pro Administrator PowerShell with script "Confirm-SecureBootUEFI" with a "True" response.

Secure Boot: Selected;

Secure Boot Mode set to Standard;

Platform Key set to Installed;

Key Exchange Key set to Installed;

Signature Database Installed;

Blacklisted Signature Database set to Installed;

Install Intel Platform Key greyed-out in a deselected state.

In order for Eventghost to recognize the remote signals from the Nuvotron reciever (if you're using a standard microsoft ehome remote like the Rosewill RR-126) , you'll first need to add the correct plugin in EventGhost. Open eventghost and go to "Add Plugin", then under "remote receiver" choose "Generic HID." Now choose the "generic ir receiver' which is the 3rd option down from the top (any of them will work but this one works the best that i've tested so far), and uncheck the box labeled "Trigger enduring events for buttons," and check the box under it, labeled "Use raw data as event name." Click OK, and now any button press of your remote should show up as events in the leftmost window.

Once you see the commands popping up in the left window, you should be able to reprogram the buttons as needed. Hope this helps someone because it took me forever to reprogram my generic rosewill remote to work with Plex/XBMC commands.

Hello,

I have a NUC6i5SYH and I get random restarts. Two times directly after I started the system and one time while it was running (Running VirtualBox).

In the Windows Event Viewer it is always Event 41, Kernel-Power.

My system:

Windows 10 Professional (64bit)

NUC6i5SYH

2 x Kingston HyperX Impact HX424S14IB/8

Samsung SSD SM951-NVMe 256GB

Samsung HM640JJ

WLAN, Bluetooth and IR are deactivated in BIOS.

BIOS Version 0033 and all driver are newest form Treiber und Software.

Any suggestion?

Bye,

Andreas

This question has been asked a dozen times:

1. How to use the watchdog timer on the NUC
2. Application watchdog
3. https://intel-openport-v7.hosted.jivesoftware.com/message/362684#362684

Please give me a link to a guide

I cannot find a guidance that explains how to use a Watchdog Timer, either in Windows or Linux. I am not interested in discussion of a particular NUC model. I want general guidance on how to use it. What drivers are needed, what functions does one use, libraries. What programming languages can be used.  Does Intel have any documentation on the subject?

I really can't find anything.

This thread's initial OP appears below this Workaround Alert. Since folks afflicted by Intel's 'Linux Suspend > Dead NUC' intermittent defect can no doubt benefit most from learning how to avoid getting their NUCs bricked by it, it seems wise to present these bricking avoidance techniques at the top of this thread; and of course you're at liberty to read the whole conversation below, from which they derive.

Workaround Alert

or 'How To Avoid Getting Your NUC Bricked by Linux Suspend'

TL;DR – use wake-on-USB to wake with an input peripheral (eg: keyboard, mouse, trackpad, etc.) or wake-on-LAN from a smartphone app.

Many reports in these forums, dating back to August 2014, show that the Intel NUC is afflicted by an as yet unfixed design flaw: when run under several different distros of Linux (Ubuntu, Arch, Mint, Fedora, Debian), each use of the Linux Suspend function carries a small but real risk of initiating a NUC-bricking incident. Susceptible NUC users are those who use a short press on the Power button to wake from suspend, because the first symptoms of an impending NUC-bricking incident are as follows.

NUC-Bricking: Symptoms #1

When Linux Suspend is used and works normally, the NUC goes into sleep mode, and the Power button LED winks amber. When the 'Linux Suspend > Dead NUC' problem occurs, these are the symptoms which afflict sleep mode:

• a short press on the Power button does not wake the NUC (as it ought to, and usually does) – the amber winking just continues; and
• a long press on the Power button does not switch the NUC off (as it ought to, and usually does) – the amber winking just continues.

See 'Bricking Avoidance Workaround' below for ways in which to successfully wake a NUC exhibiting these symptoms, rather than experience...

NUC-Bricking: Symptoms #2
Once a NUC is in the grip of symptoms #1, the only way to get the NUC to power off is by disconnecting the power cable. After the power cable is reconnected:

• a short press on the Power button does not switch the NUC on (as it ought to, and usually does) – the NUC is bricked; and
• a long press on the Power button does not start the NUC up in Power Button Menu mode (as it ought to, and usually does) – the NUC is bricked.

Unbricking Workaround: to get a thus bricked NUC to work again, you have to fully disassemble the NUC, disconnect and reconnect the CMOS battery from the far side of the motherboard, and reassemble the NUC. Such a drastic remedial action highlights the nature of this failure mode as a manufacturer design defect.

Bricking Avoidance Workaround
Two ways of avoiding the NUC-bricking consequence of symptoms #2 are known to be effective, and both involve alternate ways of waking a sleeping NUC: by input peripheral (wake-on-USB), and by mobile device (wake-on-LAN). They both take some setting up, which is described below.

BIOS Settings for Wake-on-USB and Wake-on-LAN
On booting up your NUC, press 'F2 to Enter Setup' on your keyboard to go into Intel Visual BIOS Settings. On the Power tab (Advanced pull-down menu > Power), set your Secondary Power Settings to match those illustrated below.

Photo credit: sylvia_intel

Press 'F10 - Save and exit' (and 'Y' to confirm) to save these settings and reboot your NUC.This may well be all you need to do, so test to see if you can now wake from suspend with the USB-connected input peripheral of your choice (eg: keyboard, mouse, trackpad, etc.); if it works OK, then you should also be able to use it after a Linux shutdown to boot up your NUC.

OS Settingsfor Logitech Wireless Input Devices

My Logitech wireless keyboard+trackpad and wireless trackpad didn't work straight away to wake from suspend, but community assistance soon got them working flawlessly – so if you too are using Logitech wireless input devices, please see the '2. OS Settings' section of post #39 below (» https://communities.intel.com/message/362981#362981 ) for additional set up instructions.

Wake-on-LAN Apps

To boot up and wake from suspend using wake-on-LAN, you can use a smartphone/tablet app – so just search your mobile device's app store for 'wake on LAN' to acquire an appropriate app. For instance, I've tested the free 'Wake On Lan' Android app by Mike Webb, available in the Google Play store, and it works perfectly. Similar apps are also available for Apple iOS devices.

Workaround Works – Fix is Pending

Once you've settled in to routinely using either wake-on-USB (ie: wake-on-keyboard, wake-on-trackpad, etc.) and/or wake-on-LAN, then even if symptoms #1 of the 'Linux Suspend > Dead NUC' defect should arise again, they'll most likely go unnoticed, since you'll no longer be using a power button short press to end a suspend – and a simple routine tap on an input device or mobile app will wake your NUC as usual.This workaround thankfully avoids the NUC-bricking effect of symptoms #2, but it does not eliminate the 'Linux Suspend > Dead NUC' defect – so we are still waiting on Intel and System76 to come up with a permanent fix for this defect; and that's why this thread remains tagged as 'This question is Not Answered'.

__________________________________________________________________

Dear Intelistas,

I have an Intel NUC5i5RYH (rebadged as a System76 Meerkat), which was delivered on 14 Oct 2015, with Intel BIOS v.0249 in firmware, and it booted from its M.2 SSD [1] into pre-installed Ubuntu 15.04 in around 15 seconds.

My NUC has now been bricked by the well-known 'Ubuntu Suspend > Dead NUC' problem [2] fivesix* times (in 54 58 days of usage), about which many threads exist here at communities.intel.com (dating back at least a year) – and here is a list of what steps I've taken from those threads as potential fixes and implemented on my NUC, but all to no avail:

• upgrading the BIOS firmware: neither Intel BIOS v.0350 nor v.0352 (nor System76 BIOS v.0350) eliminate the 'Ubuntu Suspend > Dead NUC' problem – and upgrading has slowed down its boot time from ~15 seconds to ~2 minutes <sigh>
• mikec_intel's BIOS settings fix [3] does not eliminate the 'Ubuntu Suspend > Dead NUC' problem
• prigaux's 'echo 0 > /sys/power/pm_async' fix [4] does not eliminate the 'Ubuntu Suspend > Dead NUC' problem

For now, the only effective way to avoid getting my NUC bricked for a sixthseventh time would seem to be the major inconvenience of avoiding using the Ubuntu Suspend function altogether; and I'd be very grateful if anybody could recommend a way to get my NUC back to booting up in ~15 seconds, as it did when new (and as might be expected from a motherboard-bound SSD boot drive).

Has Intel really failed completely to address this 'Ubuntu Suspend > Dead NUC' problem?

Or is there yet another potential fix to the 'Ubuntu Suspend > Dead NUC' problem I should try?

Thanks in advance for your attention and help.

Yours in frustration and disappointment,

Tim Jones

__________________________________________________________________

* UPDATES are in red: My NUC has now been bricked by the well-known 'Ubuntu Suspend > Dead NUC' problem SIX times (in 58 days of usage).

[1] Its M.2 SSD: "M.2 SATA: Samsung SSD 850 EVO M.2 250GB : PART 0 : Boot Drive"

[2] The well-known 'Ubuntu Suspend > Dead NUC' problem:

• Mean time between failures: 9.7 days (6 failures in 58 days use, in my personal experience)  10.8 days (5 failures in 54 days of use, in my personal experience)
• Symptoms #1: each use of the Ubuntu Suspend function carries a small but real risk of bricking the NUC. When Ubuntu Suspend is used and works normally, the NUC goes into sleep mode, and the Power button LED winks amber. When the 'Ubuntu Suspend > Dead NUC' problem occurs, these are the symptoms which afflict sleep mode:
  • a short press on the Power button does not wake the NUC (as it ought to, and usually does) – the amber winking just continues; and
  • a long press on the Power button does not switch the NUC off (as it ought to, and usually does) – the amber winking just continues.
• Symptoms #2: the only way to get the NUC to power off is by disconnecting the power cable. After the power cable is reconnected:
  • a short press on the Power button does not switch the NUC on (as it ought to, and usually does) – the NUC is bricked; and
  • a long press on the Power button does not start the NUC up in Power Button Menu mode (as it ought to, and usually does) – the NUC is bricked.
• Workaround: to get my NUC to work again, I have to fully disassemble the NUC, disconnect and reconnect the CMOS battery from the motherboard, and reassemble the NUC.
• Users of Linux distributions other than Ubuntu (eg: Arch Linux, Fedora, Linux Mint) have also reported experiencing this NUC bricking on using Suspend, so it could be described more inclusively as the 'Linux Suspend > Dead NUC' problem.

[3] mikec_intel's BIOS settings fix – as detailed in:

● 'NUC5i7RYH did not wake from sleep mode', 11-Sep-2015 to 15-Nov-2015

» https://communities.intel.com/message/331090#331090

...and involves making changes in Intel Visual BIOS settings.

[4] prigaux's 'echo 0 > /sys/power/pm_async' fix – as detailed at post #10 in:

● 'NUC dead after suspend mode in Ubuntu 14.10', 23-Dec-2014 to 28-May-2015

» https://communities.intel.com/message/309188#309188

...and involves using rc.local to write '0' into /sys/power/pm_async at each boot up.

PS: I've sought help from System76 tech support, but sad to say they're about as useful as a chocolate teapot –  so I'm hoping the Intel NUC community might be of some actual help in addressing these problems. After an email of complaints to System76 CEO Carl Richell, the 'chocolate teapot' tech (non-)support staffer has been replaced by a honest and helpful operations manager, and a possible fix has been encoded in a 'System76 Driver' update, so System76 are at least striving to address this defect; meanwhile Intel are asking for more time to investigate the problem (07 Jan 2016 update).

I have what appears to be the D54250WYKH (the one with a bigger case), and am kind of confused about compatibility with M.2 cards:

- Is it a B-keyed or M-keyed SSD slot available on this motherboard?

- I have heard that some M.2 SSDs still make use of SATA controllers instead of PCI-e; what's the difference?

Thanks!

Since a couple of days I have an NUC6i5SYH. Up to now (unfortunately) not a very pleasant experience. After freezes, reboots, M.2 ssd not found etc.etc. I just got a whea_uncorrectable_error and a booting loop.

My setup is;

Samsung SODIMM DDR4-2133 8GB

Samsung Evo 850 m.2 ssd 240gb

Samsung Evo 850 sata ssd 500gb

Don't know what to do any more.

Any suggestions?

Are there recommended settings for the BIOS (Skylake NUC) to take full advantage of an M.2 NVMe SSD? Thx for any suggestions!

Hello,

I purchased the NUC6i5SYH and installed G.SKILL Ripjaws Series 16GB 260-Pin DDR4 SO-DIMM DDR4 2133 (PC4 17000) Memory Model F4-2133C15D-16GRS, with HyperX SSD (known working flawlessly on previous system). The BIOS is 033 with all default settings.

Initially I installed a fresh version of Windows 10 x64 and all of the drivers found online. The PC began freezing as soon as I opened Firefox, Kodi and even as soon as I logged in. When the freeze occurred, the whole screen was either baby-blue or white color. The mouse and keyboard were not responsive. The only way to recover was to power cycle. I looked into the Event Log but did not see a log of any issues, except the unexpected shutdown.

Next, I reinstalled a fresh copy of Windows 10 x64 again, this time I only installed the LAN drivers, the PC appeared to be fine opening Firefox and Kodi. I had the system up for over a day. Next, I installed the graphics driver, that's where the freezing began happening again.

I decided to install a fresh copy of Windows 7 x64. It seems to be more stable, but after using Kodi for few minutes, the same happens,  even as soon as I start playing a video on youtube, the same freeze occurs.

I should also note that I tried using the HDMI and DP ports with different monitors and using different cables but the issue always remained the same.

I've been trying to find a solution, but most people only report similar problems, closest I found was related to memory. In my case I am not sure that memory is the issue...

Is there anyone who had similar issue and successfully resolved it? I want to use the NUC as a 4K HTPC, but obviously cannot. Are there any logs I can gather that could be helpful?

Any help would be much appreciated!

I installed Ubuntu Linux 15.10 from a USB thumb drive on my NUC6i5SYK.  I had to add 'nomodeset' to get the LiveCD environment to boot, as the display would sleep if I didn't (as described Intel NUC NUC5i5RYH - Boot - only mouse pointer appears (Xubuntu 14.04, 14.10) - Ask Ubuntu and other places).  I was able to successfully install Ubuntu from the LiveCD environment.  Now I see the same issue with the installed version, i.e. it gets to the splash screen and the display immediately sleeps. 'nomodeset' doesn't seem to do anything.

If I add the 'nomodeset' to the GRUB line and hit F10, the purple background is displayed but the boot process freezes... keyboard and everything are unresponsive.  I have to cold boot.

Any ideas?

Hi

My new NUC6 really doesn't seem to like me. After struggling with it for several hours to get Windows 7 x64 Pro to install, I am now facing blank screens (no video signal) when I start / reboot the computer.

This means, I don't see anything on the monitor until the login screen of Windows. From then on, no problem with the video signal.

Because of this malfunction, I can't enter the BIOS or select a boot device at startup. Quick/Fast boot is not enabled in the BIOS.

Regards,

keepcoding

I have problems in almost every 3d game. I know this is not a gaming pc, but occasionally i like to play some old games like Descent(1994), Unreal Tournament(1999), Worms etc.. The problem appear after about 30-60 minutes of gameplay, sometimes i get BSOD other times my system just freezes and i have to hard reset it.

I'm running:

Windows 10 64 bit

16GB Crucial Ballistix 1600Mhz

128GB Samsung SM951-NVMe

The system boots really fast(my display starts slower than the PC from a cold boot) and generally it seams very stable in all other tasks. I have the newest drivers, and have experimented with earlier graphics drivers without luck. I also have the newest bios. Here are some of the BSOD's:

Descent 1 and 2 ran just fine on my passively cooled i486 with 66Mhz and 8 mb of ram back in 1995! I just purchased this PC, and if this can't be fixed i will return it.

I have a NUC6i5SYH and an EIZO LCD monitor connected using DisplayPort. I used the monitor with my previous desktop PC (an AMD E-350 based system) without any problems so I don't suspect that there are any problems with the monitor. I'm running Gentoo Linux as I did with my old PC. But of course then I was using the Radeon driver. Now I've re-installed Linux and are using: VIDEO_CARDS="intel i965"

The problem is that whenever the PC goes into sleep mode I can't get it to wake up. I can get some flickering, but as soon as I move the mouse it will go back into sleep. The only way I can get back to nomal mode is to power cycle.

Are there any ways to reslove this issue?

I tried to download a BIOS upgrade while in the BIOS, but it always

results in failure.

cpu family      : 6

model           : 78

model name      : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz

stepping        : 3

microcode       : 0x57

Hello,

My Config first:

NUC6i5SYH

2 * 8GB Kingston HyperX (KHX2133C13S4/8G)

M2.Sata Samsung SSD 950 512GB

Seagate 1TB Hybrid ST1000LM014

Windows 10 Pro build 1511

My questions:

• M2.Sata drive not recognized in BIOS (Works well though)
• Long wait time at boot app. 10-15 seconds wait on NUC logo and boot options screen. I like to speed this up. How to do this.
• What is the function of changing the minimum IGD memory size and maximux Aperture size. Tested it with 3Dmark but did not notice a difference.
• What is the best (SAFE) way to improve gaming performance (is this done in the bios)

Question two is the most annoying factor.

Using PowerDVD 15 I am seeing inconsistent playback of 3D blu ray. When I start a 3D movie (TV is a Vizio M801D-A3; 1080p/24Hz; frame-packing), the image may distort frequently and cause an image that appears to almost look like its viewed underwater. Depth of the image is also incorrect for seemingly random parts of the image. If I then pause the movie for a few seconds, or back up to the beginning of the chapter, the issue so far resolves itself, but sometimes it takes a few tries to do so.

This seems like a driver bug. I did not have this issue using PowerDVD 15 with Nvidia graphics on my previous build. Attached is my Intel system profile and dxdiag report if that helps. I'd appreciate any assistance.

JimK

This question has been asked a dozen times:

1. How to use the watchdog timer on the NUC
2. Application watchdog
3. https://intel-openport-v7.hosted.jivesoftware.com/message/362684#362684

Please give me a link to a guide

I cannot find a guidance that explains how to use a Watchdog Timer, either in Windows or Linux. I am not interested in discussion of a particular NUC model. I want general guidance on how to use it. What drivers are needed, what functions does one use, libraries. What programming languages can be used.  Does Intel have any documentation on the subject?

I really can't find anything.

Hello,

I have two screen, one is connected over hdmi (main screen, Samsung SyncMaster 2493HM) and the other one is connected on the mini dvi port (HP w2207h), with a mini dvi to hdmi cable. After the screens go to sleep and I wake them up, all windows are on the main screen.

This is very annoying, when I was working and after I get a coffee, I have to rearrange all the windows ... anyone an idea? I searched and searched but there is nothing which affects this behavior ...

While researching this behavior I also find out:

- That after waking the screen up, the side screen always activates for a split second and the goes black for a split second and all windows are on the main screen. It's like it detects the the screens again.

- Both monitors are also recognized as speakers. Sometimes after waking up it doesn't has any speakers and after a split second they are recognized again. But sometimes it doesn't recognized the speaker on the second monitor.

I think it doesn't think it doesn't memorize the monitors and that's the reason why it moves the windows. Any suggestions?

My system:

Windows 10 Professional (64bit)

NUC6i5SYH

2 x Kingston HyperX Impact HX424S14IB/8

Samsung SSD SM951-NVMe 256GB

Samsung HM640JJ

WLAN, Bluetooth and IR are deactivated in BIOS.

BIOS Version 0033 and all driver are newest from Treiber und Software.

Bye,

Andreas

i have the nuc 5i5ryk. How many monitors can it handle?  Thanks.

Hello.  I have the BOXNUC6I5SYK (new 6th generation) and have installed 8GB (2x4) of Corsair RAM (CMSO8GX4M1A2133C15) and the m.2 Samsung 250GB SSD.  I am trying to install Windows 10 from a bootable USB.  Everything boots fine, I get to the part where I select the partition to install on, on the next screen the countdown begins and every single time, Windows crashes with a BSOD during the progress bar.  The error message varies, but this time the error was CACHE_MANAGER.  Last time it was MEMORY_MANAGEMENT.  The only thing consistent is that I can't get past this screen without a BSOD.

I have tried the install with two different SSDs, two different NUCs, and with only one memory chip (I have tried both chips separately).  I have tried the install with different USB drives and different versions of Windows (I tried both Windows 8 and 8.1).  Obviously, it's got to be me.  I have installed several older generation NUCs with no problem at all.  Can you tell me if there are any tricks to installing Windows on the new NUCs?  I am completely lost with this problem.

I have connected my Nuc5ppyh to a home cinema system that can decode DTS and AC3 streams through the toslink interface. When I play a video with that type of audio, the decoder do not recognize it, and I only get stereo sound.

In the Realtek Digital Output device I can't set my speaker configuration (button grayed out), but when testing compatible formats, DTS and Dolby Digital works fine and the decoder recognizes the stream properly.

Operating system is Windows 10

If I play the same files with OpenElec installed on a SDCard, I have no problem, everything works as it should