I'm trying to upgrade from BIOS 45 to BIOS 49, and have downloaded the new BIOS to a flash drive.  When I try to start the NUC (with the flash drive plugged into a USB port), and press the F7 key, the NUC freezes at the Intel logo screen, with the F2, F7 and F10 prompts in the lower right hand corner.  I have to power off the NUC, and when I power on, it will ultimately go to the Windows 10 HP login screen as normal.

Anyone able to shed some light on this?  I've successfully upgraded BIOS in this manner in the past.

The NUC8i7HVK running Windows 10 Home is unable to sustain an HDMI signal to the LG 38WK95C-W ultrawide monitor. HDMI works perfectly when I use an older 24" Dell display, but on the LG panel the result is what you see in the attached video.

What I've done:

• Updated all drivers and BIOS.
• Tested all the HDMI ports (on both the NUC8i7HVK and the 38WK95C-W).
• Obtained new HDMI cables - specifically, HDMI to HDMI and mini DisplayPort to HDMI.

None of the above help. The only way I'm able to get this to work is by using a USB-C to USB-C cable or a mini DisplayPort to DisplayPort cable. This is sub-optimal, because the whole point of this setup for me was to use the LG's PBP feature to have the Windows box output to half the screen via HDMI and for my MacBook to charge and output via USB-C. Unfortunately, the 38WK95C-W has only one USB-C input and the PBP feature doesn't work with DisplayPort.

Intel: can this be fixed?

I purchased a new NUC locally today.  Had problems getting it to start, so the first thing I did was install the latest firmware version (*051).  I am running the most recent version of Windows 10 Pro x64 - the USB drive was created today using the Microsoft Media Creation Tool.  I have installed 2x8GB G.Skill Ripjaw PC-2666 SODIMMs, 1x500GB Samsung 970 EVO (system drive) and 1x1TB Samsung 970 EVO (media drive).  I was able to successfully download and install every driver package from the drivers page except for RST.  Every time I try to install, regardless of which version, i get an error message that says "This Platform is not Supported".  I have attached the InstallRST installation log.  I am not running a RAID setup, but it am very much bothered by the fact that I am unable to install this software, as I was originally considering running raid.  Any help is appreciated.

I have encountered an issue with the BIOS of my NUC7i5DNHE.

In Visual BIOS setup, whenever the M.2 SSD checkbox under PCI is unchecked, then save & exit, the Intel Ethernet Connection I219-LM also gets disabled, so UEFI PXE IP4 and IP6 disappear from the UEFI boot list.

Attached are 3 pics showing:

1. BIOS main screen with M.2 SSD checkbox enabled: 3 items under UEFI (SSD, PXE IP4 & PXE IP6) are visible

2. BIOS screen where M.2 checkbox is located

3. BIOS main screen with M.2 SSD checkbox disabled: no boot items under UEFI are visible

The internal PCIe SSD should of course not show up after it is manually disabled, but the two UEFI PXE boot entries (IP4 & IP6) should remain but they are gone as well.  I disabled the M.2 SSD temporarily since I wanted to do UEFI PXE IP4 booting.

My setup is as follows:

* NUC7i5DNHE   SA# J57828-504, BIOS 0058

* 2 x 4GB Samsung DDR4 4GB 1Rx16 PC4-2400T-SC0-11 SODIMM (M471A5244CB0-CRC)

* Samsung 960 PRO 2TB PCIe NVMe M.2 SSD (MZ-V6P2T0)

* Acer T232HL display (connected via HDMI)

* Logitech k830 wireless keyboard (Logitech USB dongle plugged into any front or rear USB port)

I'd also like to add that after I physically removed the Samsung 960 PRO PCIe M.2 SSD from the NUC7i5DNHE, the UEFI PXE boot entries returned and functioned normally (only PXE IP4 tested), so these UEFI PXE boot entries disappear only when an M.2 SSD is installed but set to disabled via checkbox in the BIOS Setup.

This looks like a BIOS bug to me, and is reproduced 100% without booting any OS from the PCIe SSD.  I also tried loading BIOS defaults via F9 but it made no difference.

Hi,

Recently I bought NUC7i5BNK, but after connecting it to my old hdmi monitor (iiyama ProLite E2481HS-B1) I didn't get any output over hdmi, not even efi splash screen, the screen remains black, without backlight (it flashes "No signal" at the beggining of the boot process then turns off). At first I thought that's issue related to the RAM/SSD versions, but after I borrow newer monitor (LG 27UD68-W 4K) I saw that everything works fine. After confirming that NUC works fine, at least with newer monitor, I tried to disable HDMI CEC and power controls (in uefi), because I thought that maybe this older model is not supporting it and there's communication issue between NUC and monitor. Unfortunately this doesn't work, so my last resort was to try to pass exact monitor spec via kernel parameters "nomodeset i915.modeset=0 video=HDMI-A-1:1920x1080@60"  and hardcoding gfxpayload by grub (I'm using ArchLinux), but this doesn't work either, when I checked '/sys/class/drm/card0-HDMI-A-1/status"  the message was "disconnected" (same for */card0-DP-1, */card0-DP-2). I'm quite baffled, because it's first time I encountered situation. So my question is with which HDMI input versions this NUC is compatibile with? Only 2.0/2.0a?

Regards,

Lukas

intel_corp

The withdrawal of the Express BIOS updates for new versions means that there appears to be no way to remotely update system firmware on NUCs that don't support AMT (which is almost every model).

What solution does Intel have for those who need to update firmware remotely (i.e. without being physically present at the machine)?

This is a serious issue that has the potential to become an emergency if there's a sudden requirement to update firmware on Intel NUCs - for example if serious security flaws are discovered. I would appreciate a proper, thoughtful response from Intel on this issue.

• https://www.techradar.com/news/intel-might-launch-a-super-powered-8-core-core-i9-ghost-canyon-x-nuc-mini-pc
• https://wccftech.com/intel-ghost-canyon-frost-canyon-nucs-9th-gen-core-i9-8-cores/

NUC9i7FNH Frost Canyon?

Awesome possibilities ...

The "Frost" namesake for the 2019 NUC9i7xxx seems intentional, and an awesome return to those lower TPCs. The Radeon partnership on the NUC platform appears to be over starting in 2019. The 2020 NUC9i9's are rated at 45w, if the charts are to believed. I like the bump to max memory of 64GB.

All Speculation Until The Specifications Are Published

In May I purchased a NUC7i5BNH to use as a media server. Initially it was fine. I have a large high resolution music library that I play though an external DAC using Amanero USB Audio. I switch between that audio output device and the Intel Display Audio, which I use to play video through my home theater receiver.

Lately I've had a lot of issues with the Intel Display Audio device malfunctioning, disappearing from my computer, or simply failing to perform. Right this minute the Intel Display Audio is the only one that will play audio, however. The USB audio output is now the one malfunctioning. Are these two devices in conflict with one another? Can I only have one or the other on this device? I didn't have any of these issues with a friend-built PC from 2012. Only with the brand new NUC.

I have run the audio device troubleshooter more times than I can count. Sometimes it finds an issue, but usually it doesn't. Sometimes rebooting works. But today it isn't working. At the moment I have the Amanero USB device selected for playback, but sound is continuing to issue from my home theater receiver, not the two-channel system it is supposed to play through.

One possible lead today was this error code I received prior to a forced reboot: "Stop code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"

The computer said it would reboot after gathering the necessary information. That never happened, and I had to reboot manually with the power button.

I can't believe I'm having so many more problems with a new computer than I did with one from 2012. But I am. Not happy.

The display automatically gets dimmer or brighter according to the brightness of the content that is displayed. Neither the NUC or my monitor has a sensor of the ambient light. I have no idea why it has the need to change brightness. Especially, when the content is dark, it automatically get darker. It gets really annoying when playing game or watching films. And there seems to be no turning off this auto adjustment feature.

Would you please help me with that? Thank you.

As the title specifies, I ordered myself a pair of NUC7PJYH devices, with Kingston SA400S37/120G SSD drives and 1x Corsair CMSO4GX4M1A2133C15 (4GB 1.2V 2133Mhz DDR4 CL15) stick of RAM each.

I've been unable to get either of the systems to boot with the specified memory modules, but both the RAM sticks work fine in other systems that I've tested them in.

I was able to boot a NUC using a RAM stick from a laptop, and ran a BIOS upgrade with that, to no change.

I've also attempted seating the memory sticks in both of the slots, both solo as well as with both sticks in one system. All to no avail.

Is there anything else I can attempt, or am I completely out of luck here?

Following RFC 5970 - DHCPv6 Options for Network Boot with reference to DHCPv6 option 59 (boot-file URL), we can successfully boot a unit over IPv6 when specifying a TFTP URL. (i.e "tftp://[2001:fb::1]/netboot.efi")

However, when specifing a HTTP URL (i.e "http://[2001:fb::1]/netboot.efi") the NUC simply disregards the opion presented, without any feedback, whilst going into a "Start PXE over IPv6" loop.

The units were updated with the latest firmware [JYGLKCPX.86A] (0046) dated 11/03/2018 as obtainable from Download BIOS Update [JYGLKCPX.86A] as to ensure the issue had not been addressed as yet.

Alternatively, is there some oversight on our behalf ?

Hi all,

I have encountered an issue with the WOL setup between my NUC8I5BEK (32GB RAM, WD Black 1TB M.2 NVMe SSD) and ESXi 6.7 Update 1. 

FYI, I had successfully installed ESXi 6.7U1 on my NUC8I5BEK and everything works fine except

   - The Wake-Over-LAN (WOL) only works every time right after a complete power down of the NUC (i.e. after switch off and switch on the NUC's power adaptor).

   - After wake up (via WOL), my NUC can start the ESXi 6.7u1 successfully, however, after a proper system shutdown via ESXi, the NUC can no-longer be Woke-up via WOL.

   - although the NIC's LED light was GREEN, the NUC will no longer response to the WOL magic packet until a complete power down of the NUC.

   - It seems ESXi 6.7U1 didn't put the NUC's network interface back into a proper state for WOL after the system shutdown.....

I trust I had properly configured the NUC's WOL related BIOS settings as I can wake up my NUC every time right after a complete power down.

Any idea/suggestion on how to fix it?

Thanks and regards

Leo Luk

I have HDMI plugged in the back of the NUC to Samsung (4K) monitor (HDMI) and by default, it auto detects if the signal is from HDMI 1 or 2. The same HDMI cable works with a mac-mini.

The NUC8i7HVK is brand new. Installed components and first tried to install Linux Mint. Yeah, I know Intel doesn't officially support it on this NUC. Anyway, sometimes on restart there's nothing for the monitor to display. So I abandoned Linux thinking the OS is the problem.

Switched to install Windows 10 Pro. I didn't get a chance yet to install any specific intel drivers because after Windows restarted it doesn't display on my monitor most of the time. When it does show, it displays in a squashed format taking up a quarter of the top part of the screen, and the desktop is duplicated 2 to 3 times. I've attached a screenshot and that's the biggest it's ever displayed it lately and that's with the front HDMI connector. The back HDMI connector mostly doesn't display anything.

Most of the time the HDMI (front/back) does not display anything and sometimes I can get into BIOS with F2 and it displays that fine. So, I cannot get into Windows to install the drivers when I cannot see anything and other times it's completely ineligible (with the duplicated desktops). I set the date and time in BIOS, but I swore that one other time when I was in there it didn't keep the time set correctly. The NUC box says it was manufactured in May of this year.

Is there something wrong with the hardware of this NUC?

Should I flash BIOS again or go back to an earlier version?

HELP!

Things I've done:

Updated to latest BIOS (51) as the first thing I did.

Tried in BIOS having performance > Graphics between Auto and Enabled.

Ran RAM test (from USB) and it passed fine.

Tried another HDMI cable. I don't know if either cable is 2.0 certified. But the cable worked to install OS's.

Tried front HDMI connector.

Unplugged CMOS battery connector for 15 minutes and reconnected.

Powered on and off numerous times, most of the time no signal for the monitor to detect.

Nuc has:

BIOS 51 (10/24/2018) with F9 defaults set (Graphics enabled)

16GB Corsair (8GB x 2) - CMSX8GX4M1A2400C16

1 TB Samsung Evo 970 NVMe PCIe M.2 2280 (slot 1)

250GB WD Blue SSD m.2 2280 (slot 2)

Samsung Monitor model: U28E590D

USB Keyboard and mouse

Hi. Seems like I have the same problem as in "locked" thread
DN2820FYKH  slow boot with SSD.

In my case this is MBR, GRUB2 boot loader with dualboot Linux Mint 18.3 and Windows 10.
But found several other "dead" threads (e.g. NUC5PPYH Slow Boot Time ) with Windows 8.1 and other OS's.

So. On my desktop PC this exact SSD booting this exact GRUB/Linux takes like 3 seconds till GRUB and 7-10 seconds most for kernel. For GRUB/Windows combo it takes 3 + 12-15 seconds.
On my brand new NUC6CAYH with 2x4 PC3-14900 (Ah and to kill all the excuses from start - even the SSD is Intel ) it is !40! Seconds till GRUB and some crazy !30! second between the GRUB and start of kernel/Windows boot.
OK. You may blame spooky Linux and "that Linux bootloader" for Windows for second delay after GRUB. But there should be no excuse for first delay.
As I told it is MBR and I see no reason to move to GPT for UEFI. In setting I tried lots of stuff - leaving both UEFI and Legacy boot mods, disabling/enabling FastBoot, disabling network boot etc.
The BIOS was BIOS Version 0053 - AYAPLCEL.86A.0053.2018.0727.1436, I updated it with BIOS Version 0057 - AYAPLCEL.86A.0057.2018.1105.1536 - all the same.

My guess was that it tries to connect to WiFi (it has no SSID credentials anyway) and resolve something (Ethernet is disconnected), it might be the stupid guess.

Ah. And I have second nasty problem. The keyboard is not working in GRUB menu. So to select Windows I have to change default choice and reboot all the time.
As with this guy in also "dead" thread Keyboard and Mouse not working on Intel NUC Kit NUC5PGYH

Also no change with BIOS update/ GRUB_CMDLINE_LINUX="iommu=soft"/ playing with "Legacy USB" setting.
In BIOS and in OS's the keyboard works fine. As well as the same keyboard in same SSD GRUB on PC.
Again my guess - all the "easy to use" ports are USB 3. Maybe GRUB can not in USB 3 backward compatibility (will check on desktop PC today). And I have no internal USB (that is told to be USB 2) to normal USB A adapter to test the idea on NUC.

If no response to this second problem - will start the new thread.

All this seems like 2 bugs (at least the first problem) and poor testing in "Legacy" MBR mode. As you see - I am way not alone with this issue. If need any more information or test something - you are welcome. Will appreciate any help. Thanks in advance.

Hi

I just updated my NUC8i5BEH from 0051 to 0056 (updated from 0048 to 0051 just some days ago).
I did the update manually using the .bio-File from Intel.

After the update, only white noise was displayed on my screen (it looked like the TV pictures after the end of broadcasting a few decades ago). Unfortunately I didn't take a picture, but it looked pretty much like this one ... (Link).

This picture occurred both when connected via HDMI and when connected via DP.

I then set the BIOS to its default values (via the Power Button menu).
After that the picture was ok. Next I adjusted my settings bit by bit back to the way I had them before the update.

As soon as I set the IGP Aperture Size to 2048 MB in the BIOS, the image is disturbed again. Up to 1024 MB everything is fine.

I'm now thinking about reinstalling the old BIOS 0051. Is this recommendable?
Is it possible to just flash the 0051.bio from a higher version?

EDIT: Maybe I should add that the picture is disrupted right after turning on the NUC, so I guess its nothing with the Screen Resulution.

Nachricht geändert durch Trial Member: Added more details.

Good day

Just set up a NUC 7i3 and installed Windows 10pro  I cannit get the internal mic array to work, I have updated all the drivers using the Intel driver detection and still cannot get the mics to respond. I am trying to use it with cortana as its advertised that this system should work with it yet I still have not figured it out. Any assistance would be appreciated

Dan in Oregon

Hi,

I got myself this hardware (NUC7I3DNK TC2) and would like to use 2 displays with displayport input.

I use HDMI to diplayport cable.

I tried it with 3 different display already. all of them stay dark.

Could someone tell me what i might be missing?

thnx

I have a new Intel NUC7i7DNKE and Samsung 970 EVO 250GB NVMe SSD. The advertised speed of this is 3,500 MB/s for read, and the most I can get is half of that, i.e., 1.8GB/s. Supposedly, BIOS version 52 was made to resolve this issue.

The NUC came with BIOS V44. I read the release notes for V56, and downloaded DNi70056.bio and applied it via the F7 bios update method. Nowhere did I see a note that said apply one BIOS update at a time to get from V44 to V56 either in the release notes or the read me. The update went fine, reset BIOS settings, set machine up, and, was disappointed to see 1.8GB/s speed. I started reading on this site, and found several with the same issue, a few threads were here:

Performance problem with Samsung 970 Pro on NUC7i7DNKE

NUC7i7DNK not achieving proper NVME speeds

But there were others as well. The solution was BIOS V52 apparently, which was long before I even had said machine. Later BIOS versions said nothing about needing to use the jumper recovery method. The notes for V52 say:

Fixed the issue where M.2 PCIe SSDs would run at Generation 2 speeds. and

To fix the M.2 issue, the BIOS must be installed using the jumper recovery method.

But no later BIOS have those notes. So, I thought I would simply go back to V52 with a jumper recovery method, but, it appears this is not possible as V53 says:

Due to the Intel® ME firmware update in BIOS version 0053, you can’t downgrade to version 0052 or earlier.

In case the jumper method still worked, I decided to use the jumper method for V53, it worked, and then I updated back to the more recent V57. Speed was still 1.8GB/s.

I inquired in the other thread about this but was told to make a new case so here it is. I was certainly unaware that only V52 could be used as it was not stated anywhere, nor was I aware of this defect.

Surely there is some sort of method to still update the NUC to get the M.2 SSD fix? Otherwise, all NUCs sold that have an older BIOS and people not realizing this will be permanently defective.

So, what I am wanting is a path to get my NUC7i7DNKE fixed as far as the M.2 SSD speed issue goes.

I would like to run TensorFlow and Caffe, also this library OpenPose GitHub - CMU-Perceptual-Computing-Lab/openpose: OpenPose: Real-time multi-person keypoint detection library for body, fa…

I have a Nuc:

• Intel Core i7-7567U
• Intel Iris Plus Graphics 650. 2.5" SSD/HDD bay
• M.2 22x42/80 (key M) slot for SATA3 or Pie X4 Gen3 NV Me or AHCI SSD
• Dual channel DDR4-2133 SODIMMs, 32GB maximum
• 500GB Samsung SSD
• 16 GB DDR4 etc.

How can I add a GPU with CUDA to execute DNN?

Thanks for the support

Hi,

Recently I bought NUC7i5BNK, but after connecting it to my old hdmi monitor (iiyama ProLite E2481HS-B1) I didn't get any output over hdmi, not even efi splash screen, the screen remains black, without backlight (it flashes "No signal" at the beggining of the boot process then turns off). At first I thought that's issue related to the RAM/SSD versions, but after I borrow newer monitor (LG 27UD68-W 4K) I saw that everything works fine. After confirming that NUC works fine, at least with newer monitor, I tried to disable HDMI CEC and power controls (in uefi), because I thought that maybe this older model is not supporting it and there's communication issue between NUC and monitor. Unfortunately this doesn't work, so my last resort was to try to pass exact monitor spec via kernel parameters "nomodeset i915.modeset=0 video=HDMI-A-1:1920x1080@60"  and hardcoding gfxpayload by grub (I'm using ArchLinux), but this doesn't work either, when I checked '/sys/class/drm/card0-HDMI-A-1/status"  the message was "disconnected" (same for */card0-DP-1, */card0-DP-2). I'm quite baffled, because it's first time I encountered situation. So my question is with which HDMI input versions this NUC is compatibile with? Only 2.0/2.0a?

Regards,

Lukas