Event id 1003 - Serious error occurred

Status
Not open for further replies.

Jslayton

Posts: 6   +0
Let me start by giving a little history. My girlfriend's computer was built a few weeks ago and worked fine during that time. A few days ago it started randomly rebooting and reporting the event id 1003 in the event log and coming up with "Windows recovered from a serious error" every time the machine successfully booted up. I troubleshot this problem extensively and was able to isolate a faulty DIMM using Memtest.

After removing the module, the event id 1003 persists. It referenced the attached minidump file.

Any insight on this problem would be appreciated :)
 

Attachments

  • minidump.zip
    12.3 KB · Views: 104
Welcome to Techspot!
Just a suggestion . post files as a .txt .......
>zip files can carry anything ,I don't doubt you are cool ,but then again why should I take a chance.
 
Jslayton said:
Let me start by giving a little history. My girlfriend's computer was built a few weeks ago and worked fine during that time. A few days ago it started randomly rebooting and reporting the event id 1003 in the event log and coming up with "Windows recovered from a serious error" every time the machine successfully booted up. I troubleshot this problem extensively and was able to isolate a faulty DIMM using Memtest.

After removing the module, the event id 1003 persists. It referenced the attached minidump file.

Any insight on this problem would be appreciated :)
Jslayton,

Your minidump is inaccessible by windbg. It is a symptom of server hardware error at your girl's computer's. Usually it is a RAM problem. Attach more dumps here if you want to confirm RAM is the culprit.

cpc2004
 
Is it normal for this type of error to persist after the bad RAM has been removed? I tested the remaining module of the two with memtest and it runs great, and the machine has run good since then, but the event id 1003 and the serious error keep coming up every reboot.

And if you think it would help, I'll gladly post more minidumps.

Thanks in advance.
 
It is abnormal to have event id 1003 if your XP does not crash. Redefine the paging space may resolve XP keep generating system event 1003.
 
Oh that makes sense, the pagefile is probably set to something appropriate to 1GB of RAM, and the system is now down to 512 MB of RAM.

I'll try that! Thanks :)
 
I resized my Pagefile to the Windows recommended setting of 768-1536 and the error persists.

Attached is the most recent minidump file.
 

Attachments

  • mini061205-01.zip
    24.3 KB · Views: 19
Applied service pack, changed the page file size one last time, and the error is gone. Great tips! Thanks again.
 
Having the same problem...

Hi! My PC restarts randomly. Particularly during gameplay. My specs are:
CPU: Athlon 64 3200+
Motherboard: ASUS A8N-SLI Premium
Ram Speed, size and #sticks: 2 sticks of 1GB DDR400
GPU: nVidia GeForce 6600
PSU: 400W (make: ALLIED model: AL-C400ATX)
OS: WIN XP PRO


Here are the last 2 errors in the Event Viewer:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/29/2006
Time: 11:36:53 AM
User: N/A
Computer: SAKURA
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bfae9dfb, parameter3 ba0279d0, 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 61 65 39 64 66 62 bfae9dfb
0040: 2c 20 62 61 30 32 37 39 , ba0279
0048: 64 30 2c 20 30 30 30 30 d0, 0000
0050: 30 30 30 30 0000

AND

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/29/2006
Time: 11:36:11 AM
User: N/A
Computer: SAKURA
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bfad5cbf, parameter3 ad1af9ec, 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 61 64 35 63 62 66 bfad5cbf
0040: 2c 20 61 64 31 61 66 39 , ad1af9
0048: 65 63 2c 20 30 30 30 30 ec, 0000
0050: 30 30 30 30 0000

Don't know how to attach the minidump files :(

Any help is GREATLY appreciated.
 
Status
Not open for further replies.
Back