1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

need help on reading the minidump!!

Discussion in 'Windows XP' started by robotbegone, Apr 1, 2010.

Thread Status:
Not open for further replies.
  1. robotbegone

    robotbegone Thread Starter

    Joined:
    Feb 5, 2008
    Messages:
    36
    So I have the minidump and I have the dumpchk.exe. What do I do now? I tried to db-click the dumpchk.exe but didn't seem to open anything.

    How do I load the .dmp file so I can read it?

    Thanks!
     

    Attached Files:

  2. Phantom010

    Phantom010 Trusted Advisor

    Joined:
    Mar 9, 2009
    Messages:
    34,796
    All 3 minidumps show the following. This is quite a generic error message:

    Loading Dump File [C:\Documents and Settings\Minidump\Mini040110-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
    Debug session time: Thu Apr 1 17:06:45.640 2010 (GMT-4)
    System Uptime: 0 days 0:02:32.203
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000000A, {4c, 2, 0, 804f8fec}
    Probably caused by : ntoskrnl.exe ( nt!PsGetProcessSectionBaseAddress+a )
    Followup: MachineOwner
    ---------
    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000004c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804f8fec, address which referenced memory
    Debugging Details:
    ------------------

    READ_ADDRESS: 0000004c
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!PsGetProcessSectionBaseAddress+a
    804f8fec 66394616 cmp word ptr [esi+16h],ax
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT
    BUGCHECK_STR: 0xA
    PROCESS_NAME: services.exe
    LAST_CONTROL_TRANSFER: from 86beb223 to 804f8fec
    STACK_TEXT:
    f79fbed0 86beb223 f0227370 00000000 00000000 nt!PsGetProcessSectionBaseAddress+0xa
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    f79fbed8 00000000 00000000 f79fbf14 f67aed47 0x86beb223

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!PsGetProcessSectionBaseAddress+a
    804f8fec 66394616 cmp word ptr [esi+16h],ax
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nt!PsGetProcessSectionBaseAddress+a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntoskrnl.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e9e60
    FAILURE_BUCKET_ID: 0xA_nt!PsGetProcessSectionBaseAddress+a
    BUCKET_ID: 0xA_nt!PsGetProcessSectionBaseAddress+a
    Followup: MachineOwner
    ---------
     
As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/914157

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice