Random freezes with windows 7 - 64 bit

The random freezes are likely not from any specific program your using but high memory usage. One of the problems was a package transfer protocol or something that was having trouble. it wasn't sure what to do at times so the system would stop responding. 

Basically, anytime you're running something that uses high system memory you have a high chance of running into freezes.

Yes, I reached that conclusion several program changes ago. I just want to share what I have tried when someone mentions doing the exact same thing as their next step.

That said, your post is helpful. Thanks to everyone for contributing!

FYI after installing the hotfix goneil99 mentioned in this link:

http://www.technize.net/fix-windows-7-service-pack-1-random-freezes/

I have been stable for almost 24 hours. I'm starting to feel good about this one again.

My issue is a completely frozen desktop, mouse pointer included. I'm running Win7 pro 64bit with 8GB in 4 x 2GB dimms.

to recap my changes:

• latest drivers across the board
• changed from MS Security Essentials to Norton
• changed from Firefox to Chrome (nice change honestly)
• tested RAM, added ram cooler (pulled half ram, rotated DIMMS after subsequent failures)
• underclocked/overclocked/undervolted/overvolted in every combination on CPU and memory
• held my nose and ran Norton360 reg cleaner (never really liked using any of those types of utilities, not a ding on Norton in particular)
• changed from dual 9800gt's in SLI to a single 9800gt, swapped to the other one after failure, changed to Radeon HD6850 after no help (another good change overall in terms of power usage and heat, but really, will Microsoft pay me for the ram cooler and new video card, and the hair transplant?)
• and of course, the new hotfix (previous hotfix suggested that I am too lazy to find was already on my machine via SP1 I believe).
• (added with edit) disabled all cores except core 1 on my quad core cpu. Renabled in every possible combination after new lockups, no help

What seems clear to me is that so many people are seeing differing symptoms that it is hard to discern one specific cause.

I've been freeze-free for something like 48 hours now (previously couldn't go more than about 15 minutes after boot).

My freezes were variable, in that sometimes I could open a new application and work for a while whilst the original program stayed locked, although the system gradually froze around me. On any number of occasions I was able to open the Task Manager and monitor CPU usage, which was rarely anything significant. On one occasion after leaving the system to sweat for a few minutes it actually recovered itself, although this happened only the once. On all occasions I could still move the mouse.

I did as the Creator suggested and tried TuneUp Utilities 2012 (£13.99 sterling at Amazon for 3-user licence). I have no doubt that correcting the squillions of issues that program found contributed to a resolution.

For me, with a system that I built just under a year ago, I think installing the 8 or so Windows Updates that were available helped (still don't understand why the update program hadn't told me they were there) but I think probably the latest drivers for the motherboard, several of which had been updated in October or November '11, were the key for me, perhaps in concert with the Windows Updates. As a non-overclocker I also uninstalled a couple of the less useful utilities that had come with the motherboard, as I am sure that the one relating to USB performance was a real key; that program had frozen several times on its own whilst the Windows desktop was building.

To summarise, though, it seems a complete Microsoft shambles that only Apple and Linux distributors can win from.

Thanks to all who have come up with suggestions. I shall continue to monitor this thread, hopefully from a bystander's perspective!

RandomFellow, please clarify what you mean by "High memory"

Do you mean a high usage of available memory (i.e. little or no free memory), or

Use of memory at the high end (i.e. memory with high addresses.

Please also clarify why you feel that is the cause.

Sorry for being pretty vague there. I don't know much about the whole issue aside from what I read of the hotfix and what's happening to me. It looks like there's more than one cause to this so... with a grain of salt and all.

Sorry, I meant available memory. According to the info they gave on the first hotfix Microsoft put out last year in August (I'm pretty sure it was August), the more information being processed the more likely it is for this protocol, or whatever it is to, to have a conflict and stop responding. I've noticed I have far more freezes playing games than when I'm typing in messangers or sending emails. It's even more frequent with games that are resource hogs.

I know I'm not offering much in the way of solutions, but if it's true for some people, it'd make things less frustrating to know whats actually causing it.

RandomFellow, please clarify what you mean by "High memory"

Do you mean a high usage of available memory (i.e. little or no free memory), or

Use of memory at the high end (i.e. memory with high addresses.

Please also clarify why you feel that is the cause.

Sorry for being pretty vague there. I don't know much about the whole issue aside from what I read of the hotfix and what's happening to me. It looks like there's more than one cause to this so... with a grain of salt and all.

Sorry, I meant available memory. According to the info they gave on the first hotfix Microsoft put out last year in August (I'm pretty sure it was August), the more information being processed the more likely it is for this protocol, or whatever it is to, to have a conflict and stop responding. I've noticed I have far more freezes playing games than when I'm typing in messangers or sending emails. It's even more frequent with games that are resource hogs.

I know I'm not offering much in the way of solutions, but if it's true for some people, it'd make things less frustrating to know whats actually causing it.