Problems loading WinPE using WIMBOOT

[Vladimir]

I try loading custom [with drv + add pack] WinPE30 (Win7) and WinPE51(Win8.1) using WIMBOOT.
boot.wim (PE30) - 111 mb original
boot.wim (PE30) - 176 mb custom
boot.wim (PE51) - 264 mb custom
Depending on the hardware platforms the obtain different reslts:

Chipset H77, RAM Size-4Gb
Loading original WinPE30 - OK
Loading custom WinPE30 - ERROR bootmgr.exe: STATUS: 0xc000000D An Unexpected error has occurred
Loading custom WinPE51 - OK

Chipset H77, RAM Size-2Gb
Loading original WinPE30 -OK
Loading custom WinPE30 -OK
Loading custom WinPE51 -OK

Chipset H81, RAM Size -4Gb
Loading original WinPE30 -OK
Loading custom WinPE30- ERROR bootmgr.exe STATUS: 0xc000000D An Unexpected error has occurred
Loading custom WinPE51 - hang on the starting Windows logo.

By the above configurations loading WinPE 30\51 is OK using command -chain.
part of my menu:

*************************
#Chain Boot
:PE3_Chain
set DIR BootingOS\WinPe30\x86
chain pxeboot.n12 # Boot loader WinPE30

# Loading from WimBoot
:PE3_Wimboot
set DIR BootingOS\WinPe30\x86
cpuid --ext 29 && set arch amd64 || set arch x86 kernel wimboot
initrd /BootingOS/WinPe30/x86/bootmgr.exe bootmgr.exe
initrd ${DIR}/boot/bcd BCD
initrd ${DIR}/boot/boot.sdi boot.sdi
initrd ${DIR}/sources/boot.wim boot.wim
boot

:PE5
set DIR BootingOS\WinPe51\x86
kernel wimboot
initrd /BootingOS/WinPe51/x86/bootmgr.exe bootmgr.exe
initrd ${DIR}/boot/bcd BCD
initrd ${DIR}/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd ${DIR}/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd ${DIR}/boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd ${DIR}/boot/fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd ${DIR}/boot/boot.sdi boot.sdi
initrd ${DIR}/sources/boot.wim boot.wim
boot

*************************
What is the problem ?

P.S.
iPXE -last build
Wimboot ver: - try 1.04 \1.05 \ 2.00 \ 2.23

[mcb30]

(2014-09-09 12:45)Vladimir Wrote:  What is the problem ?

No idea, sorry. If it works with the standard .wim images, then the problem is probably somewhere in your customisation. You could try making minimal changes to the standard .wim file, to find out which change causes the problem.

Michael