The Problem: - Windows 7 would randomly freeze for about 30 seconds, while frozen there would be no error messages or BSOD.... the mouse still worked, but icons and windows and even task manager didn't respond. After 30-45 seconds the computer would come back to life and act normally as if nothing had happened. This problem with Windows 7 freezing would happen at random times, in random applications. Most frustratingly there wasn't an apparent trigger. Nor were there any signs anything had happened immediately after the computer momentarily froze. Task Manager showed nothing. There was no crash message, no BSOD error message, nothing showed up in Event Viewer... there simply wasn't a trace.

PCSTATS tried a number of solutions that didn't work:

Changing the computer power mode to "High Performance" (no change)
Updating every single hardware driver (no change)
Patching the OS to the latest updates (no change)
Update to the latest BIOS (no change)
Disabling Services, cleaning out MSCONFIG (no change)
Virus Scan and Malware searches (nothing showed up)
System Diagnostic scan (no problems, no change)
MemTest or Memory Diagnostic (no faults, no change)
Installing more memory wouldn't have changed anything as this issue is not an memory problem.

Short of reinstalling Windows 7, we'd exhausted just about every problem solving solution in PCSTATS's extensive Beginners Guides. After wading through countless forums it became clear that reinstalling Windows 7 wasn't going to fix anything either.

Based on systematic troubleshooting; 1) update all drivers, 2) update BIOS, 3) ensure no hardware faults by testing with diagnostic programs 4) updating graphics drivers 5) cleaning out MSCONFIG 6) scanning through Services and last but not least 7) contacting the manufacturer Support department for Tech Support help (no help, recommendation was to reinstall from factory OS image) we had eliminated most of the potential errors that normally would be responsible for a computer crashing, hanging or freezing up.

In the end, we did everything right. It wasn't any one of these things. It was a much more complicated issue solved with a very specific Microsoft Knowledge Base Patch released just two weeks ago!