0x00000024 when saving from Office 2016

Update six days after original post.

Buoyed by hope that the problem was fixed, feeling confident on a nice Friday, and also about to step away from the computer for an hour, I created a blank document, saved it, entered more characters, saved, etc.

Four saves went well, but the fifth save blue screened me, with another 0x00000024 error.

I've attached the DM log collector files for the three such crashes since 9/29.

FWIW, my Office 2016 remains signed in - the prior two crashes happened when I was not signed into the associated account.

A chkdsk /r /f of both my C system drive, and D data drive, all came back error free.

The file saves out of Office 2016 programs have been the ONLY blue-screen trigger for this computer.

The event file shows no errors, other than the 0x00000024, associated around the time of the critical blue screen error.

Any new insights for me, please?

Post 11 above has some information that might help smarter people analyze this for me, but I wanted to share a bit more.



Above is the summary output from WhoCrashed, a utility I saw recommended.

It analyzed the three crashes that appeared - all 0x00000024 - when saving Excel or Word files from Office 2016.

Two were me "just using" Word or Excel as I normally would, probably saving a second time in a session.

The third, from two days ago, came as described in 11 above. I would type a line in Word, save, type another line, save, and on the fifth save it crashed.

WhoCrashed simply "flagged" ntfs.sys for the first two crashes, but for the third it identified mrfoldr.sys.

This is a driver for MirrorFolder, which I've had for probably 10+ years on my computer. It keeps the D and F data drives synced. Save a file, change a file, delete a file, on data drive D, and MirrorFolder mirrors that change to F.

I opened a support ticket with MirrorFolder on Friday night after discovering this, but, probably because it's the weekend, I've not heard anything other than an autoacknowledgement of the ticket being open.

Pending what they say, I could (should) of course disable the MirrorFolder syncing and experiment to see how saving from Office goes then. I just hate the experience of a crash, and the slow (20 minutes or so) recovery of my computer until it's functional again.

I can't necessarily think of a lot of other files I edit and save. Some images with paint.net and Irfanview freeware, some sound files with Audacity sound editor. I will often do incremental saves with these programs and not have a problem.

But I'm of course wondering if Mirror Folder and the syncing between D and F data drives, is the problem, based on mrfoldr.sys being flagged.