I have also been looking it up in the related Microsoft's site. Let’s read, from what I see, everything is clear there:
<A HREF="http://msdn.microsoft.com/library/en-us/ddtools/bccodes_4w6f.asp?frame=true" target="_new">http://msdn.microsoft.com/library/en-us/ddtools/bccodes_4w6f.asp?frame=true</A>
<font color=blue>"<b>Cause</b>
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a bug-ridden system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
<b>Resolving the Problem</b>
<i>Resolving a faulty hardware problem:</i> If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.
<i>Resolving a corrupted NTFS volume problem:</i> Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.
<b>Comments</b>
Typically, this address is in freed memory or is simply invalid.
This cannot be protected by <b>try - except</b>; it can only be protected by a probe. "</font color=blue>
I think that Microsoft's comment about SCSI we can extend to an IDE RAID controller and disk(s).
And there is a more simple explanation on one of possible causes of the problem:
<A HREF="http://www.computing.net/windows2000/wwwboard/forum/18848.html" target="_new">http://www.computing.net/windows2000/wwwboard/forum/18848.html</A>
<font color=green>” You could very well have a bad RAM module. It may also be that one of the modules are not seated properly...”</font color=green>