Hi,

I'm experiencing boot Issue with the NUC6CAYS + Ubuntu Server 16.04.02 LTS (kernel 4.8), Ubuntu Server 17.04 (kernel 4.10) and even with the UEFI USB Installer.

• BIOS Version 0038 and 0040 tested
• HDMI 2.0 Firmware fix.
• Default values in bios except: eMMC is disabled + supervisor password set ( I tried without a supervisor set too). Also tried the UEFI OS Selection to Linux, same issue
• ADATA SP550 SSD is installed inside

Here is the story:

• First I installed Ubuntu Server 16.04.02 LTS with HWE Stack (Kernel 4.8), everything was working fine BUT I noticed that sometimes, after a reboot, my NUC was stuck on a black screen right after the GRUB Menu.

• I decided to give Kernel 4.10 a try so I installed Ubuntu Server 17.04 (kernel 4.10) and nothing else except updates. I did a small script to restart the computer every 30 seconds or so and again, randomly, the NUC was not rebooting. I see the GRUB Menu with Ubuntu selected and after the 2 seconds timeout, screen go black and nothing more happen.

• After hours and hours of debugging and trying to find what the problem was, I decided to use a brand new SSD (same model) that I had on hand.
  • Disconnected the power of the NUC
  • Replaced my SSD
  • Connected my Ubuntu Server 17.04 USB installer made with Rufus
  • Connected power
  • Started NUC
  • Pressed F10 on boot, selected my USB and displayed the GNU GRUB Menu where I selected * Install Ubuntu Server and.....the same issue occurred,  black screen and nothing!!
  • I restarted the computer and tried it again... this time the Ubuntu Server installer started correctly.

1. Boot
2. Wait for GRUB Menu (eMMC is disabled and ssd brand new, so the USB boot automatically)
3. Press Enter to start installation
4. If the installer start, press CTRL+ALT+DELETE and do it again.

• I did it again, and again, again, at least 30 times without any issue than, after many retries same problem, black screen and nothing!

It's totally Random and really seems to be a BIOS issue to me since this time. When the black screen happen, ctrl+alt+del do nothing. I have to long press the power button for about 5 seconds to power off the NUC.

I should have a brand new NUC6CAYH tomorrow to test if it's specific to my NUC or not, since I already have NIC issue with this one but I need it for development (NUC6CAYS - Ethernet Issue )

Tested with a brand new NUC6CAYH, a different 4GB Kingston memory module and a different brand SSD (PNY) - Same Issue

Procedure to reproduce the issue in this post: Re: NUC6CAYS - Random boot freeze and can be downloaded here: https://communities.intel.com/servlet/JiveServlet/download/485079-171358/RebootScript.md.zip

Thanks a lot for support

Hello,

        GFX_WIN10_64_15.46.2.1.4729 latest driver for NUC 7i7BN will not install HDMI  audio drivers, get code 28 error in device manager.

INTELAUDIO\DSP_CTLR_DEV_9D71&VEN_8086&DEV_0222&SUBSYS_00000022&REV_0001 show on HDWR id

Update 170806

After uninstalling and then reinstalling latest drivers ... again, looked in device manager at the IRIS 650 Display driver install and found

that an event: Device PCI\VEN_8086&DEV_5927&SUBSYS_20688086&REV_06\3&11583659&0&10 requires further installation.

was showing. HDMI works to a Dell U2410.

Message was edited by: Dave Notnim

I have Intel 5TH NUC ( nuc5i3ryh ) + (nuc5i5ryh)

Both are already upgrade to Latest BIOS. [RYBDWi35.86A]

1.

I planned to upgrade to M.2 SATA SSD - Sandisk X110 SD6SP1M-64G which is from my laptop.

Sandisk X110 SD6SP1M-64G  can be detected on 5th NUC visual BIOS ....  but not on Windows 10 installation process.   It can not detect anything.

2.

I change to M.2 NVMe SSD - SAMSUNG PM961 - 128G which is from my laptop

Everything is OK with SAMSUNG PM961 and 5TH NUC. 

completed - Windows 10 Installation

But I can see a signification BUG with  SAMSUNG PM961 and 5TH NUC.

Windows 10 --> Shutdown --> Power on --> Visual BIOS Screen --> Boot to Windows 10 ---> It's OK

Windows 10 --> Restart --> Visual BIOS --> Boot to Windows 10 (FAIL !!!) --> Windows 10 EMS Repair Mode .................Power OFF --> Power ON --> Visual BIOS --> Boot to Windows 10 (OK!!!)  ...... Everytime

It's seem to be a Bug with Visual BIOS and SAMSUNG PM961 SSD ....

Is there any advice ?

Thanks

I've had the system for 4 months and it works great for the most part but recently it started rebooting itself randomly--at least a couple times a day.  I ran a windows memory test and the test said I have a memory problem that should be addressed by the manufacturer. 

Before I pursue that I thought it would make sense to try to update all the drivers and BIOS. It looks like most drivers and the bios all have updates since I bought the system in April 2017.  I downloaded the driver bundle and found on-line the recommendations to do the updates manually instead of using the Intel Driver Update Utility.  I'm about to get started but since I'm not a hardware/BIOS/Drivers expert I thought I post a question: 

Is my approach here the right one?  That is, to update everything before trying to get the memory vendor to replace the memory?  Or is this just a waste of time?

Thanks.

Hi,

I recently got a Intel NUC7i3BNH and installed ubuntu 16.04 on it. Audio over hdmi does not work on Samsung UN46EH5300F TV. However, when I try it on Asus VE247H monitor the audio works all the time. Also audio over headphones or speakers also work all the time. I posted a question to ubuntu forums followign their audio troubleshooting page https://help.ubuntu.com/community/SoundTroubleshootingProcedure. It includes all the information about my nuc.

I also came across https://downloadcenter.intel.com/download/26609/HDMI-2-0-Firmware-Update-Tool-for-Intel-NUC-Kit-NUC7i3BN-NUC7i5BN-NUC7i7BN-NUC6CAY and it looks like intel made an firmware update because some nucs were facing some graphics issues for Samsung 6000 series TVs. I think what I am facing is similar. I don't get audio over hdmi for Samusng 5300 series TV.

I have been googling and it looks I am not the only person who is facing this issue. I was wondering if there was any solution to this problem.

Thanks.

INTEL® NUC KIT NUC7I3BNH

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.

Hi,

I'm trying to activate a display. The display has an HDMI port. I'm using a mDP to HDMI cable. The display works fine when connected to another computer using the same cable. However, the NUC doesn't recognize this display (it does recognize other HDMI displays).

If before I connect the display, I connect another HDMI monitor which is recognized, I can activate the unrecognized display by issuing the following commands:

xrandr --newmode 1024x600 48.96  1024 1064 1168 1312  600 601 604 622  -HSync +Vsync

xrandr --addmode HDMI1 1024x600

xrandr --output HDMI1 --mode 1024x600

This "forces" to activate a 1024x600 resolution display, and the display turns on and everything is OK (although xrandr still reports HDMI1 as "disconnected").

However, if I don't start by connecting an identified monitor, the last command fails with "xrandr: Configure crtc 0 failed" message.

My guess is that connecting the recognized monitor switches the port from DisplayPort mode to HDMI mode, and then the xrandr activation command works.

The display should be inside an embedded device, so there's no way to ask the user to first connect a different monitor.

Is there a way to force the port to switch to HDMI mode? Or, alternatively, is there something I can do to make the NUC recognize the HDMI display?

I'm using NUC5i5MYBE, Ubuntu 16.04.

Thank you very much,

Noam

Hello

I am trying to run the windows 10 IOT on the Intel® NUC Board DE3815TYBE, which should be supported according to SoC Options | Windows IoT , has the E3800 processor is listed as compatible.

I have followed the guide here; https://developer.microsoft.com/en-us/windows/iot/Docs/GetStarted/joule/GetStartedStep1.htm, and tried to setup the board with the installation files for both the Intel Joule and Intel Compute stick, but after the installation of the OS on the 4 GB built in eMMC memory the system  can not boot from the files.

I have installed a 4 GB DDR3L ram module.

I have updated the bios to the latest version TYBYT10H.86A  0060 from Download BIOS Update [TYBYT10H.86A] .

My windows 10 version is 1607, and I have used the corresponding ADK from Windows ADK downloads - Windows Hardware Dev Center .

During the WinPE drive creation I have generated the drive with amd64, and the copied the JouleInstaller.cmd and the flash.ffu to the USB. I have tried to use both the flash.ffu for the minnowboard and the Intel Joule, however only the minnowboard could be used for installation of the OS.

When I turn on the system I am met with the following:

"Intel UNDI, PXE-2.1 (build 083)

Copyright (C) 1997-2000 Intel Corporaton

This product is covered by one or more of the following patents:

US6,570,884, US6,115,776 and US6,327,625

Realtek PCIe GBE Family Controller Series v2.59 (01/13/14)

PXE-E61: Media rest failure, check cable

PXE-M0F: Exiting PXE ROM.

Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key. "

I have the eMMc enabled in the BIOS, and have enabled UEFI Boot, with "UEFI: MMC - SEM04G: PART 1 : OS Bootloader" selected.

Under Legacy Boot Priority I have selected "MMC - SEM 04G : PART 0 : Boot Drive" as the first choice and "LAN : Realtek PXE B03 D00" as the second priority.

If I enter the boot menu during startup I can choose the same three options. If I choose the UEFI option the screen goes black a couple of seconds and nothing further happens. If one of the other two options are chosen I get the above listed error screen.

Thank you in advance

Hello,

I have recently bought an NUC7I7BNH, which I am using with Windows 10, and connected via HDMI to a Denon AVRX2300 receiver, and a 4K 60hz-capable Vizio TV.

I am using the Kodi media player, and have noticed frequent audio drops when bitstreaming (particularly high bitrate streams, it seems), and sometimes video drops (usually when outputting, say, 2160p@24hz + DTS-MA) . The audio drop-outs can occur as frequently as every 20 seconds or so. All the drivers, including the HDMI firmware are up-to-date.

Everything worked fine on my previous build with a NVidia GTX 950, so I'm sure the issue is related to the NUC, especially as I simply swapped the SSD from the old rig to the new NUC.

Another odd issue I've noticed is that while Kodi displays 1080p movies by selecting an output resolution of 1920x1080@24hz, as expected (debug log confirms this), the AVR actually receives an 'upscaled' 2160p@24hz video stream from the NUC. Very strange, and most undesirable. It might be that this 'upscaling' is also exacerbating the audio drop-out problem, as my suspicion is that the frequency of drop-outs correlates directly with the overall HDMI bitrate being outputted.

The drop outs make the system currently unusable as a media player. Any help would be greatly appreciated.

Hi - I have exhausted my knowledge and patience with this NUC over the past 24 hours.

I have a NUC6i3SYH that was happily running Linux for 6 months without a bother and unfortunately I had to install Windows for work. After the process of creating the ISO, updating the USB 3.0 drivers installing Windows 7 Pro and then upgrading to Windows 10 Pro I thought it was all good.

Tonight I rebooted the machine and.... no boot device.

I looked in BIOS and nothing was listed against UEFI or Legacy boot options - I know the 500Gb SATA drive was there because I saw it when I upgraded the BIOS to v61 last night. I the BIOS file manager I can see the 500GB SATA drive, I can browse it, I can see the Windows 10 install etc.

I created a new USB boot drive to try and reinstall and now I can't even boot from that - it doesn't show up in the boot devices. I have been through the exact same process to create the USB drive as I used last night (and this isn't the first time I have done this - the method I use works fine elsewhere)

I'm not a noob - I have been doing this as a job for 20 years almost and I have NEVER had this amount of drama with a machine.

When I take the internal 500GB SATA drive out of the NUC and put it in a USB 3.0 caddy and plug it in and boot..... low and behold it shows up as bootable (Windows then has a fit and want to do a repair but thats beside the point ). Obviously the HDD works, I knew that anyway because as I said I could see it in the NUC's BIOS file manager.

I have downgraded BIOS to v60, same thing. I have cleared CMOS. I have set BIOS settings to default. Nothing works.

Machine is running a single Kingston 8GB SO-DIMM that is on the Intel NUC6i3SYH website as being 'user tested' - KVR21S15D8/8

System Memory for Intel® NUC Kits NUC6i[x]SY

Not sure what to do now.

I am trying to add a Sata controller to my little NUC and make it a FreeNAS server.  To do this, I installed a M2 -> PCI-E x4 adapter board  (from ali, marked LM-141X-v1.0)

If I add this converter to my NUCi3SYK and connect power to the floppy style power connector on the board, it works great.. my sata controller or network cards will show up in the bios, and work just fine in freenas.

Weird thing is, if I try the same setup on my NUC5i3RYK nothing happens. The bios says there is no card installed, and it wont show up in freenas or any other os I tested ???

I compared the pinout of the m2 slot in the technical docs of both nuc's and cant see any difference ?

Any ideas on why this does not work ? I have tried it with a few different m2 <-> pci-e converters, pci-e cards, all kinds of bios settings etc.. it just wont show up.. Bus as soon as I plug in into the nuc6 it just works..

Not really a NUC specific question, we have had this working perfectly on NUCs under Linux, and we're getting there on the NUC7i5/NUC7i7 units under windows, too.

.

We're embedding NUC motherboards in units for film- sets, and the units don't even have a power on/off button... Actually there are no buttons at all.
Basically they turns on when power is present, and closes when power is off, and in-between they act like the small robots they are...
In linux we made this a dead robust solution. Had them on set for 18 months and they always worked.

There is no way to attach a screen to the unit (HDMI/display port is not exposed), they are remotely serviced and basically you interface with the units through web-apps.
we also really want to avoid the user hooking up a screen, a keyboard and a mouse and start playing solitaire on them. To the user, this is just a smart IoT device.

We're still early in the Windows testing, compared to our linux experiences, but any tips and tricks are advised. But BSOD at startup is a bugger if/when it happens, though it seems pulling the plug and re-plugging it solves most BSOD we have lately. (We have done a bit of config)

But what are your advices for this kind of setup. I am pretty certain we're not the only ones using windows like this.

We have to use Pro 64, not IoT

Gunleik

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.

Hi,

I want to know if there is any issue by installing win10 pro on NUC D34010WYKH ? I install the win with no problem after disabling the UEFI but after finishing the installation it doesn't reboot from SATA.

Please give me a hint!!

Regards

Saeedeh

Hi there,

I'm having issue to get the serial over lan working on Centos 7.3. Could you please let me know what are the specification of the serial, ie: speed, unit, word.

Thanks.

Intel has released a firmware update for the TB3 controller. The download page lacks the release notes/changelog. The PDF on the page shows the update for FW Ver 18....

What is new in FW 25?

Can Intel please include a changelog+releasenotes with every driver/firmware/bios update?

I noticed that the NUC DE3815TYBE does not restart while HDMI display is connected.

I run Linux and I tried many BIOS version TYBY10H.86A.0060, 054,052.

Did you ever face this issue ?

So this was mentioned in another discussion that was marked as answered but looks to have just been abandoned by the original poster (Thread 115121).  I am seeing UEFI PXE boot problems on the 7th gen nucs similar to what was mentioned in that thread.  We have 50+ of each of the following NUC models...D34010WYK, NUC5i3RYK, NUC6i5SYK.  All of them transitioned fairly well from Legacy PXE Boot to UEFI PXE Boot (Some did need BIOS updates but that is to be expected).  However our newest stock of NUC7i5BNK's will not boot to PXE in UEFI (BIOS updated and all).  The options exist in the BIOS options and the device recognizes and serves up the option to network boot.  Selecting the IPv4 boot option event initiates the process and sees the network (Media detected message), but it wont go any further.  I can even flip the device to non-secure boot non-UEFI, and PXE boot the device perfectly fine using Legacy network boot.  I would REALLY prefer to move forward and not build the newest NUCs in legacy mode while all the older model NUCs transition over to UEFI and secure boot.

I have a new NUC7i5BNH and I noticed that the fan ran at constant speed. I found the Cooling page in the BIOS and set it to Quiet - this allowed the fan to slow down and stop when the CPU was not loaded.

I then updated the BIOS - the previous one had a March date, the new one July. With the new BIOS, the fan runs at a constant 3700RPM no matter what I set for the fan mode. I see several other threads reporting the same problem (but was asked to start a new thread). Given that it worked before the BIOS update, it is evidently not a hardware problem and is instead a bug introduced into the BIOS. How can this be escalated to the proper team to fix it?

Hi

I have just set up a NUCi57BNK connecting on HDMI to my ACER S240HLBID. I press the power button on the NUC and the monitor (previously on an amber standby light) powers off. Even if I press the monitor power button it refuses to light up and the monitor remains black. If I unplug the monitor power cable for at least 10 seconds and plug in again I can get the monitor running again. This only happens when the NUC has been powered off for at least 10 minutes. Any less and the monitor works OK. Any ideas?

Ian