Contents tagged with Corporate Error Reporting

  • Microsoft Online Crash Analysis now detects worms and viruses!

    Posted by bink on December 27 2005, 6:27 PM. Posted in Corporate Error Reporting.

    OCA detects virusses

    Click for larger view Online Crash Analysis is now capable of detecting some Internet worms and viruses. This error report was generated right after Internet Explorer became unresponsive and was closed by the user. OCA page shows that the application error was likely caused by Small.M worm and it is right. After doing a full scan in Windows Live Safety Center (http://safety.live.com) you can see that the computer has been infected.   Direct link to this report: http://oca.microsoft.com/en/response.aspx?SGD=4b4b3ab4-ce87-4a63-9410-02233f1d06dc&SID=1847More problems that can be detected by OCA: http://www.google.com/search?hl=en&lr=&q=%22was+likely+caused+by%22+site%3Aoca.microsoft.com
  • Coprperate Error Reporting (CER) 3.0

    Posted by bink on November 16 2004, 5:09 PM. Posted in Corporate Error Reporting.

    December Beta will be wide available, annoucement will followRTM CER 3.0 summer 2005CER vNext 1st half 2006Written from the ground up, data in SQL database, built in analyzer, SQL reporting services.

    Potential Services in the final:vba macro identifoicationmalware error iddentivfocation*report templatecorp IT response service*comparative error analysis*3rd party ISV serviceerrors fixed by update service*With * will be targeted in final, they narrowed down 25 services to these top 4.

  • Windows Error Reporting and Online Crash Analysis are your friends.

    Posted by bink on June 2 2004, 3:14 AM. Posted in Corporate Error Reporting.

    When you get an “your application has crashed, do you want to let Microsoft know about it?” dialog, then yes, please send the crash report in.  We’ve learned a huge amount of where we need to improve our systems from these reports.  I know of at least three different bug fixes that I’ve made in the audio area that directly came from OCA (online crash analysis) reports.  Even if the bugs are in drivers that we didn’t write (Jerry Pisk commented about creative lab’s drivers here for example), we still pass the info on to the driver authors.

    In addition, we do data mining to see if there are common mistakes made by different driver authors and we use these to improve the driver verifier – if a couple of driver authors make the same mistake, then it makes sense for us to add tests to ensure that the problems get fixed on the next go-round.

    And we do let 3rd party vendors review their data.  There was a chat about this in August of 2002 where Greg Nichols and Alther Haleem discussed how it’s done.  The short answer is you go here and follow the instructions.  You have to have a Verisign Class 3 code-signing ID to do participate though.

    Bottom line: Participate in WER/OCA – Windows gets orders of magnitude more stable because of it.  As Steve Ballmer said:

    About 20 percent of the bugs cause 80 percent of all errors, and — this is stunning to me — one percent of bugs cause half of all errors.

    Knowing where the bugs are in real-world situations allows us to catch the high visibility bugs that plague our users that we’d otherwise have no way of discovering

  • Corporate Error Reporting's Public Debut

    Posted by bink on March 26 2004, 1:22 PM. Posted in Corporate Error Reporting.

    Microsoft's Watson technology, for soliciting semi-automatic bug reports from end users and plowing the data back into the bug-fixing effort, has been mostly for the computer industry. But last week at the Microsoft Management Summit in Las Vegas, the company demonstrated software to help in-house enterprise developers use Watson to improve ongoing quality and maintenance of in-house applications. While Corporate Error Reporting, as Microsoft calls it, has been available to Software Assurance subscribers since September, Microsoft hasn't highlighted it before. "This is the first show where we've really talked about it a lot," says David Hamilton, a director in Microsoft's Enterprise Management Division.

    The public face of Microsoft's Watson technology is the pop-up prompt that confronts users of Office, Windows XP and Windows Server 2003 whenever an error occurs that forces an application to shut down. If the user approves sending an error report to Microsoft, Watson sends information on the failure back to Microsoft. Armed with the reports, Microsoft can determine which bugs are causing the most failures and prioritize its bug-fixing efforts accordingly.

    In addition to its own applications, Microsoft has encouraged developers of drivers for hardware devices and independent software vendors to take advantage of Watson, as well. Microsoft says it segments its database of bug errors to allow third-parties to see bug reports related to their applications. The company has also approached companies whose drivers caused a disproportionate number of crashes about getting problems fixed.

    Most software development, however, takes place not in the computer industry but instead inside companies where internal business applications are written -- and Corporate Error Reporting is designed to extend the benefits of Watson to those users. Continue at source