TechSpot

Windows XP BSOD Minidump Debug Log

By Markvis14
Oct 23, 2008
Topic Status:
Not open for further replies.
  1. Hello guys,

    I'm getting BSOD's when playing games for like 1 month now.
    I did some research and found out I had to make a debug log.
    Here is my log so if anyone can tell me what is wrong and what I have to do.

    --------------------------------------------------------------------------------------------------------

    Unable to load image ati3duag.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ati3duag.dll
    *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {d, 0, 0, 0}

    Probably caused by : ati3duag.dll ( ati3duag+107e58 )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x7f_d

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: Wow.exe

    LAST_CONTROL_TRANSFER: from bf2a5e58 to e22ba90d

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    abfde90c bf2a5e58 e36fbac0 abfde9a0 e368e42c 0xe22ba90d
    abfde910 e36fbac0 abfde9a0 e368e42c bf2a5e82 ati3duag+0x107e58
    abfde914 abfde9a0 e368e42c bf2a5e82 e368e438 0xe36fbac0
    abfde918 e368e42c bf2a5e82 e368e438 e368e2e0 0xabfde9a0
    abfde9a0 00000000 7dccccce 7dccccce 7dccccce 0xe368e42c


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ati3duag+107e58
    bf2a5e58 ?? ???

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: ati3duag+107e58

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ati3duag

    IMAGE_NAME: ati3duag.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d99dc6

    FAILURE_BUCKET_ID: 0x7f_d_ati3duag+107e58

    BUCKET_ID: 0x7f_d_ati3duag+107e58

    Followup: MachineOwner
    ---------
  2. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,202

  3. Markvis14

    Markvis14 TS Rookie Topic Starter

    Okay ill give it a try thank you.
    And what is the best way to uninstall the display drivers?
  4. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,202

  5. Markvis14

    Markvis14 TS Rookie Topic Starter

    Thanks alot peterdiva !
    I can now play my games properly again. ( some weird text glitches in WoW though )
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.