Rather than opening a new topic, I have the same problem so I'm adding my issue here. I think my problem with the constant rebotting is memory related since the problem didn't happen until I put a new 512 SDRAM in about 2 weeks ago. I had to turn the PC off with the switch because it just kept rebooting. Any advice on getting XP to load again until I can get the info you suggest?

On the possible memory error...it was a $55 512 MB chip...maybe that's it? But when I ran diagnostics from the Crucial memory site, the new chip was recognized as was the 128MB. But the 256 MB chip didn't show up. Here's what it gave me:

Slot 1 512 MB SLOT 2 128 MB SLOT 3 Empty. It never read the 256. (Both the 256 and 128 were stock I believe. I just added the 512 to fill all 3 slots and moved the first two over so the 512 got SLOT 1)

Any suggestion will be appreciated.

Just to get XP to load I would try your old RAM configuration or just one stick at a time & see.

Originally Posted by jephree

Just to get XP to load I would try your old RAM configuration or just one stick at a time & see.

I tried this by moving the memory around. Didn't work. Then I removed the 128MB memory chips since the third slot apparently was not recognized and it loaded XP. All was well for awhile, so I made the chenges you suggested so the blue screen would come up with the errors instead of rebooting. Good thing I did because it went down again after about a half hour.

Here is the Technical Information:

***STOP: 0X0000008E (0XC0000005, 0XBF827B97, 0XF3561D84, 0x00000000)

***win32k.sys - Address BF827B97 base at BF800000, DateStamp 41107f7a

Beginninjg dump of physical memory
Physical memory dump complete.

I also have this info from the log:

System Error

Error code 10000050, parameter1 e2955fff, parameter2
00000000, parameter3 8054be34, parameter4 00000001.

EventID 1003

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data Bytes:
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 65 32 eters e2
0030: 39 35 35 66 66 66 2c 20 955fff,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 38 30 35 34 62 65 , 8054be
0048: 33 34 2c 20 30 30 30 30 34, 0000
0050: 30 30 30 31 0001

If you need more info, let me know, but I think this is all you may need. Thanks!

Just to clarify: returning to your old RAM configuration didn't work?
& now no single stick will maintain XP?

If you can get back in:

1) Download and install the
Debugging Tools from Microsoft
2) Download and install this
debugwiz
3) Open the Wiz & Browse to your MEMORY.DMP
4) After the Wiz creates a Text document post it back to this thread.

After I posted, I pulled the 512 MB thus restoring my original 384 MB config. It booted properly and seems stable at this point. Now the question is what to do with these two 512 MB modules (one was for my wife's pc and I'm not sure trying it would be a great idea....) thanks...

Are they all the same Brand? Type? etc.

I don't know about the brand (I doubt they're the same). But I bought the presumably defective 512 from Compuvest. The original 128 and 256 Memory Modules (shipped) were
133/100/66-MHz 64-Bit 4-Clock SDRAM DIMM.

You may want to start a new thread in the Hardware Section for a more detailed response but I have seen it advised to run the same brand together. Also no matter the speed of particular sticks they will all run at the lowest. There are many little tips for mixing RAM so what you have might be OK in itself but just not compatible.