Tech Support Forum banner
Status
Not open for further replies.
1 - 4 of 4 Posts

· Registered
Joined
·
6 Posts
Discussion Starter · #1 ·
A year or so ago, I upgraded my computer from K6-400 to Athlon 950. I changed the motherboard, CPU, and fan. I reused the other components. However, often, while the computer is booting up, it will get part way through, beep, go black for a second, and then restart. Then it will come up with scan disk because it was not shut down properly. Sometimes, the computer starts up just fine. Other times it does that. Once in a while, it will go through the restart routine up to 5 times. Nothing seems to be hurt by it, but it is frustrating and annoying, not to mention time consuming. It NEVER did this with the old K6-400 motherboard and CPU. Any ideas? Thanks again.
 

· Registered
Joined
·
6 Posts
Discussion Starter · #3 ·
After I installed the new motherboard and CPU, I did format the hard drive and reinstall Windows. I didn't know if it was a problem with the motherboard or CPU. If it is software related, it would be great to be able to fix it. If you can help, I'd appreciate it.
 

· hey
Joined
·
10,244 Posts
Windows 98 comes with a program called msconfig to run it click on:
start > run > (type) msconfig (hit enter/click ok)

There is a options there for selective startup. Check that. Then uncheck the load startup items. It will ask you to reboot. If it goes through booting fine, try rebooting several more times. If you are satisified with it, then run the msconfig program again. This time click on the startup tab and check the first item there. click apply then ok. Reboot the machine, if that goes through fine, do the same thing, but check the next one down until you find the program that is causing it to reboot on startup.

If you ran msconfig and unchecked the load startup items and it still doesn't load correctly then it either has a bad driver for your sound/modem/video a bad windows file or a bad piece of hardware. Let me know if you need help trouble shooting that.

Also, I've been starting to here from some other techs that if the bios has not been updated in a while, that can cause some of the errors you described.
 
1 - 4 of 4 Posts
Status
Not open for further replies.
Top