Hi

I have latest Reflect Home version 7.2.4440 and I also use 'Veracrypt' software. When I plug in my external USB drives which are encrypted by Veracrypt, all goes well until I dismount the drive and then use the 'safely remove/eject' as usual. It gives a blue screen referring to mrcbt.sys. Even if I insert the USB drive and not mount with Veracrypt, i.e. just insert then eject, the same BSOD occurs.

Note that the BSOD does not happen when ejecting a normal USB drive (i.e. not using Veracrypt at all).

I restored a backup image from when Reflect was at v 7.2.4325 and this doesn't occur. I use Veracrypt frequently so I know it has only happened after updating to 7.2.4440. I see the release notes refer to a version 7.2.4433, I did not update to that version previously, so not sure if the BSOD would have happened with that version or not.

I have however restored my system back to using 7.2.4440, and until (hopefully) the issue is fixed I can stop this happening by shutting down my computer, then removing the USB drive.

My OS is Windows 10 Pro 64-bit and Windows Update fully up to date, and am on the recent '1903' Windows 10 build.

Hope this can be resolved.

Thanks.

It seems to be a problem with ejecting external drives and Changed Block Tracker driver.  Others have reported problems, too, with ejecting discs and getting BSOD's.  Others who have provided debugging information indicate it's a problem with mrcbt.sys, which is the Changed Bock Tracker driver.


Unfortunately, it's probably not going to be resolved until the other posters who posted about it try fixes from Macrium tech support.


As you say, if you restore back to the previous version of Reflect, it doesn't seem to happen on that.  Plus, just from a cursory evaluation, it appears it may be only happening when images are written to the ejected disk.  I Eject my USB flash drives whenever I use them and have not encountered BSOD's, but 1.) it may not affect flash drives but USB HDD's and 2.) I didn't write image backups to the flash drives in Reflect, which may be a key indicator of the issue.

I`m having the same issue with BSODs referring to mrcbt.sys since the latest update. They only occur when trying to safely eject an Veracrypt or Truecrypt formatted Device (USB to Sata Bridge). But the images are written to another USB Disk (WD Book), not to the encrypted one. Veracrypt 1.23 Hotfix 2 and Windows 10 64 Pro are both the latest Versions. Have reinstalled the 7.2.4235 Version of Macrium Reflect.

VeraCrypt encrypted drives might be an important limiting factor.  The other posters of the same problem might or might not have had VeraCrypt installed.  And it would explain why my ejects of USB thumb drives don't trigger CBT to crash as I don't use it.  It might be a cross bug between mrcbt.sys and VeraCrypt's layer.  And the OP said it didn't happen on his USB HDD's that weren't encrypted with VeraCrypt.  So, it seems more likely some kind of cross contamination between mrcbt.sys and VeraCrypt's encryption/decryption layer.

This is the other thread about BSOD's after removing an external drive. I also posted in that thread yesterday, because I encountered a BSOD. However, I have the issue with a normal non-encrypted USB drive, so Veracrypt is not necessarily related.

There is likely an alternative temporary fix for this issue, although I have not tried it yet, but in other cases where mrcbt.sys caused a BSOD on my system it worked. Instead of reverting to v7.2.4325 you can also temporarily disable CBT by modifying the installation of Macrium and then uncheck CBT. In Windows 7 this is done via Installed Programs in the Control Panel > Modify, I believe in Windows 10 you have to go to Apps. Disabling CBT should take care of the BSOD's. Once a fix has been released it is then just a matter of checking the CBT option again when installing the update to the fixed version.

Yes, disabling the option to install CBT should resolve the issue because the driver that is causing the crashes is mrcbt.sys.  Of course, this will result in longer Incremental and Differential backup times and a few other really technical benefits you will be losing out on.  But, it beats BSOD's and having to regress back to the older Reflect version.

+x

 

Craig - 31 August 2019 7:12 PM

Hi

I have latest Reflect Home version 7.2.4440 and I also use 'Veracrypt' software. When I plug in my external USB drives which are encrypted by Veracrypt, all goes well until I dismount the drive and then use the 'safely remove/eject' as usual. It gives a blue screen referring to mrcbt.sys. Even if I insert the USB drive and not mount with Veracrypt, i.e. just insert then eject, the same BSOD occurs.

Note that the BSOD does not happen when ejecting a normal USB drive (i.e. not using Veracrypt at all).

I restored a backup image from when Reflect was at v 7.2.4325 and this doesn't occur. I use Veracrypt frequently so I know it has only happened after updating to 7.2.4440. I see the release notes refer to a version 7.2.4433, I did not update to that version previously, so not sure if the BSOD would have happened with that version or not.

I have however restored my system back to using 7.2.4440, and until (hopefully) the issue is fixed I can stop this happening by shutting down my computer, then removing the USB drive.

My OS is Windows 10 Pro 64-bit and Windows Update fully up to date, and am on the recent '1903' Windows 10 build.

Hope this can be resolved.

Thanks.

Hi @chnmanz,

Sorry that you are having problems ejecting USB devices.
​
​Please can you open​​​ a support ticket at www.macrium.com/support so that we can collect more information.​​

Kind Regards

Jamie

Macrium Development

See our reviews on

The problem has been solved for me. Had to replace the mrcbt.sys driver with a newer version.

So next update should be coming soon.

Typically messages sent privately aren't meant to be posted in a public forum, particularly when it comes to pre-release builds of components.  If Macrium was ready to release that broadly, I expect they would have done so themselves.

+x

 

jphughan - 4 September 2019 8:35 PM

Typically messages sent privately aren't meant to be posted in a public forum, particularly when it comes to pre-release builds of components.  If Macrium was ready to release that broadly, I expect they would have done so themselves.

TBH I do not agree. It depends on what has been privately communicated. In this case I am glad to know that Macrium likely has an upcoming fix, particularly because I have reported the same bug, but have not been requested to submit a support ticket. I have already been wondering what the status was, I could only assume Macrium was working on it. In a similar situation when I submitted a ticket I have done exactly the same: I reported that a fix was forthcoming, because I received a new version of mrcbt.sys that worked, but did not publish anything else. Craig did exactly the same and I am glad he did. The purpose is to inform other users suffering from the same bug that a fix is forthcoming. I do not see any problem with that.