It generally could be different on 2000 and XP, because there were some updates in the past, that had bugs and so the CPU usage was alway on a high level. In this case, the fan is running on high speed. This happend under 2000 and XP in the past.

0

Idle temp, W2K = 61 deg, XP = 36 deg. Thermal paste and HSF position correct. Paulsep, thanks , I'll look into your suggestion.

0

Paulsep, you were on the money. I have reinstalled W2k+Sp4 sans any further updates. Fans working normal. Cheers, mnay thanks.

0

eddiebelfast If your idle temps are really 61C then you need to address that issue. I don't believe the OS can affect idle temps that much. At least one of your reading must be wrong. Your attitude is kind of like wearing ear plugs so you can't hear your car engine knocking.

0

Great, problem solved.

0

paulsep Am I missing something here? If the temperature is still at 61C how is the problem solved. Getting the fan to run slower is just going to make the temps higher. There is a reason why the temperature reading is high. Could be in error, but that needs to be determined. There are offsets in most monitoring programs. Maybe that is all that is wrong. Or maybe it is giving false readings.

0

A fan will speed up, the more the temperature of the cpu rises. So as eddiebelfast wrote, the fan is now working at normal speed. So now we can assume, that the temperature is also at a normal level, because it's regulated by a BIOS routine that triggers an onboard chip to let the fan run faster or slower. FYI: In the past, Microsoft release some really bugy updates. Sometimes it seamed, that a function of a procedure was hanging in a loop. So this function never ends and the cpu had to work for even nothing worthy, but it has to work. Till now, I worked arround this problem by restoring my last Ghost image and wait for the next patch day of Microsoft. Microsoft did not announce all the problems, concerning their patches. And some patches do only have problem under specific conditions like e.g. AMD CPU and ATI graphics adapter. I always install new patches for Windows Systems one week after Microsofts Patch day to avoid such faultys.

0

Any work Windows can do should not raise the temps to 61C. The OP states that is the IDLE temperature anyway. That means no work. Refer back to #2 where the OP stated that nothing was using CPU cycles in Task Manager. It would be helpful to know how the temps are monitored. eddiebelfast I suggest you install an active real time monitoring utility like speedfan. See what the temps are when the fan is not running fast in Win2000. You either have a real or perceived problem and it isn't the fan running too fast.

0

Otherhill, Yes mate you are missing something. Try reading message #8 . It clearly states the Win2k temp plus the XP temp. Idle temp, W2K = 61 deg, XP = 36 deg. Thermal paste and HSF position correct. Maybe a new pair of glasses?

0

eddie You are the one missing something. It is the SAME damn hardware. Shouldn't be running that much difference. The version of Windows isn't going to change the temperature that much, if at all. You have a problem with your hardware of the monitoring utility. There is no problem with Win2000 or WinXP. I am done trying to convince you. Fry your CPU if you want.

0

You can still check the temperature in most bioses, where you can configure the temperature at what the system should shut down. If temperature in bios is ok, and when starting w2k it's not, the problem is w2k. As I stated in message #13, software, drivers, patches a.s.o. can cause that much difference in temperature. It's just the same, when you're using Adobe Photoshop and use a lot of graphics filters and effects a.s.o. for a high resulution photo, the temperature will rise and the fan speeds up. But in this case, you know, that Photoshop is responsable for that effect. When a driver or a bugy patch causes that problem, it's hard to figure out.

0

paulsep If Task Manager is showing NO CPU usage by anything, where do you suppose the load on the CPU is coming from? Of course temperatures can rise when the processor is hard at work. That is not the case here. The OP has stated NOTHING is showing in Task Manager. I am not going to debate this issue any further. Seems like common sense is absent here.

0

Ok, but if a virus or trojan causes the problem, you may not be able to start taskmanager, or the shown processes are incorrect. Also viruses and trojans will hide themself from the taskmanager. So what you see, is not always the real usage or process list.

0

The OP SAID he looked in Task Manager. Reread #2.

0

But under influence of maybe a virus or a trojan, you can not say, whether you see all running tasks. I said, sometimes you MAY not be able to open the taskmanager. It's not a must. However, concerning viruses and trojans, I've seen a lot of different effects on windows machines.

0

I give up.

0

Me too.

0

OK! one final time. I reinstalled W2k without any updates. The temp at idle was 38deg, same as Xp and Suse. So, if I install the updates and the temp at idle soars to 61 deg what do you suppose is causing the temperature rise. THE UPDATES!!!!!!!

0

What else could it be, if you only installed additional updates. Have you already installed the drivers for your mainboard manufaturer? This is generally a must.

0

eddie If that were to happen then my guess would be that one or more of the updates is causing the monitoring program to give a false reading. Or you have picked up a nasty of some sort. I can't recall if you mentioned how you are monitoring the temps. One thing I would do is this. Use custom option for any updates and don't accept any updates for hardware. I might add, I just upgraded an older computer from Win98 to Win2000sp4 plus ALL available updates (70). That system is running a AthlonXP1700. BIOS CPU temp 32C. Speedfan CPU temp in Win2000 34C at idle. Did all that yesterday. So, I don't see where any updates are causing Win2000 to place an excessive load on the processor. Are you going on the net to get the updates without any firewall?

0

Guys, I assembled a box from some spares. Amd 3200, 1 gb ram and an all in one M/brd. Installed from the same cd, W2K+SP4 and booted. Perfect! Then D/L latest updates , again perfect! I then looked at the box giving me the trouble. I have always used Speedfan for temps and when I read one of your questions as to what I read my temps with, I thought I would look in the Bios and check there. Now, when I initially set up this box I was using the AMD standard HSF and the Bios showed 38 deg at idle, well today it showed 51 deg. I removed the Artic 64 and reinserted the original AMD HSF and the temp went down to 38 deg,( speedfan shows 37 deg). I have removed W2k from the drive so I will install it onto a scsi I have spare and see what happens. I have to buy a cable first. But, I'm betting it will be OK!

0

I have installed the software, W2K+sp4 and it idles at 38 deg. I have just had the automatic updates installed and now its idleing at 53. So it it the updates. It's the updates, I repeat , it's the updates.

0

Reboot to the BIOS and check the temp there to see if it concurs with speedfan. Do you know if AMD cool and quiet is enabled in the BIOS? Did you use Auto update to get the last updates? Microsoft sometimes feeds hardware updates. If a hardware update was installed it may have changed how cool and quiet functions.

0