Community
cancel
Showing results for 
Search instead for 
Did you mean: 
MBuri1
Beginner
537 Views

BOXNUC8i7HVK2 Hades Canyon BIOS Deep S4/S5 setting keeps reverting to OFF

BIOS setting for "Deep S4/S5" keeps reverting to OFF. It works one reboot after setting it to ON, then next reboot it is OFF again. (BIOS version is the latest: 58).

 

We need to turn off the power from the thunderbolt ports, otherwise our connected HMD will not turn off and stays on. Without DeepS4/S5 this is not possible.

 

Would be very nice to have this issue fixed!

 

 

0 Kudos
9 Replies
Wanner_G_Intel
Moderator
256 Views

Hello MBuri1,

 

Thank you for submitting your question on this Intel® Community.

 

To better assist you, we would like to gather more information about your system configuration.

 

  • Please generate a system report with the Intel® System Support Utility (Intel® SSU) and attach it to this thread.

 

  1. Intel® SSU Download link
  2. Open the application and click on "Scan" to see the system and device information. By default, Intel® SSU will take you to the "Summary View".
  3. Click on the menu where it says "Summary" to change to "Detailed View".
  4. To save your scan, click on "Next", then "Save".

 

  • Are date and time values in BIOS accurate after rebooting the unit?
  • Do other BIOS settings show the behavior reported on this thread?

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

MBuri1
Beginner
256 Views

Yes the date and time values are accurate after rebooting the unit. As far as I know the "Deep S4/S5" setting is the only one showing this behaviour. Other settings are saved correctly.

 

I've attached the SSU output

Wanner_G_Intel
Moderator
256 Views

Hrllo MBuri1,

 

Thank you for your response.

 

  • Try loading BIOS default settings first.

 

1. Press F2 during boot to enter BIOS Setup.

2. Press F9 to set defaults.

3. Press F10 to save and exit BIOS.

 

  • Then, enable DeepS4/S5 and check if it remains enabled after rebooting the unit multiple times. 
  • If the issue persists, please let us know so that we can do further research. 

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

MBuri1
Beginner
256 Views

Hello Wanner,

 

I've tried but still the same issues unfortunately. Seems like this particular setting is not stored permanently and is lost after powering off once. I can remember that this setting was missing when we bought the NUC, I had to update the BIOS first to have it. So maybe it is still not added to the settings which are actually stored in memory?

 

Thanks for the help and quick responses so far.

 

Maarten

LeonWaksman
Super User
256 Views

Hi @WannerG_Intel​ ,

I can confirm Maarten findings. Tested on my NUC8i7HVK and the DeepS4/S5 is also disabled after reboot. Did you checked this in your lab?

 

Regards

Leon

 

Wanner_G_Intel
Moderator
256 Views

Hrllo MBuri1, LWAKSMAN

 

Thank you for your input. 

 

We will do further research and update this thread as soon as possible. 

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

Wanner_G_Intel
Moderator
256 Views

Hello MBuri1, LWAKSMAN

 

Thread update.

 

We would like to gather more details about your units. We have sent you a private message requesting some information about your Intel® NUC kit NUC8i7HVK.

 

Please let us know if you receive the message and reply to us at your earliest convenience.

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

Wanner_G_Intel
Moderator
256 Views

Hello MBuri1, LWAKSMAN

 

Thank you for providing us with the information requested.

 

We are doing further research about this behavior. We will update this thread as soon as possible.

 

Wanner G.

Intel Customer Support Technician

A Contingent Worker at Intel

Ronny_G_Intel
Moderator
256 Views

Hi MBuri1, Leon,

 

We have replicated this issue and filed a bug report that is being addressed by the product team, I cant tell you when a fix will be ready for this issue but I will keep you posted.

Bug report number is 2209673523 so I will be closing the case that was created for this community incident and will keep an eye on the bug report.

 

Regards,

Ronny G

Reply