none
Stackhash: Faulty module RRS feed

  • Question

  • Hi,

    While trying to run an exe I just built (namd2.exe), the program crashed with the following issues:

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    namd2.exe
      Application Version:    0.0.0.0
      Application Timestamp:    487c5e92
      Fault Module Name:    StackHash_7fed
      Fault Module Version:    6.0.6001.18000
      Fault Module Timestamp:    4791adec
      Exception Code:    c0000374
      Exception Offset:    00000000000a6e97
      OS Version:    6.0.6001.2.1.0.274.10
      Locale ID:    1033
      Additional Information 1:    7fed
      Additional Information 2:    90bd527864f46f496069cdf0605b7b57
      Additional Information 3:    25eb
      Additional Information 4:    02fcd364b3a8608abb6bfa6f15a973fc

    Any help on this?
    Wednesday, July 16, 2008 11:49 AM

Answers

  • 0xc0000374 = STATUS_HEAP_CORRUPTION.  That happens, good luck finding your pointer bug.
    Hans Passant.
    • Marked as answer by Yan-Fei Wei Monday, July 21, 2008 10:43 AM
    Wednesday, July 16, 2008 1:09 PM
    Moderator
  •  

    Hi,

    As nobugz stated, there is a heap corruption occurring in the application.

    Generally, heap corruption may occur as a result of several types of programmatic errors involving heap processing. An application may allocate a block of heap memory and write beyond the end of the block. Another scenario may involve an attempt to free a block of heap that has already been freed. It is also possible to corrupt a heap location by writing to a location using data that is invalid.

    To troubleshoot and solve this issue, I suggest you use Pageheap.exe tool. There is an article on usage of Pageheap.exe, you can take as reference.

    http://support.microsoft.com/kb/286470

    YanFei Wei

    Best Regards!


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Yan-Fei Wei Monday, July 21, 2008 10:43 AM
    Friday, July 18, 2008 6:32 AM

All replies

  • 0xc0000374 = STATUS_HEAP_CORRUPTION.  That happens, good luck finding your pointer bug.
    Hans Passant.
    • Marked as answer by Yan-Fei Wei Monday, July 21, 2008 10:43 AM
    Wednesday, July 16, 2008 1:09 PM
    Moderator
  •  

    Hi,

    As nobugz stated, there is a heap corruption occurring in the application.

    Generally, heap corruption may occur as a result of several types of programmatic errors involving heap processing. An application may allocate a block of heap memory and write beyond the end of the block. Another scenario may involve an attempt to free a block of heap that has already been freed. It is also possible to corrupt a heap location by writing to a location using data that is invalid.

    To troubleshoot and solve this issue, I suggest you use Pageheap.exe tool. There is an article on usage of Pageheap.exe, you can take as reference.

    http://support.microsoft.com/kb/286470

    YanFei Wei

    Best Regards!


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Yan-Fei Wei Monday, July 21, 2008 10:43 AM
    Friday, July 18, 2008 6:32 AM