Microsoft’s Online Crash Analysis – so maybe it is useful after all

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My Windows-based PC just crashed (hardly surprising given all the rubbish I have installed on it recently – despite all of the bad press that Windows attracts, I maintain that a well-patched and well-managed Windows NT, 2000, XP or Server 2003 system will generally be reliable).

In the past, if this has happened, I have ignored the message about error reporting (“yeah, yeah, yada, yada – I need to get back to work and did I manage to save that document I was working on before it crashed?”… etc.) but this time I let it report the problem – and I read the results. It was even useful.

You see what happens, is that if I experience a blue screen crash event, or stop error, while using Microsoft Windows XP (or later), I can upload the error report to the Microsoft Online Crash Analysis (MOCA) site for analysis (Microsoft say this is “to further improve the quality and reliability of Windows”). They then analyse the error report and prioritise it based on the number of customers affected by the error in the report. They then try to determine the cause of the error submitted, categorise it according to the type of issue encountered, and send relevant information when such information is identified.

What I like is that, using MOCA, I can check the status of the error report for 180 days and this time it told me that my system “crashed because the random access memory containing Windows program code was corrupted. Microsoft is unable to determine if this corruption was caused by a hardware or software issue. The nature of the corruption suggests that a hardware issue is more likely. To determine if this is the case, Microsoft developed a Windows memory diagnostic that tests your PC memory. We recommend you download and run this tool on your computer system”.

Sure, so the Windows memory diagnostic tool didn’t find any memory errors so I still don’t know why the PC crashed, but at least it feel like someone actually cares and is trying to fix things… much better than just getting a blue screen of death (or even a red screen of death!).

2 thoughts on “Microsoft’s Online Crash Analysis – so maybe it is useful after all

  1. I used to hate the error reporting feature myself and never allowed Windows to use it. I have since learned my lesson, and know that with any software product, the squeaky wheel gets the grease. If I like the product and want the bugs worked out, then I need to submit error reports. Windows makes this very easy and quick, so why not do it? I recommend that all my customers use error reporting, so that Windows overall can be made to work better. On the other hand though, I absolutely do not condone Microsoft’s habit of releasing what should still be in Beta and letting users finish the testing.

  2. I’m not sure that Microsoft releases too much code that “should still be in Beta” these days – it’s a lot more stable than in the bad old days. Most of the problems I see are based on poor OEM-supplied software, device drivers, etc.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.