Debugging crashdump

This is a discussion on Debugging crashdump within the Windows Programming forums, part of the Platform Specific Boards category; I'm trying to figure out why that pesky bluescreen occurred, but seeing as I haven't done it before, I'd like ...

  1. #1
    C++まいる!Cをこわせ! Elysia's Avatar
    Join Date
    Oct 2007
    Posts
    22,449

    Debugging crashdump

    I'm trying to figure out why that pesky bluescreen occurred, but seeing as I haven't done it before, I'd like to see if anyone could give any good information as to where to start on debugging the cause of this.
    Since, as usual, the screen did not provide any information about where the error occurred. The only thing I do know is
    0x1000008e (0xc0000006, 0x8060bf81, 0x8a86d5dc, 0x00000000).
    From what I'm told, it's a kernel exception.

    Information would be appreciated.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  2. #2
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    0x1000008e is "kernel mode trap not handled", and 0xC0000006 means "STATUS_IN_PAGE_ERROR" (or "EXCEPTION_IN_PAGE_ERROR"), which seems to indicate a "not-present page" in general.

    Edit:
    0x8060bf81 = EIP at exception
    0x8a86d5dc = Address being accessed.
    0x00000000 = read/write flag (0 = read).

    --
    Mats
    Last edited by matsp; 03-27-2008 at 07:54 AM.
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  3. #3
    C++まいる!Cをこわせ! Elysia's Avatar
    Join Date
    Oct 2007
    Posts
    22,449
    Does not help identify the culprit.
    But I'm guessing it means something along the lines that the kernel was starved for memory or because something screwed up and tried to use pages memory.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  4. #4
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    The EIP at crash should be possible to use to identify the culprit, but you need the loaded symbol table at the time of the crash. If you have WinDBG you can load the minidump and type "!analyze -v" to give you that.

    It may be that you are running low on memory and the page should be locked in memory, when it actually isn't, and thus gets paged out.

    --
    Mats
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  5. #5
    C++まいる!Cをこわせ! Elysia's Avatar
    Join Date
    Oct 2007
    Posts
    22,449
    It's true that there was a process that was frozen and eating up all virtual memory, but... I hope this isn't a Windows bugs, but merely a driver who was inproperly coded.
    I do, after all, have a whopping 3 GB of memory. It could easily page out something else.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  6. #6
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    If the driver writes weren't using the "make all unlocked memory unavailable" tool when writing the driver, it would seem a plausible explanation. I have yet to see Windows itself fail in this manner.

    --
    Mats
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  7. #7
    C++まいる!Cをこわせ! Elysia's Avatar
    Join Date
    Oct 2007
    Posts
    22,449
    Seems the culprit is "Procmon11.sys", at least according to WinDbg. At least it isn't Windows. That's good news.
    I'm uninstalling Process Monitor until they fix it.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Dev-C++: Problems with Breakpoint Debugging
    By Thileepan_Bala in forum C Programming
    Replies: 1
    Last Post: 01-17-2008, 09:48 AM
  2. Problem in debugging in Eclipse
    By Bargi in forum Linux Programming
    Replies: 1
    Last Post: 08-21-2007, 09:53 AM
  3. gdb no debugging symbols found
    By Laserve in forum Linux Programming
    Replies: 8
    Last Post: 09-17-2006, 08:56 AM
  4. Debugging book recommendation
    By dagans in forum Projects and Job Recruitment
    Replies: 1
    Last Post: 09-13-2005, 07:35 PM
  5. debugging directx apps
    By confuted in forum C++ Programming
    Replies: 1
    Last Post: 08-16-2003, 08:56 AM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21