BSOD and IRQL_NOT_LESS_OR_EQUAL

[Dwayne]

We've been performing a reboot test in our office with the intention of
trying to corrupt the Windows XP Embedded OS which is not using EWF.

The following PC/104 hardware was used:

PM-1033 VGA board
Tri-M TMZ104 with a M-Systems 384 DiskOnChip formatted using NTFS and
144 MB of RAM
PCM-3115B PCMCIA Adapter with an IDENTEC SOLUTIONS i-CARD III in the
top slot and a Cisco AIR-PCM352 wireless LAN card in the bottom slot
PCM-3660 Ethernet adapter

We wired up the system so that it would randomly cut power to the
TMZ104 board and thus the stack between 10 and 600 seconds.

After about 795 power downs we encountered a BSOD with the following
related messages.

First BSOD message
IRQL_NOT_LESS_OR EQUAL
STOP: 0x0000000A(0xBAD0B214,0x000000FF,0x00000000,0x804ECBC1)

First reboot after encountering the above message resulted in the same
stop message as above.

I removed the Cisco card suspecting this might be the culprit but got
the next BSOD message.

IRQL_NOT_LESS_OR EQUAL
STOP: 0x0000000A(0xBAD0B16C,0x000000FF,0x00000000,0x804ECBC1)

So I powered down and removed the i-CARD III and got the next BSOD
message

IRQL_NOT_LESS_OR EQUAL
STOP: 0x0000000A(0xBAD0B1A4,0x000000FF,0x00000000,0x804ECBC1)

Next power down I removed the Ethernet adapter board from the stack and
got the next BSOD message less the IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000007E(0xC0000005,0x8052259B,0xFC296C40,0xFC296940)

So then I placed back on the Ethernet board back onto the stack and
removed the VGA adapter board on and attempted to ping the PC with no
luck.

Put everything back on the stack and in their slots and got the
original BSOD message.

IRQL_NOT_LESS_OR EQUAL
STOP: 0x0000000A(0xBAD0B214,0x000000FF,0x00000000,0x804ECBC1)

I'm looking for suggestions on why this occurred and how it might be
possible to fix the problem. This test still didn't produce the
corruption that we are experiencing. I'll post this corruption in
another thread.

Thanks,

Dwayne

 

[Slobodan Brcin \(eMVP\)]

Hi Dwayne,

Just wondering what is the problem that you have. (You wanted to crash XPe and you have succeeded.)

Regards,
Slobodan

 

[Dwayne]

Slobodan,

LOL, true enough. I'm hoping that someone had a better explanation
for why this would occur other than "It's Windows what else would you
expect?" Typically this doesn't go over well with a customer.

Dwayne

 

[Dwayne]

Slobodan,

LOL, true enough. I was hoping that someone would have a better
explanation for why this would occur other than, "It's Windows what
else would you expect?" Typically that doen't go over well with a
customer who wants an explanation for why his system went down due to a
BSOD or corrupt file.

Dwayne

 

[Slobodan Brcin \(eMVP\)]

Hi Dwayne,

It is problem with interrupted writes to registry, and it is occurring. This is why EWF is made for XPe, sorry but I do not think
that you can avoid it without EWF :-(

Regards,
Slobodan