0x00000024 when saving from Office 2016

[450125]

I had stubbornly clung to an Office 2000 for more than 15 years, and through Windows 98, 2000, XP, and 7 environments.

However, somewhere along the line in Windows 7, saving a Word file multiple times in a session (no constant number, but usually between 3-7 times saving in one session) would BSOD me.

So I finally installed Office 2016, and for a couple months it ran flawlessly.

However, starting last week, I've had one episode from Excel, and one from Word, where saving a file BSODs me with an 0x00000024.

I've attached the dump from these, plus one from earlier in the year, the genesis of which I don't remember. It's the two most recent (9/30 and 10/5) about which I care.

I ran a sfc scannow, and no errors were found.

Also did a chkdsk /r /f on a restart. Here are the results:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
Cleaning up instance tags for file 0x46afe.
445440 file records processed. File verification completed.
3228 large file records processed. 0 bad file records processed. 2 EA records processed. 101 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
590948 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
445440 file SDs/SIDs processed. Cleaning up 1481 unused index entries from index $SII of file 0x9.
Cleaning up 1481 unused index entries from index $SDH of file 0x9.
Cleaning up 1481 unused security descriptors.
Security descriptor verification completed.
72755 data files processed. CHKDSK is verifying Usn Journal...
35347784 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
445424 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
24275773 free clusters processed. Free space verification is complete.
Windows has made corrections to the file system.

244092927 KB total disk space.
146194856 KB in 360888 files.
236140 KB in 72756 indexes.
0 KB in bad sectors.
558839 KB in use by the system.
65536 KB occupied by the log file.
97103092 KB available on disk.

4096 bytes in each allocation unit.
61023231 total allocation units on disk.
24275773 allocation units available on disk.

Internal Info:
00 cc 06 00 4b 96 06 00 ac fa 0b 00 00 00 00 00 ....K...........
2e 1d 00 00 65 00 00 00 00 00 00 00 00 00 00 00 ....e...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

I've had this computer for almost 10 years, replacing all the hard disks (a C system disk, and mirrored D/F disks for data) to retain integrity.

I know there will be "quick help copy/paste" solutions offered - no offense intended to those trying to help - saying it's my RAM, or run these 25 other diagnostics, or reinstall Windows.

But it's a fact that, other than power failures (the electricity going out in my house), the only BSODs I have suffered in years came from the saving a file in Word 2000, and now Excel and Word from Office 2016. No other causes.

Hope someone can give me some insight.

Of course I'm going to have to bite the bullet very soon and finally upgrade to Windows 10, which, I am guessing, will fix this annoying quirk.

 

[Snick]

Hi 450125
run
sfc /scannow
reboot

click rb:
click computer
uninstall programs
click on Office 2016
click repair
reboot

work now?

Bill

 

[450125]

Hi 450125
run
sfc /scannow
reboot

click rb:
click computer
uninstall programs
click on Office 2016
click repair
reboot

work now?

Bill

Thank you.

I am reluctant to take the simple steps (repeated saves from Excel or Word) that would test this, because it's then minimum of 15 minutes before my computer is again usable (the time to rebuild the desktop, and have the internet and application access working is LONG), should I get the error.

I'll update as I know more, but am probably just going to use the programs "normally" (I rarely save repeatedly, unless doing complex sequential edits).

So I'll just cross my fingers.

Some notes though:

1. sfc /scannow found nothing wrong, today, as it did last week when this first happened.
2. The Office repair took awhile, and threw out no informational messages. Is there a log I can read somewhere to see what it did?
3. I don't know how material this fact is, but I'll mention it. For some reason, I can only stay logged in to my Office account for a few days on this computer (my work computer I've never had to relog into again after installing and configuring Office). I got sick of logging in, so stopped doing so, to see what would happen. These BSODs started occurring about four weeks after the last time I'd been logged into the Office account. Tonight, I logged in again. Not sure if not being logged into Office somehow contributed to the problem. While not logged in, I had been able to edit, create, and save Office files.

The BSOD is the bigger issue, but any idea why I keep having to log into Office every few days?

 

[torchwood]

Hi 450125

I was going through the event logs, it does show multiple hangs and failures on numerous programs.
BUT what struck me the most tho was the high number of system time changes, I see your not are using the inbuilt MS one, this does affect certain actions especially windows updates.
Which brings me back to you saying youve changed a fair few parts on your 10 year old comp
The CMOS battery might also be on its way out.


Roy

 

[450125]

Hi

I was going through the event logs, it does show multiple hangs and failures on numerous programs.
BUT what struck me the most tho was the high number of system time changes, I see your not are using the inbuilt MS one, this does affect certain actions especially windows updates.
Which brings me back to you saying youve changed a fair few parts on your 10 year old comp
The CMOS battery might also be on its way out.


Roy

Probably a fair assessment for the CMOS battery. I will likely do a new system when I go to Win10, and assume a new mobo will take care of that.

You mention not using the inbuilt MS time changes. Best of my knowledge I am - when I click on the time in the bottom right of the display, there is an "internet time" tab, which says that I sync to time.nist.gov automatically. And my Windows update "looks" and "seems" right - updates after the first Tuesday of a month, with the occasional major update pushed to me other times. There was one late this past week.

Not sure that this would cause a blue screen though, and only from Office programs, and only on saving my work.

 

[torchwood]

Hi
That is NOT the MS time sync program.
see here

How to Make Sure Your PC Has the Right Time | Gizmo's Freeware

Roy

 

[450125]

Hi
That is NOT the MS time sync program.
see here

How to Make Sure Your PC Has the Right Time | Gizmo's Freeware

Roy

Well, this link seems to look exactly like this:

Although there was no mention of last time sync until I clicked on "update now" in the settings.

So if the above from my computer matches what's in the article, what do you mean that it's not the MS time sync program?

And if it's not, what do I do to get the MS time sync program?

Also, as helpful as this advice might be, it's off-topic (I think) to my concern about blue screens sometimes when saving from Word or Excel.

 

[torchwood]

Here mine showing the standard MS Windows default

hit the change settings button.


IF it is the CMOS battery changing the time server wont make any difference

the battery should be a bulk standard cr2032, cheap and cheerfull get one from your local Auto spares shop
(im not kidding)

Roy

 

[450125]

Here mine showing the standard MS Windows default

hit the change settings button.


IF it is the CMOS battery changing the time server wont make any difference

the battery should be a bulk standard cr2032, cheap and cheerfull get one from your local Auto spares shop
(im not kidding)

Roy

Thanks. Mine looked like that too, before I manually synced it today.

Your screenshot uses the Windows time server; my computer uses time.nist.gov. But no other differences that I can find.

By the way, I was far from aggressive today, but edited and saved Excel, Word, and Power Point files today. The Excel was one simple save; Word and PP I saved first as a pdf, then immediately as their native default format. And no blue screens.

 

[450125]

Update four days after original post:

I've been pretty timid - Simply creating a blank document, saving it, typing a few characters, saving, and repeating 10-20 times, would nicely flush out whether my Office is stable or not, and I'm too "chicken" to try.

But I have created/saved one Excel file without incident, and multiple Word and Power Point files.

In the case of the Word and Power Point, I've edited, saved as a pdf, then saved in native format. And no more than those two saves in any one session. Pretty wimpy, yes.

But no problems since Post #3 above. So I am hoping the "Repair Office" fixed things.

 

[450125]

Problem not fixed

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?

 

[450125]

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.