BSOD with system error 1003 in Windows XP SP1

Status
Not open for further replies.

Nazca

Posts: 9   +0
Hi all,
please could someone help me identifying the origin of the BSOD in my PC?

The computer is a DELL Latitude D600 with Windows XP professional SP1.
And during the the last month I am getting a Blue Screen with System Error 1003 every some days.

Looking into the eventviewer I see the following:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/10/2006
Time: 5:00:25 PM
User: N/A
Computer: RODRIGUEZJC1
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf833d5c, parameter3 f1a34c94, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 38 33 33 64 35 63 bf833d5c
0040: 2c 20 66 31 61 33 34 63 , f1a34c
0048: 39 34 2c 20 30 30 30 30 94, 0000
0050: 30 30 30 30 0000

And I am also attaching the minidump files created with the BSOD.

Please could someone help trying to identify the source of the problem?

I ran a memory test, but all seems to be Ok in that part, not errors were found. And I have not added new hardware to the computer in the last months, so I suspect that the cause can be a driver or software.
Any help is welcomed.

Thanks in advance !!!

Nazca
 
1 minidump crashes at TEC2PS.DLL. I can`t find any info for this DLL file. It has a bugcheck of 8E.

3 minidumps crash with a bugcheck of 218.

0xC0000218: UNKNOWN_HARD_ERROR

A necessary Registry hive file couldn’t be loaded. The file may be corrupt or missing (requiring either an Emergency Repair Disk or a Windows reinstallation). The Registry files may have been corrupted because of hard disk corruption or some other hardware problem. A driver may have corrupted the Registry data while loading into memory, or the memory where the Registry is loading may have a parity error (turn off the external cache and check the physical RAM).

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

See HERE for more info about your stop errors. Particularly the 218 error.

Regards Howard :)
 
Thanks

Thanks Howard for your help,
I will continue investigating with that info.

Regards,
Nazca
 
Status
Not open for further replies.
Back