I want to mention another weird freeze that was caused by archiveinvalidation and the mods that use it. I don't know if it's related, and it might be difficult to reproduce, but it was weird so I'll mention it. Relevant mods include mart's mutant mod, fook2.
Update 2: After further research, it seems like the problem isn't so much archive invalidated, but a texture placed by another mod or texture replacer as seen in this post -> http://www.thenexusf...e-invalidation/
In other words, it turn out that the problems are not at all related to archive invalidated, but to corrupt meshes and textures installed by mods. Archive invalidated just simply makes these custom textures and meshes available in game. So if you have any crashes in the future with feezes + the sound continuing to play, you be sure it's not archive invalidated but a corrupt textures or mesh.
It was in the Museum of History Offices, in the foyer of a two story area with a turret directly in the center. It's towards the very back of the museum. I was on the first floor, looking toward the stairwell in front of me. I go to look a dead Rambler (a MMM addition), and take a finger, which causes the hand to explode and spew blood particles from the arm stub. If I attempt to look away while these particles are spweing the game freezes just as the particles go out of view. If I wait a few seconds for the particles to stop flowing, I can look away without a problem.
Hmmm, I used to have issues like that with my rig. As soon as I turned off Vertical Sync, the crashes mostly stopped. Is it the same type of crash that you described before (with the sound continuing to play)?
If you want to try, here's a good article on how to get rid of vertical sync -> VSync: Vertical Synchronization (VSync) is the synchronization of your graphics card and monitor's abilities to redraw an image on the screen a number of times each second, measured in Hz - for full details, see this page. Whether LCD or CRT, your monitor will have a maximum rating in Hz for each resolution (e.g. 1280x1024 at 75Hz). When VSync is enabled (ticked), your maximum FPS will be capped at your monitor's maximum refresh rate at your chosen resolution, and more importantly in some areas your FPS may drop by as much as 50% if the graphics card has to wait to display a whole frame. Thus enabling VSync can have a negative performance impact. To offset this impact, you can enable Triple Buffering.
Unfortunately in Fallout 3 VSync is enabled at all times, even if this box is unticked. You can force VSync off by editing the iPresentInterval=1 variable in the Fallout.ini file to iPresentInterval=0 (See the Advanced Tweaking section). You should also check to make sure your graphics card's control panel doesn't have VSync forced on - whether via a specific Fallout 3 game profile or in the global options (see the Nvidia Forceware Tweak Guide or ATI Catalyst Tweak Guide for more details). Disabling VSync should be the optimal option, as it can increase framerates and more importantly, it will reduce mouse lag. However unfortunately in Fallout 3 it can also increase the micro-stuttering/juddering/skipping issue (as covered in the Troubleshooting Tips section). In any case experiment to see what your results are with this setting, though again, remember that it can only be turned off properly by manually editing the relevant line in the .ini file mentioned above. If you just want to reduce mouse lag without disabling VSync, see the Max Frames to Render Ahead tweak on the last page of this guide.
This information was taken from this guide: http://www.tweakguides.com/Fallout3_5.html Best guide I've come across bar none, it is really worth your time to go through it if you haven't already.
On a related note, the same guy (Koroush Ghazi) who made the fallout 3 tweaks guide, does guides for a bunch of other games and a most excellent guide for XP users -> http://www.tweakguides.com/TGTC.html (I usually don't promote anyone, but these guide are worth the $5.00 price tag IMHO). There's a free edition as well, so there's no reason not to take a look.
Tell me if deleting the file worked for you as well, good luck.