The 1st way (For normal users):
CTM could catch crushes itself. It it crushes, it should show the dialog for saving mini dump.
The 2nd way (For normal users):
If any application crushes, Windows should generate minidump. The minidump will be saved in temp folder. You can get more information(path and file name) from crush dialog.
The 3rd way (For professional users):
Generate crush dump using Windbg. Set Windbg as default debugger firstly, then if any application crushes, winbug should catch it. Then use .dump command. For more information, please visit here: http://www.microsoft.com/whdc/devtools/debugging/default.mspx
Ok, thanks.
But I never saw an application crash (a CTM crash).
What I’m seeing is a computer crash (BSOD). Well, I need to try the 2.8.155286.178 although.
I’m running it for ages on Corsair S128 here. :o
Maybe because it’s without TRIM.
BTW, doskey/brad007 do you have any idea why after I’ve uninstalled previous stable release and installed latest stable release I have my C partition (that Corsair SSD) twice? Once as Hidden and Protected and once as System and Unprotected? ???
CTM seems to work perfect fine but I’m curious.
I already asked for a two-step uninstallation process to avoid this.
1st step: restore to a particular snapshot that is working (or the current one). Boot.
2nd step: uninstall. Boot.
You’ve restored the baseline… everything after than that was lost…
Well, let’s be fair… You’ll done more harm than good defragmenting: increase the snapshots size and just redirecting the writes to the free space of the disk.
But you can’t say you don’t “need” defragmentation as CTM protected disk is still fragmented. CTM does not immunize the disk against defragmentation.
Well, my opinion.
I know, that there is no need to defrag. But in another thread I have read, that CTM 2.8 deactivates Windows Defragmentation. And that not happens -please look at the attachment.
Because of that I ask whether it