Microsoft Office Save Document causes BSOD

[mstanis]

Over this past one year I have noticed more and more frequent BSOD crashes so I started paying close attention to what I was doing. Since then 100 percent of the BSOD occurred almost immediately after trying to save (via clicking the save icon, ^s (shortcut), or even save as). I found the probability of BSOD decreases a lot when you are doing a save a new filename. In fact I can't recall a single time where saving to a new file caused a problem. Overwriting an existing file seems to trigger it. The driver causing the BSOD is NTFS.sys. Note, it doesn't happen on each and every save, the average is like 1 of 7. My work-around has been to avoid saving early and often (which is a serious problem with Microsoft Office which isn't the most stable application around) and when I do save make sure it is via save-as and to a new filename. Just tack on a number or letter prefix. I mostly use Word ands Excel and have noted they both have this problem. Other applications may not have this issue, but then I don't overwrite too many files so that may be the reason for the lack of BSOD.

It's hard to say when it started. I allow Microsoft to update my PC as updates become available. I was never a fan of Microsoft roulette having been burned, but a couple friends insisted Microsoft cleaned up their act so I gave it another try. On the up side some of their updates did correct a couple minor issues. I believe one (or more) of their updates is responsible for this issue. Likewise I was hoping a future update would resolve the issue. I've since stopped hoping.

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.