Bluescreen

  • Thread starter Thread starter ismail
  • Start date Start date
I

ismail

Hello,

we have some Problems with Bluescreens on our Devices with Windows XP
Embedded SP2. Enclosed you will find the Dumpfile of the Bluescreen.

Start of Dumpfile
###################################################################

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer EmbeddedNT SingleUserTS
Built by: 2600.xpsp.050301-1521
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Jan 19 12:59:40.704 2007 (GMT+1)
System Uptime: 0 days 6:21:44.274
Loading Kernel Symbols
...........................................................................................
Loading unloaded module list
.............
Loading User Symbols
****************************************************************
*
*
* Bugcheck Analysis *
*
*
****************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {5402f7a0, ff, 0, 804df0a0}

Probably caused by : ntoskrnl.exe ( nt!Kei386EoiHelper+44 )

Followup: MachineOwner
---------

kd> !analyze -v
****************************************************************
*
*
* Bugcheck Analysis *
*
*
****************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid)
address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 5402f7a0, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804df0a0, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 5402f7a0

CURRENT_IRQL: ff

FAULTING_IP:
nt!Kei386EoiHelper+44
804df0a0 8b54244c mov edx,[esp+0x4c]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 806f372a to 804df0a0

STACK_TEXT:
80550160 806f372a badb0d00 00000000 01c73bc1 nt!Kei386EoiHelper+0x44
805501d0 804dbb37 00000000 0000000e 00000000 hal!HalProcessorIdle+0x2
805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


FOLLOWUP_IP:
nt!Kei386EoiHelper+44
804df0a0 8b54244c mov edx,[esp+0x4c]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!Kei386EoiHelper+44

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42251106

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_nt!Kei386EoiHelper+44

BUCKET_ID: 0xA_nt!Kei386EoiHelper+44

Followup: MachineOwner
---------

###################################################################
End of Dumpfile


If someone have any ideas of this bluescreen please post it. The
Bluescreens arise on the idle time.

MFG

T. Ismail
 
Ismail,

I am going to shoot in the dark here (no info you posted about your platform) but please check if the right processor component in
included in your image. And, in case you are using AMD processors, remove the Intel Processor component.

--
=========
Regards,
KM

Hello,

we have some Problems with Bluescreens on our Devices with Windows XP
Embedded SP2. Enclosed you will find the Dumpfile of the Bluescreen.

Start of Dumpfile
###################################################################

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer EmbeddedNT SingleUserTS
Built by: 2600.xpsp.050301-1521
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Jan 19 12:59:40.704 2007 (GMT+1)
System Uptime: 0 days 6:21:44.274
Loading Kernel Symbols
..........................................................................................
Loading unloaded module list
............
Loading User Symbols
****************************************************************
*
*
* Bugcheck Analysis *
*
*
****************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {5402f7a0, ff, 0, 804df0a0}

Probably caused by : ntoskrnl.exe ( nt!Kei386EoiHelper+44 )

Followup: MachineOwner
---------

kd> !analyze -v
****************************************************************
*
*
* Bugcheck Analysis *
*
*
****************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid)
address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 5402f7a0, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804df0a0, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 5402f7a0

CURRENT_IRQL: ff

FAULTING_IP:
nt!Kei386EoiHelper+44
804df0a0 8b54244c mov edx,[esp+0x4c]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 806f372a to 804df0a0

STACK_TEXT:
80550160 806f372a badb0d00 00000000 01c73bc1 nt!Kei386EoiHelper+0x44
805501d0 804dbb37 00000000 0000000e 00000000 hal!HalProcessorIdle+0x2
805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


FOLLOWUP_IP:
nt!Kei386EoiHelper+44
804df0a0 8b54244c mov edx,[esp+0x4c]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!Kei386EoiHelper+44

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42251106

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_nt!Kei386EoiHelper+44

BUCKET_ID: 0xA_nt!Kei386EoiHelper+44

Followup: MachineOwner
---------

###################################################################
End of Dumpfile


If someone have any ideas of this bluescreen please post it. The
Bluescreens arise on the idle time.

MFG

T. Ismail
Click to expand...
 
Hello,

here is my Hardware configuration:

3,5" SBC Board with PC/104+ Slot:
******************************************
ADVANTECH PCM-9387F-M0A1
with Celeron M 600 CPU onBoard
tested with BIOS-Version: v1.12 and v1.15

Memory:
***********
CSX or MDT DDR SO-DIMM, 256MB and 512MB, PC333

Compact Flash Disk Drive:
********************************
Silicon Systems SiliconDrive 2GB, SSD-C02G-3500
with DMA on, Auto Sense and SiSMart

PC/104+ Board:
*********************
Hilscher Profibus CIF 104P-DPS\S

4-port USB-Hub 2.0 connected on the internal USB PIN connector:
******************************************************************************
eQuip USB 2.0 internal 4 port Hub 3.5" / 5.25"

USB 2.0 Camera für Image processing:
**********************************************
for example 1 x uEye

We have some systems with XP embedded Service Pack 2 (without any
Hotfixes or Patches) wich has
NO Bluescreens, and some Systems with SP2 and installed round about 60
Hotfixes from Windows XP Professional
and this Systems seems to be generate a Bluescreen when the System is
idle (for example after 6 hours, see Minidump).

The Software which is on the system is NeuroCheck 5.1 Prof. for image
processing.

The complete Hardware has no failures, testet with some software tools
like Memtest, BurnInTest and others.

We think that the problem is the installation of the Hotfixes from
Windows XP Professional (the hotfixes after SP2).

Has someone any experiences with the installation of the hotfixes from
Windows XP Professional on systems with
Win XP Embedded ??

Sincerly yours

T. Ismail
 
here is my Hardware configuration:

3,5" SBC Board with PC/104+ Slot:
******************************************
ADVANTECH PCM-9387F-M0A1
with Celeron M 600 CPU onBoard
tested with BIOS-Version: v1.12 and v1.15
Click to expand...

I think you should contact advantech regarding this problem. Some of
these boards may have a hardware failure, that can occour, if you are
using more than 256 MB RAM. If you buy these boards from distributors,
they may have not all been reworked yet. I suggest, to change the
board for testing. We had to fight with many of these boards, and some
strange failures.

Try to uninstall graphic drivers for testing. If your system will run
afterwards, then you got that failure.

Steffi
 
Back
Top