After having solved (it seems) the last boot issue ( which I will update soon) now I have, every time I boot into windows 10, a sort of delayed refresh on the bottom half of the displayport 4K screen.

Latest bios, latest graphic drivers.

You can see what I mean here Intel® NUC Kit NUC6i7KYK Skull Canyon DisplayPort Issues - YouTube

It's also quite obvious when I scroll up and down on a website, windows folder, etc.. and half the screen reaches a stop before the other half.

Interestingly, if I go to the Intel Graphics Settings panel and I change anything, apply, back to what I had, and apply again, this problem described above does not show any more, making it all even more puzzling.

Has anyone had a similar issue?

I'd like to love this little machine but I'm afraid it's infested with bugs and problems

Hello

I have 2 NUC6i7 and I would like to transfer data from one NUC to the other NUC. Via a NIC-Ethernet-USB-Port I can send data to the other NUC (1 GB)

Is there a more direct way to get the full speed of the thunderbold or USB3.1. I think about a USB3.1/thunderbold-cabel with crossover-function or something like that.

Does anyone already has experience and where can I get such a product.

Thanks a lot for your response

Ritzo

My NUC7i3 BHN sometimes has problems with recognizing the monitor (AOC 2275W). NUC and monitor are HDMI-connected. The problem that sometimes occurs is that after starting the NUC the monitor, which is set to HDMI, will not display anything: The orange light on my monitor that is always on, should change to green, but "HDMI" and "no signal" appears on screen. As said, this problem sometimes occurs, so some part of my configuration is not stable. I tried different HDMI-cables: no luck.

I hope someone can help me.

System = NUC6CAYS

Attempting to boot from restore media created by Acronis True Image 2014, 2016, or 2017. 

2 problems

#1 I can't get any version of the Linux based recovery to load on the NUC

a.  2014  Linux based CD image on an external DVD drive.  Starts to load, displays applicable patents, screen changes to:  "Loading Please,  wait ..." and hangs

b.  2017 Linux based CD image on an external DVD drive.  Starts to load, displays applicable patents, screen turns black, and activity stops

#2 I can't get a boot on Acronis Recovery Media on a Thumb Drive to even start loading

a1.  2014, 2017  Linux Thumb drive works on Dell (intel based) E4310, and two different ASUS AMD based motherboards.  I click on F10 during startup to get a list of eligible boot items.  The thumb drive shows up in the list of choices.  If you choose it, the screen flashes blank, and comes back to the same list, but no action is taken. 

a2.  Acronis True Image 2017 also will build a Recovery Media based on WinPE instead of Linux  As a thumb drive, it gets the same treatement.  It boots on the other machines listed above.  Thumb drive appears in the NUC boot list, but choosing it causes the screen to flash and go back to the list with no action taken.

The only form of Acronis True Image Recovery Media I can get loaded on the NUC is the 2017 WinPE on a CD. 

Secure boot is off, EUFI boot is active.

2014 Form      CD       | ThumbDrive       2017 Form      CD      | Thumb Drive

                   -----------------------------                          -----------------------------------

Linux            NoLoad   |    NoStart            Linux             NoLoad  |     NoStart      

WinPE         Unavail    |    Unavail             WinPE           Loads    |    NoStart

I have upgraded to the latest BIOS:  AYAPLCEL.86A.0038.2017.0310.1633, 3/10/2017

I also let it update to all the latest drivers, though I suspect that the BIOS is mainly involved in the boot process.

When I am listening to music on iTunes or youtube, and I reload a webpage, I get a lot of distortion of the sound.  I am listening on headphones plugged into the 3.5mm audio jack.

When the page finishes loading the distortion stops.  Happens the same whether using Chrome or Edge. 

Other network access (like downloading a file using a powershell command) does not cause the issue.

I have updated the BIOS to the latest available.  The audio device (Realtek High Definition Audio) reports that it has the most up to date driver.

NUC5i5RYH

16GB Ram

C: drive is Samsung 850 EVO SSD

D: drive is 2TB Seagate HDD

Any ideas what may be causing this?  Some interaction between audio and video when the page is being rendered perhaps?

Hi,

in my NUC there ist a M2 SSD (Windows installed) and a "normal" SSD (Ubuntu installed). I would like to change the boot Sequence, that Ubuntu starts when I turn on the NUC.

What I tryed so far is to change Boot priority in the BIOS. First the "normal" SSD and second the M2. But it won't help. The NUC starts Windows first.

To start Ubuntu I have to press the F10-Button and choosing the "normal" SSD which listed is on the first place(?).

So what to do, to start start Ubuntu first?

Greeting,

Septimus

Hi All,

I have a Skull Canyon NUC with 32GB RAM and 512GB Samsung 950 NVME drive and its running Windows 10 Pro (v1703 - Creators Update)

My monitor is an LG 27UD88 - a 27 inch, 4K monitor with support for USB-C input.

I've used the monitor via HDMI and DP and it works fine but what I really want to do is to be able to use all the extra USB ports this monitor provides since it's USB-C input capable.

When I use a USB-C to USB-C cable and connect it from my Skull Canyon TB3 port to the monitor's USB-C port, it does work.

Here's the problem - if the monitor goes to sleep, it will not come back up again. I will literally have to restart the machine.

It seems the TB3 port is unable to initiate the monitor again from sleep.

Also, the monitor has to be ON first before I switch the NUC on. If I switch the NUC on before the monitor, again - no display.

The monitor simply states - no input found, will switch off to save power etc...

This behavior does not happen with HDMI or DP.

I'm on latest 0046 version of bios and my Thunderbolt software package version shows up as 16.2.55.275

Hello,

I am following the instructions on the Ubuntu developer site to install Ubuntu 16.04 LTS on a NUC Skull Canyon. I have updated the firmware to KYSKLi70.86A.0046.2017.0407.1426 then booted from a Live USB flash drive, selecting "Try Ubuntu without installing”. I then ran:

xzcat /media/ubuntu/<disk label>/ubuntu-core-16-amd64.img.xz | sudo dd of=/dev/mmcblk0 bs=32M status=progress; sync

got an error and rebooted the NUC. After the reboot, I no longer see /dev/mmcblk0 despite reloading the firmware and using fresh copies of the Ubuntu iso image. I also decided to abandon installing the Ubuntu Core, and instead installed the Ubuntu Desktop on my SSD drive. However, I still don't see /dev/mmcblk0.

I suspect that data in the internal 32GB eMMC storage device got corrupted during the botched write and made it inaccessible. How do I resurrect the eMMC?

thanks in advance,

Ben

Today I download file BIOS AYAPLCEL.86A.0038.EB.EXE from Download BIOS Update [AYAPLCEL.86A]   and verified antivirus DrWeb CureIT that detected  trojan Muldrop6.50036 (see screenshot).  Comment , please! 

The file AYAPLCEL.86A.0038.EB.WINPE64.EXE  was firus-free .

Regards

Hi. I have a NUC with an M2 ssd, 16GB of RAM. I installed Windows 10 64bit, as well as several programs.

I downloaded the link to all the components for the kit and installed as many as I can. No items in Device Manager are showing missing drivers. All updates have been installed.

I ran sfc /scannow and all hardware came back as correct.

I installed the very latest bios, but it still happens. I have not altered any bios settings other than to allow boot from USB, which is how I installed Windows.

The following is from BluScreenview. It details the dumps in the last few days.

==================================================

Dump File         : 040917-4281-01.dmp

Crash Time        : 4/9/2017 5:14:20 PM

Bug Check String  :

Bug Check Code    : 0x00000139

Parameter 1       : 00000000`0000001d

Parameter 2       : ffffda81`3c587480

Parameter 3       : ffffda81`3c5873d8

Parameter 4       : 00000000`00000000

Caused By Driver  : igdkmd64.sys

Caused By Address : igdkmd64.sys+11ddaa

File Description  :

Product Name      :

Company           :

File Version      :

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040917-4281-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 727,028

Dump File Time    : 4/9/2017 5:15:22 PM

==================================================

==================================================

Dump File         : 040917-3859-01.dmp

Crash Time        : 4/8/2017 3:39:34 PM

Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code    : 0x00000050

Parameter 1       : fffff580`b4f38000

Parameter 2       : 01000000`00000002

Parameter 3       : 00000000`00000000

Parameter 4       : 00000000`00000008

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14a510

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 10.0.14393.447 (rs1_release_inmarket.161102-0100)

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040917-3859-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 689,852

Dump File Time    : 4/9/2017 12:00:08 PM

==================================================

==================================================

Dump File         : 040817-6265-01.dmp

Crash Time        : 4/8/2017 3:34:37 PM

Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED

Bug Check Code    : 0x0000001e

Parameter 1       : ffffffff`c0000005

Parameter 2       : fffff803`cc578d8b

Parameter 3       : 00000000`00000000

Parameter 4       : ffffffff`ffffffff

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14a510

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 10.0.14393.447 (rs1_release_inmarket.161102-0100)

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040817-6265-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 726,996

Dump File Time    : 4/8/2017 3:38:02 PM

==================================================

==================================================

Dump File         : 040817-5968-01.dmp

Crash Time        : 4/8/2017 2:08:16 PM

Bug Check String  : IRQL_NOT_LESS_OR_EQUAL

Bug Check Code    : 0x0000000a

Parameter 1       : ffffffff`ffffffff

Parameter 2       : 00000000`000000ff

Parameter 3       : 00000000`00000082

Parameter 4       : fffff802`ae0a5b22

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14a510

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 10.0.14393.447 (rs1_release_inmarket.161102-0100)

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040817-5968-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 792,732

Dump File Time    : 4/8/2017 2:09:10 PM

==================================================

==================================================

Dump File         : 040817-5765-01.dmp

Crash Time        : 4/8/2017 12:50:57 PM

Bug Check String  : SYSTEM_SERVICE_EXCEPTION

Bug Check Code    : 0x0000003b

Parameter 1       : 00000000`c0000005

Parameter 2       : fffff802`5f007688

Parameter 3       : ffff8e81`7c1f63e0

Parameter 4       : 00000000`00000000

Caused By Driver  : FLTMGR.SYS

Caused By Address : FLTMGR.SYS+7688

File Description  : Microsoft Filesystem Filter Manager

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 10.0.14393.0 (rs1_release.160715-1616)

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040817-5765-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 727,044

Dump File Time    : 4/8/2017 12:52:11 PM

==================================================

==================================================

Dump File         : 040817-6078-01.dmp

Crash Time        : 4/8/2017 10:37:38 AM

Bug Check String  : SYSTEM_SERVICE_EXCEPTION

Bug Check Code    : 0x0000003b

Parameter 1       : 00000000`c0000005

Parameter 2       : fffff800`31cd94b1

Parameter 3       : ffff8c80`45b465f0

Parameter 4       : 00000000`00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14a510

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 10.0.14393.447 (rs1_release_inmarket.161102-0100)

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040817-6078-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 727,028

Dump File Time    : 4/8/2017 10:38:58 AM

==================================================

==================================================

Dump File         : 040817-8703-01.dmp

Crash Time        : 4/8/2017 10:01:31 AM

Bug Check String  : CRITICAL_PROCESS_DIED

Bug Check Code    : 0x000000ef

Parameter 1       : ffffce83`d3ba8800

Parameter 2       : 00000000`00000000

Parameter 3       : 00000000`00000000

Parameter 4       : 00000000`00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14a510

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 10.0.14393.447 (rs1_release_inmarket.161102-0100)

Processor         : x64

Crash Address     : ntoskrnl.exe+14a510

Stack Address 1   :

Stack Address 2   :

Stack Address 3   :

Computer Name     :

Full Path         : C:\WINDOWS\Minidump\040817-8703-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 14393

Dump File Size    : 726,900

Dump File Time    : 4/8/2017 10:02:44 AM

==================================================

No method of updating the BIOS works:

1. Windows executable

2. F7 (With .BIO file on USB stick)

3. Visual bios (With .BIO file on USB stick)

The bios updater simply reboots and ignores the update, and fails silently.

The only workaround is to disable Fastboot and Secureboot, apply the bios update, and then re-enable Fastboot and secureboot.

Regards,

Avi

Hi,

While troubleshooting a BCD configuration error on windows 10 (for an unknown reason it got corrupted somehow), I've noticed that while my BIOS had "Fastboot enabled, and Secureboot enabled", there was no USB port that was active. That meant that i could not connect any keyboard / mouse and troubleshoot my windows issue.

Do note that i already found a workaround by removing the security jumper, the bios allowed me to bypass the fastboot, and enter the visual bios safely. This allowed me to boot from an USB stick, and rebuild the BCD.

Do note, that i'm already using the latest available bios (46).

Regards,

Avi

Anyway, I am attempting to reset BIOS to default, and am referring to the following page:

http://www.intel.nl/content/www/nl/nl/support/boards-and-kits/000005845.html

Can someone confirm that the directed key-pressed for resetting the BIOS to defaults are as follows (taking from above page)...

If BIOS settings were changed, revert to default values:

1. Press F2 during boot to enter BIOS Setup.
2. Press F9 to set defaults.
3. Press F10 to save and exit BIOS.

I am almost positive that there a few extra key-presses in there, but without a monitor, I'm unsure if it's working. 

Of course, if it's even possible without the monitor functioning, that is. 

I just posted this question over at unix.stackexchange.com and thought I'd bring it to the attention of this community for input here or to benefit from any responses that may be contributed by the stackexchange users.

==== snip ====

I have a working Centos7 system on a NUC5CPYH. To get the drivers for video and wireless that aren't in the Centos 3.10 kernel, we're using a 4.10.9 kernel. Since the NUC5CPYH is coming up on end of life, I'm trying to migrate to the NUC6CAYH.

Our system plays video in Chrome. On the NUC5CPYH, everything runs fine. On the NUC6CAYH I'm seeing high CPU on gnome-shell which I found (atop "y" command) to have 4 threads of `llvmpipe-[0-3]` attached to gnome-shell's PID -- so we're using CPU (not GPU) rendering.

On the NUC6CAYH, glxinfo errors with message  `i965_dri.so does not support the 0x5a85 PCI ID` which looks to be a Mesa error message from `src/mesa/drivers/dri/i965/brw_device_info.c` Looking at `include/pci_ids/i965_pci_ids.h` the 5a85 PCI ID is not in the 11.2 (Centos 7 includes mesa 11.2.2-2.20160614.el7)  tree but is in the 12.0 and later.

It appears that we need a new version of Mesa. So the question is how do I do that?

- Is this analysis correct?

- Is there a better way to solve this problem?

- Intel has a nice "[recipe][1]" for a video stack, but it looks to be a daunting task to implement.

- Is there a packaged path for Centos 7 to get to Mesa 12+.

- Could this be as "simple" as building Mesa from source? I tried to build 12.0.6 and ran into a series of errors so it doesn't look so simple...

  [1]: https://01.org/linuxgraphics/downloads/2017q1-intel-graphics-stack-recipe

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.

Is it possiable to develop PHY SW on Transcede® 2xxx for IOT basetation?

Hi,

I have Intel NUC5i5RYH, using Windows 10.

In the last few months I'm experiencing screen flickering randomly.

Restarting the machine helps for some time and then again it start flickering  - the flickering rate varies from once in every few minutes to (sometimes) very frequently, and then I have to restart my PC.

I have tried a fresh clean install of Windows 10 lately but the problem got worse.

The latest Graphics Driver after Win10 installation was 15.40.28.4501.

I tried to update the driver manually to the latest Beta 15.40.4539 (which identifies on my PC as 20.19.15.4539) which helps a bit, and brings me to the state before, when the flickering has occurred but less frequently.

Could you advise me how to solve this issue?

Thanks & BR,

Avishay

I'm using an nuc6i5syh with an 4k Display at the DP port. It worked fine for month. Yesterday I tried to start but got no signal on the display. The PC seemed to start (some sound of the vent and the LED went on). I connected the monitor to the HDMI port without success. The monitor works fine at the HDMI output of my laptop. Does anybody have an idea, what ist wrong? SW issue or has the graphics just been gone?

Anyone had issues with the night light mode stopped working? It worked once but after that it is just greyed out.

We have an external mic feeding a mixer and plugged into one leg of a Y cable (TRRS) going into the audio port of the NUC5i5MYHE (running Ubuntu) and the other end of the Ycable feeds an amp/speaker.  The issue is when the unit has a power interruption, or the NUC is rebooted, there is a loud thump and then the unit just continuously makes unacceptable noise that continues.  We tried adding a noise filter but then the NUC doesn't sense the mixer/mic.  Any suggestions.