4 replies to this topic

[mastermindpro]

I have a Win7PE_SE image that I've built that occasionally bluescreens with the error in the title. On a full Windows install, that usually points to Windows not being able to access the hard drive, but that's not the case with my PXE-booted image, as there is no hard drive attached to the machine. I've run Memtestx86 for over 24 hours on an affected hardware platform, and it passes all tests with 0 errors, so I don't suspect memory.

Any other ideas on what I could look for that might throw this sort of error?

[panreyes]

First at all, info about 0xf4.
http://msdn.microsof...2(v=vs.85).aspx
It's not the same as an 0x7B, 0x24, and etc... which is directly related to not being able to read the volume.

I don't know about Win7PE_SE, but WAIK's WinPE 3.1 sometimes won't boot on some machines.
It may be because some damaged hardware, but I've also seen a few cases where the motherboard not supporting Vista/7 correctly.

I would suggest you to try a BIOS update.

[mastermindpro]

I'm running the latest BIOS on all of my hardware platforms. I actually have ~30 identical hardware platforms, of which only about 5 or so exhibit this error consistently. I'll pay more attention to the additional error codes to see if I can track down which process crashed.

[mastermindpro]

I have the entire set of error codes now, but haven't found how to decipher the 0x codes other than the 0xF4. The full Stop line is:

*** STOP: 0x000000F4 (0x00000000000003, 0xFFFFFA801992F360, 0xFFFFFA801992F910, 0xFFFFF80037394DB0)

So, a process crashed (first code), but I can't tell which one, which other process caused it, or what the explanation was from the last three 0x's. Google shows 0 hits on all three of the last codes. Any ideas?

[panreyes]

Try using a clean WinPE 3.1.
If it does not fail, it will be something caused by your software compilation.