This is a weird one. I'm hoping for some clues.
I've got an ASUS I3220T based system that I use to run an instance of Windows Server 2008 R2. It's been fine, up until a week or so ago. The symptoms now are that it still runs fine, immediately after a re-boot, but within minutes (sometimes 10, sometimes a half hour "or so") it starts to slow down - significantly. For example, if I run winsat disk -drive d (the server's system drive) within 5 minutes or so of the system coming up, it returns what looks like normal measurements. However, if I run the identical test 15-20 minutes later, the test runs forever - literally hours - before it returns results and they are of course horrible. I thought perhaps it was heat related - I discovered the CPU heatsink was dusty and blew it out, but that doesn't seem to have helped much. As I write this, I have a winsat disk test running on it right now that has been going for over an hour and appears to be about halfway done, yet both processor cores are at 35 degrees C. I did manage to get sfc /verifyonly (system file checker) to run on it a couple days ago and it reported no problems found. I briefly suspected a DOS attack, so I completely disconnected the server from the network --- that didn't help. Whatever this is, a reboot will fix it --- briefly. I also have an Windows 7 installation on the same machine that hasn't been booted since I turned it into a server more than 3 years ago. I brought it up earlier and it seems to have the same problem. The onset may not have been as rapid, but I've only tried it once so I can't be sure about that since the problem seems to be somewhat random anyway. Something's going on here, but I'm sure having a tough time zeroing in on it.
I've got an ASUS I3220T based system that I use to run an instance of Windows Server 2008 R2. It's been fine, up until a week or so ago. The symptoms now are that it still runs fine, immediately after a re-boot, but within minutes (sometimes 10, sometimes a half hour "or so") it starts to slow down - significantly. For example, if I run winsat disk -drive d (the server's system drive) within 5 minutes or so of the system coming up, it returns what looks like normal measurements. However, if I run the identical test 15-20 minutes later, the test runs forever - literally hours - before it returns results and they are of course horrible. I thought perhaps it was heat related - I discovered the CPU heatsink was dusty and blew it out, but that doesn't seem to have helped much. As I write this, I have a winsat disk test running on it right now that has been going for over an hour and appears to be about halfway done, yet both processor cores are at 35 degrees C. I did manage to get sfc /verifyonly (system file checker) to run on it a couple days ago and it reported no problems found. I briefly suspected a DOS attack, so I completely disconnected the server from the network --- that didn't help. Whatever this is, a reboot will fix it --- briefly. I also have an Windows 7 installation on the same machine that hasn't been booted since I turned it into a server more than 3 years ago. I brought it up earlier and it seems to have the same problem. The onset may not have been as rapid, but I've only tried it once so I can't be sure about that since the problem seems to be somewhat random anyway. Something's going on here, but I'm sure having a tough time zeroing in on it.
Facebook
Twitter
Instagram