I have an intel NUC 5i7RYH, my BIOS is RYBDWi35.86A.0355.2016.0224.1501.
That system ran flawlessly under 15.10. I recently upgraded to 16.04 LTS on April 23rd. The unit was bricked the next morning, and the NUC has now bricked four times in total, twice the last four days. My power setting is "Don't Suspend" -- it's set there to avoid inviting the situation where the unit becomes unresponsive and will not wake up (not just to mouse and keyboard inputs, it won't even respond to the power button). When bricked, the unit has to be disassembled, the CMOS battery disengaged, then put together again. Such a fun way to start the morning. Every occurrence happens the same way. I stop my work and leave the system running overnight. When I return to my desk in the morning I hit the keyboard and mouse and there is no reaction. Than I hit the power button -- now cringing because I know there is about a chance that there will be no response when I do so.
I am using a wireless Logitech mouse and Keyboard. My Advanced Power BIOS settings are as advised by Intel:
Wake from S3 via CIR Wake from S4 and S5 via CIR USB S4/S5 power
I wonder if I need to resort to a crappy USB mouse/keyboard setup rather than wireless.
Windows users do not seem to be plagued with this issue. Or at least they can recover from it using the "Wake on LAN" feature to start an unresponsive unit from a mobile app. That doesn't work for me. The 16.04 settings for Ubuntu allow me to set that feature for the wired ethernet connection but the wifi connection -- which is what I am using -- does not expose that option. Setting the wired option and using the wifi does not work.
The unit will accept a remote control, and that also works for Windows users. I can steal a remote from my TV if required, but when I searched for the "directions" to add a remote to a NUC running Ubuntu too many of the posts starting out saying, "After two days of trying everything . . ."
These NUCs are great little machines when they run, but it absolutely sucks that Intel hasn't been able to fix this long-standing problem. They have advised me to post the issue over here.