CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums
Results 1 to 3 of 3
  1. #1
    John E is offline Elite Member Power Poster
    Join Date
    Apr 2001
    Manchester, England

    Windows crash logs

    Can't we start a campaign somehow for Windows to show human readable crash logs? Linux and Mac have been doing this for decades and it's high time Windows joined the club...

    Ever since its inception, Windows has stubbornly refused to generate crash logs with even the tiniest bit of useful information Apart from telling you which module crashed, the rest of it's full of memory addresses and other hexadecimal nonsense which doesn't help anyone at all (probably not even Microsoft). If Microsoft won't address this problem voluntarily, surely it's time we all shamed them into it.?
    "A problem well stated is a problem half solved. - Charles F. Kettering

  2. #2
    Arjay's Avatar
    Arjay is offline Moderator / EX MS MVP Power Poster
    Join Date
    Aug 2004

    Re: Windows crash logs

    Why not take charge and provide your own logging/error handling? If you take care of the error handling inside your app, the app will never crash (and Windows won't need to be involved).

    Help Windows out - it's got more important things to do than trying to help make sense of a crashed app.

  3. #3
    Join Date
    Jan 2013
    Largo, FL.

    Re: Windows crash logs

    Have you tried some of the BlueScreenView type apps that will display the BSOD dump file in an easy to read report so you can see what caused it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width