also @ TechSpot: Gamers spend more money on iOS than dedicated handhelds

Memory dump during Media Player 10 install

Discussion in 'Windows OS' started by scrappy, Jan 6, 2006.

  1. scrappy Newcomer, in training

    ok ive been fooling with this for way to long... recently i developed a "
    cannot create direct show player" while attempting to view video clips online *newest version of firefox* ....anyhow read some articles.. reinstalled directx and attempted to install media player 10.... while installing mp10 it gets to about 61% each time then i get the blue screen with the memdump error

    Stop : 0x0000008E (0xC0000005, 0x8056E2A2, 0xB89B4AE8, 0x00000000)

    so i did what i knew and checked the dump file but i have no idea what any of it meas...


    Microsoft (R) Windows Debugger Version 6.5.0003.7
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini010506-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Thu Jan 5 23:13:11.177 2006 (GMT-5)
    System Uptime: 0 days 0:07:02.757
    Loading Kernel Symbols
    ..........................................................................................................................
    Loading unloaded module list
    ..........
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 8056e2a2, b98e6ba4, 0}

    Probably caused by : ntoskrnl.exe ( nt!HvpGetCellMapped+5f )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8056e2a2, The address that the exception occurred at
    Arg3: b98e6ba4, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!HvpGetCellMapped+5f
    8056e2a2 8b4304 mov eax,[ebx+0x4]

    TRAP_FRAME: b98e6ba4 -- (.trap ffffffffb98e6ba4)
    ErrCode = 00000000
    eax=00001ff0 ebx=00001ff0 ecx=8225bfe0 edx=00000067 esi=e17edb60 edi=00000fff
    eip=8056e2a2 esp=b98e6c18 ebp=b98e6c60 iopl=0 nv up ei pl zr na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nt!HvpGetCellMapped+0x5f:
    8056e2a2 8b4304 mov eax,[ebx+0x4] ds:0023:00001ff4=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from 80579058 to 8056e2a2

    STACK_TEXT:
    b98e6c60 80579058 e17edb60 0cffffff e17edb60 nt!HvpGetCellMapped+0x5f
    b98e6c74 80578ed3 e17edb60 0cffffff c438082c nt!HvpGetHCell+0x10
    b98e6c90 80599b9e e17edb60 0cffffff e17edb60 nt!HvMarkCellDirty+0x30
    b98e6cb0 80590c8d e17edb60 0013f828 e10e2368 nt!CmpMarkKeyDirty+0x68
    b98e6cc8 80590dad e17edb60 0013f828 00000001 nt!CmpFreeKeyByCell+0x14
    b98e6cf8 80591025 e3946c48 b98e6d64 00beeca0 nt!CmDeleteKey+0x8c
    b98e6d58 804de7ec 00000552 00beecc8 7c90eb94 nt!NtDeleteKey+0x138
    b98e6d58 7c90eb94 00000552 00beecc8 7c90eb94 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00beecc8 00000000 00000000 00000000 00000000 0x7c90eb94


    FOLLOWUP_IP:
    nt!HvpGetCellMapped+5f
    8056e2a2 8b4304 mov eax,[ebx+0x4]

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!HvpGetCellMapped+5f

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

    STACK_COMMAND: .trap ffffffffb98e6ba4 ; kb

    FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

    BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f

    Followup: MachineOwner
    ---------
  2. cpc2004 Newcomer, in training Posts: 2,044

    Hi,

    Form the stack trace, I believe that it is software hive corruption. Use regedit to repair the software hive.

    b98e6c60 80579058 e17edb60 0cffffff e17edb60 nt!HvpGetCellMapped+0x5f
    b98e6c74 80578ed3 e17edb60 0cffffff c438082c nt!HvpGetHCell+0x10