CPU Fan Error

So how much RAM is installed and what CPU is in use here.

The old P43 Chip Set M'Boards where designed long before Windows 7 became available so while there are 7 Drivers it wasn't actually designed with 7 in mind. Also the type of Windows 7 may be playing a part here so is it a 32 or 64 Bit Version of 7?

When 7 Opens have you opened the Task Manager and looked at what the CPU and RAM Usage actually is?

Col

Needing to be replaced. This is a Coin Battery CR2032 and a commonly used battery by many devices. It provides power to the Real Time Clock in the CMOS or as some prefer BIOS and not only provides correct Date & Time but it also saves the settings. So things like CPU Fan Settings and CPU Temp as well as CPU Type and amount of Installed RAM and HDD are covered by this. They should cost between a few cents to a couple of dollars depending on where you buy one.

When the battery goes flat these settings get lost and you have to press the F1 Key to continue which effectively accepts the current BIOS Settings which would be the Defaults and proceeds to load the system.

If the CPU Fan Control is messed up it will cause this to happen but before rushing out and buying a new battery you should look at the CPU Heat Sink. These get clogged with Dust and other Air Borne Gunk and in sever cases can prevent the fan from spinning. When this happens all that is required is to open the case and with some Canned Air blow out the Heat Sink while preventing the CPU Fan From spinning.

The CPU Fan is nothing but a Electro Magnetic and a Permeant Magnetic which will generate Power if it's allowed to spin and that power will cause damage to the M'Board and other fitted components.

So the two things to look at are the CPU Heat Sink for a buildup of Crud and the BIOS Battery for going flat.

If you have to replace the BIOS Battery remember to unplug the system before removing the battery as it's a metal case if it's dropped onto the M'Board while there is power there it will cause a Short Circuit. I've had many systems brought in that should just need a replacement Battery but after their owners have attempted to change the battery they now need a new M'Board because of damage that has been caused by Dropped Batteries.

Col

It could be that some thing messed up in the Windows Registry has caused the Program not to start till well after Windows has loaded.

I've seen something similar with USB Scanners which slow down the Load Process dramatically and will cause several Apps not to start or start late. In instances where there is a USB Scanner involved I just put in a password and wait till all HDD Activity has stopped and then enter the Password and start the OS.

Seems that you need to slow down the Boot Process to allow the system to catch up and load fully. Granted I've only ever seen that when USB Scanners where involved but that by no means implies that other things may not do the same thing. It's just that I haven't run across them yet. ;)

Col

[b]Windows Tells you Lies[/b] and doesn't always do as it's says it will.

Do not ever expect what windows tells you to be correct. If it is so much the better but it's as likely to lie to you and drive you crazy in the process.

I vividly remember a M$ Error Message I got many years ago Device 6 is Missing, turns out according to M$ that Device 6 was is the CPU but just how a system without a CPU generates a Display and a message like that is a bit beyond my limited understanding of Electronics. I'm fairly simple and understand that No Logic Processor there no Output as the system doesn't work.

The Professor that I had at Uni for some strange reason suggested the same thing and all my previous experience sort of reinforced that as well. ;)

Try this grab a copy of the Ultimate Boot CD

http://www.softpedia.com/get/System/Back-Up-and-Recovery/Ultimate-Boot-CD.shtml

Burn it to CD and then boot off it. If the CPU Fan still plays up you have a Hardware Problem and if it just works you have a Software Problem. It's at least a starting point to work from if nothing else.

Col

Updated BIOS and chipset drivers and it resolved the issue.

Thanks everyone!