BIOS Update [FNCML357] on FNHJA1 caused boot issue, always see BSoD post BIOS update

[NY0001]

Was prompted BIOS update from installer, installed after the Windows update.

After the dots start spinning for Win10 boot, it will BSoD. Stop Code: Inaccessible Boot Device

[LeonWaksman]

1.    Try Bios Recovery with the yellow security jumper removed:

2.     Prepare USB stick fully formatted to FAT32 with Bios file FN0041.CAP. Format your USB with Quick Format option unchecked. Do not format your USB in MAC (OS) or Linux machine. Use Windows. Important : the USB device must contain a folder \EFI\Intel, which contains the FN0041.CAP file. Otherwise the recovery will fail. Example: \EFI\INTEL\FN0041.CAP

3.     Disconnect the power adapter and remove the bottom panel from your NUC.

4.     Remove the Yellow Bios Security Jumper. (page 41 in Technical Product Specification )

5.     Insert the USB with the FN0041.CAP file into rear USB slot.

6.     Reconnect the power adapter and power ON the NUC. Wait 30 sec - 2min. The Recovery process will start automatically and will end after 2 -5 minutes.

7.     When bios recovery is completed, press and hold the Power Button to switch the power OFF, remove the power adapter and replace the Security Jumper (pins 1-2) . Reinstall the bottom panel.

8.     Power your NUC ON.

9.     Enter Bios setting by pressing F2 during boot process.

10. Press F9(followed by "Y"), to set Bios to default settings. Press F10 (followed by "Y"), to save the settings and exit to O.S. Let the NUC fully reboot.

Leon

[NY0001]

Tried this, still see BSoD.

Used this same method to try and flash the 39.CAP file, see the same BSoD issue now .

[AlHill]

Leon, I tried helping another user with the same issue after updating from 0039 to 0041. I am thinking it is a bios issue.

Doc

[LeonWaksman]

I saw reports of bricking NUC after attempt to update with the Aptio V core BIOS (it happened in NUC8i7INH). So, could be that there is a Aptio V BIOS problem. Any way, trying to recover BIOS may not help, but will not make worse. So, I would try to do this. Intel should debug this problem, since bricking NUC during BIOS update can't be tolerated.

Leon

[AlHill]

Intel should debug this problem, since bricking NUC during BIOS update can't be tolerated.

Agreed. Too many bios problems of late.

Doc

[n_scott_pearson]

Guys,

Let's not jump the gun here. This can happen if the BIOS settings are somehow modified in the process. For example, if the SATA Mode was reset from RAID back to AHCI, it would cause this same kind of BSOD (not saying this is what actually happened; it's just an example). The first step in checking out this possibility is to go into BIOS Setup and use F9 to reset its configuration to defaults. Then see what happens during boot.

...S

[LeonWaksman]

We are not talking about unsuccessful BIOS updating. We are talking that during unsuccessful BIOS update, the NUC is bricked (i.e. can't recover BIOS and NUC have to be replaced). If the problem is corrupting Windows boot, this I can understand, since this can be fixed by user. We have seen 3 report at least for NUC8i7INH (Aptio V BIOS), that NUC was bricked.

Leon

[NY0001]

Already tried this before submitting question.

[LeonWaksman]

Hi @NY0001​ 

It is not clear to me what did you tried? You can enter BIOS? If yes, your BIOS is O.K. and Windows boot is corrupted.

Leon

[LeonWaksman]

1. O.K. I understand (I saw your post above), that your BIOS works, but you can't boot into Windows.
2. Try to boot in Safe Mode from Command Prompt. The Command Prompt can be reached from Advanced Option Menu. 
3.  Press Power Button to switch NUC ON
4. When you see the Intel NUC logo, repeatedly depress F8, you will see words: Please wait. Stop depressing F8, NUC will enter Advanced Option Menu.
5. Click/tap on Troubleshoot.
6. Click/tap on Advanced options.
7. Click on Command Prompt
8. In the Command Prompt write the following command: bcdedit /set {default} safeboot minimal and press enter to execute this command
9. Close the Command Prompt window by clicking the X in the upper right corner of the Command Prompt window.
10.  Select Continue and sign in to Windows 
11. While in Windows, press Windows key + r. Run msconfig
12. Chose Boot tab and uncheck Safe boot. Reboot your system. 

Leon

Note: If you can't reach the Advanced Menu by pressing F8, boot form Windows Installation USB.

Select your language preferences and click/tap on Next.

Click/tap on Repair your computer at the bottom.

Continue from para . 5 above

[NY0001]

Following steps. At 8, got the following issue:

"The boot configuration data store could not be opened. The requested system device cannot be found"

Running from Windows Installation device, can't get past 10 (no Continue shows up...)

Ran the following commands:

bootrec /Rebuildbcd

(completed successfully)

bootrec /Fixmbr

(could not find any device)

bootrec /Fixboot

(Successfully scanned Windows installations: 0). This is concerning.

Reinstalled Windows on a new drive (main drive is locked from BitLocker):

Windows Boot Manager now sees 2 instance for boot:

New default is the newly installed windows.

Original instance will always BSoD still.

Used the new instance of Windows to format and wipe the original drive main drive. Reinstalled Windows on the main Drive that was previously locked.

Installed chipset driver, network driver, then Intel DSA. Works now.

[LeonWaksman]

Lesson learn from this event - always keep backup of your drive and/or prepare backup before major Windows update or BIOS update.

Leon

[n_scott_pearson]

Leon,

If there are (separate) issues where folks are reporting BIOS bricking, then these need to be forwarded to Mr. Chris, Either do so directly or give me the links and I will do so.

...S

[LeonWaksman]

OK, will do.

Leon