Solved 0xc000000e - HD crash, switched to cloned backup drive

[Alloy25]

Hello. My 8 year old 500GB Seagate hard drive failed a few days ago and I switched over to my recent backup from a cloned drive (about a week old backup). The last time I backed up my drive, the only error was something like Adobe font pack failed to copy. No other errors appeared. I have the original backup without any changes. I’m currently cloning the disk using Hiren’s Boot CD and CloneDrive to make a new copy if things get too hosed while i’m trying to fix the issue.

This is not a dual boot machine. Just A basic Windows 7 install. 3 x Partitions: 100 mb System Reserved (Active), Pagefile, and Win7. Custom build

Tested the current hard drive i’m troubleshooting from and passed.

Ran chkdsk from Hiren’s Boot CD. Corrected a few things.

I get an error message under “Windows Boot Manager” screen = Windows failed to start.
File: \Windows\System32\winload.exe
Status: 0xc000000e
Info: The selected entry could not be loaded because the application is missing or corrupt.
Alternately after some troubleshooting Info might show “The boot selection failed because a required device is inaccessible”.

I hit enter to continue and the next screens gives me one option to choose an operating system “Windows 7” and returns to the previous screen mentioned above.

Booting to the windows installation DVD:
After selecting repair computer it’s “Searching for Windows Installations...” and after about 10 seconds it shows:
OperatingSystem ---------- Partition Size ---------- Location
Windows 7 -------------------- 0 MB ------------------------(Unknown) Local Disk

System Recovery Options.
Choose a recovery tool.
Operating system: Windows 7 on (unknown) Local Disk.


I’ve booted using the Windows 7 installation DVD and tried Startup Repair (repair 3 times) multiple times after major troubleshooting steps when Startup Repair can attempt to repair the problem. Usually it just gives the error message below:

I use “wmic logicaldisk get name” to list the drives. The only drives that show are D: for the cd and X: for the recovery environment.

DiskPart will recognize the drive and partitions. System Reserved partition is active with other partitions inactive.


It usually shows “Startup Repair cannot repair this computer automatically”.
Problem Details:
Problem Signature:
Problem Event Name: Startup Repair Offline
Problem Signature 01: 0.0.0.0
Problem Signature 02: 0.0.0.0
Problem Signature 03: unknown
Problem Signature 04: 0
Problem Signature 05: unknown
Problem Signature 06: 1
Problem Signature 07: unknown
OS Version: 6.1.7601.2.3.0.256.1
Locale ID: 1033


Startup Repair diagnosis and repair log:
--------------------------------------
Number of repair attempts:1

Session details
-------------------------------------
System Disk = \Device\Harddisk0
Windows Directory = <<<<<<<<<<Missing?
AutoChk Run = 0
Number of root causes = 1

Test Performed (shortened to show ones that passed)
Completed successfully: Error code = 0 x 0
Name:
Check for Updates
System disk test
Disk failure diagnosis
Disk metadata test
Target OS test

Root cause found:
---------------------------------------
Boot configuration is corrupt

Repair action: Partition table repair
Result: Failed. Error code = 0x490
Time taken 453 ms
Next i tried:
BootRec with switches:
/FixMbr = Completes Successfully
/FixBoot = Completes Successfully
/ScanOs = Zero OS found
/Rebuild BCD
Also tried delete and /Rebuild:

• bcdedit /export C:\BCD_Backup
• c:
• cd boot
• attrib bcd -s -h -r
• ren c:\boot\bcd bcd.old
• bootrec /RebuildBcd

Same error message after reboot

I referenced the following link for the next section:
https://support.symantec.com/en_US/article.TECH160475.html

When I type in BCDEDIT:

Windows Boot Manager
-------------------------------
identifier ---------------------------------------- {bootmgr}
device -------------------------------------------- partition=\Device\HarddiskVolume1
path ------------------------------------------------ \bootmgr
description -------------------------------------- Windows Boot Manager
locale ---------------------------------------------- en-US
inherit --------------------------------------------- {globalsettings}
default --------------------------------------------- {default}
resumeobject -----------------------------------{23512ef6-c62b-11e0-a274-99f9dbd9b8b1}
displayorder -------------------------------------{default}
toolsdisplayorder -----------------------------{memdiag}
timeout30

Windows Boot Loader
----------------------------
identifier ------------------------------------------ {default}
device ---------------------------------------------- unknown
path -------------------------------------------------- \Windows\system32\winload.exe
description ---------------------------------------- Windows 7
locale ------------------------------------------------en-US
inherit ------------------------------------------------{bootloadersettings}
osdevice --------------------------------------------unknown
systemroot -----------------------------------------\Windows
resumeobject -------------------------------------{23512ef6-c62b-11e0-a274-99f9dbd9b8b1}
nx -------------------------------------------------------OptIn

Device and Osdevice show up as unknown. Tried to fix this by:

bcdedit /set {DEFAULT} device partition=c:
(press enter)
bcdedit /set {DEFAULT} osdevice partition=c:
(press enter)
bcdedit /set {BOOTMGR} device partition=c:
(press enter)

All three reported:
An error has occurred setting the element data.
The request is not supported.



When i try F8 for safe mode i get:

Windows 7/Vista/server (Pointer)
Windows 7/Vista/server
Windows 7/Vista/server (Debug - Default mode)
Windows 7/Vista/server (Debug - Legacy mode)
Windows 7/Vista/server (No SLIC - Pointer)
Windows 7/Vista/server (No SLIC)
Windows NT/2000/XP
Loader Help

<Use the Uparrow and Downarrow to highlight an entry. Press ENTER or 'b' to boot.>
<Press 'c' for a command-line

Not familiar with the above options.

I moved the hard drive to another computer and can see my files. I know I can reinstall windows and start over, but it would be great to get this up and running, at least for a little while longer.

Anything else to try? I’ve read dozens of posts trying to figure this out, but this one has me stumped.

Thanks!

 

[Alloy25]

Deleted the System Reserve partition and let 3 x Startup Repair rebuild the partition.
Fresh install and cloned the Windows partition to the new drive with the fresh System Reserve partition.
Same errors with both.

 

[GokAy]

Can you post a screenshot of the final drive layout from bootable Partition Wizard free? Bootable Partition Manger | MiniTool Partition Wizard Bootable Edition. Make sure all partitions and details are visible.

Deleted the System Reserve partition and let 3 x Startup Repair rebuild the partition.

You have to mark active the Windows partition, then run the startup repairs. Can be done with DiskPart or Partition Wizard.

 

[Alloy25]

You have to mark active the Windows partition, then run the startup repairs. Can be done with DiskPart or Partition Wizard.

With or without deleting the System Reserved partition? Deleted the System Reserved partition, marked Windows partition as Active and ran Startup Repair. It didn't rebuild the System Reserved Partition. I've seen it done several ways in the forums.


Thanks for your response. System Reserved is marked Active.

 

[GokAy]

You don't need a System Reserved partition unless you are using BitLocker feature.

Please read the whole article to get a sense:
http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

10. Using the Partition Wizard CD you can also try a last-resort fix that often works for me when the boot files are corrupted beyond repair: Delete the System Reserved 100mb partition, or if you don't have one shrink C from the left by 200mb using Partition Wizard to Resize Partition. In that space use Partition Wizard to Create a Primary Partition which you Mark Active. Reboot into Win7 disk or System Repair Disk to run Startup Repair - Run 3 Separate Times which should on the first attempt write the boot files, on the second attempt make partition bootable when it notices it is not, and possibly need a third attempt to complete all repairs including writing System Recovery Options to the F8 Advanced Boot Options.

Marking Windows partition active and running startup repair won't create a System Reserved but make Windows partition a system one (bootmgr files here).

So either try making Windows or System Reserved partition bootable (after setting active, run startup repair 3 times with a restart in between each attempt).

Also the errors you are getting may be due to:
- a corrupt media
- non Service Pack disk for a SP1 install

 

[Alloy25]

Previously I've been in tech support for several years and started thinking/remembering MS error messages usually weren't that accurate in certain instances. Then i ran across this thread:
http://answers.microsoft.com/en-us/...-recover/3a6e0014-9942-4d37-86b6-b19b93af32ef

File: \Windows\System32\winload.exe
Status: 0xc000000e
Info: The selected entry could not be loaded because the application is missing or corrupt.

Winload.exe missing or corrupt was a symptom but not the actual problem. Like a red herring.

It's there, but System Reserved can't reference Winload.exe because there is no drive letter assigned to the System partition. Every time I would reboot after assigning the System partition a letter, it would disappear. Noticed this in Disk Management. My Computer under Hiren's boot cd would assign a letter so it slipped by me for awhile. Should have pursued this earlier.


I started looking at the message below as the problem:

Booting to the windows installation DVD:
After selecting repair computer it’s “Searching for Windows Installations...” and after about 10 seconds it shows:
OperatingSystem ---------- Partition Size ---------- Location
Windows 7 -------------------- 0 MB ------------------------(Unknown) Local Disk

Diskpart could see the disk and volumes so at least the data was still there but couldn't boot. I needed to manually assign a drive letter and run BCDedit without rebooting so the System drive is accessible through the Command Prompt.

To fix this error:
Load Windows DVD
Repair Computer
Command Prompt
Diskpart
Diskpart> list disk
Diskpart> select disk <#> (Disk 0 for my install)
Diskpart> list volume
Diskpart> select volume <#> (Volume 3 for my install)
Diskpart> assign letter=c
Diskpart> exit

Then I could go into C: and view files under Command Prompt.


When I type in BCDEDIT:

Windows Boot Manager
-------------------------------
identifier ---------------------------------------- {bootmgr}
device -------------------------------------------- partition=\Device\HarddiskVolume1
path ------------------------------------------------ \bootmgr
description -------------------------------------- Windows Boot Manager
locale ---------------------------------------------- en-US
inherit --------------------------------------------- {globalsettings}
default --------------------------------------------- {default}
resumeobject -----------------------------------{23512ef6-c62b-11e0-a274-99f9dbd9b8b1}
displayorder -------------------------------------{default}
toolsdisplayorder -----------------------------{memdiag}
timeout30

Windows Boot Loader
----------------------------
identifier ------------------------------------------ {default}
device ---------------------------------------------- unknown
path -------------------------------------------------- \Windows\system32\winload.exe
description ---------------------------------------- Windows 7
locale ------------------------------------------------en-US
inherit ------------------------------------------------{bootloadersettings}
osdevice --------------------------------------------unknown
systemroot -----------------------------------------\Windows
resumeobject -------------------------------------{23512ef6-c62b-11e0-a274-99f9dbd9b8b1}
nx -------------------------------------------------------OptIn

Device and Osdevice show up as unknown.



Now that the System partition had a drive letter assigned, BCDEdit could point to the correct partition.

Referenced for the appropriate commands - Steps 4, 5, 6, and 7:
https://support.symantec.com/en_US/article.TECH160475.html

Previously BCDEdit would give an error message. Now "The operation completed successfully.)

bcdedit /set {DEFAULT} device partition=c:
(press enter)
bcdedit /set {DEFAULT} osdevice partition=c:
(press enter)
bcdedit /set {BOOTMGR} device partition=c:
(press enter)
7. Reboot the system after removing the OS disk.

Now after running BCDEdit:
Windows Boot Manager
-----------------------
Device -------------- Partition=C:

Windows Boot Loader
----------------------
Device -------------- Partition=C:
osdevice ------------ Partition=C:

Now it will boot!

Let me know if any of the terminology needs correcting.

 

[GokAy]

Good one Startup repair should have done this for you. I wonder now, did you run startup repair 3 times when you first set system active?

Also, out of curiosity, why a pagefile partition?

 

[Alloy25]

Good one Startup repair should have done this for you. I wonder now, did you run startup repair 3 times when you first set system active?

That's what I thought! That's the way I read it. Then I found a thread about using BCDEdit to repair the issue. Still wasn't able to access the System partition because there was no drive letter.

I tried the 3 x startup repair a minimum of 6 times (I kept notes) after making sure the partition was active through diskpart and MiniTool Partition Wizard. Like you suggested, I also tried 2 times - deleting the System Reserved partition, marking Windows partition as active and ran 3 x Startup repair. The error message changed to 0xc000000f after that, but still the same issue. Even installed Windows 7 on another drive and cloned the system partition to it.

Around the time I did my last backup, the computer took a very long time to boot up. Probably sat there 5 minutes with no disk activity when the desktop appeared. The drive was probably failing then and I figured my Windows 7 partition backup was corrupt.

I've probably cloned the original backup 10 times so I could experiment without destroying everything.

I check the EULA on the W7 disk and it had SP1 installed.

Also, out of curiosity, why a pagefile partition?

I'm working off a secondary hard drive right now. I put the primary hard drives page file on the secondary hard drive. Left just enough space for a memory dump. 300 mb. Probably a throwback to XP days. I set this up over 4 years ago when I installed W7. Back then, every article I read on the subject had a different suggestion for the page file size.

What's your opinion of this setup? I have 4gb of ram.

 

[GokAy]

I saved this page for future reference. One more method doesn't hurt

With respect to pagefile, I would say; move it to C and let Windows manage it (delete this partition and add to C with Partition Wizard free). If you had another drive, performance would have been improved if you had it on the secondary. Or perhaps some on both drives.

 

[Alloy25]

This will be my setup:

Primary:
System Reserved
Windows

Secondary:
System Reserved
Pagefile
Windows.

I ran across a HotFix where you can eliminate the pagefile on the primary hard drive and still create a Memory Dump:
https://support.microsoft.com/en-us/kb/2716542

I set it to 300mb on the System partition previously and 2 times the RAM size on the secondary drive. Never found a consensus on the correct size for W7.

Another thing I noticed, the Restore Points were turned off for the backup drive and it had them turned on for the old drive (marked as missing under Protection Settings).