Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Outlook is crashing worldwide with 0xc0000005 errors

bleepingcomputer.com

Post reply on HN
Print view View original

81–90 of 109 posts

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#81

Post by WarOnPrivacy »

Shorel wrote: post #15
fortran77 wrote: post #9

Yup! I just updated Windows and got a crash. Relaunched it and it was ok Faulting application name: OUTLOOK.EXE, version: 16.0.13001.20266, time stamp: 0x5ef2a169 Faulting module name: mso98win32client.dll, version: 0.0.0.0, time stamp: 0x5ef2771f Exception code: 0xc0000005 Fault offset: 0x00000000000beef2 Faulting process id: 0x3be0 Faulting application start time: 0x01d65ad25f628bf7 Faulting application path: C:\Pr…

So that's why I have not been affected. I only shutdown "my" work laptop on weekends.

Rebooting didn't work for us. Rollback did tho.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#82

Post by annoyingnoob »

ocdtrekkie wrote: post #23

It'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…

I can spend a lot of cash up front on Exchange and Office, then deal with constantly patching them. Or I can spend only per seat/per month and the patching is automatic and the service is likely more reliable. After 3 years the costs are almost the same. Its not like my private environment is so much more stable than an MS datacenter. And the software has the same amount of bugs.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#84

Post by aflag »

acqq wrote: post #74
boramalper wrote: post #68

Earlier quoted context omitted.

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…

They could have the error code, name and a small explanation about what the error means. Eg.: The program tried to access an invalid memory address and had to be terminated. That is likely a bug in

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#85

Post by monroeta »

After 5 hours of uninstalling and failed windows system restore points, and a quick 24 google search worked! The below link mentioned really fixed the issue on multiple pcs. Thank you!!!!

"%Programfiles%\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.12827.20470

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#86

Post by monroeta »

fortran77 wrote: post #9

Yup! I just updated Windows and got a crash. Relaunched it and it was ok Faulting application name: OUTLOOK.EXE, version: 16.0.13001.20266, time stamp: 0x5ef2a169 Faulting module name: mso98win32client.dll, version: 0.0.0.0, time stamp: 0x5ef2771f Exception code: 0xc0000005 Fault offset: 0x00000000000beef2 Faulting process id: 0x3be0 Faulting application start time: 0x01d65ad25f628bf7 Faulting application path: C:\Pr…

That worked perfect for me also. "%Programfiles%\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.12827.20470

After 5 hours of failed attempts and many failed system restore points the updatetoversion link above worked on multiple pcs

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#87

Post by philistine »

CWuestefeld wrote: post #73
16bytes wrote: post #59

I 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 outputt…

A company that valued good design would have went with the floppy image. It's a very Microsoft thing to go with the inscrutable error.

On the other hand, this is the OS/2 project, which Microsoft did as a political hedge instead of a true desire to invest in that particular future. I don't fault them for not overthinking their decisions.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#88

Post by jrumbut »

acqq wrote: post #74
boramalper wrote: post #68

Earlier quoted context omitted.

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…

Your computer has performed an illegal operation.

sirens heard outside

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#89

Post by 16bytes »

akira2501 wrote: post #76
16bytes wrote: post #59

I 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\Of…

I would've expected a DLL load error to be ACCESS_DENIED instead of ACCESS_VIOLATION because the path for the DLL goes through a system call to open the file.

ACCESS_VIOLATION would be more like dereferencing a null pointer, but it's been a number of years since I had to troubleshoot this far in on Windows.

I suppose it's possible they didn't check for the error in the open file syscall then tried to use the uninitialized file handle for the DLL which caused the segfault.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#90

Post by 16bytes »

boramalper wrote: post #68
16bytes wrote: post #59

I 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?

For printing the codes? The programmer in me says something like:

"Error: 0xC0000005 - STATUS_ACCESS_VIOLATION - (Error, Microsoft defined, unreserved) Error: This is an internal error that prevented normal operation of the application. Please contact support at X."

Which conveys all of the information in the code and tells the user what they should do and that it wasn't their fault. Then it's a different story to say which code would be the most useful for the user.

NPM does something like this[1].

[1] https://stackoverflow.com/questions/22445371/npm-install-err...

Post reply on HN