Here is the system i started with:
ECS motherboard
P4 2.4 processer
512 MB PC133 Ram
80 Gb harddrive
Geforce 4 ti 4200 videocard
CD-Rom
Floppy disc drive
400 Watt power supply
It was a new installation of Windows XP on this new HDD about 2 weeks ago. Worked good for almost 2 weeks and then started freezing up. Within the day it had regressed to the point that the bios wouldnt even load up, and then the power wouldnt come on. SO i did a barebones hook up with an older MB and P3 700 processor and windows loaded. I then took my machine to another computer with a similar setup and tested my processor on that other machine and it worked normally.
So it appeared at this point that the problem had been isolated to the MB and/or RAM. I then went a bought a Soyo Dragon2 MB and 512 MB of PC2100 RAM. I also picked up a new 430 Watt power supply. I hooked all of this back up and now the BIOS runs through but instead of loading windows i get a quick flash of a blue screen which goes way too fast to read, and then the machine restarts itself.
The only common devices are the video card, disc drives and the processor (which worked in a diff MB) and the HDD (which worked with another MB/processor combo). Does anyone here have any ideas!?!?

I take it you are using the new Soyo motherboard, new memory and new PSU, but that you are using a hard disk with Windows XP which was installed on a different motherboard.

Windows is still trying to load drivers for the old MB and that may be the heart of your problem. The ECS drivers won't work on the SOYO MB.

Try booting in safe mode and see if you still have the same problem. If the computer runs without rebooting, then I would reformat C: drive and reinstall WinXP and it should work fine. A clean install of Windows is always better than trying to repair an old one.

At least, that is where I would start.

If you had re-run Windows “Setup.exe” to “repair” the installation each time you created a new combination of hardware, then all the new hardware would have been detected, the necessary files installed, the hardware initialised, and this hardware combination would be added to the “Hardware Tree” in the registry.
Then you could connect ANY of the previously installed combinations of hardware, the correct combination in the hardware tree would be selected at startup, the correct drivers used, and all would be well.
BUT, BUT, BUT:
The big difference is that Windows XP is designed to be registered for use with only ONE combination of hardware.
If you change the hardware, it thinks you’re trying to cheat by installing the software on a second PC.
It’s designed to stop functioning after 30 days if you don’t contact Microsoft and re-register the O/S for use with this “new PC” [new combination of hardware].

At least, that’s my understanding of how it works.
Perhaps someone else knows better.

If you replace the motherboard then you definitely need to run at least a repair installation to get XP to work. I had to do it myself when I replaced my motherboard and processor recently.
If you run a repair installation on XP to get it to recognise certain new hardware, especially the motherboard then XP will require that you re-activate it, since it does think its on a different computer and it will stop functioning after the period expires.

So did you have to contact Microsoft?
What was it like?
What was the re-activation procedure?

I had read that a special code is generated automatically, and that code is determined by the various items of hardware installed.
So if the hardware is changed, the identification code for the PC changes and since that code [or PC] has not been registered and no activation key given, then the O/S will refuse to operate when 30 days expires.

Contact micro$haft?
I can honestly say I have never needed to contact mico$haft about anything.

So how did you reactivate Windows XP and prevent it from ceasing to operate after the expiry period of 30 days?

A handy little thing known as pre-activation available with the pro-corporate version.