System crash - Event ID 1003

[rkwilcox@gmail.com]

I recently formatted and upgraded to XP x64... ever since then, I am
getting multiple random crashes during the day. This is not a BSOD,
the machine just restarts. Here is the event viewer stack trace, any
help would be greatly appreciated.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 4/12/2008
Time: 11:29:46 AM
User: N/A
Computer: FOO
Description:
Error code 0000000000000050, parameter1 fffffa802d125000, parameter2
0000000000000000, parameter3 fffff97fff17f664, parameter4
0000000000000000.

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 30 30 30 30 30 30 30 0000000
0020: 30 30 30 30 30 30 30 35 00000005
0028: 30 20 20 50 61 72 61 6d 0 Param
0030: 65 74 65 72 73 20 66 66 eters ff
0038: 66 66 66 61 38 30 32 64 fffa802d
0040: 31 32 35 30 30 30 2c 20 125000,
0048: 30 30 30 30 30 30 30 30 00000000
0050: 30 30 30 30 30 30 30 30 00000000
0058: 2c 20 66 66 66 66 66 39 , fffff9
0060: 37 66 66 66 31 37 66 36 7fff17f6
0068: 36 34 2c 20 30 30 30 30 64, 0000
0070: 30 30 30 30 30 30 30 30 00000000
0078: 30 30 30 30 0000

 

[Carlos]

Hi,
I would start by running an intensive memory check program like Memtest86
http://www.memtest86.com/
downloadable here:
http://www.memtest86.com/download.html
or its sibling
Memtest86+
http://www.memtest.org/
downloadable here:
http://www.memtest.org/#downiso

XP x64 tends to be picky when dealing with memory.

Carlos

"rkwilcox@gmail.com" wrote:

> I recently formatted and upgraded to XP x64... ever since then, I am
> getting multiple random crashes during the day. This is not a BSOD,
> the machine just restarts. Here is the event viewer stack trace, any
> help would be greatly appreciated.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 4/12/2008
> Time: 11:29:46 AM
> User: N/A
> Computer: FOO
> Description:
> Error code 0000000000000050, parameter1 fffffa802d125000, parameter2
> 0000000000000000, parameter3 fffff97fff17f664, parameter4
> 0000000000000000.
>
> 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 30 30 30 30 30 30 30 0000000
> 0020: 30 30 30 30 30 30 30 35 00000005
> 0028: 30 20 20 50 61 72 61 6d 0 Param
> 0030: 65 74 65 72 73 20 66 66 eters ff
> 0038: 66 66 66 61 38 30 32 64 fffa802d
> 0040: 31 32 35 30 30 30 2c 20 125000,
> 0048: 30 30 30 30 30 30 30 30 00000000
> 0050: 30 30 30 30 30 30 30 30 00000000
> 0058: 2c 20 66 66 66 66 66 39 , fffff9
> 0060: 37 66 66 66 31 37 66 36 7fff17f6
> 0068: 36 34 2c 20 30 30 30 30 64, 0000
> 0070: 30 30 30 30 30 30 30 30 00000000
> 0078: 30 30 30 30 0000
>

 

[Tony Sperling]

Here's what the KB has to say about it:

http://support.microsoft.com/kb/280364


Tony. . .


<rkwilcox@gmail.com> wrote in message
news:be9ff96c-9d03-41b6-b70b-18bddebe94d4@e67g2000hsa.googlegroups.com...
> I recently formatted and upgraded to XP x64... ever since then, I am
> getting multiple random crashes during the day. This is not a BSOD,
> the machine just restarts. Here is the event viewer stack trace, any
> help would be greatly appreciated.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 4/12/2008
> Time: 11:29:46 AM
> User: N/A
> Computer: FOO
> Description:
> Error code 0000000000000050, parameter1 fffffa802d125000, parameter2
> 0000000000000000, parameter3 fffff97fff17f664, parameter4
> 0000000000000000.
>
> 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 30 30 30 30 30 30 30 0000000
> 0020: 30 30 30 30 30 30 30 35 00000005
> 0028: 30 20 20 50 61 72 61 6d 0 Param
> 0030: 65 74 65 72 73 20 66 66 eters ff
> 0038: 66 66 66 61 38 30 32 64 fffa802d
> 0040: 31 32 35 30 30 30 2c 20 125000,
> 0048: 30 30 30 30 30 30 30 30 00000000
> 0050: 30 30 30 30 30 30 30 30 00000000
> 0058: 2c 20 66 66 66 66 66 39 , fffff9
> 0060: 37 66 66 66 31 37 66 36 7fff17f6
> 0068: 36 34 2c 20 30 30 30 30 64, 0000
> 0070: 30 30 30 30 30 30 30 30 00000000
> 0078: 30 30 30 30 0000

 

[rkwilcox]

On Apr 12, 1:22 pm, Carlos <Car...@discussions.microsoft.com> wrote:
> Hi,
> I would start by running an intensive memory check program like Memtest86http://www.memtest86.com/
> downloadable here:http://www.memtest86.com/download.html
> or its sibling
> Memtest86+http://www.memtest.org/
> downloadable here:http://www.memtest.org/#downiso
>
> XP x64 tends to be picky when dealing with memory.
>
> Carlos
>

Sorry... should have provided some additional information. I ran
Memtest86 for over 6 hours and there were no problems found. I was too
going down the memory path, but recently have been finding random
posts having to do with driver issues. I went and made sure I had
current of everything, unfortunately the same problem exists.