Hello

From what I have read the Win XP STOP message 0x00000050 relates to
either a memory or motherboard failure.

1. Is there anywhere a reliable index of what STOP messages mean? Such
as on Microsoft.com etc.

2. Has anyone had the experience of a graphics card causing this
error?

Yous Mark


--
mlewis

Update:

I installed win 98 on the defective machine concerned in place of xp.
It works fine. So its something specific to xp. But what?


--
mlewis

mlewis wrote:

>
> Update:
>
> I installed win 98 on the defective machine concerned in place of xp.
> It works fine. So its something specific to xp. But what?
>
>
It could still be bad RAM. XP is far fussier about the quality of RAM.
Here is the link you asked for earlier about where to look up Stop
Errors: http://www.aumha.org/win5/kbestop.htm

And I would definitely test your RAM. I like Memtest86+ from
www.memtest.org. Obviously, you have to get the program from a working
machine. You will either download the precompiled Windows binary to
make a bootable floppy or the .iso to make a bootable cd. If you want
to use the latter, you'll need to have third-party burning software on
the machine where you download the file - XP's built-in burning
capability won't do the job. In either case, boot with the media you
made. The test will run immediately. Let the test run for an hour or
two - unless errors are seen immediately. If you get any errors,
replace the RAM.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Thanks for the useful reference. The solution was the graphics card.
Strange since the card was old and simple and worked fine on 98. This
was the next logical choice since the memory worked on another pc. Mark


--
mlewis

mlewis wrote:

>
> Thanks for the useful reference. The solution was the graphics card.
> Strange since the card was old and simple and worked fine on 98. This
> was the next logical choice since the memory worked on another pc.
> Mark
>
>
Yes, XP (and other modern operating systems) has more stringent
requirements that hardware not be marginal or faulty. I'm glad you got
it sorted. Thanks for taking the time to let us know the solution.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Malke wrote:

> mlewis wrote:
>
>
>>Update:
>>
>>I installed win 98 on the defective machine concerned in place of xp.
>>It works fine. So its something specific to xp. But what?
>>
>>
>
> It could still be bad RAM. XP is far fussier about the quality of RAM.
> Here is the link you asked for earlier about where to look up Stop
> Errors: http://www.aumha.org/win5/kbestop.htm
>
> And I would definitely test your RAM. I like Memtest86+ from
> www.memtest.org. Obviously, you have to get the program from a working
> machine. You will either download the precompiled Windows binary to
> make a bootable floppy or the .iso to make a bootable cd. If you want
> to use the latter, you'll need to have third-party burning software on
> the machine where you download the file - XP's built-in burning
> capability won't do the job. In either case, boot with the media you
> made. The test will run immediately. Let the test run for an hour or
> two - unless errors are seen immediately. If you get any errors,
> replace the RAM.

.... and send the 'defective' RAM to me :-)

Seriously, memtest86 errors definitely point to a hardware problem, but
not necessarily to defective RAM - don't condemn the RAM unless it tests
bad in another system.

Just last week one of my XP systems froze, then hung repeatedly at
agp440.sys on restart. Memtest reported a gazillion errors, but the
problem turned out to be a Slot-1 processor that simply needed to be
pulled and reseated.

Sunny