Check your hard drive and its corresponding controller is OK (SMART or other checks). I think I mentioned this in another thread, but an abnormal I/O wait for the hard drive can cause this kind of behaviour on regular basis - I experienced the same thing under XP with a dud HD (and everything just goes into 'limbo' waiting for the drive to respond)
This is especially likely in light of the fact it only happens when saving/opening files (and I'm surprised no-one has mentioned it yet)
Quote: "Not responding doesn't mean crashing. It just means be patient."
It isn't crashing, but that doesn't necessarily make it good/valid behaviour either. For all we know, there could be a catastrophic failure somewhere, and some kind of deadlock prevention/timeout is the only thing preventing complete lock up etc. If Windows suddenly decides every single application isn't responding, then there's
something they're all depending on/using which has 'asploded' so to speak
EDIT:
Quote: "I've done a thorough drive analysis/scan and the drive checks out fine mechanically."
Scan/check with what though?
09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0