I've been experiencing a strange slowdown in my system over the past two days and wondered if anyone could shed some light on the possible causes. The system is a 233MMX with 192Mb of RAM running Widows 98SE on a 4Gb main HD (5200), 1.25Gb free space with a 40Gb secondary HD (7200), 5.9Gb free space. The drives are run through an Intel 82371 AB/EB PCI control card and only 31Gb of the second drive is available (seen by the system).
Two days ago I replaced what I suspected was a CPU fan gone bad. After I finished and rebooted, the system was behaving strangely, the mouse was slow or non responsive and all the windows and menus open and close in slow motion, almost like a fold-out menu or a window slowly collapsing into the taskbar. I also noticed my system clock was loosing time at a rather rapid rate and I was unable to get it to synchronize with the atomic clock in Boulder, CO. It would get to within 1 second, but no closer, and then begin to lose time right away. Tried doing some backups to save what I could, but the system is too slow and Herkey-Jerkey to get the job done (system keeps crashing or locking up). The CPU fan is running at close to normal RPM 3600 vs 4550, before the problem, but I suspect that the reading is not accurate, and the system temp is about 35. When I shut down and let it cool for an hour or so and then reboot, I get a red text warning in the post about some hardware not working properly and to hit any key to continue. Hitting the key brings the machine up and then it starts running in slow motion. The mouse is for the most part fine except when multi-tasking and the system resources run between 55 & 75% free. Subsequent reboots do not produce the hardware error. The fan speed is 1886 RPM on the cold boot when the error occurs and increases with each subsequent reboot. I'm suspecting this area may be where the problem lies, but am at a loss as to what it might be. Also noticed today that after the system was shutdown overnight as a precaution for possible overheating, the clock was accurate (after being on battery power overnight) but once the system was started it began to loose time again. I started the system this AM at about 7:35 and now, some 12 hours later, the clock reads 11:13 AM.
Any and all thoughts on the subject would be appreciated. Excepting those concerning a jolly elf in a red suit and the 25th of the month. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>