Hi!

I have found two bugs in Intel NUC NUC6CAYH with BIOS version AYAPLCEL.86A.0041.2017.0825.1152:

1. When You select legacy boot and disable UEFI boot in BIOS, then booting from Samsung SSD 850 EVO fails with "A bootable device has not been detected" or "No bootable device found". When You press F10 and select hard drive from menu, then it is able to boot just fine with legacy boot. To solve this issue, You have to also enable UEFI boot - then legacy boot works automatically.
2. If You lower AGP aperture size to minimum possible value in BIOS, then NUC will not boot at all if You disconnect monitor from HDMI port. If You want to run NUC in headless mode, without monitor, raise AGP aperture size.

Posting here just in case someone would need it.

I am having issues with some audio, particularly in games, when my TV is set to 4k@60Hz resolution.  I mentioned this in the massive flickering thread and cvare told me to break it out, even though I think this is all related.

Setup: NUC7I5BNH, Vizio m55-C2 4k TV, Audio either through TV or using ARC to Sony XT:HT1 soundbar. 

Problem: When I have the resolution set to 4k@60Hz, ifI start a game in full screen mode that is at a different resolution than the desktop, I get no sound.  If Windows resolution is set to 1080p in the Intel Graphics Settings, the sound is fine (but I don't want to change settings and reboot every time I want to pay a game).  In one of the games, I can select windowed mode and the sound then works.  However, when my resolution is set to 4k, it only displays in 1/4 of the screen so there is obviously another problem there.  From looking around online, it sounds like others have experienced this before and it might be an HDMI handshake issue or some problem caused when trying to switch to a different resolution. 

Games: LEGO Star Wars: The Complete Saga

LEGO Star Wars III: The Clone Wars

LEGO Star Wars: The Force Awakens (this is the one that the audio works in windowed mode but the video is weird)

The LEGO Movie Videogame

So the symptoms are different than with the flickering issues, but it all seems related to HDMI/driver issues.  Is this a problem with the LSPCON chips in these NUCs?

Hi there,

Working with Device Guard on NUC5i5MYBE´s and having a problem clearing UEFI and Secure Boot data after some tests with UEFI lock and signed policies...

The problem is that the NUC is not able to boot from UEFI devices with Secure Boot enabled in the BIOS/Firmware, if I disable Secure Boot everything works in legacy mode (Before the UEFI Lock, everything worked with UEFI and Secure Boot from DVD, USB and PXE boot in UEFI mode.

To reset to NUC i did a BIOS Recovery by the Security Jumper and a USB device with the latest BIOS currently 038, and even after this it seems like there is some information left in the BIOS

In did reproduced this on another NUC with same result, so now I have 2 NUC´s that cannot boot using UEFI Secure Boot

So, any input on how to clear the UEFI, Secure Boot?

Kind Regards

Jesper Hanno

Hi,

Cooling/noise seems to be one of the big issues of these nice little NUCs. They are not any more placed under the desk as the old big boxes, but very close to your ears. I've managed to get my NUC7i5BNK quiet by turning the fan down to a default value of 32 cycles. Now I plan to replace my old display (1280x1024) with QHD or 4K display. My fear: Will this cause the fan to work harder if the graphics unit has to do more work, so that noise gets inacceptable again?

Thanks if someone could share his/her experience.

Regards,

Stefano

Two issues:

From day one, my Nuc7i7bnh has not been able to wake up the monitor after going to sleep.  The Nuc will wake up, the screen will not wake up.  The screen claims it is not receiving a signal.  This occurs with every HDMI cable I have tried.  My brother has the same exact issue with his NUC.  Several of of my colleagues who own Nuc's are having the same exact issue. By the way, other computers wake up correctly with this monitor (Dell P2415Q, 4k 60hz monitor).   So the issue does not appear to be with the monitor.

The only way I was able to get around this wake up issue was to use a USB c to display port cable.  With this cable the Nuc was able to wake up the monitor.

In July, I started to have the dreaded black screen flicker.  Colleagues are also having the exact same issue.  So is my brother.  It is driving everyone nuts!

I had great hope when Intel delivered the new display driver.  It appeared to work for a while.  Unfortunately, the dreaded black screen flash has reappeared.  Not as frequent as in the past, nevertheless, it is back!  I also discovered that this new driver is not operating at 60hz, it is operating at 29hz (according to Windows 10).  I have totally uninstalled the driver, switched to the generic Microsoft display driver, rebooted several times and reinstalled the latest Intel display driver.  Same results every time!  29hz.

Please note:

The difference in the display hertz for the Microsoft generic display driver and the latest Intel display driver.

Unfortunately, returning the Nuc is not a good option.  Why?  The Nuc was only part of the expense.  I have the expense of an SSD, 32gb of ram, a Bluetooth keyboard and mouse, a monitor.

So far, the Nuc is about the most troublesome computer I have ever owned.  (I have owned computers since 1985.)

Here is a video where it refuses to wake up:

Amazon Drive

Equipment:

Intel Nuc 7i7bnh

SecurOmax HDMI cable 2ft - HDMI 2.0 (4K @ 60Hz) Ready - 28AWG Braided Cord - High Speed 18Gbps  (Only will do 30Hz in 4k with newest Intel display driver)

(Alternative Cable - USB C to Display port cable)

Samsung 960 EVO - 1tb PCIe NVMe - M.2

Crucial 32gb DDR 2133 MT/s (PC4-17000)

Dell KM 717 Bluetooth keyboard and Mouse

Dell P2415Q - (4k monitor, 60hz capable)

Dell AC511 usb soundbar

Windows 10 Pro (64bit)

New NUC7i7BNH system with 32Gb Optane Memory, 16Gb RAM, 1,5Tb HDD.

I am trying to connect system to Sony Bravia TV via HDMI cable/port.

For first week of using the system I had no problem connecting to TV.

Late last week, following either a Win10 update and/or Intel BIOS update, I have not been able to connect to TV.  Now, after POST,  I get a black screen with error display - 'Unsupported signal. Check device output.'

I am presuming it is a problem with BIOS as computer doesn't even get to point of loading operating system.

Do I need to roll back to previous BIOS or is their a new BIOS fix?

Thanks,

David Sanderson

I am experiencing problems using the AMT SOL feature on a NUC5i5MYHE. Here's the symptom:

• Windows 7 just hangs when using the port (e.g., using PowerShell). If I configure a timeout, I just get the timeout, but no serial output.
• Linux experiences a long delay after printing the characters, but it also complains about unexpected interrupts. Using the "irqpoll" cmdline option, it works fine.
• A baremetal kernel works fine without interrupts, and even the interrupt-driven configuration works if you find the correct interrupt to use.

Interestingly, the interrupt that both Linux and Windows report (17) does not match the actual one that can be observed (19). Furthermore, IRQ 19 is also the SATA interrupt, which makes me wonder if 17 is actually the correct one, but for some reason it is not being used.

This happens on several machines of this model, and I have tried multiple BIOS versions, including the most recent one (86A.0038).

Has anyone else seen this? I would really appreciate some help

There is an endless loop in the installation request of the actual LAN driver.

It seems that the service helper isn't able to detect the installed version or the new driver package has an old version number...

In my case the wireless driver was updated correctly, after reboot only (and again) the LAN driver schould be installed.

Regards

Holger

Hello,

I have an Intel NUC5PPYH and I cannot have a flawless duplex printing. I am currently running Win 10 Pro 64 bit built 1703. Whenever I try to print a 2-page document, created on MS Office 2010 Word, I end up with a sheet of paper where the front page print does not 100% overlap the print on the back page. Lets say that the front page has 32 lines of words typed and the back has also 32 lines of words typed. In an ideal situation, the front print (i.e the first 32 lines) should overlap the next 32 lines. In my case, printing of the front page starts lower than usual (4 lines lower to be precise) whereas the back page printing starts normally on the top of the page, thus I am having a sheet of paper where if you place it under any light, you could see that the 2 printings (front & back) do not overlap. Sorry for my english, this is the best way I can describe the problem, treat the document in question as an x-ray and place it under normal everyday lighting. Every paper has some degree of transparency.

I am using the default settings in MS Word, margins, spaces etc are used as is.

I was facing the same problem when running Win 10 Pro 64 bit built 1607. I updated to built 1703 hoping for a fix. My printer was an HP DeskJet Ink Advantage 4535 AiO, which had automatic 2-sided printing and was connected to my NUC through usb cable. I had to return it to the store. I have also used a Samsung Multifunction Printer Xpress M2885FW which also had automatic 2-sided printing, connect it through usb, the problem still persists.

Moved my NUC to a place where another HP printer which also had automatic 2-sided printing, unfortunately, problem persists.

I have also converted the aforementioned 2-sided file to a PDF, still facing duplex error.

I have also uninstalled Win 10 Pro and installed Win 7 Ultimate 64 bit. I didn't solved the problem.

While running built 1607 (Win 10 Pro 64 bit) I also used MS Office 2007 and 2016 Pro, faulty duplex printing continued. I am currently on built 1703 with MS Office 2016 Pro.

Purchased heavier paper (120gr instead of 80gr), thinking that it may be a roller issue (or whatever mechanism is used to grab the paper), didn't solved it either.

I have also installed Libre Office and used it for printing only documents that were created in MS Office and magically the problem was solved! Used Libre to open other files created under MS Office, and printing was fine.

Lastly I have also emailed the above document to a couple of friends that I knew they had printers with automatic 2-sided printing, asked them to not change any Office parameter and print it. 2-sided printing was fine.

Looking forward to a solution.

Thank you.

My Intel NUC NUC7i5BNH frequently has bluescreens and apps (Chrome, Opera, Adobe Lightroom, iTunes, MMC/EventViewer...) are crashing suddenly or report errors in application log (ZeroConfigService.exe [Version: 19.60.0.0])

The lastest minidumps (from today) are attached

HW: 1x Samsung SSD 850 EVO (500GB), 2x Cruical CT8G4SFD8213 RAM (2x, 8GB, DDR4-2133, SO-DIMM 260 pin)

BIOS Version 0049

Windows Edition: 10 Pro 64-Bit Version 1703

Regards

Holger

I am running my NUC with BIOS .050 and want to downgrade it to .047

No matter how I try to downgrade, it seems impossible for some reason, even using the jumper method.

I was on BIOS 51, tried to downgrade to 47, as it has the previous UEFI graphics, but the BIOS says that it's incompatible BIOS (despite it still has the same ME version).

Tried to downgrade to 50 - worked.

Tried from 50 to 49, incompatible.

Tried the F4 method - getting blank screen when booting, doesn't do anything  (tested on 4k TV or 1080P monitor).

Tried removing the security jumper (following the exact instructions here)  - getting blank screen when booting, doesn't do anything  (tested on 4k TV or 1080P monitor).

I have asked other members in the NUC forum and they have the same results.

Is there any way to downgrade to .047?

Hi,

what's the best way to connect a display (QHD or 4K) to my NUC7i5BNK? HDMI/HDMI, HDMI/Displayport (with adapter), Thunderbolt/HDMI or Thunderbolt/Displayport?

Thanks for sharing your experience,

Stefano

I have a kiosk system I setup and due to the NUC's inability to come out of sleep from my remotes I'm trying ready mode.  Problem is even if I disable password on startup, password to resume from sleep or hibernation, when coming out of ready mode it requires me to login again.  How do I stop this?

Thanks.

Steve

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!

I have one of the more annoying issues ever which would simply won't go away.

Some background first:

I'm using a Windows 10 x64 PC with BitLocker encryption backed by TPM.

In every 3-4 COLD boots at the beginning of the day i would get a message from windows at boot time that the TPM is unavailable, and because of that windows could not automatically DE-crypt my drive, and i should use the recovery key instead.

At this point more often than not, i cannot even do that because my keyboard isn't working until i disconnect the usb hub cable, and reconnect it.

At this point there is a simple work-around, to simply press CTRL-ALT-DELETE and perform a warm boot. The next boot ALWAYS work using the TPM which is available at this point. Notice i cannot reproduce the issue using warm boots.

In addition do note that i usually leave the machine completely unplugged for several hours / days to save power.

Sometimes the problem escalates to the point the BCD data is corrupted, and a manual repair is needed. But this is far more rare.

My boot settings are: Fastboot disabled , secureboot enabled, and TPM is active and used for BitLocker.

I'm using the latest available BIOS (49)

This is lengthy but for those who read it and for Intel, trying to avoid any unnecessary questions.  Been working in this for a long time.  I think eventually I get somewhere, but still not solved.

I am having trouble with my infrared port on my NUC.  Problem I've read others are having as well.  My problem is specifically around turning the unit on from sleep.  Other buttons seem to work including powering it off.  To start, my setup:

• Intel BOXNUC7I3BNK NUC Kit
• Corsair Force MP500 Series M.2 SSD 120GB Internal Drive (CSSD-F120GBMP500)
• Ballistix Sport LT 8GB Kit (4GBx2) DDR4 2400 MT/s (PC4-19200) SODIMM 260-Pin - BLS2K4G4S240FSD (Gray)
• Windows 10 Pro all updates
• ITECIR and eHome Infared transceivers both show under HID in Device Manager
• Connected to a Panasonic Plasma with HDMI cable, no CEC.

For drivers:

• All Windows updates
• BIOS at latest 0051 version
• Have all drivers as of today on this site: https://downloadcenter.intel.com/search?keyword=NUC7I3BNK

Only software on this system is KODI.  And frequently on my many Windows re-installs didn't bothering even with KODI.  The reason I bought the NUC was it would run Windows, and came integrated with infrared.  Infrared doesn't work?  No value.

Bios Settings of relevance:

• Enhanced Consumer IR checked
• Unchecked HDMI CEC Control due to other forums with people troubleshooting IR that sounded like this may tie to loosing the IR all together.
• S3 and S4/S5 set to allow wake on CIR
• Power set to Max Performance

What's happening:

I have a number of remotes, all of them 95% of the buttons work, including putting the device to sleep/off, only 1 (Harmony) can actually bring the device out of sleep and online again but not the remote I want to use.  The remotes I'm testing with:

• Harmony 880 programmed as a Microsoft Digital Media Remote.  This remote has zero ability to turn on/off my XBox 360, however it's discrete on and off, as well as it's power toggle button will turn the NUC on and off.  All other functions work as well on the NUC.

• Microsoft XBox 360 newer media remote.  All functions work on this remote except power on (pressing the XBOX button on top right).  This will turn on and off an XBox 360 though.  I mention this because there seems to be a difference between how/what signals the buttons are sending.  The Harmony can't control the XBox but can the NUC.  This remote can control the XBox power on and off and all functions except power on for the NUC .

• Also have the older XBox 360 media remote.  This one functions the same as the newer XBox 360 media remote above.

According to Intel's ecosystem list, the last two remotes above are supposed to be compatible:

Things I've tried without any change in intended results to get the power on working.  Each was done with a refresh of the OS so no overlaps:

• Windows 10 out of the box.
• Windows 8 with as many drivers as I could get ot work.  The IR drivers did install and show the CIR and eHome drivers.
• Tried the MCE remote mapper tool but that seemed to have no impact.  Tried setting the X button to wake but nothing. 
• Tried going in registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\Four-digit_number and setting ForceHCResetOnResume to 1.
• Tried going in registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da and changed CodeSetNum0 to 0.  Also tried with just that change and deleting CodeSetNum1 - 3
• Tried going in registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da and changed CodeSetNum0 to 8 as some say.  Also tried with just that change and deleting CodeSetNum1 - 3
• Tried in regedit  going to key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da"  and in "ReportMappingTable"  change the line "0c,00,00,00,03,82,00," to "0c,00,00,00,03,81,00,".  Sounded more for shutdown but tried it.
• On the eHome Receiver in Device Manager I have it set to not allow the computer to turn off the device to save power.  The open to allow to wake is grayed out.
• I decide well why is everyone saying to go to the RC6 only registry entry I go to the RC6 XBox 360 area instead at Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57df.  I change the "0c,00,00,00,03,82,00," to "0c,00,00,00,03,81,00,".  After rebooting remote doesn't work to send to sleep.  OK that's something that it effected the remote.
• Sticking with this, I try Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57df.  I change the "0c,00,00,00,03,82,00," to "0c,00,00,00,03,83,00,".  This time it shuts down the computer completely.  No ability to turn it back on again from remote as usual.
• Then tried Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57df.  I change the "0c,00,00,00,03,82,00," to "0c,00,00,00,04,04,3D,".  This time Windows asked if I wanted to shutdown.  When i clicked enter it shutdown but couldn't power on still with the remote.

This was supposed to be a simple project for my father who is in a home to watch movies and enhance his life.  It's turned into a two month nightmare for me.  I know there are many threads out here with similar problems.  Can someone please help?  And the point of my effort in documenting this is I have all the drivers, bios update, HDMI 2.0 update, etc.  No stone left unturned that I know of.  Any help?  I can no longer return this to Amazon as my time has expired to do so.  Thinking the trick is in the XBOX360 RC6 branch of the registry "maybe?" but can't figure it out.  Still scratching my head why my Harmony remote turns it on and off with the power toggle or the power on and power off discrete commands.

Note since I've already spent a lot of money on remotes that don't work and actually have another NUC on it's way to test it, glad to physically send Intel whatever they want to test.  The NUC, the remotes, whatever.  This would eliminate Intel "not being able to reproduce this problem" that I see lots of people having in various ways.

Thoughts?

Thanks.

Steve

New NUC7i7BNH system with 32Gb Optane Memory, 16Gb RAM, 1,5Tb HDD.

I am trying to connect system to Sony Bravia TV via HDMI cable/port.

For first week of using the system I had no problem connecting to TV.

Late last week, following either a Win10 update and/or Intel BIOS update, I have not been able to connect to TV.  Now, after POST,  I get a black screen with error display - 'Unsupported signal. Check device output.'

I am presuming it is a problem with BIOS as computer doesn't even get to point of loading operating system.

Do I need to roll back to previous BIOS or is their a new BIOS fix?

Thanks,

David Sanderson

What does the NUC6i5 memory slots support, 260 or 288 pin memory modules?

Hello,

I have an issue with multiple NUC6CAYS NUC's.

I have 12 of those running as video playback devices.

Now I started to notice that in seemingly random intervals the NUC's completely lose their ethernet connectivity.

When checking the player it looks like the NIC just disappeared, it is nowhere to be found in the windows device manager or in the network adapter settings.

The only solutions I have found so far is turning off the device for approx. 10min. and restarting it. Normal reboots without the waiting period don't work.

Since these devices are deployed in a professional environment this is not a solution.

Hopefully there will be a solution for this soon.

I'm trying to enable TPM (PTT or fTPM) on the NUC 6i7KYB. I am currently running BIOS 42 (KYSKLi70.086A.0042.2016.0929.1933) which is the newest I can find.  I have turned on PTT in the BIOS and am booting secure UEFI.  I don’t see any the PCRs and my kernel module is throwing an error on loading.  I think I have debugged the problem down to ACPI IO Resources.  The MSFT0101 memory region (as defined in APCI) is at 0xFED40000 – 0xFED4087F.  When the TPM driver (tpm_crb.ko) starts, it reads the command buffer size (0xF80) from the TPM2 command size register and tries to allocate space at starting at 0xFED40080.  This is larger than the size of MSFT0101 and the module loading fails.  So one value is wrong, either the size of MSFT0101 or the command/receive buffer size reported by the TPM2 (PTT) registers.  I have modified the driver to use a smaller buffer size (0x7F0) but that does not work so I think it must require the entire buffer space.

Disassembling the ACPI tables, I can see that the _CRS method returns 0x880 but I don't know enough about ACPI to understand why.  So, is there a newer BIOS I should be using?  I know Intel doesn't like to support Linux, but that is a requirement.  I know that there is active development on this module by several Intel developers and I don't think this is a Linux problem.  Any help would be appreciated.

Message was edited by: John Ewalt