NUC8i7HVK - Error: BIOS has detected unsuccessful post attempt(s)

[OBaue1]

Hello together,

my name is Oli from Germany and I have recently purchased a NUC8i7HVK. I use it with a Samsung 970 Pro and a 960 Evo and 2x 16GB Crucial Ballistix Sport 2400 (BLS16G4S240FSD).

I also have a Skull Canyon for about 2 years now and I was so convinced of it that I thought, I need the successor now.

I have installed Win10 Pro and everything seems to work so far, except for one thing that I have not gotten fixed yet.

Every time I reboot the NUC, the Intel NUC-startup-screen appears for a short time, then it turns off completely (lights off) and immediately comes back again to the NUC-screen, followed by a message:

"Error: BIOS has detected unsuccessful post attempt(s). Possible causes include recent changes to BIOS. Performance Options or recent hardware change. Press Y to enter Setup or N to cancel and attempt to boot with previous settings"

I haven't done any changes, but the message appears anyway. If I then press N or either Y and go to the BIOS and save, it starts again 1x normally. The whole thing does not occur on complete shutdown and manually switch on again, but as I said only with reboot. Although I can disable the message with the help of "Disable Failsafe Watchdog" in BIOS-settings, but the "double" reboot with 2x NUC startup-screen and short off in between, still remains. I also have tried different BIOS-versions, but it's still the same. I would be glad if someone could tell me if this behavior is known or what I could still try to do about it or if it could possibly be a malfunction.

Thanks in advance

Oli

[OBaue1]

Ok, it seems that I've found it out. I use a power socket strip with master/slave-function and it was probably not adjusted properly, which has led to the short switch offs. This never happened with Skull Canyon, but you never stop learning;)

[idata]

Hello ratzler,

Thank you for joining the Intel Community Support and sharing your experience dealing with this issue. Hopefully, other community peers facing the same issue will benefit from your troubleshooting process.Wanner G.

[OBaue1]

I have now discovered that the problem is not related to the power strip, but seems to be caused by an external USB-hard drive "Western Digital 12TB My Book Duo WDBLWE0120JCH" running in Mode RAID1. I'm using Win10 Pro and the latest firmware for the WD-device v1.033 is installed. I also have tried different cables and USB-ports. The problem described above always occurs only when the WD-device is connected to the NUC during a reboot.

It is not particularly tragic, but i think it may be helpful if you know about this problem and perhaps you have an idea what else I could try here.

[RBell1]

I had the same error message with BIOS version 0040. Doing a BIOS recovery -- F4 from the power button menu -- with the same BIOS version fixed the problem.

See thread /thread/126432 126432

[OBaue1]

I've tried it with F4-recovery but the same problem as you've described it first occurs. After F4 it won't boot from the stick (tried 2 with FAT32 and new formatted [not quick] ).

[LTorr11]

Hi,

were you able to fix this? I have the same problem with a WD external drive and now I'm experiencing it with a Seagate drive too. It doesn't happen always but it is quite frequent. I have installed both Ubuntu and Windows 10 Pro (dual boot) but the message appears before the grub prompt.

[OBaue1]

I have enabled "suppress alert messages at boot", but it sometimes still occurs a 2nd reboot when the external drive is connected, but no message anymore and no key to press.

[stevenriz]

Hi everyone. We have over 10x of these that all do this every few restarts of the computers. These are graceful windows 10 pro restarts. Only thing connected is a web camera and a Logitech kb and mouse dongle. No memory device at all. I've updated the BIOS and keep it up to date. Along with all other drivers. Dont know what else to do. We've been living with it. Any other thoughts or help?

Thank you

[n_scott_pearson]

Have you guys tried upgrading to BIOS 63? There are a whole bunch of fixes included in this release that were backlogged up by the BIOS 60 SSD hang issue. I am not seeing one that specifically says it addresses this issue, however; I will follow up with developers...

...S

[Ronny_G_Intel]

Hi everyone,

I am currently investigating this issue but I need more evidence, I have a couple of Hades Canyon at the lab and I test 2 or 3 external USB Hard Drives ( Seagate* Expansion Portable drive 2TB and WD* My Passport 4TB) and I had no issues. Can you please provide the Brand and Model of the devices that are causing this error to show up? Please make sure that your system is already running BIOS version 0063.

OBaue1,
BIOS 63
Western Digital 12TB My Book Duo WDBLWE0120JCH

RBell1
Are you in BIOS63 already?
Did you rule out the issue to a specific device connected to the NUC, can you provide me with the Brand and Model?

LTorr11,
Are you in BIOS63 already?
Can you provide me with the WD* and Seagate* models?

MGonz38
Are you in BIOS63 already?
Can you provide me with the Brand and Model of the drives you have issues with?

stevenriz,
Are you in BIOS63 already?
Did you isolate the issue to the webcam? If yes, can you provide me with the Brand and Model?

Thanks,

Ronny G

[Voodoo]

I got the same issue with my Hades Canyon NUC on every BIOS version.

If I had the WD MyBook Duo (2 bays, 12TB*2, JBOD) connected to the NUC with USB Type-C cable before power up, then it was 100% that the BIOS would promote "unsuccessful POST attempt" after several on and off cycle.

I tried to connect a 14TB WD MyBook external disk (single bay) to NUC with a normal Micro USB 3.0 cable, and there was no issue at all.

There was actually another issue with the USB Type-C/Thunderbolt port on this NUC.

If one of the rear USB Type-C/Thunderbolt ports was connected to a external HDD like WD MyBook Duo, and another USB Type-C/Thunderbolt port was connected to a external Thunderbolt GPU at the same time before powering on(Razer Core X in my case), then after logging in to the Windows 10, the USB Type-C port which connected to the external HDD will be malfunction. There will be a yellow sign on the device called "TPS65988 Device" in Windows Device Manager.

The only solution is to power off, disconnecting one of the USB Type-C/Thunderbolt device, powering on again, and plug the device to the NUC again.

[MGonz38]

Not a fix but I was experiencing the same problems after I plugged all my external HDDS and the only solution was enabling fast boot but this disable booting from thunderbolt or Ethernet I believe.

[Sebastian_M_Intel]

Hello everyone, 

We would like to know if any of you have an update on this matter? Remember that we would like to check the following details for internal investigation: 

• If the BIOS version is the latest 0063. 
• The full brand and model number of the device you have issues with (drive, camera, etc). 

Regards,  

Sebastian M  

Intel Customer Support Technician  

[iosifgarleanu]

Hello,

I'm having this issue with a b170 logitech mouse wireless receiver connected in the back of a BOXNUC8i3BEK2.

I use the NUC for data acquisition and I connect remotely to it from time to time for maintanance.

I received the unit for verification after there was a power outage on site.  When the power came back, the NUC wouldn't connect to the main server. 

The BIOS Version is BECFL357.86A.0064.2019.0213.1122

I suspect that the NUC got stuck in the "Error: BIOS has detected unsuccessful post attempt" screen because of the USBs I use for data acquisition and thus would not boot up Windows and connect to the main server.

EDIT: Forgot to mention. If it is a cold start then it boots normally. On the other hand, if I dare to restart the unit it would go to the "BIOS has detected unsuccessful post attempt(s)" screen. 

A resolution for the issue would be nice to have.

Thanks in advance.

Best regards,

Iosif G.

[n_scott_pearson]

No hijacking conversations! We are discussing another user's issue here, not yours. Using the Post a Question button on the main Community page, open you own conversation to discuss your issue(s).

...S

[Sebastian_M_Intel]

Hello everyone, 

@iosifgarleanu, as @n_scott_pearson mentioned, please open a new thread as you are facing a problem with a completely different system, this thread is specifically related to NUC8i7HVK with the mentioned above BIOS versions and devices. 

@RBell1, @LTorr11, @MGonz38, @stevenriz, 

We would like to know if you have been able to gather the information previously requested: 

RBell1 

Are you in BIOS63 already? 

Did you rule out the issue to a specific device connected to the NUC, can you provide me with the Brand and Model? 

LTorr11, 

Are you in BIOS63 already? 

Can you provide me with the WD* and Seagate* models? 

MGonz38 

Are you in BIOS63 already? 

Can you provide me with the Brand and Model of the drives you have issues with? 

stevenriz, 

Are you in BIOS63 already? 

Did you isolate the issue to the webcam? If yes, can you provide me with the Brand and Model? 

Regards,   

Sebastian M   

Intel Customer Support Technician   

[Ronny_G_Intel]

Hi everyone,

We haven't been able to replicate this issue with the 3rd party USB devices we have available in our labs, which makes me believe that this issue is pretty specific to only some devices.

I can only recommend going into BIOS and Suppress Alert Messages:

We will keep an eye on this issue and I will get back to the community if I get any update but I cannot promise anything at this point.

Regards,

Ronny G

[OL_highway]

Hi,

I am interested in this thread and wish to pursue the discussion.

I just acquired a used NUC8i7HVK and face the same error message every time I try to resume the unit from sleep mode.

I performed a full clean install of the OS (W10 pro), all drivers updated through Intel tool yesterday 2020-12-31.

so BIOS is on version 64.

The only USB device attached is the RF transmitter for the Microsoft All-in-One Multimedia keyboard, part number N9Z-00007.

The message appears when I resume the unit from sleep mode either through the keyboard key or through Windows power menu.

The message does not appear upon a full restart.

The message continues to display even if BIOS set not to display messages.

Various BIOS settings on power options were unsuccessful, same with Windows 10 power settings.

One thing I have not tried yet, is the change the CMOS battery.

I would appreciate some insights.

Olivier

[n_scott_pearson]

CMOS memory has not been used for BIOS configuration storage for a very long time (more than 15 years). Seeing a CMOS clear is, however, used as a signal that the BIOS should ignore its current configuration and boot using a default configuration. This is used to get around changes to (or corruption of) the BIOS configuration that result in a system hang. Since, in your case, you have not lost the ability to boot or enter BIOS Setup, using it will accomplish nothing.

There is a 'however', however. If the battery is at or near exhaustion, replacing the battery with a new one may fix some issues. Usually, these are POST issues, which you aren't seeing (you've mentioned no issues with transitions from S4/S5). Still, if it was me purchasing a used system that is maybe 2-3 years old, I would be replacing the battery regardless. [Aside: be careful purchasing new batteries; there are a lot that look right but are wired opposite to what is needed.]

Hope this helps,

...S

[OL_highway]

Thank you Scott

You can guess through my question that I am getting older... first computer was a ZX80!

I am indeed about to swap the battery as it is a used unit.

Good tip, I will check voltage is right.

In the meantime, I will continue to research what can be the cause of this message and if anyone else stops by, I am eager to read advices or better, fixes!