Error code 1003
I have a PC that has occasionally restarted by itself. it now seems to be doing it more often. It is running Windows XP and it comes up with the following error in the system log:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 30/10/2007
Time: 11:30:31 AM
User: N/A
Computer: ADMIN2
Description:
Error code 1000008e, parameter1 c0000005, parameter2 418d5000, parameter3 f2740a70, 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: 34 31 38 64 35 30 30 30 418d5000
0040: 2c 20 66 32 37 34 30 61 , f2740a
0048: 37 30 2c 20 30 30 30 30 70, 0000
0050: 30 30 30 30 0000
Could someone please point me in the right direction of where to fix this problem?
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 30/10/2007
Time: 11:30:31 AM
User: N/A
Computer: ADMIN2
Description:
Error code 1000008e, parameter1 c0000005, parameter2 418d5000, parameter3 f2740a70, 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: 34 31 38 64 35 30 30 30 418d5000
0040: 2c 20 66 32 37 34 30 61 , f2740a
0048: 37 30 2c 20 30 30 30 30 70, 0000
0050: 30 30 30 30 0000
Could someone please point me in the right direction of where to fix this problem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran a memory test over night on the PC - it did 18 tests and only one failed. Is this one failure enough to say that the memory stick is faulty?
I will locate the minidumps and send them to the link above.
I will locate the minidumps and send them to the link above.
"Is this one failure enough to say that the memory stick is faulty?"
Yes, I would say so. You might want to remove the memory, clean the contacts with a pencil eraser, reseat firmly, and try the tests again. With the power off, of course, and avoiding any chance of static.
Yes, I would say so. You might want to remove the memory, clean the contacts with a pencil eraser, reseat firmly, and try the tests again. With the power off, of course, and avoiding any chance of static.
agreed, one bar will screw you over
Oh ya - 1 in 18 failure rate is definitely no good. I would never run a production box with those odds.
The Minidump files should be in folder c:\windows\minidump with names like Mini070604-01.dmp (e.g.) and size of each should be about 80 KB approx.