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.

I'm trying to figure out if the NUC7i3BNH is capable of passing through an Atmos signal? In the specs of the NUC it reads "7.1 digital". So I'm not quite sure if this includes a 5.1.2 channel for example. My setup consists of a Denon Atmos-Receiver and I want to run Kodi Krypton.

Intel® NUC Kit NUC7i3BNH Specifications

Thanks for your input.

I've a brand new NUC 7i5BNH.

It's connected to a Iiyama G-Master GB2888UHSU-B1 28" monitor with the iiyama supplied HDMI cable. The monitor has speakers.

I've installed Windows 10 and used the Intel driver update facility to update all the drivers it recommends. I've also installed the latest Intel Iris Plus 640 graphics driver (and am getting screen flicker but that's another story).

The problem is there's no sound. There's a red cross across the speaker symbol in the bottom right and if I right click it says no audio devices are installed. I've tried the troubleshooter but it can't detect the problem.

Can anyone help?

Thanks

Hi there.

I've come across an annoying issue where the HDMI video is fine but the audio doesn't seem to work on a Samsung UN32EH5300 when paired with a NUC7i3BNH. The audio on the TV has worked fine with both a PS3 and a PS4 as well as an older NUC, the D34010WYKH.

Swapping for a different brand of cable did nothing however switching to different TVs (Samsung HPT5064X/XAC and Sony KDL-37XBR6) did show the audio from the NUC7i3BNH working fine on them.

OS: Ubuntu Mate 16.10

Bios: bnkbl357.86a.0036.2017.0105.1112

I assume this is a bios issue but was wondering if there's anything else I can try.

Hi!

I'm having some issues with my brand new NUC6CAYH: The screen will randomly turn completely black for a few seconds.

This happens almost every minute. The NUC is hooked up to a display via VGA (resolution: 1920x1080@60 Hz). I'm not experiencing the same issue when I'm using an HDMI display (different resolution and refresh rate).

I have Windows 10 installed with the latest updates. The BIOS version is AYAPLCEL.86A and I applied this HDMI firmware update: Download HDMI 2.0 Firmware Update Tool for Intel® NUC Kit NUC7i3BN, NUC7i5BN, NUC7i7BN, NUC6CAY .

I have also installed the latest graphics drivers (15.46.2.4729) but I got the same problems with the previous drivers.

Any workarounds? Thanks in advance!

Hello,

here comes a critical experience report about NUC5PPYH with a few questions and recommendations to Intel:

HARDWARE:

I bought the NUC5PPYH in october 2016, installed Corsair Valueselect DDR3l 1x8GB 1600Mhz, no hard disk, all OS-installations I tried used either USB3-readers (SanDisk or Kingston with fast SD-cards) or a USB-DVD-drive (Samsung).

OPERATING SYSTEMS:

Ubuntu 14 LTS and 16 LTS run well.

OpenBSD 6.0 does not run well (installation is more-or-less possible, but when the system starts it has graphic problems, screen flickers already in command line mode on both HDMI and VGA, graphic mode doesn't run at all).

(interesting: the same USB-SD-card that has problems in the NUC starts and runs perfectly when I insert it in an older Compaq Notebook from ca 2011 with Intel core I3 M370 cpu)

Suse 42.1 and 42.2 boot and run extremely slow (boot takes some minutes), show graphic problems (mouse pointer traces), and behave quite instable. Not better on my other machines.

Debian 8.6.0 can be installed, but crashes completly after short time (probably graphic problems).

(interesting: the same USB-SD-card that crashes in the NUC starts and runs perfectly when I insert it in an older Compaq Notebook from ca 2011 with Intel core I3 M370 cpu)

Fedora 25 runs well and uses all 4 cores.

PROBLEMS:

The system worked well for several months, sometimes I used the Ubuntu-stick, sometimes Fedora.

The problems started in June 2017 when the system began refusing to boot, no matter if an OS-USB-stick was installed or not. Sometimes, I could reanimate it by temporarily disconnecting it from power and repeat the boot attempt. Things deteriorated, and then the system crashed with frozen and distorted screen (content mixed with green pixels). The NUC could not be started again.

I drove to the vendor, gave him the complete NUC package as I bought it (blue box, power supply, Vesa-bracket, no RAM), and they sent it to an Intel Service Station. 4 weeks later I received a new NUC with the comment that the old one couldn't be repaired, however, I got it without power supply, bracket, etc. After a short mudwrestling, the vendor opened another NUC-box from the shelf and handed me the missing parts. Back home again I installed the RAM and this time an SSD-harddrive WD Green 120GB Sata 2.5.

Then I booted the NUC and entered setup (F2): RAM and SSD had been recognized and I made only 3 changes: Boot USB Devices First (active), OS-Selection (Linux), Supervisor-PW.

I saved the changes, booted again to see if the changes were active, and everything was fine.

Then I shut down the NUC and disconnected it from AC-mains. Some hours later, I plugged it in again, this time with the DVD-drive in the lower front USB-port - and nothing happened: all devices dead: keyboard dark, mouse without light, dark screen, no noises/signs from DVD-drive, no boot, just the power lamp and fan were active.

The next days I tried all tricks to get the new NUC back to life: BIOS-jumper, power-button-menu, AC-disconnection. After many attempts it suddenly started and I updated the BIOS from version 57 to the latest version 62.    

I started the NUC again, without any drive, just to look into the BIOS-setup. I could enter it with F2, the BIOS was updated, and the 3 old changes were still in place - and then out of the sudden the BIOS-screen froze with distorted content and green pixels again. Could not leave the BIOS properly, just power down. Boot is not possible anymore, tried again all tricks, this time I even disconnected the battery (tried it 3 times, waited ca 3 minutes), no improvement, just power lamp and fan become active. So, the life of the 2nd NUC was quite short!

QUESTIONS, COMMENTS, AND SUGGESTIONS:

1) Is there anything more I can try? (besides BIOS-jumper, battery connect/disconnect, power-button-menu, AC-connect/disconnect)?

2) Can the problems be caused by disconnection from AC-mains? (even the 1st NUC had boot problems when I left it disconnected for some weeks)

3) Can the NUC be permanently damaged when the user plugs devices, that draw more current than a normal memory-stick, in the 3 weak USB-ports? (the DVD-drive starts immediately running when I plug it into the upper/charge port, but stays quite when I plug it into one of the other USB-ports). No hint in the documentation. I used Kingston-readers with the first NUC even in the weak USB-ports, and saw that those readers got hot under operation (means: they draw some current).

4) When Intel makes the next redesign of the NUC-boards, please, locate the battery connector on the component side (where the RAM is), so that the customers don't need to disassemble the whole device when they try to reanimate a crashed NUC.

5) I don't like to drive back to the innocent vendor and have long/angry discussions (they would probably throw the NUC away like the 1st one and maybe send me a new, but what's the benefit? I have no reason to believe that the 3rd NUC would work better than the others. And then, what? Complain-and-warranty-loop until the end of the warranty-period is reached?). Hence, I would prefer to send it directly to the responsible Intel-NUC-development/quality department so that the engineers can analyse it and learn from this case (and send me a new and improved NUC later on, maybe next year). Is that OK for Intel? Can Intel give me the correct contact/shipping address, please?

6) Concerning the OS-installation issues above:

If an OS-USB-installation runs on an older machine (e.g. Compaq Notebook from ca 2011 with Intel core I3 M370 cpu), is there any BIOS-configuration possible that makes the NUC compatible to the older Intel-computers? (Example: virtualization features that can be switched off).

Would be great to have compatibility switches in the BIOS (product suggestion).

Many thanks for Your response in advance.

Best regards,

Martin

New Unhappy Customer

Hi there,

I'm new to this blog and support site, so bare with me with my issue.

I also have flickering with my LG TV 65UH7650 with my intel Nuc NUC7i5BNH.

Before this I had my NUC5i5RYH specs: Samsung 850 EVO SSD 250GB, Kingston 32GB, which had no issues with and I think the cable was a HDMI 1.4.

So my specs for the new NUC: NUC7i5BNH, Samsung EVO 960 M.2 250GB, Corsair Valueselect DDR 16GB 2133MHz. The HDMI cable is from Primecables.com specs: Premium HDMI 2.0 with nylon jacket model pc-5100n2-6ft.

Once I unplugged the NUC7i5BNH and to plug it in my other tv Haier 50" 1080p there's no issue of flickering.

I will be updating the LG TV with a new update but not sure what are the updates. I'll get back to you if it works or don't.

Thank You

Follow up: When I first had the NUC7i5BNH the flickering was every 15 seconds but now with down graded the graphics drivers to 15.45.18.4664 the flickering is every 5-8 minutes.

The LG TV firmware version is 04.31.20.

Any other info would be appreciated.

In the Intel RealSense forums there are several discussions about power problems with the sensor. This is due to limited power supply from the USB 3 ports.

With the 6th gen NUC, the sensor works fine, but with the new 7th gen versions, there seems to be power issues. I tried to connect it to all possible USB ports (even with an adapter to the USB3c). I deactivated all possible power saving options in Windows, but the problem stays the same. The sensor works fine when I connect it to an external active USB hub though - so it's definitely a problem of the NUC. I already updated to the newest BIOS and latest sensor drivers.

This was tested on 5 NUCs - 3 of 6th gen and 2 of the 7th gen (all i5 versions).

Is there any way to fix this?

I have just purchased a new NUC6i5SYH kit and installed:

Samsung 250GB SSD 850 EVO m.2;

Kingston 8GB HyperX DDR4

I now wish to start up the NUC to check the BIOS version, and then update as necessary before installing the OS. I am not sure whether I will use Windows 10, or LINUX at this stage, so want to update BIOS without OS.

This might sound like a total Newbie question, but how can I communicate with the NUC. I tried using a wireless Keyboard and mouse, but neither was recognised, so there was no way that I could "press F2" to enter BIOS.

Unfortunately I do not have access, at present, to a wired keyboard and mouse so cannot try that, but I did seem to remember reading somewhere that wireless can be used?

Any help on way to proceed would most welcome and appreciated.

I just received my shrink-wrapped NUC7i5BNH (Batch #CNG674K30E manufactured 21Apr2017) from Newegg by FedEx.  The grey metal between heat sink opening and lid is bent, and the heat sinks inside appear to be slightly sloped (closer to the case at bottom, further away from the case at top).  Is this normal?  I have not tried anything like removing the lid or attempting to straighten grey metal. See photo.

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

Hello,

This Super-I/O controller is installed in NUC5PPYH.

The linux kernel driver for it is incomplete!

So I'm looking for its datasheet to complete the driver. ITE doesn't provide with datasheets at all.

Can somebody provide it? I'd be very glade to get it!

Thanks in advance,

Michael

Hello all,

After working on building up my NUC, thinking I'm going to have a sweet running computer for years and years, I'm wondering now if I'm still going to be using this computer!  This is currently working into being a pain.  The computer doesn't want to wake up after being idle for 10 minutes or more.  I have to hit the power button on monitor two or three times to wake the computer up!  It looks like something is starting to happen when I wake the computer up with mouse movement, but the process never finishes.  The closest I get is "Cable Disconnected".  This has nothing to do with the OS, (Win 10 Pro) as I was getting the same problem when using multiple Linux OSs too.  This has to do with BIOS or the hardware and firmware before the OS. 

Any suggestions how to remedy this?

My computer is a NUC5i5RYH;

with

16 GB of Crucial Memory

HGST Travelstar 7K1000 2.5-Inch 1TB

K350 Logitech  Wireless Keyboard

Acer H213H monitor

I bought my NUC to use as a media center connected to both my TV (HDMI) and projector (DVI).

The HDMI connection on the TV works well and gives me full color. Using a HDMI-DVI adapter or a USB-C to DVI adapter and connecting multiple different DVI cables to my projector gives me a purple / pink screen where green displays as black. Changing the green slider in the graphics control panel doesn't change anything on the output whereas the red and blue sliders do. See the attached images.

I am using the latest BIOS and display drivers but the problem has existed with previous versions too. The pink hue is also present in the boot up screens so I don't think it's driver related. When connecting the same setup to a different pc with a GTX980Ti or a GTX760 over HDMI to DVI the colors look fine so the projector is also not to blame.

There are  pops and ticks noise when the sound start (NUC7I7BNH, Windows 10 x64, Apple earpods). This noise is very annoying. Sometimes peaks of ticks deafen me.

I think the issue was about the audio card power management but I found nothing in the current Realtek driver Fix for Realtek sound popping and/or high pitched tone/squeal | NotebookReview

Intel, make something, quiclky, PLEASE

Currently my main monitor is running 3840x2160@30Hz via HDMI and the 2nd monitor maxes out at 1920x1080 on the mDisplay Port.

I updated all the drivers but still the 2nd display is resolution limited, Reading the documentation this should be capable.

my code is

#include <bluetooth/bluetooth.h>

#include <bluetooth/hci.h>

#include <bluetooth/hci_lib.h>

#include <stdio.h>

#include <stdlib.h>

#include <stdbool.h>

#include <sys/ioctl.h>

#include <sys/socket.h>

#include <iostream>

#include <bluetooth/hci.h>

using namespace std;

//#define HCI_MAX_DEV 64

#define BLUE_ERROR 2

#define BLUE_NOT_CONNECTED -1

bool error;

int findConn(int s, int dev_id, long arg) {

        struct hci_conn_list_req *cl;

        struct hci_conn_info *ci;

        if ((cl = (hci_conn_list_req*)malloc(HCI_MAX_DEV * sizeof(*ci) + sizeof(*cl))) == NULL) {

                perror("malloc");

                error = true;

                return 0;

        }

        cl->dev_id = dev_id;

        cl->conn_num = HCI_MAX_DEV;

        ci = cl->conn_info;

        if (ioctl(s, HCIGETCONNLIST, (void *)cl)) {

                perror("Could not get connection list");

                error = true;

                free(cl);

                return 0;

        }

        int i;

        for (i = 0; i < cl->conn_num; i++, ci++) {

                if (!bacmp((bdaddr_t *)arg, &ci->bdaddr)) {

                        free(cl);

                        return 1;

                }

        }

        free(cl);

        return 0;

}

int rssi(char *address) {

        struct hci_conn_info_req *cr;

        int8_t rssi;

        int dd, dev_id;

        bdaddr_t bdaddr;

        str2ba(address, &bdaddr);

        error = false;

        dev_id = hci_for_each_dev(HCI_UP, findConn, (long)&bdaddr);

        if (dev_id < 0) {

                if (error) {

                        return BLUE_ERROR;

                }

                else {

                       return BLUE_NOT_CONNECTED;

                }

        }

        dd = hci_open_dev(dev_id);

        if (dd < 0) {

                perror("Could not open HCI device");

                return BLUE_ERROR;

        }

        if ((cr = (hci_conn_info_req*)malloc(sizeof(struct hci_conn_info_req) + sizeof(struct hci_conn_info))) == NULL) {

                perror("malloc");

                hci_close_dev(dd);

                return BLUE_ERROR;

        }

        bacpy(&cr->bdaddr, &bdaddr);

        cr->type = ACL_LINK;

        if (ioctl(dd, HCIGETCONNINFO, (unsigned long)cr) < 0) {

                perror("Could not get connection info");

                free(cr);

                hci_close_dev(dd);

                return BLUE_ERROR;

        }

        if (hci_read_rssi(dd, htobs(cr->conn_info->handle), &rssi, 1000) < 0) {

                perror("Could not read RSSI");

free(cr);

                hci_close_dev(dd);

                return BLUE_ERROR;

        }

        free(cr);

        hci_close_dev(dd);

        return rssi;

}

int main()

{

    cout<<"rssi = "<<rssi("80:A5:89:3D:85:3A")<<endl;

    cout<<"rssi = "<<rssi("E4:02:9B:84:A4:76")<<endl;

}

In output I am getting rssi = -1(BLUE_NOT_CONNECTED),. Any suggestions , what I should do?

My NUC7i5BNH has worked perfectly for 3+ months until the last week when the main display blanks out for 2-3 seconds multiple times an hour (depending on what I am doing). I have all the latest drivers All latest drivers as of 6/15/2017 and and believe the issue only started when I upgraded to BIOS 0048 in the last few days.

I run 2 monitors:

Dell U3415W (3440x1440@60p Hz) running on the thunderbolt connector

Dell U2717D (2560x1440@60 Hz) running on the HDMI connector

Only the Dell U3415W monitor blanks out, however the audio playing through the monitor speakers continues working fine even when the screen is blank.

I can't be absolutely certain that it happened as a result of 0048 but I can say that I haven't updated any other drivers on my NUC since mid June when the last Intel HD Graphics Driver (4678) came out.

I've seen other threads with issues that seem similar but those people are using 4K TVs/Monitors.

Intel SSU (System Support Utility) output attached

Please can Intel provide an update on this issue and what the fix is.

thanks

I have not found how to change the video resolution to the maximum allowed.

In Kodi, I only encounter up to full hd 1920x1080 and would like to keep the NUC at the maximum resolution allowed.

Is the 4K resolution available only when the hdmi cable is connected to a 4K TV?

My TV is full HD 1920x1080 and will that be the issue? I do not think so, and I'd like some tips on it, because the NUC will be connected to a 4K TV.

Using NUC7i5BNH with latest virtual BIOS I am stuck in that when I boot into the Windows recovery disk I get a failure to restore message as there is a data disc in the boot BIOS. On looking at the BIOS all disks are shown as legacy with nothing under UEFI, which I don't know why that would be. So then I thought maybe the resolution is simply to remove the back up USB drive from the legacy BIOS list, but no, you cannot remove one USB device it has to be all, which is unhelpful as the drive with the recovery CD is USB driven. Thus I then wonder why the HD with Windows is not showing as a UEFI drive? But, even if it was possible that doesn't solve the problem of how to stop a USB data drive showing up in the legacy BIOS window and curtailing the recovery operation. Which brings me to my last question as to why should Windows care if a data drive is shown in BIOS, as it is the same drive it is going to get its data from anyway?

Thanks,

Jim.