• Registrarse
  • Iniciar sesión


  • Resultados 1 al 2 de 2

    Error:KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 1000008E, {c0000005, 80637e33, ba2c799c, 0}

    Resumen del tema: Error:KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 1000008E, {c0000005, 80637e33, ba2c799c, 0} - Hola. Tengo la pantalla azul (volcado de memoria) de la cual creo soy culpable: descuidadamente actualicé la Bios sin tomar ninguna precaución y empezaron los problemas con mi PC. Lo último es la pantalla azul ...

    1. #1
      Usuario Avatar de compungido
      Registrado
      may 2011
      Ubicación
      En mi casa
      Mensajes
      42

      Error:KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 1000008E, {c0000005, 80637e33, ba2c799c, 0}

      Hola. Tengo la pantalla azul (volcado de memoria) de la cual creo soy culpable: descuidadamente actualicé la Bios sin tomar ninguna precaución y empezaron los problemas con mi PC. Lo último es la pantalla azul que aún no puedo solucionar, copio el texto del último volcado, ojalá puedan ayudarme. Gracias.


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


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

      Symbol search path is: *** Invalid ***
      ************************************************** **************************
      * Symbol loading may be unreliable without a symbol search path. *
      * Use .symfix to have the debugger choose a symbol path. *
      * After setting your symbol path, use .reload to refresh symbol locations. *
      ************************************************** **************************
      Executable search path is:
      ************************************************** *******************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      ************************************************** *******************
      Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
      *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
      Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
      Product: WinNt
      Machine Name:
      Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
      Debug session time: Sat Aug 11 01:16:45.968 2012 (GMT-4)
      System Uptime: 0 days 0:05:41.687
      ************************************************** *******************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      ************************************************** *******************
      Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
      *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
      Loading Kernel Symbols
      .................................................. .............
      .................................................. .............
      Loading User Symbols
      Loading unloaded module list
      .....
      ************************************************** *****************************
      * *
      * Bugcheck Analysis *
      * *
      ************************************************** *****************************

      Use !analyze -v to get detailed debugging information.

      BugCheck 1000008E, {c0000005, 80637e33, ba2c799c, 0}

      *** WARNING: Unable to verify timestamp for mssmbios.sys
      *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
      ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

      ************************************************** ***********************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      ************************************************** ***********************
      ************************************************** ***********************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      ************************************************** ***********************
      ************************************************** *******************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      ************************************************** *******************
      ************************************************** *******************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      ************************************************** *******************
      Probably caused by : ntkrnlpa.exe ( nt+160e33 )

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

      1: 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: 80637e33, The address that the exception occurred at
      Arg3: ba2c799c, Trap Frame
      Arg4: 00000000

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

      ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

      ************************************************** ***********************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      ************************************************** ***********************
      ************************************************** ***********************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      ************************************************** ***********************
      ************************************************** *******************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      ************************************************** *******************
      ************************************************** *******************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      ************************************************** *******************

      ADDITIONAL_DEBUG_TEXT:
      Use '!findthebuild' command to search for the target build information.
      If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

      MODULE_NAME: nt

      FAULTING_MODULE: 804d7000 nt

      DEBUG_FLR_IMAGE_TIMESTAMP: 4fa3cc43

      EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

      FAULTING_IP:
      nt+160e33
      80637e33 ?? ???

      TRAP_FRAME: ba2c799c -- (.trap 0xffffffffba2c799c)
      Unable to read trap frame at ba2c799c

      CUSTOMER_CRASH_COUNT: 6

      DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

      BUGCHECK_STR: 0x8E

      LAST_CONTROL_TRANSFER: from e1038008 to 80637e33

      STACK_TEXT:
      WARNING: Stack unwind information not available. Following frames may be wrong.
      ba2c7a0c e1038008 e1038008 e12ca054 e12ca050 nt+0x160e33
      ba2c7a58 806304d8 e1038008 00790063 e1038008 0xe1038008
      ba2c7a74 80639696 e1038008 e12ca054 e1038008 nt+0x1594d8
      ba2c7a90 8063993b e1038008 0034f4e0 e14d0e94 nt+0x162696
      ba2c7aac 806399d8 e1038008 0034f4e0 e13904e4 nt+0x16293b
      ba2c7ae8 8063a216 e1038008 0032f608 e137060c nt+0x1629d8
      ba2c7b2c 8063a389 e1e52000 00000400 00000003 nt+0x163216
      ba2c7b5c 806268ba e1038008 000001b8 e1038008 nt+0x163389
      ba2c7ccc 80622176 00010002 ba2c7d64 ba2c7ce8 nt+0x14f8ba
      ba2c7cdc 8054168c 00000004 ba2c7d64 80500499 nt+0x14b176
      ba2c7ce8 80500499 badb0d00 ba2c7d60 00000000 nt+0x6a68c
      ba2c7d64 7c91e514 badb0d00 0007fe50 00000000 nt+0x29499
      ba2c7d68 badb0d00 0007fe50 00000000 00000000 0x7c91e514
      ba2c7d6c 0007fe50 00000000 00000000 00000000 0xbadb0d00
      ba2c7d70 00000000 00000000 00000000 00000000 0x7fe50


      STACK_COMMAND: kb

      FOLLOWUP_IP:
      nt+160e33
      80637e33 ?? ???

      SYMBOL_STACK_INDEX: 0

      SYMBOL_NAME: nt+160e33

      FOLLOWUP_NAME: MachineOwner

      IMAGE_NAME: ntkrnlpa.exe

      BUCKET_ID: WRONG_SYMBOLS

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

    2. #2
      Ex-Colaborador Avatar de Lucky!
      Registrado
      ene 2010
      Ubicación
      Catalunya
      Mensajes
      8.845

      Re: Error:KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 1000008E, {c0000005, 80637e33, ba2c799c

      Hola compungido

      Después de actualizar la Bios, le colocaste los Valores Optimizados por defecto?

      Es una opción que reza "Load Optimized Defaults" o "Load Fail Safe Defaults".

      Saludos