Boot\BCD Error

[Poonani]

File: \Boot\BCD

Status: 0xc000000e

Info: An error occurred while attempting to read the boot configuration data

I have a WinPE image that I use to capture and deploy from however when I try to boot to WinPE on a "HP DX2000MT" I get the error above.

I have seen on this forum that you can edit the BCD file using BCDedit.exe however I am not only unsure how do this, but what it is meant to achieve.

I know that the BCD file is in the boot folder of my ISO (later moved to USB) but I don't know why it does not load on these machines so I don't know what it is that I should be editing in\out.

If any one could clear this up I would be in your debt

[Tripredacus]

The stock model for this specific computer specs at 256MB RAM. You will need at least 512MB of RAM in order to make use of Win PE 2.0 or higher.

If this doesn't answer your problem, please provide the following:

1. How much RAM

2. How you are loading the PE, is it from a CD or PXE?

[Poonani]

The stock model for this specific computer specs at 256MB RAM. You will need at least 512MB of RAM in order to make use of Win PE 2.0 or higher.

If this doesn't answer your problem, please provide the following:

1. How much RAM

2. How you are loading the PE, is it from a CD or PXE?

Is it really that simple?

I will test this week.

Thanks for the quick reply too

[Poonani]

The stock model for this specific computer specs at 256MB RAM. You will need at least 512MB of RAM in order to make use of Win PE 2.0 or higher.

If this doesn't answer your problem, please provide the following:

1. How much RAM

2. How you are loading the PE, is it from a CD or PXE?

Nah still get this error.. even with 512mb in it.

Anyone else have anything I can try?

[Tripredacus]

You need to specify how you load your Win PE next.

[Poonani]

I am booting from USB but it does not work from CD or PXE eaither

To create it i am doing the following

On the usb and from windows vista

Diskpart

select disk 1

clean

create partition primary

select partition 1

active

format fs=fat32

assign

exit

__________________________________

At WinPE cmd prompt type the following

copype x86 c:\X86PE

oscdimg -n -h -betfsboot.com iso winpe.iso

imagex /mountrw winpe.wim 1 mount

Copy "C:\Program Files\Windows AIK\Tools\x86\imagex.exe" "C:\X86PE\mount\Windows\System32"

peimg /install=WinPE-Scripting-Package C:\X86PE\mount\Windows

imagex /unmount C:\X86PE\mount /commit

xcopy C:\X86PE\winpe.wim C:\X86PE\iso\sources\boot.wim /y

oscdimg -n -h -bC:\X86PE\etfsboot.com C:\X86PE\iso C:\X86PE\winpe.iso

I then move the files from ISO to my thumbdrive, this works accross all other machines it's just these DX200MT that don't work

Edited April 3, 2009 by Poonani

[Tripredacus]

I don't think it has anything to do with your method of creating the media, as you mention it does work on other systems.

This STOP error you are getting means that the instance can no longer access the image. I've seen this happen in the following examples:

- not enough memory to store the ramdisk

- overworked network or server (PXE only)

- certain motherboards do not work

Take a look at these two threads:

http://www.msfn.org/board/index.php?showto...st&p=749648

http://www.msfn.org/board/error-0xc000000e...90120&st=25

So let's talk about how this specific motherboard works. If at any point, the firmware re-enumerates any of the devices, this could definately happen. For example, let's say that at a certain point of the boot process it re-enumerates the bus that the USB device resides on. This would reset all devices on that bus. If the computer was in process of booting off of something connected to that bus, those devices (as far as the booting OS would be concerned) would have disappeared. This is the case in those times if PnP is not enabled (such as the early boot process of the PE) and while the device is (usually instantly) ready on the system, the PE will not see it until PnP is enabled. Since it cannot see the device, it can't finish loading. This is my guess about the situation since I've also experienced a couple odd-ball boards that can't boot.

This same premise is used for certain (or sometimes bad) RAM, or an overloaded PXE server. At some point, the PE at boot time, cannot access all of the boot information as it needs to. It doesn't necessarily mean that the device has been reset. I can easily replicate this issue if I attempt to boot 9 clients via PXE to my 2003 WDS. The maximum connection limit (found via testing) for this server is 4. After this, the additional clients either pause or create BCD errors. Its because the boot process tries to load the next file into memory, or execute it, but if the server is overloaded, It cannot provide those extra computers their next peice of data. In some cases, the PE will wait until it can get it, but other cases it will immediately error out.

As far as where to go, I would say try making a flat-file PE to see if you can get that to load. The flat-file method is one that does not create a ramdisk. So this means you will not be able to use the scratch space.