What are some of the causes of this? the cdrom and the burner leds stay on. I can hear something wind down when it first turns off. xp home,1.0amd .
comp keeps rebooting...
- Thread starter daves66nova
- Start date
- Status
CPU overheating, random shorts on the motherboard, bad PSU, maybe even bad RAM.
How long have you had the computer? It might be time to remove the heatsink and reapply some thermal paste (wipe off the old stuff first). I find the factory stuff lasts two years on average.
Also remove the motherboard, go through both sides with a can of compressed air, and check the case to see if there's a loose or extra standoff, screw, or anything else metal that could be rattling around shorting things.
It's a little harder to diagnose a faulty PSU or RAM if you don't have another computer.
How long have you had the computer? It might be time to remove the heatsink and reapply some thermal paste (wipe off the old stuff first). I find the factory stuff lasts two years on average.
Also remove the motherboard, go through both sides with a can of compressed air, and check the case to see if there's a loose or extra standoff, screw, or anything else metal that could be rattling around shorting things.
It's a little harder to diagnose a faulty PSU or RAM if you don't have another computer.
What the guys upstairs said.
And, pull out RAM. Use pencil eraser to gently clean metal contacts. Ensure debris is blown off. You know, the old huff and puff routine that was so hard on the porcine abodes. Well, except for the little piggy utilizing bricks but he likely had union connections.
Anyway, if the stuff upstairs doesn't work you may be really lucky and have the simple fixes actually fix the problem.
And, remember the last resort. Heave the thing out the window and buy a new one!!!!
And, pull out RAM. Use pencil eraser to gently clean metal contacts. Ensure debris is blown off. You know, the old huff and puff routine that was so hard on the porcine abodes. Well, except for the little piggy utilizing bricks but he likely had union connections.
Anyway, if the stuff upstairs doesn't work you may be really lucky and have the simple fixes actually fix the problem.
And, remember the last resort. Heave the thing out the window and buy a new one!!!!
Gee, i wonder if it had something to do with me messing with the cpu? It didn't seem to do nothing right after i changed it,but i will change it back and stop changing stuff i don't know about.
You swapped out the CPU chip?
You did apply thermal grease between the CPU and the heatsink, right? If you didn't, changing it back won't help. Just apply a good amount of the stuff on the chip, then rub some into the copper surface of the heatsink as well. Then do a few heat/cool cycles to allow the paste to get into all the crevices.
You did apply thermal grease between the CPU and the heatsink, right? If you didn't, changing it back won't help. Just apply a good amount of the stuff on the chip, then rub some into the copper surface of the heatsink as well. Then do a few heat/cool cycles to allow the paste to get into all the crevices.
If it's rebooting during the OS load, put it into the bios setup from a cold boot and then go to the hardware monitor screens. These should give you an indication of non-loaded CPU and MB running temps. And running voltages.
An overheating CPU will cause reboots. As will an overstressed PS or flaky RAM. Sometimes poor cooling management will push a system over the edge. Check your mainboard temps. If they're too high, then you have general cooling problems to deal with. An upgraded CPU or GPU can overload some OEM boxes not designed for the heat load. These same boxes also tend to have PSUs with insufficient rail headroom.
Any CPU work needs to be followed by a good cleaning/re-greasing of the cooler/chip interface, but you know that. Sometimes, with a CPU transplant, it is also a good idea to clear the cmos and then reset the configuration in the bios. Of course, you want to make sure that you have the latest bios to support any CPU upgrade . . . not that a 1 ghz Athlon is all that cutting edge, but I don't know your mainboard.
And lastly, driver issues can also cause reboots, and you seem to be getting reboots at about that time in the OS load. Make sure that the OS is not set to reboot on errors. Sometimes, if you have a sudden driver conflict, the blue screen data can be very helpful. I would also try booting into safe mode to eliminate all driver conflicts. If the system runs without reboots in safe mode, it's almost certainly software related.
An overheating CPU will cause reboots. As will an overstressed PS or flaky RAM. Sometimes poor cooling management will push a system over the edge. Check your mainboard temps. If they're too high, then you have general cooling problems to deal with. An upgraded CPU or GPU can overload some OEM boxes not designed for the heat load. These same boxes also tend to have PSUs with insufficient rail headroom.
Any CPU work needs to be followed by a good cleaning/re-greasing of the cooler/chip interface, but you know that. Sometimes, with a CPU transplant, it is also a good idea to clear the cmos and then reset the configuration in the bios. Of course, you want to make sure that you have the latest bios to support any CPU upgrade . . . not that a 1 ghz Athlon is all that cutting edge, but I don't know your mainboard.
And lastly, driver issues can also cause reboots, and you seem to be getting reboots at about that time in the OS load. Make sure that the OS is not set to reboot on errors. Sometimes, if you have a sudden driver conflict, the blue screen data can be very helpful. I would also try booting into safe mode to eliminate all driver conflicts. If the system runs without reboots in safe mode, it's almost certainly software related.
I would get someone to download a bootable (linux) cd for you; then you can tell if its OS related or hardware.
Sorry for the bad info. What i meant to say was that i changed the freq. from 100mhz to 133.I've since changed it back,hopefully this will correct it.
since that was the only higher speed i could of went, i thought it wasn't too much.
That speed was your front side bus (FSB) speed. A CPU's internal clock speed is determined by the FSB x a multiplier. For example, if your multiplier is 26, then your original clock speed would be 2.6 GHz. Changing your FSB speed to 133 MHz would increase CPU clock speed to roughly 3.5 GHz.
i would assume bad ram, clock back up to 133 and run a memtest86 boot cd on it to find out for sure.
if the cpu is designed with a 100MHz bus, then it freaked the #@$%! out.
if it is designed to run at 133 and was underclocked previously, i would assume bad ram, clock back up to 133 and run a memtest86 boot cd on it to find out for sure.
if it is designed to run at 133 and was underclocked previously, i would assume bad ram, clock back up to 133 and run a memtest86 boot cd on it to find out for sure.
Pencil erasers can leave a film on the contacts you've just tried using it to clean. I would suggest a q-tip and isopropyl alcohol.
- Status
