Multiple Computers Rebooting with Same Error Code

[Guest]

My company has about 30 workstations. For the past few months, I have found
a pesky little error that is causing random restarts on numerous machines
throughout the company. I have read many posts that say my error type is
related to hardware, but that is impossible as it is occuring on multiple
different hardware configurations. All computers are running XP Pro SP1.
Here is a copy of the error code:

Error code 10000050, parameter1 ffffe9f8, parameter2 00000000, parameter3
8053d071, parameter4 00000000

I have used dumpchk to analyze the minidump.dmp files and I have had no
success. Can anyone point me in the right direction? This problem is
becoming a severe annoyance.

 

[Ron Martell]

My company has about 30 workstations. For the past few months, I have found
a pesky little error that is causing random restarts on numerous machines
throughout the company. I have read many posts that say my error type is
related to hardware, but that is impossible as it is occuring on multiple
different hardware configurations. All computers are running XP Pro SP1.
Here is a copy of the error code:

Error code 10000050, parameter1 ffffe9f8, parameter2 00000000, parameter3
8053d071, parameter4 00000000

I have used dumpchk to analyze the minidump.dmp files and I have had no
success. Can anyone point me in the right direction? This problem is
becoming a severe annoyance.

Here is what the Windows XP Resource Kit says about your error:

"Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

The Stop 0x50 message indicates that requested data was not in memory.
The system generates an exception error when using a reference to an
invalid system memory address. Defective memory (including main
memory, L2 RAM cache, video RAM) or incompatible software (including
remote control and antivirus software) might cause Stop 0x50 messages.

This Stop message has four parameters:

1. Memory address that caused the fault.
2. Type of access (0x00000000 = read operation, 0x00000001 = write
operation).
3. If not zero, the instruction address that referenced the address in
parameter 0x00000001.
4. This parameter is reserved (set aside for future use)."


Because it is happening on multiple computers it is far more likely to
be a software issue rather than hardware.

Hope this is of some assistance.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

You may want to try installing SP2.