BSOD While Running - What is it saying?

[Tom Salicos]

My systems have had a couple of instances where they get the BSOD and the
message "Windows has encountered a hardware error and is shutting down to
prevent damage..." or pretty close to that.

How can I find what kinds of hardware errors would trigger that?

Do I have any options for a less drastic failure mode?

These systems run on an Advantech 5820 SBC and DFI motherboard systems.
Problems have occured on either platform, maybe two times out of 200 or more
systems.

System is MinLogon with TCP/IP, MFC, basic computer and a couple of NICS.

Thanks,
Tom Salicos

 

[dferencz]

BSODs are caused by faults in the kernel-level code. You can get more
information about the error based on the first number (usually appears
as STOP: oxNNNNNNNN, ...) Search the MS KB for the first number, or
look here for a more comprehensive list:
http://www.updatexp.com/stop-messages.html

Unfortunately there is no way to prevent a shutdown, since these are
generally unrecoverable errors. It's best to figure out what the cause
is. In XPe, it's most likely a configuration issue (i.e., something
missing in the config, wrong driver, etc.) The module name, specified
in the blue screen, should give a clue as to what component is the
problem.

-- Don

 

[richard]

I have had one bad memory chip from Advantech which have done the same exact
thing.
I also had one board which had a problem with the superIO chipset that would
fail randomly.

When you have a few hundred systems running with the same exact software and
hardware encountering no problems, and you have a small number doing this,
it's generally something like what I mentioned. Hardware issue, corrupt
flash drive....

Good Luck,
Richard