Low temprature test got a C0000021a error, some one can help?

[Tony Guan]

Hi there,
I built a xpe image, it runs fine in normal conditions, but when our test
engineers put the target device in the low temprature-say, around 0¡æ(0
degree Celsius), the device refuses to boot, instead, it shows blue screen
with:

C000021a{Fatal System Error}
The Windows Logon Process System process terminated unexpectedly with a
status of 0x00000402(0x00000000 0x00000000).
the system has been shut down.

Can someone show me some clue?

Thanks & BRGs
Tony Guan

 

[Slobodan Brcin \(eMVP\)]

Hi Tony,

I guess that Microsoft OS-es does not handle very well cold temperatures,
perhaps using some Russian OS would help Perhapt XPe was trying to say
COOOOLD# but it was limited by hex numbers only

Seriously don't you think that this is hardware problem of some sort please
tell us following so that someone might give you some additional infos.
What MB do you use?
What boot medium?
What additional hardware on board?
What processor?
What memory?
What casing do you use?

What each manufacturer from above guarantee for their product operational
temperatures.

Regards,
Slobodan

 

[KM]

Tony,

For the MB you use on target you should read documentation. Usually manufacturers state about their MB operational modes and
temperatures it has been tested with and guaranteed to work under.

 

[Matt Kellner \(MS\)]

Hi Tony. This sounds like a hardware problem - your computer may have a
defect somewhere in the motherboard, an expansion device, memory slot/chip,
the CPU, etc., that experiences thermal stress in cold environments. My
suggestion would be to first check and make sure that everything is properly
seated in the system - pull out any expansion devices (such as a video card,
memory, etc) and put them back in, making sure it's fully and securely
seated in its slot. Then try your test again. If it still fails, I'd
suggest trying another equivalent machine with the same runtime.

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================

 

[Tony Guan]

Hi Matt,KM,Slobodan,

Thank you for your prompt answer! Please see mine below.

What MB do you use?
--- SouthBridge ALi M1535+
What boot medium?
--- 1.8' Hard Disk OR 1' Micro Drive (both IDE interface)
What additional hardware on board?
--- 802.11g miniUSB/TFT-LCD 8.4¡±, 800x600 color TFT LVDSWith Touch screen/
What processor?
--- CPU:Crusoe TM5900 1Ghz
What memory?
--- DDR 128M SO-DIMM
What casing do you use?
--- It's still in develop mode, so I think it will be tested naked.

What each manufacturer from above guarantee for their product operational
temperatures.
For the MB you use on target you should read documentation. Usually
manufacturers state about their MB operational modes and
temperatures it has been tested with and guaranteed to work under.

----We installed XP Pro too, and it works under the same temprature
condition.

This sounds like a hardware problem
-----
Our colleagues also doubt it's hardware fault, but we are not sure about
that.
Can somebody help to tell me what the error code means?
I tried to explain it through Windebug, but failed.

Thanks & RGRs
Tony Guan

 

[Slobodan Brcin \(eMVP\)]

Tony,

This error is the nasty one.
http://groups-beta.google.com/group...t.public.windowsxp.embedded&q=C000021a&qt_g=1

But suberror code is even stranger and I have not seen it. Does it change or
it is always the same? Check following links although I do not think that
you will find true meaning for this subcode.
http://groups-beta.google.com/groups?q=STOP+0x00000402

Even I remember this error but with different subcode and probably different
cause:
http://groups-beta.google.com/group...e50251c190b/eea7439136a1ddfe#eea7439136a1ddfe

At that time I fought 5-6 simultaneous errors of different kind all hardware
software related. So there was many changes and I never figured completely
what caused this error. Either hardware that I replaced, but I would not
think so.

Most probably cause that I figured was that I have influenced too much on
driver load order and system initialization procedure on very low driver
level to cause some higher interface functions not to work properly at the
required time.
Later system services that relied on these interfaces were unable to work
and reported this error as consequence.

In your case it might be that temperature and absence of other drivers
present in XPP were just enough to cross some tight time constant and change
initialization order of drivers. Which lead later to error.

This is not even enough info, but this is all that I can offer you on this
strange bug.
Matt might be more successful in obtaining info about this error subcode
that bug you.

Regards,
Slobodan

 

[krigbc]

HI, I just got the same stop error code, but it was due to somethin
different. I was using norton partition magic, and I moved, resized an
merged multiple partitions on my system. It rebooted just fine, an
rebooted again just fine after creating a new partition, which I als
did. ( I merged N: into M:, and then created another N:, which is wher
I'm thinking the issue lies. After a couple reboots, I ran anothe
program that comes with partitioin magic to make sure there wes nothin
referring to drive N:, (forgetting I created another drive N, an
that's when the bluescreen started.
I am using win2000 on a compaq presario with intel celeron, 256 ram
and 2 HDD's; one 80gig, one 120gig.

I'm now trying to find a fix for it, if anyone can help let me know
and I'll post anything I find out


-
krigb

 

[Tony Guan]

Dear all,
I think we've got to somewhere that near to the real reason.
Only yesterday did I know that the target has a thermal sensor. And if fix
the reported temprature of the sensor, then the blue screen will not occure.
But I am not quite sure about this is the root cause(though I believe it).
Because XPP will not have such problem.
I tried to disable the system device "ACPI Thermal Zone" for further test,
but when I opened "Device Manager", I find there is no 'disable' option for
the component. And if I uninstall it, system will automatically find and
reinstall it after reboot.
So I am asking for a method to make certain.

How can I disable/uninstall the system device "ACPI Thermal Zone"?
Or can someone help me with another idea that will make the final conclusion
out?

Many thanks!

--
BRGs
Tony Guan

First International Computer ShangHai Software Lab.
Add: Garden Business Center,889 JuLu Rd,ShangHai,P.R.C.
Tel: +86-21-62495726 Ext: 223
Fax: +86-21-62495712

 

[KM]

krigbc,

Is this XPe Embedded related?
If not, please post your questions to microsoft.public.windowsxp.general newsgroup.

IIRC, there was a KB article on MS Support website that was referring to the bugcheck code that is discussed is this thread. The
reason for BSOD was something about playing with drive letters.
You may want to do a quick search there.

 

[KM]

Tony,

Maybe just removing the "ACPI Thermal Zone" component from your image configuration would help?

 

[KM]

Tony,

Please disregard my previous reply. the problem is that it is a system (NO_DRV) service and removing the component will unlikely
help since PnP would install the component from machine.inf anyway.
I don't think even devcon would help you there.

How about tweaking the machine.inf? E.g., removing the following line from there:
%ACPI\ThermalZone.DeviceDesc% = NO_DRV, ACPI\ThermalZone ; ACPI Thermal Zone

Btw, you can try building an image for the target based on Standard PC HAL. Then you would see if it is the ACPI HAL standard system
services are the cause of the blue screen.

 

[Tony Guan]

KM,

Thanks, your suggestion is exactly what I am thinking.

I will try!
--
BRGs
Tony Guan

First International Computer ShangHai Software Lab.
Add: Garden Business Center,889 JuLu Rd,ShangHai,P.R.C.
Tel: +86-21-62495726 Ext: 223
Fax: +86-21-62495712

 

[Slobodan Brcin \(eMVP\)]

Tony,

All MB have one or more termal sensors on them. They are read trough I2C SMB
bus.

If you don't have component "Microsoft System Management Bus Host
Controller" or some third party alternative chanches are most likely that OS
and programs will never be able to read termal sensor states.

Also I do not know any MS driver that read termal sensors on board since
there is no standard and each MB manufacturer can include what ever sensors
they want and like on I2C bus.
Some manufacturers like Intel will suply you with their drivers and programs
for reading temp sensors.

Buf if you do not have third party drivers then this should not be a cause
for your error :-(

Regards,
Slobodan