WinPE via USB STOP error

[Tripredacus]

Strangely enough, I've never tried to get WinPE to work on USB key. Currently I am without my dev environment (importantly a WDS) so to pass the time I was going to redo some stuff on my boot images. I am 0/2 right now and here is what's happening.

First, I made a new WinPE 3.0 x64 boot image, but my PC is a Win7 x86 and using a 2GB USB key formatted NTFS... not sure if that matters.

The first attempt, there was an unmount error. When you boot a PC up with that, it would load the PE shell (no wallpaper with black background) and you could move the mouse cursor around, and after about 1 minute the system would reboot.

So I figured the unmount error was the problem so I rebuilt the boot image again. This time there was no unmounting error so I thought it was fine. When the system boots, it gives the following STOP error:

File: msrpc.sys

Status: 0xC0000098

FYI the system is now running a Memtest (it was recently moved to a new office, maybe it got damaged) and it was able to boot off a WinPE CD, so maybe I had made it wrong. I used the USB boot instructions found here:

Not alot of hits on the Google for that stop error, so posting here!

Update - I did a reload of the UFD by using the XCOPY command (instead of Copypasta) and The PE did actually boot. The command structure of this test key is:

- wpeinit

- wpeutil initializenetwork

- ping itself for 10 seconds

- launch HTA.

I receive this error If I try to launch MSHTA:

mshta.exe - Application Error

The instruction at 0x00000000770F1E00 referenced memory at 0x000007FF7503600C. The required data was not placed into memory because of an I/O error status of 0xC0000001.

BTW, system completed 30 passes of Memtest overnight.

Conclusion - It is my best guess that the computer I used to create the boot image is just not powerful enough to properly handle the mount/dismount and anything else I was running. I had gotten a boot image from another site and put that on the USB key and that worked perfectly. So the actual reason why it wasn't able to boot properly may never be solved, but at least now I can do some (sort of) real work for a change.

Edited January 27, 2011 by Tripredacus