kaled - 7:56 pm on Jan 21, 2011 (gmt 0)
It's VSS that's causing the crash. That's what it's telling me.
Not my area of expertise, but I believe that with a BSOD all you can be confident of is that the address at which the error occurs is mapped to the specified module. That can be a lot less than you think, for instance...
Would you immediately associate a BSOD in VFAT.SYS with file encryption software (I won't say which one).
I had a quick look to see if there was anything useful out there with regard to the "bad pool header" error - all I would say is ignore advice to run a registry cleaner. The likelihood of that fixing the problem is vanishingly small. If you use one routinely anyway I suppose running it one more time would do no harm (or as a last resort before a reinstall).