Gen4 NUC D34010WYK - after (meltdown/spectre - 046) BIOS Update NUC starts itself every 24h

[FS_]

Hi, I did a BIOS upgrade from 027 to 046 a few das ago and since that time the NUC starts by itself (with or without LAN) cable attached every 24 h - consistently. This 24 h startup is around the time the FW update was done - 11:45 UTC

Tried BIOS defaults and finally I did a hard BIOS recovery to 027 (Jumper and USB stick) but the problem persists. Now the 24h start cycle is in sync with the firmware recovery time from yesterday. Now it start itself at 12:45 UTC.

I should mention that I checked the relevant Power and Boot setting with regard to WOL and this S5 timer Option. No changes I did between up and downgrades.

I did not find similar issues yet but something that might related to it:

Though no help for me as my NUC never had a WIndows on it. It is or was home for OpenElec and now LIbreElec.

Any help or recommendation is appreciated.Thx!

[idata]

Hello, lazyman.

Thank you very much for sharing your issue with the Intel® Communities Team.I understand your NUC is now restarting every 24H after a BIOS installation. Allow me to help you regarding this issue you are facing.I would like to know if the page where you downloaded the BIOS version was the https://downloadcenter.intel.com/ Intel® Download Center and which method you used to complete the installation.By the way, I will highly recommend you to verify with your Operating System Support Team if they have any update on the Spectre and Meltdown issue as well.Antony S.

[FS_]

Thx for taking care, Antony.

Yes, BIOS downloaded from here:

https://downloadcenter.intel.com/download/26632/NUCs-BIOS-Update-WYLPT10H-86A-?v=t Download BIOS Update [WYLPT10H.86A]

Attached the corresponding readme for 046.bio

Interesting: 046 from December 2017 is gone and now 045 ist latest. Anyway I flashed 046 via F2/F7 method to upgrade from 027 to 046. After that the 24h start issue begun. I tried CMOS/settungs wipe via bios options, disconnected the LAN cable but every 24h the system starts itself at the same time. After four days and various tests (disabling evverything WOL or power related) i downgraded to 026 (by accident) via F4 recovery and after that upgraded to 027 via the HW yellow jumper procedure. Though the 24h start up issue is still present.

btw, during the 026 to 027 upgrade I got an error message 'fwUpdateFullBuffer' . (see attachment). After that I upgraded by yellow jumper method.

Curently I'm more interested in getting back a system that does not start by itself every day. The OS mitigations will happen soon.

[idata]

Hello, lazyman.

Thank you very much for your reply.In this case, at this level of support, I am not able to provide a solution. I will escalate this case to a different level. Please be aware that it might take some time to have a solution.Thank you very much in advance for your patience.Antony S.

[FS_]

Ok, thx.

Meanwhile I did some changes to my config that solved the 24h restart issue - at least this is what it looks like.

These changes were not meant to be get into the root cause so maybe one or all of them helped. This is what I did (still with 027)

1. I disconnected the PSU for ~ 3h

2. Is set and unset the timer function the BIOS offers. I activated the function and let it start the NUC for exactly one time. After that I disabled it again.

3. I checked with ethtool the NIC settings. eth0 WOL flag was set to 'g'. This did not change after a reboot. So I added a 'ethtool -s eth0 wol d' into a startup shellscript - made me feel better :\

So whatever I did It solved the issue for the time being. I'm now 48h without a spontaneous NUC boot. And the IR-RC is still working :-)

Don't know if you will still look into it. If not I might flag this as 'magically' solved.

[idata]

Hello, lazyman.

Thank you very much for sharing that information with our Community, I really appreciate it.Please let me know if the issue persists after the steps you performed.Antony S.

[FS_]

Hi again, one year later I am faced with the same situation as before. I had to upgrade to an new BIOS to change the CIR settings (as my new Sony LCD remote did interfere with the NUCs CIR reveiver - powering it on when pressing 5 on the remote *sic* - and 027 did not offer the option to switch from "generic" to "rc5 remote"). So I installed 049. Yes, not the latest one but the one I could downgrade just in case (see above).

Now with 049 installed, BIOS settings wiped/reset, and yellow jumper recovery procedure executed the NUC (still) starts every day at the same time. For the time being it is 2:10 pm (MEZ) - that's the last trail and error test I did with the S5 timer settings to on/off. Currently it's off and all timer values seem to be filled with defaults as I reset toBIOS default (like 00:00:01 as wake up time) - but the NUC does not care. It's still wakeing up every day at 2:10 pm.

Does anyone have a clue or an idea how I could get this fixed? The fix I used above (downgrading to 027) might help - I did not try, yet - with the daily wakeup but than the Sony remote will interfere again ...

Any ideas are appreciated. Is there some hard CMOS (?) reset method I could use? I am somewhat good with a soldering iron :-)

Thanks

[FS_]

Ok, today, even after another BIOS factory reset the NUC started again at 2:10 pm. Great! So I now did the CMOS battery disconnect; after going crazy how to remove the MB from the case ... those little plastic pins at the audio jack drove me #?! ... but finally I left the battery disconnected for about 5 minutes and reassembled everything. Got a warning and checksum error on the CMOS values and time but besides that the BIOS values were the same as before ... what?!

Now let me see what's it going to happen tomorrow at 2:10 pm

[FS_]

It seems the CMOS Battery stunt mitigated the/my problem. It's been over 36h and no spontaneous power on, S5 wake up or whatever this was.