Intel Next Unit of Computing Kit NUC6i3SYK is for sale, "http://www.macmall.com/p/Intel-Desktop-Computers/product~dpno~13739010~pdp.jihcjib". Where can one find compatible memory and SSD?

I have used my NUC5i5RYK with Intel ready mode enabled as my home server. Sometimes I need the NUC to perform some computationally intensive tasks, so I tried to force the NUC exit ready mode remotely by sending Wake On Lan (WOL) magic packet via LAN. What I have found is that the NUC ignores WOL packet and keeps in ready mode. Is this the expected behavior or a bug?

To be clear, I can confirm that my system can wake up by WOL from S3 state when I disable ready mode in Intel Ready Mode Modern UI application. And when I enable the ready mode, the system could wake up by keyboard and mouse input without problem.

Any help would be appreciated.

NUC5i5RYK

Windows 8.1 Pro

All drivers updated to the latest version (16 Dec 2015)

Bios: 0352

LAN: 20.4.1

Chipset: 10.1.1.9

Intel Ready Mode: 1.1.70.506

I just recieved my new NUC5I7RYH and added 2 X G.Skill Ripjaws - DDR3L 1600Mhz CL9 SO-DIMM Module - 8GB  and aSamsung SM951 - M.2 - 256GB

Now when I try to install windows 7 on the ssd I get the following message:

Windows cannot be installed to Disk 0 Partition 1 (show details)

Those details are:

Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu.

In the bios version 350 it detects the harddrive and it seems fine.

Does anybody have a clue how I can fix the issue?

I tried installing Windows from USB drive and a network drive both are giving the same problem.

Tried some different bios settings, but none seem to fix the problem?

When I inserted a normal sata harddrive I was able to install windows to that partion.

So it really seems a M.2 PCIe problem.

I have read that there are problems with the 350 version of the bios which I am on, but this is the version it was shipped with and also the most recent one.

Should I try and downgrade my bios version? Or is there a problem with my SSD? Or is there a problem with my NUC?

Is it a hardware problem of a software (BIOS) problem?

Any ideas on how I can enable the SSD for windows installation are welcome.

I'm unable to boot UEFI devices of any kind. If I press F10 it will list my UEFI W10 install stick, but once I select it the screen flashes and takes me back to the select boot device. I'm trying to install Windows 10 on a M2 which requires me to install under UEFI boot mode. The same USB W10 install stick boots UEFI on other computers, but not this NUC. I've tried flashing bios 0247 through 0352 with the same results. After bios 0249 I can no longer boot legacy devices either, but I'm unable to boot UEFI devices under any bios version.

I'm open for any help.

Thanks

NUC5i5RYH support Intel® Smart Response Technology?

My Intel NUC no longer displays video when booting kernel 3.10.0-327.3.1.el7.x86_64.  It boots fine when using 3.10.0-229.20.1.el7.x86_64.  In fact, when I boot using the CentOS 7.1.1511 CD, I don't get any video output.  Anyone else experiencing this?  I have already updated the firmware on my NUC and that has not resolved the issue.

Regards,

Ultrajones

Hi,

I would like to control the Netflix app under Windows 10, after much research I do not see how.

Intel NUC D54250WYK + App Netflix  Win 10 + Harmony 900        It doesn't work

I contacted technical support logitecht and tell me that they have in their database the command for Intel NUC D54250WYK

Intel is the need to provide for inclusion,  you can see it here Harmony 900 + Intel Nuc D54250WYK + App Netflix Wi... - Logitech Forums

You can fix this? or someone can help me set the remote control to control the Netflix app

Regards

There have been many posts about NUCs failing to wake up and/or getting completely bricked after the Linux kernel puts the device to sleep. It would seem there is an incompatibility between how the Linux kernel puts the NUC to sleep, and the NUC's hardware or BIOS. I don't have a clue whose fault this is, but it SEEMS LIKE* a successful workaround is to force the Linux kernel to use synchronous power management, meaning the NUC's hardware devices will be shut down one by one, rather than all at once in parallel (which is the default).

* I have not reproduced the problem after implementing this solution, but that doesn't mean it's solved -- it could just be a rare issue, or I might just have been lucky since following these steps. Please reply with your experiences so we know if this info is correct.

If your NUC is bricked and will not power on, you can probably recover it by disconnecting the CMOS battery for a short time. Briefly: Disconnect power. Flip over. Remove four foot screws. Ground yourself. Expose sensitive underbelly. Remove M.2 drive if needed (it may block access to one of the motherboard screws). Remove two black screws holding motherboard down. Gently lift motherboard out, being careful not to scratch its components or circuit traces against anything hard or metal. Unplug CMOS battery for a minute, then plug back in. Reverse steps. NUC should now turn on when power button is pressed.

TO PREVENT THIS PROBLEM FROM HAPPENING IN THE FUTURE:

sudo bash

cat << EOF > /etc/systemd/system/disable-async-power-management.service

[Unit]

Description=Disable asynchronous power management

DefaultDependencies=no

OnFailure=emergency.target

[Service]

Type=oneshot

ExecStart=/bin/sh -c "echo 0 > /sys/power/pm_async"

RemainAfterExit=yes

[Install]

RequiredBy=sysinit.target

EOF

systemctl start disable-async-power-management.service

# The next command should print 0 and not 1

cat /sys/power/pm_async

systemctl enable disable-async-power-management.service

Joined the community  in hope someone can help me.

I bought a NUC5i5RYH and have installed Openelec and Windows 10, which automatically starts within 2 seconds of a shutdown from both Openelec (Kodi) or Windows 10, this is running with Hyper X 8gb DDR3L 1600 SODIMM memory and 320gb 2.5" Toshiba HDD. I have updated the bios to the current 0350 bios from the Intel website and have also switched off WOL or any wake setting in the bios to no avail. I don't see any settings for Deep S4/S5, the settings i have are Wake on LAN from S4/S5, Wake from S5, Wake S3 via CIR, Wake from S4 or S5 via CIR.

Obviously this is a problem many share and is there a solution out there, as i can't find one that works for me. is Intel doing anything about this?

Dear Intelistas,

I have an Intel NUC5i5RYH (rebadged as a System76 Meerkat), which was delivered on 14 Oct 2015, with Intel BIOS v.0249 in firmware, and it booted from its M.2 SSD [1] into pre-installed Ubuntu 15.04 in around 15 seconds.

My NUC has now been bricked by the well-known 'Ubuntu Suspend > Dead NUC' problem [2] fivesix* times (in 54 58 days of usage), about which many threads exist here at communities.intel.com (dating back at least a year) – and here is a list of what steps I've taken from those threads as potential fixes and implemented on my NUC, but all to no avail:

• upgrading the BIOS firmware: neither Intel BIOS v.0350 nor v.0352 (nor System76 BIOS v.0350) eliminate the 'Ubuntu Suspend > Dead NUC' problem – and upgrading has slowed down its boot time from ~15 seconds to ~2 minutes <sigh>
• mikec_intel's BIOS settings fix [3] does not eliminate the 'Ubuntu Suspend > Dead NUC' problem
• prigaux's 'echo 0 > /sys/power/pm_async' fix [4] does not eliminate the 'Ubuntu Suspend > Dead NUC' problem

For now, the only effective way to avoid getting my NUC bricked for a sixthseventh time would seem to be the major inconvenience of avoiding using the Ubuntu Suspend function altogether; and I'd be very grateful if anybody could recommend a way to get my NUC back to booting up in ~15 seconds, as it did when new (and as might be expected from a motherboard-bound SSD boot drive).

Has Intel really failed completely to address this 'Ubuntu Suspend > Dead NUC' problem?

Or is there yet another potential fix to the 'Ubuntu Suspend > Dead NUC' problem I should try?

Thanks in advance for your attention and help.

Yours in frustration and disappointment,

Tim Jones

__________________________________________________________________

* UPDATES are in red: My NUC has now been bricked by the well-known 'Ubuntu Suspend > Dead NUC' problem SIX times (in 58 days of usage).

[1] Its M.2 SSD: "M.2 SATA: Samsung SSD 850 EVO M.2 250GB : PART 0 : Boot Drive"

[2] The well-known 'Ubuntu Suspend > Dead NUC' problem:

• Mean time between failures: 9.7 days (6 failures in 58 days use, in my personal experience)  10.8 days (5 failures in 54 days of use, in my personal experience)
• Symptoms #1: each use of the Ubuntu Suspend function carries a small but real risk of bricking the NUC. When Ubuntu Suspend is used and works normally, the NUC goes into sleep mode, and the Power button LED winks amber. When the 'Ubuntu Suspend > Dead NUC' problem occurs, these are the symptoms which afflict sleep mode:
  • a short press on the Power button does not wake the NUC (as it ought to, and usually does) – the amber winking just continues; and
  • a long press on the Power button does not switch the NUC off (as it ought to, and usually does) – the amber winking just continues.
• Symptoms #2: the only way to get the NUC to power off is by disconnecting the power cable. After the power cable is reconnected:
  • a short press on the Power button does not switch the NUC on (as it ought to, and usually does) – the NUC is bricked; and
  • a long press on the Power button does not start the NUC up in Power Button Menu mode (as it ought to, and usually does) – the NUC is bricked.
• Workaround: to get my NUC to work again, I have to fully disassemble the NUC, disconnect and reconnect the CMOS battery from the motherboard, and reassemble the NUC.
• Users of Linux distributions other than Ubuntu (eg: Arch Linux, Fedora) have also reported experiencing this NUC bricking on using Suspend, so it could be described more inclusively as the 'Linux Suspend > Dead NUC' problem.

[3] mikec_intel's BIOS settings fix – as detailed in:

● 'NUC5i7RYH did not wake from sleep mode', 11-Sep-2015 to 15-Nov-2015

» https://communities.intel.com/message/331090#331090

...and involves making changes in Intel Visual BIOS settings.

[4] prigaux's 'echo 0 > /sys/power/pm_async' fix – as detailed at post #10 in:

● 'NUC dead after suspend mode in Ubuntu 14.10', 23-Dec-2014 to 28-May-2015

» https://communities.intel.com/message/309188#309188

...and involves using rc.local to write '0' into /sys/power/pm_async at each boot up.

PS: I've sought help from System76 tech support, but sad to say they're about as useful as a chocolate teapot –  so I'm hoping the Intel NUC community might be of some actual help in addressing these problems.

Hello,

I recently buy a NUC5i3RYH and today I installed Windows 10 Pro N on it. But when I transfer a big file or when the SSD is heavily used, the NUC freeze, the HD LED remains on, and the SSD usage on task manager remains 100%. I can't do anything, even Ctrl+Alt+Del doesn't respond, I need to force shutdown with the button.

My system is completely updated, BIOS and all Intel NUC drivers including the chipset driver.

Have we got an idea where it came from ? Do I need to secure erase my SSD and reinstall it ?

Thank you

Config:

-NUC5I3RYH

-SanDisk Z400s M.2 2280 M.2 6Gb/s MLC

-Kingston 8Gb ValueRAM DDR3L-1600 SO-DIMM

I have bought NUC5PGYH yesterday and today I want to install 2.5" HDD but inside NUC I have not any connectors for 2.5" drive. Why?

any reason why a Samsung EVO 850 SSD (SATA) wont work in my new NUC5i5ryh?  doesnt appear in BIOS.  SSD works fine in my other PC.  tried another regular SATA 2.5inch drive, and the NUC bios sees that fine.

i realize now that the drive is not listed in the tested compatible list, but why wouldnt it work?  i dont know enough about the technology of SSDs, so what am i missing?

Hi,

I have NUC5i5RYH and two SSD one is Kingston SV300S37A 120G and Intel 530 SSDSC2BW240A401 is another one. NUC doesnt detect any of these SSDs!!!! Why?!!! What I need to do?

Regards,

Mike

I have the BOXD54250WYK1 NUC running Windows 10 (previously Win8) and it's been great.  For years now I have streamed h.264 and 1080 video across my cat 6e network from my NAS with no issues at all.  However, I've noticed that it is a little sluggish with h.265, and downright unwatchable with 4k video.  The 4k video plays, but is in slow motion and displaying visual flaws all over the place.

Is there a NUC built for 4k?  I love my NUC.  Would love to stay with the line of products, but 4k is becoming more mainstream and I need my device to be able to play it.  Any talk about the NUCs and 4k is welcome by me.

Thanks for your time.

NUC5i3RYH  + windows 8.1 fully updated

cannot install various drivers from Intel Driver Update Utility

bluetooth 17.1.1532.1813

Raid 14.5.0.1081

Nuvoton 2.9.1007

Intel Chipset 10.1.1.9

Wireless adapter 18.21.0

It always comes up 'failed' no matter what.  This proper or a problem?!  The update utility says I need those drivers and driver versions so I expect that to be installed.

thx for the help

I am trying to install W7 Pro x 64 to run a program that will not run on W8 or W10.  I installed W7 from the disk, but the included USB 2.0 drivers would not work on the USB 3.0 ports on this NUC.  I created a bootable flash drive per instructions and downloaded and installed the Intel Windows 7 USB Creator Utility.  It appeared to install properly and even mentioned that it was installing the USB 3.0 drivers..  When I installed W7 again from the flash drive, apparently the USB 3.0 drivers that Utility said it had installed, never got installed with W7 and the keyboard and mouse plugged into the USB 3.0 ports were not recognized.  Any suggestions would be appreciated.

I need a Windows XP system to act as a Print Server to a really old Colour Laser printer, where drivers are no longer available.

My plan is to use an Intel NUC DCCP847DYE running Windows XP Home.

I have created a Floppy Disc with the Storage drivers, but I do not know which of the many drivers offered at the F6 prompt to choose.

How do I determine the correct driver to select?

Those that I have selected as my best guess have all failed with the BSOD Stop 7B. F78D2524 C00000034... I.E. The typical Boot Device inaccessible.

Just in case it is useful, I have a Plextor 64GB mSATA SSD.

UP until now this system has been running Ubuntu, so I believe the Hardware is sound.

Finally, the NUC is running a very old BIOS, Version 0028, and the latest is Version 0058. Should I update?

Thanks in anticipation.

Paul

Hi There,

Currently myself working on Intel NUC5i5MYBE board with Windows 10 Enterprise Edition.

My focus is on Low Speed Custom Solutions Header of NUC5i5MYBE.

In this Low Speed Header we have GPIO, I2C and SMBus related pins.

My target is to use attached any I2C sensor which is slave at Pin #13 and #14 for taking I2C0 as I2C port. I have done related changes in the Intel Visual BIOS to make that pins as I2C0.

javascript:;

Now in Device manager I have I2C0 port entry.

And system is serving I2C0 port as iaLPSSi_I2C_Device driver which is install by Windows 10 itself.

Here is the output of devcon.exe utility with driverfiles option.

-----------------------------------------------------------------------------------------------------------------------------------------

ACPI\INT3432\3&11583659&0

    Name: Intel(R) Serial IO I2C Host Controller - 9CE1

    Driver installed from C:\Windows\INF\ialpssi_i2c.inf [iaLPSSi_I2C_Device]. 1 file(s) used by driver:

        C:\Windows\system32\DRIVERS\iaLPSSi_I2C.sys

------------------------------------------------------------------------------------------------------------------------------------------

In My custom Linux I have no any problem while accessing GPIO or I2C in the same board because I have beautiful /dev and /sys fs infrastructure.

But Problem with Windows environment,

I know the flow how to access any device using device interface GUID in Windows using SetupDixxx APIs for gettting device path and CreateFile function to open the device.

But I don't have interface GUID or I didn't find yet till now in my system.

Previously In one of my NUC board I have combination of Atom processor with Windows 7. And what the cool things is I have got the GUID related information from Intel header files itself.

This link : https://downloadmirror.intel.com/24548/eng/Intel%20Embedded%20Drivers%20for%20Microsoft%20Windows7%20(32%20and%2064-bit)…

And Download Intel Embedded Drivers for Windows* 7 (32-bit & 64-bit)

But For Windows 10,

1) Driver installed OS itself.

2) Intel not provide any documents or header files for accessing such low level buses using standard Win32 APIs.

3) Only things I found over internet is ms-iot github site, have Windows.Devices namespace concept which I personally don't like because I don't move to C#.

Can anybody help me out here?

Thanks In advance.

Greetings, I am running (or rather WAS running) Fedora 23 on my Intel Nuc i7 kit with latest BIOS updates.

Following a failure to wake from suspend, my Intel is now a brick... the system will not boot and is completely unresponsive. No LEDs. No beeps. No fans. No video output. No sign of life whatsoever. HELP!!!

ps I was disappointed to notice NUC i7 uses the Sunon MagLev GB0555PDV1-A fan. This is the same cooling solution Intel uses in the Celeron NUCs that generate 1/8th the heat! My i7 NUC (before it died) was running 90+ degrees C under heavy processor load with the noisy fan on full blast. Is it possible to install an upgraded or aftermarket fan that will keep my NUC at a reasonable temperature? I am concerned that the high internal temperatures will damage my hard drive leading to possible data loss.