Windows 7 Freeze Final Solution?
...so I've had the same freezing issue with Windows 7 Home Premium. I have a similar system to that of many posters (X58 motherboard, Core i7 920, 16GB RAM, NVidia GeForce GTS 250, 700w power supply, 5 HDDs totalling 7.5 TB). I run MS Office 07, a host of other software programs, incl. Flight Simulator displayed via my overhead HD projector (onto a 12 ft screen).
I've tried just about every idea proposed on all the boards I can find. In the end, NOT ONE of them worked. Except what I've found after just feeling helpless and angry. My system is now working just fine...until the next time, and I have a solution for it.
Here's the thing. I believe it's not one single or even a couple of issues that causes this problem. It's a combination of many scenarios, complicated by the forced and uninvited Windows critical updates (which oftentimes occur even if you have Windows update turned off--mine was set to "Never update"). Every time MS does an uninvited update, after my system's been up and running just fine, the screen goes blank, and then does a forced reboot, after which, once Windows comes back on, it freezes within 3 minutes, requiring a hard reboot.
My "go to" solution, after trying everything else, has been to simply restore back to a point prior to the last update. But I've found that only solves the problem about half the time.
Now, follow me on this analogy: being a pilot, I know that it's normal to experience heavy buffeting just before reaching and surpassing the speed of sound. The gut reaction is to throttle back and ease back into a comfortable profile. But you have to fight that urge, and throttle forward, through the buffeting, and once you exceed 768 KIAS, everything smooths out. If you allow all the updates, your PC will crash (freeze) a few times. You'll spend a good chunk of your time getting frustrated, doing hard reboots, etc. But push through, and at the end of all that your PC will work just fine. Until the next uninvited Windows update. I just think all of this is somewhat unavoidable, given the idea it's a combination of factors, which NVidia (or ATI), MS, ASUS, etc., all have failed to resolve as an interactive team.