Random freezes with windows 7 - 64 bit

OK its been nearly 2 weeks and crash free so far, touch wood.

I noticed by accident.. the batteries died on my MS v5000 wireless mouse. Not having another charged set handy, I plugged in a USB mouse. From that point, my freezing disappeared, but I didn't make the connection.

So the next week, I have to demo a PC for a customer, and I grab the wireless mouse combo to take with me, as I have new batteries for it but still havent plugged it back into my own PC. I've been building this customers PC for awhile, adding stuff, experimenting... its had no problems at all. I get to his place, plug in the wireless set and boot into Windows with a proud smile on my face... it loads.. I move the mouse and the whole damn PC locks instantly.

Embarrased, I mess around with it for awhile and cant make the problem go away.. just keeps freezing on me. SO then I have a brainstorm.. plug in a USB mouse.. and the problem is solved. The customer bought the PC (over a month ago now) and has never experienced the problem since then.. not once.

I've tried the same mouse on 3 other Win7 PCs now with identical results. Use it, freeze. Use something else, no freeze. On my own computer, since the day I removed that particular Wireless mouse, I havent had a problem at all. I've tried other Wireless mice with no issues. I've tried several USB mice with no issues.

I'm convinced we are all having driver issues, just for different pieces of equipment. Win7 may have drivers to suit almost everything but they are far from perfect at this point. Like previous editions of Windows it will take time to sort them all out I guess.

Windows 7 Professional x64

i7 930 2.8GHz (stable OC @ 3.9GHz)

Asus P6T

6G DDR3 1600 Kingston Hyper-X (triple channel)

9800GT silent pipe (fanless) x2 - SLI linked  * these things are huge but they run at less than 50C and this is the quietest PC I have ever owned*

150GB WD 10000rpm Raptor   System drive

1TB WD 7200rpm Data drive

Some more detailed symptoms... I am convinced disk writing errors are behind virtually all the symptoms reported in this thread.

I disagree.  My system freezes.  I don't, however, experience any of the symptoms you discuss re: file/disk writing errors, and I never have any difficulty restarting my system after a freeze.

It is quite possible that different users are experiencing freezing for different reasons (some are obviously due to a bad memory module, or BIOS misconfiguration; others appear to be directly related to Windows 7, as the same hardware is stable in XP).

I didn't realize I had a disk error problem either for a few weeks even though I checked the integrity of the disk multiple times a day. W7 simply didn't see the errors. There were no warning signs when the freezes occurred. The event log noted a few times that a program I was using while freezes were occurring was having trouble writing to some of its working files. I initially put this down to the system simply timing out rather than a disk integrity issue.

What finally made me realize the disk structure was compromised was during one of my many restore procedures. I used a BartPE disk I had made with True image and a bunch of other utilities on it and decided to run chkdsk from dos on this disk even though W7 repair had just given the disk a clean rating.

Using this older chkdsk noted some problems but could not fix all of them. It did change the state of the disk enough that W7 chkdsk saw some errors and was able to complete the repair. This worked about 80% of the time. Sometimes I went back and forth between the 2 chkdsk's multiple times until both declared there were no errors.

I understand that using an older chkdsk could potentially introduce it's own problems but felt the results were valid because it spotted the erroneous "disk full" condition which the newer chkdsk didn't see.

Had a lot of trouble re-partitioning the drive this time. There was an area of the disk no low level formatting program wanted to touch even the routines from western digital. I checked the disk again with HDD regenerator and there were no bad sectors. I messed with a bunch of different MBR repair programs and eventually got Western Digital's wipedisk routine to run successfully. From that point on the restore process went normally. The partition is now Fat32 instead of NTFS. This took most of the day yesterday but I got the system back running last night around 10pm. I used it for about 2 hours with no sign of freezing. I shut it off overnight which will normally start the freezing process on the next boot but so far this morning after a couple of hours there is no sign of freezing. It will take a few days to confirm the system is now clean.

* I am also trying Dakster1's solution and am currently using a wired mouse and keyboard. If the system is ok for a few days I will switch back to the logitec wireless ones and see what happens.

I suspect the firefox issue is not valid. I think what is happening is that whatever program the user happens to be using the most in the time frame that the problem occurs will appear to be the one causing the problem. This was true in my case. Many different programs have been reported as causing the problem. If we asked very likely everyone would agree it was the program they were using the most at the time.

It is a matter of probabilities. Generic errors will occur the most in programs you use the most.