Same goes for TrueCrypt and possibly also for Bitlocker, once the disk is crypted you'll get a message in your eventlog at system startup that the crashdump driver could not be loaded because of this.
I'm NOT talking about the startup BSOD. I'm talking a BSOD while Windows is running or even manually invoked. My system disk in NOT crypted, neither the disk where I'm saving the dump (a simple NTFS disk without CTM protection).
The part where the BSOD writes the dump is so low that the drivers arn't even loaded.
I'm not in a startup BSOD.
So running disk encryption is the end of crashdumps...
I'm not using disk encryption at startup.
CTM is NOT conflicting with TrueCrypted drivers.
The problem could even not being CTM but any other driver of any other application/hardware.
The problem seems that CTM is blocking the dump to be saved!