Random freezes with windows 7 - 64 bit

Half way through writing this message my computer froze again. This is driving me nuts and I just don't know what to do. My BIOS and all drivers are up to date and  my computer just freezes randomly. Two weeks ago I was running the 32bit version and never had any problems so should just reinstall that and forget 64bit? When my computer freezes, all I can do is hit the reset button which is certainly not a good idea. Any help would be much appreciated!

My rig is: 

Operating System: Windows 7 Ultimate 64bit (6.1.7600)

CPU: Intel Core 2 Quad Q8400 @ 2.66GHz

Motherboard: Asus P5Q Pro Turbo

Video Card: ATI Radeon HD 5770

Sound Card: Asus Xonar Essence ST

RAM: 4Gb

Day 2 and no freezes so far. I used the computer a lot yesterday and this morning and also shut it down overnight.

I am now back to using the logitec wireless mouse & keyboard.

I will summarize in one place here what I think is going on.

While we work on our computer there are a number of files opened regularly in the background that we are not aware of. These vary from system logs to data files kept by specific software we are using.

Sometime in march something changed in the environment of W7 x64 installations. The cause could be an update from microsoft or a viral attack targeted to that environment.

March was a period when I got a lot of badly infected machines to repair. Most had good security in place but still some really viscous stuff got through. 

Whatever the cause, the result was that regularly background working files were not closed properly destroying the integrity of the disk indexing in a way that W7 chkdsk doesn't recognize as an erroneous condition. Because of the nature that disk space is used the majority of background working files that are regularly open likely exist close to each other physically on the disk. Once one file is compromised others located in the same area soon follow.

The os has a timeout routine on reads and writes and when a program attempts to read or write  to these damaged working files (often initiated by a mouse click or [enter]) the os sits there and spins it's wheels until it times out. Because the os does not recognize the error condition no error code is generated. The more read and writes scheduled by the program the longer the spinning takes. As more damage is created from the initial error condition, more and more programs are impacted at an ever increasing rate until the system becomes unusable.

Running chkdsk or repair does not resolve the problem as these routines do not recognize the error.

Chkdsk of the XP vintage catches some of the errors that newer chkdsks don't.

I suspect most of those affected are using NTFS formatting on their disks. The errors reported by the older chkdsk almost exclusively were found within the extra security structures of NTFS. I have reformatted to Fat32 with the hope that the routine causing the problem does not exist in this environment. So far so good after about 2 days which is substantially more time than I got from restores recently.

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.

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.