Or mobo problem, or cpu overheat. Check cooler. Try other xp distr. Try any live cd. Try replace cpu.

voltage problems on the mobo? switch out the mobo to see if that works. CPU heat sensor might be broken.
Caps might show fine but testing/replacing them might be a better choice. Do note you may be able to test some caps just fine but others give straight errors even though they might be fine and must be removed to do so.

First of all thanks for the input,I slapped in a different CPU today.I put in a P4 2.4 mhz Northwood .Same thing occurs.I left the machine on all night and morning.When i got into the room the machine was still on and still reading at 50c .Its not a heat issue unless im missing something. Ill state again when i been fooling around with.
Pentium 4 3.2ghz Prescott 800mhz FSB (New) and Now P4 2.4 ghz 500mhz FSB Northwood (new)
Soyo p41875p dragon 2(used)
Sapphire 1600xt 512mb AGP 8(New) and Geforce 3 ti 200(used)
Thermaltake TR 430 430 watt PSU (NEW) Coolermaster 500watt (new) XFX 750 watt(used) old school Tiger Pro (shit) 350w(used and Codgen 350w (used)
Stock heat sinks clipped and running fine.
Corsair 1gbx2 DDR 3200 3.3.3.8
OCZ 512mb x 2 DDR 3200 3.3.3.8
The computer was left on over night.I again tried to boot up into windox xp and the setup again powers off.
I tried to boot into a linux live and again the computer powers off.
I tried to boot into a HD with windows on it and again the computer powers off
I tried mulitple DVD drives both ide and sata and its the same.
I tried to run the built memory test on windows 7 option just to see if i can get into the repair windows and soon as i select it , It powers off.
Its like detecting somthing and then bam power off.
Why would it act like this? Where it can be on all night and then poof powers off when it try to run some type of program?

I see you created a new thread. I posted there that I suspect some kind of power or fan monitoring turned on. Could also be a bad cap, like Richo pointed out. When a load is introduced the event is triggered due to unregulated voltage drop or something that messes a sensor up. Just a theory. Try going into the PC Health section and turning all monitoring off for a start.

I figured it out and here are the steps in case anyone else runs into the same problems:
Step by Step
1.) Opened up a case of Modelo Beer!(optional)
2.) Opened up a bag of Pork Rinds(optional)
3) Read the advice that was given to me.
4.) Went into the restroom to think about the advice given to me
5.) 20 mins later came out and looked into the PC Health Status menu and there is no option to change anything in it
6.) Noticed that the CPU was being run at 1.55v by default.....?
7.) scaled back to 1.5 and then 1.45 ,1.45 ended up being the sweet spot and is running fine now:)
8:) finish this awesome accomplishment with an Al Bundy Chuck Berry air guitar dance(optional)!

Glad you figured it out! Sometimes that PC Health section is actually useful. 😀