locked
"The Instruction at 0x1e43dd34 referenced memory at ... RRS feed

  • Question

  • Is there any software available which could determine which module lies at (e.g)  0x1e43dd34 in which DLL, in a running session?
    Friday, August 9, 2013 11:22 AM

Answers

  • Is there any software available which could determine which module lies at (e.g)  0x1e43dd34 in which DLL, in a running session?

    ProcExp.  However, if you are getting a crash you would also be able to get it easily from a dump, e.g. using windbg.

     
    FYI



    Robert Aldwinckle
    ---

    • Marked as answer by Niki Han Tuesday, August 13, 2013 2:57 PM
    Friday, August 9, 2013 4:24 PM

All replies

  • you have problem in  memory 

    you can use this software and check the problem 

    http://www.memtest86.com/download.htm

    or check this link:

    https://support.steampowered.com/kb_article.php?ref=1274-uohk-5653



    MCSE | MCITP [x2] | ISMS27001

    Friday, August 9, 2013 11:30 AM
  • No I've used Memtest86 several times and it's all clear.

    The address changes each session but within each is consistent with all programs which crash. Most are followed by the same message from Werfault.exe

    Friday, August 9, 2013 3:59 PM
  • Is there any software available which could determine which module lies at (e.g)  0x1e43dd34 in which DLL, in a running session?

    ProcExp.  However, if you are getting a crash you would also be able to get it easily from a dump, e.g. using windbg.

     
    FYI



    Robert Aldwinckle
    ---

    • Marked as answer by Niki Han Tuesday, August 13, 2013 2:57 PM
    Friday, August 9, 2013 4:24 PM
  • Robert, were you guessing ProcExp or do you actually know a way of searching from  a memory location in it?

    Now windbg works, but it's VERY tedious!

    Friday, August 23, 2013 7:38 AM
  • Now windbg works, but it's VERY tedious!

    Either way you get a list of modules and address ranges.  You know the address of your crash.   You find a module whose address range spans that.   Straightforward.  So tedious how?


    Robert Aldwinckle
    ---

    Friday, August 23, 2013 8:41 AM
  • No, Robert, you get a list of the modules of a PARTICULAR program. The one I'm looking for has already crashed, but the DLL which caused that also (very probably, from the session-consistancy of the address) serves another program. Also, you only (AFAICS) get start addresses and size - the DLL can be fragmented in the true memory-map so where's your "range" ?
    Friday, August 23, 2013 1:27 PM