hmm random freezes and restarts

[ryuen]

just built a comp for my friend kinda rushed as i am leaving out of town this Thurs (tomorrow). he reports he is getting random freezes and the comp restarts. this happened to me a bit when i was installing the software stuff. im not sure if its windowsxp or the hardware. i thought i was OCin and all but i put back to stock and still problems.

my only guess is it might be the power supply but i really think its fine. the PSU is made by foxconn (dont hate) but everything is on stock. i dont know how it can overpower/heat on stock!?!

it was budget comp and i dont want to spend anymore money on it.

foxconn case with 400w mustang
http://www.newegg.com/app/viewproduct.asp?DEPA=&submit=Go&description=PC%2D146+400W

P4 2.4C -stock with stock HSF
buffalo hynix 512mb

shuttle AV49N mobo
http://www.newegg.com/app/viewproduct.asp?DEPA=&submit=Go&description=AV49N

ati radeon 9500 NP non softmod no OC

khypermedia 52x24x52x (telling you to show power consumption)
floppy drv


it not really a power eating or nothin. realy have no idea whats the problem

[Graphic67]

Before I looked at the case and power supply specifications I suspected the power supply. AFTER looking I am SURE that the power supply is to blame.

$29 or $30 for a case and power supply is too cheap. That thing is probably only capable of 200W and I expect that I am being too generous.

The system that you built is using around 250W peak (assuming ond hard drive and a few fans).

Here is a link to some good reading on power supplies: http://forum.oc-forums.com/vb/showthread.php?s=&threadid=150384

[(HR)Titan]

maybe proc dont like that mobo
cose i have p41.8A and my 645 ultra dont like it ...
i have random freezes too , but sometimes i must clear cmos cose system wont run up :(

[ryuen]

hmm well i doubt that a 400w rated power suply cant even take up 250watts. i know foxconn is a POS but i doubt it cant even do 250w. i really dont know. anymore suggestions before i take actions? i really cant afford to buy more than once more to replace something.

[redduc900]

I would suggest running Event Viewer (in order to access the error logs)...Start | Run | Type eventvwr.msc and hit OK | Highlight "Application" and "System" independently in the LH pane | Right click the error message(s) (critical errors are in Red), and select "Properties" | Write down a couple of the error messages exactly as they appear (under the "Description" field), and post them in this thread. ;)

[ryuen]

ok i will tell my friend when i am over there (in china :D :D).