Intel® NUCs
Support for Intel® NUC products
Announcements
Do you have improvements you would like us to make on this community site? If so, we would love to hear your feedback! Click here for an 8 question survey. Thanks!

11305 Discussions

NUC8i7HVB "BIOS hast detected unsuccessful POST attempt(s)"

Asgard
Beginner
749 Views

I run a NUC8i7HVB with BIOS version 064 and Windows 10 Pro. Nearly every time I boot the NUC shuts down, comes back on again and shows the above message. If I press N it reboots and shows the message again. If I press Y and leave the UEFI without changing anything, after that it will boot correctly.

In an other thread someone had the same problem with an other NUC model and it seemed the external HDDs were the problem. I also have some external HDDs which are a WD My Book with 4 TB and a RAID 1 with 2 TB (ICY BOX IB-RD3620SU3).

Are there any new findings on this issue? I use a master/slave power supply which means that the hard drives boot up together with the NUC. Could that be the problem? Perhaps the NUC is faster than the hard drives and does not correctly recognize them?

0 Kudos
1 Solution
LeonWaksman
Super User
684 Views

Enter BIOS Advanced > Devices > USB and set the relevant USB port (where the external drive or it HUB is connected) to No Detect (instead of Enable). The attached image will help you to identify the relevant port.

 

Leon

 

View solution in original post

15 Replies
LeonWaksman
Super User
733 Views

Hi @Asgard 

Could be that the POST fails on some external device connected to the USB port. Disconnect all external devices and check if still you see this warning. If this warning disappeared, connect the external devices, one after one and find the problematic device. Then please write to which USB port it is connected.

Leon

 

Asgard
Beginner
723 Views

Could take some time to figure it out as I have 3 USB hubs with 13 devices connected .

Asgard
Beginner
718 Views

For the beginning I have deactivated "USB Legacy support" in UEFI. Because that caused much trouble on an older notebook some years ago resulting in a black screen while booting. It's just a guess. If that doesn't help I have to go deeper. Sorry for double post but as far as I can see you are not able to edit your posts here.

LeonWaksman
Super User
709 Views

Start with disconnecting all HUBs (with the 13 devices) and find which HUB with its device is causing this error.  You may leave the keyboard + mouse connected directly to NUC (or if you have wireless keyboard + mouse leave the receiver in the USB slot).

Leon

 

Asgard
Beginner
689 Views

It seems that the external Western Digital drive causes the problem - a WD My Book with 4 TB.

LeonWaksman
Super User
685 Views

Enter BIOS Advanced > Devices > USB and set the relevant USB port (where the external drive or it HUB is connected) to No Detect (instead of Enable). The attached image will help you to identify the relevant port.

 

Leon

 

View solution in original post

Asgard
Beginner
673 Views
n_scott_pearson
Super User Retired Employee
667 Views

There's a 'but' to consider - if we are indeed talking about a hub, you should not have the keyboard and mouse connected to this hub as disabled USB ports are not scanned and thus the keyboard and mouse will not be available to support BIOS POST/Setup operations (at least not without jumping through hoops (accessing Power Button Menu, etc.).

Hope this helps,

...S

Asgard
Beginner
659 Views

Yeah, I know. There are only external drives connected to that hub. Keyboard is connected to an other hub and mouse directly to the NUC.

Asgard
Beginner
580 Views

Still struggling with that absolutely annoying issue. I got rid of a whole (older) USB hub but the error message seems to appear completely random. I had days where I had to restart the NUC around TWENTY times disconnecting several USB devices. Then the next days it booted normally with all USB devices connected.

I now bought  a 3 port hub only for keyboard and mouse, connected it to USB port 4 and set USB ports 1, 2 and 3 of the NUC to "No detect" - that are all ports other USB devices are connected to.

Hope that will finally work. On some days I just want to throw the NUC out of the window which is rather sad because besides that boot problems I like it very much.

Asgard
Beginner
358 Views

@LeonWaksman could it be the rear USB ports on your image are wrong numbered? Because I set ports 1, 2 and 3 to "No detect" while keyboard and mouse connected to the port that is numbered 4 on your image. Result was both could not be detected by UEFI anymore. Connecting them to what is port 3 on your image activated them again although it was on "No detect" in UEFI. So I guess ports 3 and 4 are reverse from your image compared to how the UEFI numbers them?

Also, ports 8 and 9 aren't even listed in UEFI?

LeonWaksman
Super User
348 Views

Hi @Asgard 

You are absolutely right. The USB ports attached to my post are wrong numbered. I got this image from Intel and never tested this. Now, after getting this alert from you, I've performed tests on my Hades Canyon and I'm attaching  image with the corrected numbering. 

In addition the both Thunderbolt 3 ports on the rear panel can't be controlled in BIOS, leaving only seven ports that can be controlled.

The help comment in BIOS for USB port 7 is wrong as well (grammatically and content) instead of "USB Ports 7 are located internally on a USB header" should be: USB port 7 is located on the front panel.

Hope this will help to solve your problem and I believe that we will have correction/confirmation from Intel.

Leon

HV Ext USB OrderingCorrected.jpg

 

Asgard
Beginner
342 Views

Yeah, I think the wrong numbers were my problem because the HDDs were still detected on boot. The fact that the wrong numbers come from Intel themselves is rather bad. They should know their hardware.

LeonWaksman
Super User
338 Views

Intel is very big company, scattered around the world. So, mistakes may happen.

Leon 

 

 

n_scott_pearson
Super User Retired Employee
318 Views

Actually, that image was from me - but it was a representation of what Intel told me. If someone wants to work out how it should be correctly represented, I have attached the bare diagram files (as well as the ones with numbering that I created).

...S

Reply