Community
cancel
Showing results for 
Search instead for 
Did you mean: 
EEd
Novice
1,575 Views

NUC 2820 doesn't wake on scheduled time

Jump to solution

Hello,

my nuc DN2820FY is running a Windows 8.1 and goes in hibernate mode every night. In the morning it's triggerd to wake up via BIOS (S5 wake) at 8:00 am.

This worked fine for years.

Now I've updated the old BIOS version from 2016 to the new BIOS Version from 03/2018 (FYBYT10H.86A.0063.2018.0314.1612).

Since then the nuc doesn't wake on the scheduled time I've set in the BIOS. But as soon as I try to access a network share of the nuc, it wakes up.

I've tried this, but it doesn't helped: https://www.intel.com/content/www/us/en/support/articles/000020534/mini-pcs.html https://www.intel.com/content/www/us/en/support/articles/000020534/mini-pcs.html

Any ideas? Is it a known issue?

Thanks.

Eddy

0 Kudos
1 Solution
EEd
Novice
145 Views

As described in the first post, the device goes to hibernate mode (S4).

But the name of the BIOS option is "Wake System from S5". This means the system must be shut down.

Tried it now. And it works if I shut down the system.

This means I will always shut down the system in the future and not send it to hibernate mode.

What I do not understand is why that has always worked in the past. The hibernate mode was always executed with a task plan that has not changed.

Greets

Eddy

View solution in original post

7 Replies
n_scott_pearson
Super User Retired Employee
145 Views

Sometimes, BIOS updates can screw up the BIOS configuration. I suggest that you follow this process:

  1. During POST, use F2 to enter BIOS Setup (Visual BIOS).
  2. Use F9 (followed by Y) to reset the BIOS configuration to defaults.
  3. Use F10 (followed by Y) to save the configuration and exit BIOS Setup.
  4. During the subsequent POST, again use F2 to enter BIOS Setup.
  5. Change the BIOS configuration to wake the system each day at 08:00.
  6. Make any other changes in the BIOS configuration (boot order, etc.) absolutely necessary for your system.
  7. Use F10 (followed by Y) to save the configuration and exit BIOS Setup.

Hope this helps,

...S

EEd
Novice
145 Views

Thanks for the answer. And sorry for the late response.

I tried it yesterday two times, but it didn't helped.

Any other ideas?

Thanks.

Eddy

idata
Community Manager
145 Views

Hello eddyed,

 

 

Thank you for your response.

 

 

As N. Scott Pearson was mentioning, BIOS can become corrupted. I recommend you to try testing the unit for a couple of days following the steps provided above.

 

 

If the issue is not resolved, you can try a BIOS Recovery.

 

https://www.intel.com/content/www/us/en/support/articles/000005532/mini-pcs.html

 

 

BIOS Update

 

Version: 0063 (Latest)

 

https://downloadcenter.intel.com/download/27647/NUCs-BIOS-Update-FYBYT10H-86A-?product=78953

 

 

Another option you can try is rolling back to BIOS version 0061 and test your unit.

 

https://downloadcenter.intel.com/download/27468/NUCs-BIOS-Update-FYBYT10H-86A-

 

 

Wanner G.
EEd
Novice
145 Views

Thanks for the answer.

Tried it now for hours.

- BIOS Recovery via USB Stick to version 0063

- Once again BIOS settings reset

- Downgrade to 0061

- Downgrade to 0060

- Once again BIOS settings reset

Nothing helped.

A downgrade < 0060 is not possible. So I can't go back to my last working BIOS version.

Greets

Eddy

EEd
Novice
146 Views

As described in the first post, the device goes to hibernate mode (S4).

But the name of the BIOS option is "Wake System from S5". This means the system must be shut down.

Tried it now. And it works if I shut down the system.

This means I will always shut down the system in the future and not send it to hibernate mode.

What I do not understand is why that has always worked in the past. The hibernate mode was always executed with a task plan that has not changed.

Greets

Eddy

View solution in original post

n_scott_pearson
Super User Retired Employee
145 Views

Well, it actually shouldn't have worked, so that was a bug. This may be one of those cases where a bug was, for you, a feature. Now that the bug is fixed, however, the "feature" is gone. An interesting side note is that this has proven that the feature could be "Wake System from S4 & S5". Hhmmm. Over the course of my career, I can remember multiple times where a bug eventually became a formal feature.

As I think about it, using Hibernation (S4) adds no value in your usage scenario. You want the system powered down over night and powered back up and ready to go in the morning. This is presumably long enough before you might sit down to use it (or need it running) that the fact that it takes longer to do a full boot instead of a restore shouldn't matter.

...S

AlHill
Super User
145 Views

File under "Bugs, and Bug-like features".

Doc

Reply