Computer keeps restarting after POST

wiredvibes

Member
Jun 4, 2006
64
0
0
I just built a PC ;


ASUS P5N32 - SLI SE DELUXE
INTEL CORE 2 DUO 6700
XFX GEFORCE7950GX2
2 SEGATE 320GB HDD'S
2GB CORSAIR DDR2800 XMS 2
SEASONIC S12 600W
THERMALTAKE ARMOUR VA8000BWS


The machine worked fine for around 2 days .. FEAR oon maxiomum .. rendering in maya... . but then i installed rise of legends and ws playing it on ultra high for abt 2 hrs and it restarted. since then my machine would not restart. if i leave it shut down over night then it allows me to boot from disk otherwise it restarts before the XP loading page. but after booting from disk once , the machine restarts right after the POST screen.

I have tried formatting HDD's and reinstalling windows (it just copies setup files to HDD and then restarts)
ran memtest86 for 2 hrs
replaced Vid card with a friends
CPU temperature is 39c
reset the CMOS
ran Segates diagnostic utility.
reseated everything and checked all connections.

im going to try the PSU on a friends machine.. tom sometime.

ANY IDEAS??? i cant seee any bad capacitors on the motherboard. i really dont want to rma the mobo .. coz then i haveto remove the processor and also send the mobo and wait for a new one which will take over 2 weeks from newegg. im just hoping its somethign retarded i havent tried.

but why does it allow me to boot from disk after leaving it off for a few hrs?? and not normally and also why did it work for 2 days! ..

im maybe going to try a new IDE drive tom... hopefully that fixes it. if not.... PLEASE HELP MEEE...
 

QueBert

Lifer
Jan 6, 2002
23,121
1,274
126
try going into the bios and lowering the memory or FSB speed. I've had a similar reboot problem on a few of my older boxes and this worked for me. I know you said you reset the bios, but in my cases it still was rebooting right after the POST. changing the memory speed from 200 to 166 fixed it. Although the performance hit was crappy, it was the only thing I could do to get it working. You might be dealing with a bad MB. I've seen MB's work normally (or so I thought) and have a problem all along, but it just takes time to show itself.

 

wiredvibes

Member
Jun 4, 2006
64
0
0
thx... ill try that.. but its a brand new system like a week old... so i dont want to run crappy ... ill just rma the mobo
 

QueBert

Lifer
Jan 6, 2002
23,121
1,274
126
Originally posted by: wiredvibes
thx... ill try that.. but its a brand new system like a week old... so i dont want to run crappy ... ill just rma the mobo

on mine once I clocked it down, windows XP installed perfectly, then I bumped it back up and it would boot fine. I probably should have RMA'ed the MB, but once I had it working fine I just left it alone
 

wiredvibes

Member
Jun 4, 2006
64
0
0
if u can think of something else.. please tell me otherwise im going to RMA the mobo tom...afternoon. thx for all ure help
 

lyssword

Diamond Member
Dec 15, 2005
5,630
25
91
test memory settings, in my experience, RAM memory is responsible many times for crashes.
 

wiredvibes

Member
Jun 4, 2006
64
0
0
OK finally got ym new mobo back from RMAing... and it worked ... for the entire night and till 3 o clock today then back to the bullshit of restarting.... WTF!!! i know its not the RAM or the HDDs or the GPU or the CPU .. mobo replacement made it work for a while again but not work properly ... PSU seems to be the only thing left... !!!!what the hell is going on? please someone help me or atleast give me ideas of what to do .... could it be a voltage issue??
 

KingofFah

Senior member
May 14, 2002
895
0
76
Well, I once got a string of bad NF7-S's (hence the reason why i stay away from abit now), so you might need to RMA again; I would think that there is something else causing this. The PSU might be flaky and unstable. I had an unstable PSU kill a mobo before. Try installing to a dif mobo with a dif psu and see if the problem comes up. At least that would verify that everything is working except either the PSU or the mobo.

Don't know what else to say. I agree with the comments about the relaxed memory timings and fsb. I have had the same things happens before, where a mobo just didnt work right at the frequency it was supposed to. See if that helps.