Hello all,

I have a Windows XP Home machine that is having some weird issues. Upon starting from a cold boot, I receive two "Windows has recovered from a serious error" messages. If I then restart the machine, I have no issues. Pasted below are the two event viewer messages:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/29/2007
Time: 8:28:01 PM
User: N/A
Computer: DANIELLE-P
Description:
Error code 10000050, parameter1 a8c3f2db, parameter2 00000000, parameter3 a8c3f2db, 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 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 61 38 eters a8
0030: 63 33 66 32 64 62 2c 20 c3f2db,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 61 38 63 33 66 32 , a8c3f2
0048: 64 62 2c 20 30 30 30 30 db, 0000
0050: 30 30 30 30 0000

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/29/2007
Time: 8:28:16 PM
User: N/A
Computer: DANIELLE-P
Description:
Error code 100000d1, parameter1 f9e3d9a8, parameter2 0000000d, parameter3 00000000, parameter4 f9e3d9a8.
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 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 66 39 eters f9
0030: 65 33 64 39 61 38 2c 20 e3d9a8,
0038: 30 30 30 30 30 30 30 64 0000000d
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 66 39 65 33 00, f9e3
0050: 64 39 61 38 d9a8


I am also attaching the minidump files. Any help would be greatly appreciated!

Attached Files

Mini032907-01.zip (60.2 KB, 4 views)

This is a hardware/driver issue...

IP MISALIGNED-FTDISK.SYS (3-TIMES)
CPU CALL ERROR
PCIIDEX.SYS

I would start by checking memory. If you have 2 sticks installed, try swapping positions, then running with one at a time. Good luck

Thanks for your quick response. I planned to tackle RAM first, but I didn't want to be grasping at loose straws. I will start there.

After testing the memory look for a motherboard bios update or maybe even updated motherboard drivers, like a network interface adapter driver