Computer Problem?

[joinmeindeath417]

hey i just recently upgraded my entire pc...and well this is where the fun starts..

sold my old pc ..to start upgrading to this one...

ever since i upgraded (fresh install of xp ect) while playing games..my pc randomly reboots...

but also but rarley it reboots by itself?

any one know any problems/solutions that could cause/fix this..thanks

 

[Polaris573]

Does it do it when nothing is overclocked?

 

[KennyT772]

sounds like its too far overclocked jsut like polaris said.

 

[{JNT}Raptor]

I've yet to see an X2 3800 that cannot handle a 400Mhz Overclock...sounds like it's the PSU.....Random reboots are usually a sign of an Underpowered system.

 

[trog100]

random reboots are usually the sign of an unstable system..he..he

it might be the power supply but it might be anything.. if its overlcocked in any way take it back to stock and see if the reboots stop.. its an easy test to carry out..

trog

 

[POGE]

Sounds like its overclocked too far, like trog said. Stock settings should fix the problem.

 

[trog100]

the hard bit is finding out just what clocking it will take.. but random reboots are a classic sign of instability.. something either aint getting quite enough voltage or something is going a little too fast..

trog

 

[breakfromyou]

get rid of that X-Connect asap. they're very crappy power supplies. there are 2 revisions of them. the first ones (2 years old) and they werent that bad. the new ones are HORRIBLE.

dont overclock, the power supply is probably making your voltages fluctuate a bit, causing insane instability. i had an x-connect before. it killed my athlon xp-m 2500+

when i had the X-Connect, it started making my voltages fluctuate quite a bit. i tried underclocking the processor and giving it a little more vcore so it wouldnt crash everytime the power supply decided to drop the voltage goign to the processor. well...a few days later i smelled smoke. AXP-M 2500+ was dead.

replace the power supply and you should be good to go. a 400 MHz overclock (stock vcore im assuming) should be pretty easy on just about any socket AM2 X2 3800+.

 

[joinmeindeath417]

i have the cpu running at 1.4 volts vs the 1.3 volts it runs normal...its 400 mhz higher than it should be...it has rebooted before not oc'ed but when windows does load back up it says its a driver problem...thing is...i've reinstalled all my drivers and ...well unless its a hidden driver that isnt good that i dont know about im stumped at what it could be..the psu i bought a couple months ago..it was the original x-connect not the new ones i heard the new ones werent so good so i bought the older one (with the see through windows)

 

[trog100]

ignore the windows error messages random reboots is 99% always hardware..

with my current system.. testing out a new sandy core cpu at 3.2 gig 1.4 vcore..

the system ran perfectly for about five days.. ran all the benches and played all the games.. i thought it was "there"..

but after five days a simple rightclick attempt to create a new shortcut on my desktop and bingo windows reboots..

ramdon reboots are the baseline stability tester.. when u think its okay but u get the odd reboot.. its not quite okay..

in my case i knew exactly what it was.. the sandy at 3.2 needed just a smidge more voltage.. vcore up from 1.4 to 1.425 did the job..

now i know exactly what the chip will do.. for genuine 24/7 stability i run it at 3 gig with vcore at 1.375.. it has an easy life this way.. couse the lower vcore does mean i have to watch things for few days..

and even if your system does the odd reboot trick at stock.. its still a sign of hardware instability..

if whatever u fiddle with speedwise the problem stays the same.. take it as a sign the bit u are fiddling with isnt the problem.. look elswhere..

trog

ps.. u are still at the "could be anything stage".. it might sound back to front this but push your bits up to a point they get unstable.. properly.. once u know the limits of each piece.. u can then slow that piece down and test another piece..

simple logic this.. but if say your chip is stable or nearly stable at say 2.6 gig.. running it at 2.4 should be stable.. u can then move on to test another piece.. to find its stable speeds..

slow parts of the hardware down below stock speeds if u have to.. hardware stability is affected by speed.. period..

tweaking a rig can take several weeks to get it just right.. running sup-pi a few times means sweet bugger all..

 

[joinmeindeath417]

ignore the windows error messages random reboots is 99% always hardware..

with my current system.. testing out a new sandy core cpu at 3.2 gig 1.4 vcore..

the system ran perfectly for about five days.. ran all the benches and played all the games.. i thought it was "there"..

but after five days a simple rightclick attempt to create a new shortcut on my desktop and bingo windows reboots..

ramdon reboots are the baseline stability tester.. when u think its okay but u get the odd reboot.. its not quite okay..

in my case i knew exactly what it was.. the sandy at 3.2 needed just a smidge more voltage.. vcore up from 1.4 to 1.425 did the job..

now i know exactly what the chip will do.. for genuine 24/7 stability i run it at 3 gig with vcore at 1.375.. it has an easy life this way.. couse the lower vcore does mean i have to watch things for few days..

and even if your system does the odd reboot trick at stock.. its still a sign of hardware instability..

if whatever u fiddle with speedwise the problem stays the same.. take it as a sign the bit u are fiddling with isnt the problem.. look elswhere..

trog

ps.. u are still at the "could be anything stage".. it might sound back to front this but push your bits up to a point they get unstable.. properly.. once u know the limits of each piece.. u can then slow that piece down and test another piece..

simple logic this.. but if say your chip is stable or nearly stable at say 2.6 gig.. running it at 2.4 should be stable.. u can then move on to test another piece.. to find its stable speeds..

slow parts of the hardware down below stock speeds if u have to.. hardware stability is affected by speed.. period..

tweaking a rig can take several weeks to get it just right.. running sup-pi a few times means sweet bugger all..

First off i'd like to say thank you for the detailed explaination!!!
yes your right im betting its something hardware related also concidering i did run prime 95 on my pc for a day with no errors 0.o...i think it has to do with my graphics card concidering mainly it only happens in games...this is my second AM2 motherboard..i RMA'd the other one concidering it might have been the problemi was also thinking it could be my chipset..there is no fan on it and it gets EXTREAMLY hot...i dont mean like 50 degrees celcius i mean like dont want to touch it at all hot..but its an odd shape and i cant find a fan to fit it ...not including my pci-e card completey blocks it...my case has good airflow..i get around 22-25 degrees celcius with the system fan my CPU runs 33 idle and 56 full load...i guess as you said its going to take alot of bios tweaking til i can find out exactly what it is

P.S Thanks Again

 

[trog100]

having bin down this road many times i have never found a grfx card to cause reboots.. screen lock ups.. yes reboots no..

u have a point about your chipset getting hot.. but the only chipset now that doesnt get super hot or need fancy cooling is a via one similar to mine.. without any fan it just runs warm to the touch.. the burning your fingers factor aint that uncommon when they come without noisy fans or heat pipes.. nforce ones generate the most heat for some reason..

u could take your case side off and run like that or even rig an old fan just to blow on it.. it dont have to be a nice fitting one..

the problem with a reboot every few days kinda thing is it takes ages to test if what u last did is having any affect..

which is why i say push things to the point of quick instability.. then u know at what point real instability sets in.. u then run far slower than the instability speed and test another piece..

slow your memory down and push the cpu.. find its real abilites.. take it to the point where a single run of 3dmark 2005 bombs out.. make sure your grfx card is going slower than on the edge while u do this else it might be that..

as a general rule running each piece %10 slower than its bomb out speed should produce a stable piece of hardware..

and as someone has said if the psu dosnt keep the voltages nice and level it can affect overall system stability.. hard to test for this one thow cos all power supplies fluctuate to a certain extent..

work on the easy bits to test first..

trog

ps.. dont push your vcore to any more than 1.5 the gain aint worth the extra heat.. not without exotic cooling..