Question concerning a tempramental computer not starting up.

[TheBorderer]

Hi folks,

I know I mentioned this problem in the First time you mess up a pc? (http://www.martialartsplanet.com/forums/showthread.php?threadid=8062) thread, but I was just wondering if there is anyone that could maybe suggest to me what I can do to properly fix this.

Ok, my computer I'm working on is a Athlon XP 2400+ with a Kobian(www.kobian.com) KOB 746 FDSX motherboard(http://www.kobian.com/products.php?productid=314). Now for some reason when I seem to have restarted the computer after installing an update (and last time when I changed a setting so the quick time stuff wouldn't appear in my Systray on Win XP), it seems to stop itself from starting up, no beeps no nothin. Now when I just got my computer back today the guy I got it from said that something must be writing to the CMOS and the computer won't start so that it won't damage itself. He also said I could fix it by clearning the CMOS memory using the jumper on the board.

I just wondered if there's a way to fix this properly so I don't need to do this everytim the computer might hapeen to do this (tho I hope it doesn't do this again).

Any ideas would be greatly appreciated. :)

[Redhotdragon]

well....when my computer doesn't start up i open it up and find the silver watch-like battery, the CMOS, remove it, and put it back in 20 mins...works a treat....

[bcullen]

Hmm, no beep indicates a) the pc speaker is out or b) the system has failed P.O.S.T (power on self test) which could be as simple as not having a good connection on an adapter for the keyboard to as complex as a damaged motherboard. Driver software exists to help the OS and the device communicate so a driver shouldn't have anything to do with the CMOS. Check the simple stuff first.

Here's one that threw me: A video card that wasn't screwed down eventually worked it's way free though contraction and expansion. When I cracked the case and pushed on it I felt it reseat in the slot and problem solved.

[hongkongfuey]

Now when I just got my computer back today the guy I got it from said that something must be writing to the CMOS and the computer won't start so that it won't damage itself. He also said I could fix it by clearning the CMOS memory using the jumper on the board.

I'm a bit dubious about this being the fault, unless the update was to the bios itself. If it was a printer driver, then no way would it do this. Neither would it stop the system starting to boot up (although it could potentially crash when starting Windows)

Often with the Athlon XP, heat is an issue - I would suspect the processor might be overheating, and it is a coincidence about the driver update.

You should be able to test this by going into the bios (if you can do this) when the computer first switches on. Press Delete / F1 / F8 / F9 / F10 (it varies according to the MB - delete is most common these days). Usually there is a section that shows the heat readings from the processor, fan speeds etc.

[TheBorderer]

Thanks for the ideas folks, I realise the idea on beep codes, but the guy who I got the computer from had said that the motherboard he replaced had no faults and was fine in another system he built. I've since restarted it a few times today and it appears fine {touches wood}(!). But as far as heat goes, it could be that as the fan on the thing is a bit wee(but then that's not to say the fan isn't doing its job for the most part), tho I will have a look at the temperatures on it, maybe it could be getting to hot... in fact HKF, do you know where I can find out how hot is too hot?

bcullen, I know that my botherboard has 'quick boot' option enabled, maybe I might disable that so it does a more thorugh POST.

Thanks for the suggestions folks. :)

[hongkongfuey]

'too hot' depends on a lot of factors (inc processor) - I'd guess anything above 55C would cause issues here (and it should be a lot lower)