I had an user with Office 2016 who just had this problem. I didn’t found this article in time and I solved it with a clean installation of Office. (Safe mode did not work)
Ask Microsoft to reimburse you for your time.
Microsoft Outlook is crashing worldwide with 0xc0000005 errors
71–80 of 109 posts
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#72What is going on with Outlook for Windows? For years, it froze its entire UI whenever there was some network lag on the IMAP server, and the recent improvements for Outlook strangely focus only on their Mac, web, and mobile versions. Does the Windows version still have a future? It seems to be stuck in some maintenance limbo.
If you look at the release notes[1], Outlook for Windows is getting a lot of love too. The majority of updates are performance and bug fixes, but the UI issue you mentioned highlights the need for this type of TLC in the Windows client. That said, the frequency you receive these will be pretty dependent on which release cycle your install is set up for, as it can range from monthly to semi-annually. The Mac, web, and…
Windows 10 gets a lot of love too. So much that updates often brick the entire install and deletes files and folders.
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#73I still don't understand why Microsoft doesn't print human readable error code instead of just "0xc0000005". To figure out what the actual message is, you first have to figure out if you are seeing a HRESULT or a NTSTATUS[1]. In this case the leading 0xC is an invalid HRESULT, so it's for sure an NTSTATUS. Then you just look up the code in the bottom two bytes [2]. In this case it's just error code 5: "STATUS_ACCESS_…
A zillion years ago I was able to see some of the internal communications around the development of OS/2. One topic was the way that non-system floppies would (fail to) boot when left in the PC. What the user would see was something like (I forget the exact numbers)
SYS!012345
SYS!876543
...and they were supposed to go look that up in some reference book to see what it meant.
The question was why they weren't outputting something human readable like "Unable to boot from non-system floppy". And the answer to that question was that, as an international company, they couldn't expect everyone to understand English.
So why not output multiple different languages? Well, the code to output the message has to fit in the floppy's boot sector, so the space is very tight.
And so there was discussion about whether it makes sense to give up having only 99% of users understand it, and instead have 0% understanding.
I think the killer argument was the person who suggested outputting a message something like
______
| |__| |
| () | X
|______|
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#74I still don't understand why Microsoft doesn't print human readable error code instead of just "0xc0000005". To figure out what the actual message is, you first have to figure out if you are seeing a HRESULT or a NTSTATUS[1]. In this case the leading 0xC is an invalid HRESULT, so it's for sure an NTSTATUS. Then you just look up the code in the bottom two bytes [2]. In this case it's just error code 5: "STATUS_ACCESS_…
I really enjoyed reading this, thanks! > In this case it's just error code 5: "STATUS_ACCESS_VIOLATION", which is a memory access error, which typically means it's a bug where the program accidentally is trying to read outside of its memory space. What would be a (more) user-friendly error message for this though, given the quite technical nature of the error?
In fact the "status access violation" message would be much more confusing for the "normal" non-programmer person.
I believe the actual error would be "access violation", status is only the prefix. But I don't think that text would help normal users more.
As in: "Who is that General Protection, what has he done to my computer and why is that his fault"?
"General Protection Fault" were the words actually presented to the "normal" users before. It surely didn't help them to read that.
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#75I always thought I really disliked Outlook ( because of so many issues) until I worked for this well known startup and started using Gmail. Man, how I miss all the Outlook issues... at least it was good for reading/writing email. Disliking something can be quite relative I guess...
What's wrong with it? Just curious, I use Outlook for work and my main pet peeve is that
i) local search isn't great and
ii) in general, the application UI is very 'delicate' -- e.g., I have mail rules that move mailing lists to a folder. I browse through them from time to time but housekeeping those is a nightmare-- Outlook consistently freezes while deleting larger numbers of email.
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#76I still don't understand why Microsoft doesn't print human readable error code instead of just "0xc0000005". To figure out what the actual message is, you first have to figure out if you are seeing a HRESULT or a NTSTATUS[1]. In this case the leading 0xC is an invalid HRESULT, so it's for sure an NTSTATUS. Then you just look up the code in the bottom two bytes [2]. In this case it's just error code 5: "STATUS_ACCESS_…
> which typically means it's a bug where the program accidentally is trying to read outside of its memory space.
I tracked this down with process explorer the other day. What I determined is that outlook is trying to load it's DLLs but the permissions on the FS prevent the DLLs from being read by the user.
I reset the permissions for all subfolders in C:\Program Data\Microsoft Common and c:\Program Files\Microsoft\Office and it started working again for me.
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#77It's worth noting that this appears solely to be a failure with Office 365/Click-to-Run-based installations. If you buy your software instead of subscribing to it, and service Office with traditional Windows Update mechanisms... everything is fine today. This is what happens when you rip out well-tested IT infrastructure that has a reasonable update distribution process and entrust the cloud to update your software f…
>Office 365/Click-to-Run-based installations. If you buy your software instead of subscribing to it...
I've never been clear on what CtR describes. The first CtR Office was Home & Student 2010, which was a purchase.
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#78I still don't understand why Microsoft doesn't print human readable error code instead of just "0xc0000005". To figure out what the actual message is, you first have to figure out if you are seeing a HRESULT or a NTSTATUS[1]. In this case the leading 0xC is an invalid HRESULT, so it's for sure an NTSTATUS. Then you just look up the code in the bottom two bytes [2]. In this case it's just error code 5: "STATUS_ACCESS_…
Same for their OS, it seems to ignore power users completely. Just a few months ago I was going to connect to an SMB share by using \\nas\Downloads and it just wouldn't work, started a network troubleshooter that couldn't troubleshoot anything.
If it had just told me that the name could not be resolved I would have figured out that I needed the full domain suffix because ipconfig wasn't showing it.
This issue goes way back in Microsofts history, always getting on my nerves as a power user. But at the same time probably the best OS for any other type of user.
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#79With OWA there is no need to use the outlook client anymore
Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors
#80This a really bad outage because it happened to my partner and there is nothing obvious about what went wrong. It just...closes.
> there is nothing obvious about what went wrong. It just...closes.
Yeah, that's disconcerting from a support standpoint. Fortunately, I was able to remotely load their event logs and get the status code. DDG pointed right to the above article.