Error code 10000050 after Windows update, computer reboots.

This is somewhat weird, but I did a fresh install of Win XP Home, and installed SP2 update after that. Things were fine up till then, however, I had more updates to install after SP2 (like 60 more). So I fired up IE 6, and choose express install. When it finished, it told me to restart. When the computer restarted, the Welcome screen sort of flashed and the computer rebooted itself. After that reboot, it went into Windows. But the problem didn't go away, it kept rebooting at random times.

Here is what the Event log said:

Code:
Event Type:	Error
Event Source:	System Error
Event Category:	(102)
Event ID:	1003
Date:		10/23/2006
Time:		7:52:44 PM
User:		N/A
Computer:	Computer
Description:
Error code 10000050, parameter1 fedff124, parameter2 00000000, parameter3 804de9a4, 

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 35    1000005
0020: 30 20 20 50 61 72 61 6d   0  Param
0028: 65 74 65 72 73 20 66 65   eters fe
0030: 64 66 66 31 32 34 2c 20   dff124, 
0038: 30 30 30 30 30 30 30 30   00000000
0040: 2c 20 38 30 34 64 65 39   , 804de9
0048: 61 34 2c 20 30 30 30 30   a4, 0000
0050: 30 30 30 30               0000

My specs are:

CPU: Athlon XP 2000+
Motherboard: Epox 8KHA
Ram Speed, size and #sticks: 1 GB PC-2100 DDR. 1x512MB, 2x256MB sticks.
GPU: ATI Rage pro.
PSU (do not leave this out): Enlight 300W
OS: Windows XP Home SP2 with all the updates.

The thing is that I had windows running just fine yesterday. Its when I tried to install all of the rest of the updates, is when the problem started. So, I reformatted and did a fresh install like I said above, but the same problem: Updates after SP2 exhibit a reboot problem. I am attaching a couple of minidumps as well. Also, I did do a quick memtest86+ on just the one 512MB stick, and got no errors (took the rest of the sticks out). I think I let it memtest run for 35 minutes, or one Pass. Is that enough?

Thanks.

Added speedfan PSU rail voltages (Hrm, is the 3.3v rail slacking off?? Or could it be messed up sensors/speedfan?)
 

Attachments

  • Mini102306-04.dmp
    88 KB · Views: 5
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.

Possible Resolutions:

If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.

Also, there have been reports that faulty RAM can cause this error message. Perform a memory test to rule this out. You can use this free memory test program:

http://www.memtest86.com/
 
Back