Sluggish Everything After Resume

I updated all my Intel Chipset Drivers and this problem came back while I was working at the computer. The problem doesn't just arise after a resume. The only constant seems to be the computer having not been rebooted for several consecutive days.

I would try running for a couple days with 4GB of memory, just to see if win7 is not liking the fact that you have 32GB.

Just to clarify my previous post, I did not mention the memory because it might be bad, and did not mean there was a need to keep swapping out dimms in order to test them all and find the bad one. Even if your memory dimms themselves are perfect, win7 may not properly manage the 32GB.

After a few days ( I assume superfetch is not disabled) win7 may be overloaded with background tasks because of the abundance of memory. So removing any 28GB and just leaving 4GB one time will tell you that.

John, thanks for the clarification. Just wondering, is there a basis for this concern? My naive thinking is that with Microsoft's experience doing server OS's that big memory shouldn't be a problem.

Wouldn't those background tasks be visible through the Task manager?

I just had a lockup today. If this situation doesn't fix itself after a few more rounds of drivers and hotfixes, I should seriously consider converting this box to a x86 MacOSX.

SevenAndSeven said:

It could be the memory. I have passed the memory tests run by the BIOS. Systematically pulling out the memory and seeing the results is the rigorous way but a PITA. I would rather reboot the computer every three days and wait for Intel or Microsoft to release drivers that fix the problems. I suspect the pace of driver releases will pickup after Windows 7 is released to retail.

The most recent intel chipset package I could install was 9.0.0.15 from Dell even though the latest version from Intel downloads is 9.0.0.19. Some of the drivers installed are way older than you expect.

Just installed update

An update is available to improve the stability and reliability of Windows 7 and of Windows Server 2008 R2

we'll see.

Hi SevenAndSeven,

Thanks for the tip. This update showed up (automatically) on Windows Update a couple of days ago. I installed it but the problem persists.

bowzee.

The reason you might not see this on task manager is that you may not be waiting on the cpu. As windows has become bigger and broader, it has found things to do with all of your memory whether you want it to or not, which sometimes speeds the system up, but perhaps not always. I am not sure if there is different memory usage patterns between win7 and winserver08, but like you say maybe they are similar and this is not the issue. Memory leaks (obviously not operating as designed) and superfetch (even while operating as designed) both eat up memory over several hours/days, and got me thinking that your system with all its memory is different than most of the rest of us, so you may be exposed to different windows behavior than the rest of us.

Of course it could be many other things like a bad driver or system corruption