Windows 10: Error Code 0cX000000f; Missing/Damaged ESP System Partition

Seeking thoughts on an apparent mystery volume "DiskPart" is showing after a Windows 10 Creators Update failure forced a hard shutdown. Windows 10 major updates failing with blank frozen screens are routine for my formerly Windows 7 powered ACER all-in-one. But from version 1507 "Threshold 1" forward the previous OS restored or -- very rarely -- the update completed. But the last failure brought a restart/booting loop. The Blue Screen was one for the 0xC000000f error code:

Your PC/Device needs to be repaired.
The boot configuration data for your PC is missing or contains errors.
File: EFI/Microsoft/Boot/BCD
Error code: 0xC000000f
You'll need to use recovery tools. If you don't have any installation media (like a disk or USB device), contact your PC administrator or PC/device manufacturer.

Obviously Booting Configuration Data (BCD) was busted or lost so without checking volumes via DiskPart I tried:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanOs
bootrec /rebuildbcd

The fix seemed to be working as one Windows installation was located. But when I tried to add the installation to the boot list, I received: "The requested system device cannot be found."

So then I tried:

bootrec /rebuildbcd
bcdedit /export c:\bcdbackup
attrib c:\boot\bcd -h -r -s
ren c:\boot\bcd bcd.old
bootrec /rebuildbcd

Again the fix seemed smooth until ren c:\boot\bcd bcd.old warned: "A duplicate file name exists, or the file cannot be found." So it was time to do what I should have done first. Check DiskPart. And what I saw, shown here, seemed impossible.
Attachment 148677
What is that "Healthy" 100 MB partition in Volume 1 listed as "C" System? It seems it would be the EFI System Partition (ESP). Yet it is in NTFS rather than the required FAT32 format. So again I ask, what is "DiskPart" showing? I don't dare reformat Volume 1 to FAT32 without being sure it is the ESP containing the boot loaders or kernel images for all installed operating systems. In a fairly extensive search of Windows help sites, I found only one other individual suspecting an ESP somehow reverted to NTFS format. And the assertion met with incredulity.

Sincere thanks for reviewing this BCD issue and I close here with DSKCHK results.
Attachment 148678

:)

 

0cx000000f on Windows 10

Someone had the same error code!

Take a look at this post it may help you: error 0cx000000f

 

System Image back up failed.

Error message: backup failed to get exclusive lockon EFI system partition (ESP) (0x8078011E) Access denied (0x80070005)

Any ideas?

 

Please post results of

sel disk 0
list par

Looks like your ESP is mounted at C and windows at D.

Probably you'll need to convert ESP to FAT32 which you might be able to do without reformatting depending if it still contains anything.

 

Thanks LX07. Results for your request follow.
Attachment 148709

 

Please post a DM log collector: BSOD - Posting Instructions - Windows 10 Forums

 

ZBook ... I noted the DM tool before posting this thread via my ACER E1 series laptop. My crashed all-in-one will only boot through my Windows 10 version 1703 ISO install disk. And the only usable Advanced Options function is Command Prompt. Directions for the log collector do not indicate it can be activated through CMD.exe. And even if it can there would be no ability to create a zip file. Though I would be able to photograph any screen results. Please advise.

 

1) What information is available about the drive?
2) Were there any recent software or hardware changes or known software or hardware problems?
3) How old is the drive, HD vs SSD, previous SMART, short or long generic test results, bad blocks etc.?
4) What is the malware history?
5) Is the system 32 or x64 bit?
6) When were you last using windows 7?
7) What was the lastest version of windows 10 that you were able to upgrade to? And had you had any upgrade problems to the latest or any prior version of Windows 10 with 2 GB RAM?
8) Were you having any chkdsk scans or drive file problems before the latest software change?
9) Are your files backed up to where you could delete partitions or format the drive making a clean install?
10) Had you made a backup image?
11) Have you tried any other repair methods besides what is already in the thread?
12) had you tried a chkdsk /f /r of each drive letter?
12) Had you tried a registry repair?
13) Had you tried the Kyhi recovery method?


14) Using X: \Windows\system32\cmd.exe type:
1) dir
2) bcdedit | find "osdevice"
3) C: dir
4) D: dir
5) with a camera or smart phone camera take a picture and post an image of the results into the thread.
6) see if this method with notepad will also work to record, save, and re-post the text that you see on the monitor:
7) When the above steps have completed > right click on the top bar or title bar of the administrative X box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the notepad > connect a second flash drive to the desktop > save notepad files to the second flash drive > post the information into the thread.

 

1) What information is available about the drive?
Essentially what is shown via DiskPart and CHKDSK.
2) Were there any recent software or hardware changes or known software or hardware problems?
Although system ran perfectly with current OS, Windows Memory Diagnostics Tool recently indicated an issue. New, higher RAM modules were about to be ordered when version 1703 upgrade failed leading to boot failure.
3) How old is the drive, HD vs SSD, previous SMART, short or long generic test results, bad blocks etc.?
The HDD and all other internal parts are original since April 2012 purchase. It is a light use PC as it shares work/personal load with a Windows 10 laptop and two Android devices.
4) What is the malware history?
No malware history but several adware found and eliminated by MalwareBytes several years ago. No adware/malware detected since.
5) Is the system 32 or x64 bit?
X64 bit.
6) When were you last using Windows 7?
August 2015, at which time it was replaced by Windows 10 Version 1507 "Threshold 1" following numerous upgrade failures as detailed in "7."
7) What was the latest version of Windows 10 that you were able to upgrade to? And had you had any upgrade problems to the latest or any prior version of Windows 10 with 2 GB RAM?
Windows 10 Version 1607 Anniversary Update. As previously mentioned, Windows 10 major updates failing with blank frozen screens are routine for the formerly Windows 7 powered ACER all-in-one. But from version 1507 "Threshold 1" forward the previous OS smoothly restored or -- very rarely -- the update completed. Threshold 1 failed possibly near 10 times, while each upgrade thereafter failed at least two or three times before success through such steps as using the Media Creation Tool, deleting contents of the Software Distribution folder, etc.
8) Were you having any chkdsk scans or drive file problems before the latest software change?
No.
9) Are your files backed up to where you could delete partitions or format the drive making a clean install?
Yes. All personal files are routinely backed up on USB media and "Cloud" services, the latest backup occurring immediately before the failed version 1703 upgrade.
10) Had you made a backup image?
Given response "9" above plus the aggressive Windows 10 update schedule, chose not to create system image and to rely instead on MCT or ISO. But did create recovery drive and system repair disk. (Lesson learned.)
11) Have you tried any other repair methods besides what is already in the thread?
In terms of BCD rebuild, none beyond those listed. The recovery drive and system repair disk listed in "10" were ineffective. Setting BIOS to boot from USB device does not seem to work, perhaps because recovery USB's are FAT32. I have tried different hubs, avoiding USB 3.0 as is often suggested.
12) Had you tried a chkdsk /f /r of each drive letter?
Yes. Results follow.
Administrator: X:\windows\SYSTEM32\cmd.exe - chkdsk C: /f /r
Attachment 149580
Administrator: X:\windows\SYSTEM32\cmd.exe - chkdsk D: /f /r
Attachment 149581
12.1) Had you tried a registry repair?
Not yet. Wanted Ten-Forums input first.
13) Had you tried the Kyhi recovery method?
No. Wanted Ten-Forums input before trying Bootable PE Rescue Disk/Kyhi’s Rescue Disk.
14) Using X: \Windows\system32\cmd.exe type:
1) dir
2) bcdedit | find "osdevice"
3) C: dir
4) D: dir
5) With a camera or smart phone camera take a picture and post an image of the results into the thread.
See text-based results under "6" and "7" below. If desired, actual screen images available.
6) See if this method with notepad will also work to record, save, and re-post the text that you see on the monitor:
7) When the above steps have completed > right click on the top bar or title bar of the administrative X box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the notepad > connect a second flash drive to the desktop > save notepad files to the second flash drive > post the information into the thread.
Attachment 149582
Attachment 149583
Attachment 149584

 

1) Run memtest86+ version 5.01 for at least 8 runs.

This may take many hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool
When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.

Memtest86+ is not run by time but by passes.
The more passes the better.

There is a high incidence of false negatives if there are less than 8 passes.
A false negative is a pass when there is malfunctioning RAM.

If there is more than 1 RAM module and if it is dual channel the RAM should be tested as pairs.
Memtest86+ will take approximately 1 -2 hours /GB RAM.
Just 1 error is a fail and testing can be aborted.
Then if there is more than 1 RAM test 1 RAM at a time in the same DIMM for 8 or more passes.
if the RAM failed when tested together and passed when tested independently 1 RAM should be placed in another DIMM to test the DIMM /MB.

For all tests please use a camera or a smart phone camera to take pictures and post images into the thread.
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
MemTest86+ - Test RAM Windows 10 BSOD Tutorials

 

Interesting events to report. Using ZBook/TenForums guidance I downloaded a Memtest86+ V5.01 "Pre-Compiled Bootable ISO (.zip)." I extracted and burned the small ISO file to a DVD-RW. But the system continuously failed to boot from the Memtest86+ disk. Finally came this explanation:

ERROR: No boot disk has been detected or the disk has failed.

Perhaps I needed the "Pre-Compiled Bootable Binary (.zip)." So I removed the MemTest86+ disk and inserted my ISO install disk for Windows 10 Version 1703, Build 15063.0 to confirm it still worked. I must note here that for ZBook's question #11 regarding repair methods pursued I forgot to mention an attempted reinstall via the ISO. That attempt ended with a familiar frozen screen.

But after the MemTest86+ ISO failed to boot the system, the Build 15063.0 ISO somehow finalized my more recent installation attempt. Being disappointed, frustrated, and tired I do wonder if I clicked "INSTALL" rather than "Repair my computer" in the Recovery Environment. I honestly don't think so, but cannot "swear on it." Primarily I recall Cortana's loud unexpected voice guiding final installation steps. In any event, I do want to conduct the MemTest86+ to confirm a problem detected by Windows Memory Diagnostics Tool. But should I not have used the MemTest86+ "Pre-Compiled Bootable ISO (.zip)?" Do I require instead the MemTest86+ "Pre-Compiled Bootable Binary (.zip)?"

 

Clarification to the above. Upon reflection I definitely DID NOT accidentally select "INSTALL" rather than "Repair my computer" in the Recovery Environment. I now recall entering Advanced Options to briefly use Command Prompt. What I don't recall is exactly when Cortana popped up to finalize installation. I was about to select "Turn off Computer" but can't say I did so.
The one clear thing is somehow much prior finagling trying to get the system to boot from the disk "woke" the Creator's Update ISO. Unscientific as that is; perhaps some Power Users or Users can suggest something scientific. Or perhaps not.