Hi. I`m having issues with a recently buyed NUC6CAYH. The screen will randomly turn completely black for a second or two. (it happend once every 4 or 5 minutes or once every 4 to 5 seconds)

It has windows 10 Pro installed with latest bios (040) and drivers installed.

It is connected via VGA cable to a LCD display (resolution: 1440x900@60Hz).

The things i`ve tried so far:

• lowering the display resolution to other than the native display stops the flickering or at least makes it less frequent.
• I had keyboard, mouse and two printers connected to a back USB port through a 2.0 USB hub. removing the USB hub eliminate de flickering (or at least it has not flicker once in about an hour) [Hub works flawlessly in other PCs]
• Connecting mouse keyboard and two USB hdds makes the flickering happen at least once every 30 minutes.

Thanks in advance and excuse my english.

I work about 15 years in IT, mainly as a Windows server specialist, but also desktop support / integration and software testing.

Since they first came out, I've been using and recommending Intel NUC's, by now I've installed about 30 of them, mostly with very happy customers as a result.

About the NUC6CAYH..

Recently a client of mine needed some simple Windows 10 pc's with a VGA connection, so I installed 3x NUC6CAYH.

The NUC's have very different production dates, yet ALL of them have the same issue of 1-2 seconds of black screen, sometimes as much as every 2 minutes.

After trying everything (changing screens, changing cables, trying different BIOS versions, trying different graphics driver versions, ...), without any result, I discovered on this forum that a lot of users are experiencing the same issues.

An issue like this is not something I would expect in a 2017 product (especially coming from Intel).

The client bought new screens with a HDMI connection, only to find out this also gives flickering every few minutes, again, on ALL of them! (the screen doesn't go completely black as when using VGA, it's less severe, a kind of fast flicker).

Needless to say this is a very disappointing experience for both my client and me.  Not to mention the cost of troubleshooting, only to find out it's a faulty product.

This looks like a design flaw, I can't believe Intel is still selling these!

Probably only a few % of the people with this issue will find the way to this forum, so that means a huge amount of frustrated customers will hesitate to buy an Intel product again.

I'm sure Intel knows exactly what the issue is, they should, after all these months and probably thousands of these units returning.

So my question is:

To other NUC6CAYH (with Windows 10) users:

Is there anyone here who's problem was actually completely solved (Please specificy if you use HDMI or VGA) if yes, which actions did you exactly take?

To Intel support:

As this issue seems so widespread, please tell us what the root cause is.  If you're not aware of the root cause, please escalate this to the right engineers to troubleshoot.  My feeling is that this specific issue is causing damage to Intel's good name, not to mention the huge troubleshooting costs for all people still buying this product.

Is there an actual solution? Will the problem be 100% solved with a replacement from Intel?

Thanks!

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

How my Nuc is connected to my TV.

NUC------------>YAMAHA RVA3060 HDMI input#4.------------------------------> TV sony KD-55X9005A input 4.

I have a really strange behavior.

Plugged to my LG Monitor, I do see the flickering as well on my NUC6CAYH that a lot of us are complaining about.:

I also tried the NUC plugged on my TV as described above through My Yamaha receiver.

I do not see the flickering anymore, BUT when I start  or stop the NUC, My TV is switch automatically to HDMI1 .  The funny part is I have no cable connected on HDM1 ....   it is very easilly showable as it happens on ALL switch on/off.

REALLY strange.

Needless to say, all drivers are up to date. HDMI has been flashed to last FW.

WHAT IS THE PLAN TO GET DECENT HDMI BEHAVIOUR ?

Hi,

If I try to export and import the bios settings as an profile on a usb stick all saved settings are lost. Is there a bug in the bios version?

Thanks for the help!

Andreas

I've seen a couple posts on here about the serial number being blank. Has anything changed in regards to inputting the serial in any other way then by editing it through the EFI shell? how can one do this at scale? I love these machines (we've one off a couple of them) and want to deploy many more, but this serial number is a requirement for inventory.

I have tried installing the Windows 10 Fall Creators Update (16299.15 and 16299.19) on a NUC5i7RYH both by using Microsoft's Windows 10 Installation Media Tool to create a USB stick and also by using the Windows 10 Update Assistant.

Both times after installing the Fall Creators Update, I have no internet connection.  Although Wi-Fi is switched on, it doesn't detect any Wi-Fi networks and just says 'No WiFi networks found' in Windows Action Centre.

The adapter settings in Control Panel > Network > Change Adapter Settings, shows a red cross next to Wi-Fi.

The Windows Network Diagnostics trouble-shooter is unable to fix the problem and just says "Problem with wireless adapter or access point - Not fixed".

In Device Manager > Properties > General Tab, it says "This device is working properly".

Wi-Fi details in Settings > Status > View Your Network Properties, show no MAC address and status as 'Not Operational':
Name: WiFi
Description: Intel(R) Dual Band Wireless-AC 7265
Physical address (MAC): 00:00:00:00:00:00
Status: Not operational
Maximum transmission unit: 1500
IPv4 address: 169.254.208.191/16
IPv6 address: fe80::<SNIPPED>/64
DNS servers: 192.168.1.1, 192.168.1.1
Connectivity (IPv4/IPv6): Disconnected

IPConfig from PowerShell shows 'Media disconnected':
Ethernet adapter Ethernet:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter WiFi:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 10:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

The NUC5i7RYH has a Intel Dual Band Wireless-AC 7265 Wi-Fi card.  On Windows 10 15063.674 it was running driver version 19.51.5.3 (Windows Update version), but this doesn't work on Windows 10 16299.19.  I tried installing 'WiFi_20.0.2_PROSet64_Win10.exe' from the Intel Drivers section of the website (19.51.7.2), but that makes no difference and Wi-Fi still doesn't work on 16299.19.  At the moment I've had to restore 16299.19 back to 15063.674 so that I have internet access again.

I also went through all the steps HERE, but am unable to determine what's wrong.

As a side note, the Intel driver version and date HERE needs updating, as it still shows 19.70.0, 9/3/2017 as the latest driver, instead of 20.0.2, 10/17/2017.

yesterday I did connected my NUC to the internet after a few days and found  7 Intel new drivers versions in addition to the same upgrading utility as Windows10 Creators update update fall 1709.

I bought the NUC in March 2017 and since then I spent more time updating drivers and windows 10 then to enjoy it as HTPC.I bought it hoping it was a more flexible choice of dedicated Android based equipment but I made a big mistake.

The first problem was the driver update utility itself.The old version was 2.9.2 and I am immediately try to upgrade to a version 3.X.I try to do it but the update fails with an error message.Armed with patience I try to find the new version of INTEL site utility but with surprise in the site there is nothing left and only an awkward "on line" version as an alternative to the manual update of drivers: INTEL nice results! compliment!
Even the "on line" version maintains the same defects already highlighted by me and other users (without results): Lan drivers do not update and even Intel Management Engine.

After that I also update the windows 10 to version 1709 apparently without problems.

The results are again the same as the other times: all the efforts to fine-tune programs to watch movies (such as Kody, or VLC) are lost again; and the images are stuttering again and lack of fluidity.

Yesterday evening after hours of work I found that now the configuration that works better of the old one is to put a 60p FPS in a fixed way in the INTEL display driver configuration and cut to Kodi the function to change the FPS according to the reproduced material. If i try to use 24-FPS settings in the video driver fullHD movies (that are at 24 FPS) are played stuttering  with any others old proven configurations now is no good anymore, and also in H265 compressed videos are re-emerging  a pixelation when played using dvxa acceleration; so i must use only sowftare decoding.

Needless to say that this situation is unsustainable: INTEL and Microsoft are unable to offer a HTPC solution that has a minimum of stability.And windows 10 has more than one year old and your NUC more than nine months old.

The question is: when do you think to offer, with Microsoft, something more stable perhaps with a utility driver upgrade worthy of this name?

Surely if I had to buy again today something for use it as HTPC, I would not think of a NUC but of an Android based equipment that costs a fifth, and in the end has the same imperfections of this blond, costly and capricious NUC

A greeting

A. Corallo

Hello,

So I've been running my Skullcanyon as a linux server for almost a year, so far so good. However I moved to another server, and decided to use the skulcanyon as a living room PC. As a server previously, it was used for encoding movies and transcoder, which put the cpu at 100% all the time, however as a living room PC, I installed Steam and started playing some games and the NUC kept crashing (freezing or power off)
It went for days to figure out the problem, including for the fact that I'm using Patriot 2666mhz ram which is incompatible, so I went ahead and bought a Crucial 2133mhz ram. The NUC kept crashing, I reinstalled the OS and updated the bios, and it still crashes randomly on GPU load especially benchmarks. As a last resort, I thought that heat could be an issue and went undervolting the CPU and GPU, CPU was at -80mv, it ran cooler and stable on stress test but the GPU crashed immediately, and then I thought doing the opposite for the gpu would work, I started with small increments of increasing the GPU slice and unslice voltage from stock, it kept crashing till i reached +0.09v offset, no crash but artifact so I increased it to +0.1v and it has yet to crash.

So the TL;DR, GPU has been perfectly stable on tiny over volt, do I have a lemon? Is it safe to keep it at this current setting? At the time of the post I'm still running Heaven benchmark in loop for almost a day (~22hours) and it hasn't crashed yet.

In a nutshell, the only issue I have with the NUC system is, the CPU fan would left turned on after ESXi shutdown while the NUC power button would be turned off. To turn the system back on with the power button, I would need to first pressing the power button for 5 seconds or so until the fan is turned off (the system is then forcefully powered off), only then I can turn the system back on again by pressing the power button normally. This annoys me as if I forgot to force the units to go down completely, I'd find the units are warm in the next morning and I don't have air conditioning running all the time. I had done a bit of research and did try a few things and unfortunately I had not found a solution to this, yet. I have two NUC units with the same parts and EXSi, both have the same experience.

Would appreciate your advise on what I should try.

And as much as I'd like to get some support regarding the above subject, I'd like share on this thread my experience of running ESXi 6.5 on the NUC units.

Hardware and firmware

Important hardware and firmware remarks

• For those planning to run ESXi 6.5 or similar, and for those planning to run Linux operating system on the NUC with Intel SSD 600P, I highly recommend that the SSD is updated with firmware version 121C (or better if available)
• There were issues reported running Linux on the Intel SSD 600P, at the time I'm writing this only Microsoft Windows versions listed on the 600P product page are 'officially' supported
• Having said, I had see reports on this forum and others that firmware version 121C works good for certain Linux flavors, and for me, ESXi - see also important notes on the NVMe driver for ESXi

BIOS configuration - configured according to article here by William Lam and article here by Erik Bussink - in summary, I have the following BIOS settings. I'm listing them for reference, not that I know what each of the settings meant

VMware ESXi

• Installed on the USB boot drive
• Updated to ESXi 6.5.0 Update 01 Build 5969303 here
• Two data store on each NUC, each data store fully occupy each 600P

Very important remarks

• Replace the stock NVMe driver that came with ESXi with the one built specifically for Intel SSD here
  • After the update, it showed intel-nvme instead of nvme as the driver for the storage adapter
  • You'll see on the driver page that the model 600P isn't listed, but the driver worked well for me so far
• I did the driver update after I had applied the ESXi 6.5.0 Update 01
• And prior to that, I had both of the 600P low-level formatted with HDAT2 (by verify/write/verify), the tool is listed here here

The catch was, without the intel-nvme adapter driver, I had painful experience working on the ESXi platform with the NUC system - obviously the system or its parts are not ESXi HCL listed

• Copying virtual machine folders from one ESXi data store to another ESXi data store that was created on another 600P on the same NUC would usually fail before 20% completion
  • ESXi would lose connectivity to the data store that it was writing after the error
  • I had to reboot to recover from the situation
• Or, similarly, copying virtual machine folders to/from the same data store would also result in similar experience
• Or, deploying virtual machines with thick disk mode (-diskmode eagerZeroedThick) with the VMware ovftool would also result in similar experience
  • Having said that, I didn't get any issue deploying virtual machines with thin disk mode

Post updating ESXi with the intel-nvme driver, I had tested the system to PASS the above test cases which failed 100% previously

Edits: there are 3 items attached to each NUC units

• The DC power plug
• The USB boot drive
• Cat5e network cable

No other items are connected other than the items above. Specifically I don't have any type of displays attached to the units.

Message was edited by: scene (added items attached to the NUC units)

After few weeks use and test of 4k60Hz video output over HDMI2.0 on my NUC7I5bnk, and after updating all the driver and BIOS using Intel Driver & Support Assistant, I still have problems with my open windows, all large size open windows will shrink to small windows and position will be moved to top left corner when NUC goes to standby mode.

I was quite surprise of the problems because it never happened in the past in the other computers that I have. I thought that Intel was a good and reliable brand, and I feel otherwise now.

Please some one advise how to solve this problems.

if i do this i get:

Manufacturer:                                  <-- nothing

Model:                                             <-- nothing

on a NUC7i3BNH i get:

Manufacturer: Intel Corporation

Model: NUC7i3BNH

so i can't install it with MDT, because i need the model to install the correct drivers

i have the actual bios. can someone please correct this?

I'm having an issue where the NUC6I7 puts the monitor to sleep, but if it sits like that long enough the monitor never comes back.

I have to shut the system off.  Unplug the power, and the monitor, and the power from the monitor, then turn it all back on.

Latest BIOS, Display Drivers, etc.

Good day!

Six months ago I bought NUC6i7KYK and noticed the incorrect work of the bluetooth. At any time (this can be 10 minutes, half an hour, hour or any other), the sound may disappear or start popping, and after a few minutes it appears again. It is absolutely impossible to watch a movie normally or listen to music. During these six months I periodically checked the new drivers and installed them, but the problem was not solved. I had to disable the bluetooth in the BIOS and buy a Chinese usb-module for $4, which works perfectly. But it's not right! I always have a busy USB 3.0 port and a high-speed built-in bluetooth should work correctly, especially since this is a software problem.

I have Win10 1703 x64 and Apple AirPods. I would like to help the company's engineers solve this problem. Maybe you have instructions for this? For example, a debugging program that will write a log to determine the cause of the problem. Thank you for your attention and help!

Hello,

I'm trying to create a custom BIOS for the NUC 5CPYH kits with the Integrator Toolkit 6.1.5, which according to the download page is the most recent version and should work with my model.

I followed section 2.3.2 ("Importing Features: Step-by-step example") from the included User Guide PDF to create a custom BIO file, based on the newest BIOS revision PY0062, with my custom Visual BIOS settings, custom SMBIOS configuration and a custom logo file, with the following command in the UEFI shell:

ITK6.efi –b –x myCustomBio.bio –ib PY0062.bio –is –ic –il myLogo.jpg

The first problem was that including the SMBIOS configuration does not seem to work: The above command fails with "There was an issue getting feature data for the BIO". When I execute the above command without the "-is" flag, the "myCustomBio.bio" file was successfully created.

Since the SMBIOS is only "nice-to-have" but not strictly necessary, I went on to install the resulting custom BIOS onto another unit (same kit, same internals). The BIOS update process ran through without a problem, the BIOS settings were set as customized, but on reboot the custom logo file didn't get loaded. Instead I now have a blank screen; the different boot options (F2, F7 etc) on the bottom right are still displayed, so I assume it's only some problem with the logo file.

Re-flashing with the "pure" PY0062.bio image does not get me the "Intel NUC" logo back. After reading this thread I'm reluctant to create yet another custom image with the "default" Intel logo file, as I don't want to brick my two test units just yet.

Is there a way to create a custom BIOS image for the NUC5CPYH kit which includes a custom logo and/or a custom SMBIOS configuration?

hello, on my new NUC the mouse is lagging, i tested several mouses usb, tested bluetooth

mouse, updatetd drivers so far it works, no positiv result.

Please help, my motherlanguage is german

Thanks a lot best regards

The recent models of Intel NUC seems to have taken a bad path of soldering the wireless features (BT, WIFI and whatelse) onto the motherboard making it hard to remove these features if you want a device with no wireless features at all.

Are there any plans from Intel to revert from this bad decision and making it again possible to make the wireless features optional rather than mandatory?

Hi,

I have problems with creating a custom bios file. I have a NUC5PYH and when using this cmd line: "itk6.efi -b -x MyCustomBios.bio -il MyLogo.jpg" then I get "There was an issue creating/opening the .bio: MyCustomBios.bio.

When Using "itk6.efi -b -x MyCustomBios.bio -ic -il MyLogo.jpg" I get "There was an issue getting the current BIOS custom settings"

I have the PY0064 Firmware.

Please help?

Thanks,

Bas den Boer

NC Automatisering

• Bewerken                                                                     
• Verwijderen                                

Hi

No issue with DTS_MA (96/24) and with other encoded HD format but sound in case of PCM from and above 88.2/24 is broken more and more as quality is higher and higher.

It is same problem with Direct Sound and WASAPI, with foobar2k and Jriver and Kodi.

I tried latest three Intel Audio Drivers but problem is same.

win64_154518.4664.exe

GFX_WIN10_64_15.46.5.4771_BN.zip

GFX_WIN10_64_win64_154702.4815.zip

DAC is Pioneer Receiver SC-LX 59 which is working fine from other sources via HDMI too.

OS: Win10pro 1703

Update: I have tried over all HDMI port on the receiver. Surprisingly only 4K HDCP2.2 port were effected. I would emphasize that other sources can drive these ports too without issue.

Bonjour! Mon mini-pc Intel-Nuc NUCPYH ne démarre pas et l'écran reste noir.

La solution pour qu'il démarre c'est qu'il faut  débrancher mon cable HDMI de la tv et de démarrer le mini-pc  apres  quelques seconde la lumiere arrire rouge Optical s'allume et je rebramche mon cable HDMI a la tv et tout est reparti.

Pourquoi et comment réparer ce probleme?