This weekend I got crazy, as TrueCrypt just caused my Windows 7 when I wanted to mount a TrueCrypt file container.
This is often caused by a Windows Ext2 driver, but on my system it wasn’t. The Windows Driver Verifier tool (verifier.exe) kind of conflicted with the TrueCrypt file system driver. As this is a driver running in kernel mode, Windows immediately dies.
Many thanks to Rollin’ Rog on Tech Support Guy Forums. The thread is not tightly related to TrueCrypt itself, but it helped.
So: Disable verifier.exe when you wish to work with TrueCrypt! (Run verifier.exe, choose “Delete existing settings”)
This was one of the nice “everything is broken but I did nothing at all!” problems… reading the KB article about the Verifier tool, it sounds pretty crazy (and interesting) what it does, but I haven’t done further research to find the exact problem. Doesn’t matter to me, as long as my system is running again.
I was having BSODs when using Truecrypt and Pismo file mount under Windows 7 and tracked it down to the Comodo File backup utility device driver cbufs.sys.
Once I uninstalled the free Comodo Backup utility, the BSODs went away.
The BSOD you get is a system_service_exception. Install WhoCrashed to see if the crash is due to cbufs.sys and if it is uninstall Comodo.
Huhu,
tausend Dank für diesen Artikel. Diese ganze Sache hat mir schon Kopfzerbrechen bereitet, nun ist alles wieder beim Alten.
:)
Grüße
Yes I have been having the same problem and searching the internet for help. I have Windows 7 64bit. And it most everytime I try to mount a volume the dreaded blue screen appears. It takes several trys / reboots to mount a truecrypt volume. Anywho thanks for the information.