locked
pantalla de la muerte2 RRS feed

  • Pregunta

  • hola de nuevo!!
    siento ser tan pesao pero mi olla no da pa mas,este es otro tipo de problema que me ha dado la pantallita de los cojo...,jeje,de verdad que agradeceria cualkier tipo de comentario,asta uno obsceno,ya puestos me da igual.


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini021110-01.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
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Feb 11 08:46:58.515 2010 (GMT+1)
    System Uptime: 0 days 0:07:10.221
    *********************************************************************
    * 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 D1, {2a8, 2, 0, a6ec8b32}

    *** 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.

    Unable to load image \SystemRoot\system32\DRIVERS\PRISMA02.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PRISMA02.sys
    *** ERROR: Module load completed but symbols could not be loaded for PRISMA02.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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 : PRISMA02.sys ( PRISMA02+42b32 )

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

     

    jueves, 11 de febrero de 2010 14:59

Respuestas

  • Hola erpixa,

    Qué tal? Espero que todo vaya bien :)

    Estoy seguro de que hay un problema de driver en tu equipo. Mira si los drivers son los correctos en el sitio del fabricante de tu equipo. Mira también si es posible bajar los ultimos controladores que los fabricantes tengan disponibles para tu versión de Windows. Además, echa un vistazo en los enlaces abajo para tener más informaciones acerca del prisma02.sys.

    http://support.dlink.com/downloads/

    Un saludo,

    Átilla Arruda - Microsoft Corporation
    jueves, 11 de febrero de 2010 16:26
    Moderador
  • Eso era para que tuvieses mas info sobre el driver que estaba fallando que seria de la tarjeta de red y el enlace supongoq que para el soporte de dlink y para que buscases el driver mas actual...

    Saludos!
    sábado, 13 de febrero de 2010 22:13

Todas las respuestas

  • Hola,tengo el windows xp professional con service pack3,no se como expilcar toda mi odisea pero os dejo una copia que he sacado del error de la temible pantalla azul:

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


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.091208-2036
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Feb 11 08:57:13.718 2010 (GMT+1)
    System Uptime: 0 days 0:02:04.407
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...
    Loading User Symbols

    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {2a8, 2, 0, a83afb32}

    *** ERROR: Module load completed but symbols could not be loaded for PRISMA02.sys
    Probably caused by : PRISMA02.sys ( PRISMA02+42b32 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 000002a8, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: a83afb32, address which referenced memory

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


    READ_ADDRESS:  000002a8

    CURRENT_IRQL:  2

    FAULTING_IP:
    PRISMA02+42b32
    a83afb32 6683bea802000000 cmp     word ptr [esi+2A8h],0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  b84dfc34 -- (.trap 0xffffffffb84dfc34)
    ErrCode = 00000000
    eax=89df0010 ebx=0000096c ecx=00000005 edx=8a247108 esi=00000000 edi=8a7d9000
    eip=a83afb32 esp=b84dfca8 ebp=b84dfcbc iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    PRISMA02+0x42b32:
    a83afb32 6683bea802000000 cmp     word ptr [esi+2A8h],0   ds:0023:000002a8=????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from a83afb32 to 80544718

    STACK_TEXT: 
    b84dfc34 a83afb32 badb0d00 8a247108 8ae27008 nt!KiTrap0E+0x238
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b84dfcbc a839de8f 89df0010 8a247108 8a7d9000 PRISMA02+0x42b32
    b84dfce8 a838f6de 89df0010 8a7f6818 b84dfd24 PRISMA02+0x30e8f
    b84dfd08 a8384cd3 8a7d9000 b84dfd24 8a7d9000 PRISMA02+0x226de
    b84dfd2c a8386a3f 8ac96880 8a7d9000 8a7db340 PRISMA02+0x17cd3
    b84dfd44 a8387463 8ac96880 8a16e8f8 8a16e810 PRISMA02+0x19a3f
    b84dfd54 a839285e 8a7d9000 8a16e8d8 80564820 PRISMA02+0x1a463
    b84dfd6c b7ccabfe 8a16e8d0 8a7d9000 b84dfdac PRISMA02+0x2585e
    b84dfd7c 80538789 8a16e8d0 00000000 8b02cc98 NDIS!ndisWorkItemHandler+0xe
    b84dfdac 805cff72 8a16e8d0 00000000 00000000 nt!ExpWorkerThread+0xef
    b84dfddc 8054611e 8053869a 00000000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    PRISMA02+42b32
    a83afb32 6683bea802000000 cmp     word ptr [esi+2A8h],0

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  PRISMA02+42b32

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: PRISMA02

    IMAGE_NAME:  PRISMA02.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  440fd0b3

    FAILURE_BUCKET_ID:  0xD1_PRISMA02+42b32

    BUCKET_ID:  0xD1_PRISMA02+42b32

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

    agradeceria cualquier tipo de ayuda,como si me mandais a otra pagina,pero confio en vosotros,jejeje,gracias!!.
    Por cierto el archivo prisma02.sys se que se refiere al modem de telefonica,cualkier consulta me la haceis saber,deuuuuu!!!

    jueves, 11 de febrero de 2010 14:51
  • Hola erpixa,

    Qué tal? Espero que todo vaya bien :)

    Estoy seguro de que hay un problema de driver en tu equipo. Mira si los drivers son los correctos en el sitio del fabricante de tu equipo. Mira también si es posible bajar los ultimos controladores que los fabricantes tengan disponibles para tu versión de Windows. Además, echa un vistazo en los enlaces abajo para tener más informaciones acerca del prisma02.sys.

    http://support.dlink.com/downloads/

    Un saludo,

    Átilla Arruda - Microsoft Corporation
    jueves, 11 de febrero de 2010 16:26
    Moderador
  • hola atlla!!
    Gracias por tu respuesta tio!!,creia que perdia la informacion,creo que lo he hecho todo lo que me has dicho y ya no me sale la pantallita,(de momento).
    El link no tengo ni idea de que hacer en esa pagina,jejeje,yamame limitado!!,jejej,deuuuuuuuuu!!!
    viernes, 12 de febrero de 2010 21:14
  • Eso era para que tuvieses mas info sobre el driver que estaba fallando que seria de la tarjeta de red y el enlace supongoq que para el soporte de dlink y para que buscases el driver mas actual...

    Saludos!
    sábado, 13 de febrero de 2010 22:13
  • Holas, aqui va mi blue screen . me salta siempre cuando intento iniciar un juego online ( pangya ), aver si me podeis ayudar un pokito ;)

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


    Loading Dump File [C:\Windows\Minidump\Mini022510-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 6000.16575.x86fre.vista_gdr.071009-1548
    Machine Name:
    Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
    Debug session time: Thu Feb 25 15:45:18.622 2010 (GMT+1)
    System Uptime: 0 days 0:25:00.485
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 82401674, 8b88ebc8, 8b88e8c4}

    *** WARNING: Unable to verify timestamp for gt72ubus.sys
    *** ERROR: Module load completed but symbols could not be loaded for gt72ubus.sys
    Probably caused by : gt72ubus.sys ( gt72ubus+a0e1 )

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

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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: 82401674, The address that the exception occurred at
    Arg3: 8b88ebc8, Exception Record Address
    Arg4: 8b88e8c4, Context Record Address

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


    OVERLAPPED_MODULE: Address regions for 'int15' and 'parport.sys' overlap

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

    FAULTING_IP:
    nt!IofCallDriverSpecifyReturn+41
    82401674 8b4108          mov     eax,dword ptr [ecx+8]

    EXCEPTION_RECORD:  8b88ebc8 -- (.exr 0xffffffff8b88ebc8)
    ExceptionAddress: 82401674 (nt!IofCallDriverSpecifyReturn+0x00000041)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00000008
    Attempt to read from address 00000008

    CONTEXT:  8b88e8c4 -- (.cxr 0xffffffff8b88e8c4)
    eax=84c5f500 ebx=00000000 ecx=00000000 edx=00000016 esi=84c5f410 edi=8f28a030
    eip=82401674 esp=8b88ec90 ebp=8b88ecac iopl=0         nv up ei ng nz ac po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
    nt!IofCallDriverSpecifyReturn+0x41:
    82401674 8b4108          mov     eax,dword ptr [ecx+8] ds:0023:00000008=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  3

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

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

    EXCEPTION_PARAMETER1:  00000000

    EXCEPTION_PARAMETER2:  00000008

    READ_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
    Unable to read MiSystemVaType memory at 825117e0
     00000008

    FOLLOWUP_IP:
    gt72ubus+a0e1
    8d2fa0e1 ??              ???

    BUGCHECK_STR:  0x7E

    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

    LAST_CONTROL_TRANSFER:  from 8244b1fa to 82401674

    STACK_TEXT: 
    8b88ec90 8244b1fa 8f289ce0 8f289dc0 827a4d90 nt!IofCallDriverSpecifyReturn+0x41
    8b88ecac 8d2fa0e1 8f28a030 00000000 00000005 nt!PoRequestPowerIrp+0xd5
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8b88ecf4 8d26a710 8f289ce0 8817b0e0 a0fa1de0 gt72ubus+0xa0e1
    8b88ed10 8d2457dc 8817b028 00000000 8f28a030 usbhub!UsbhPdoIdleCC_Worker+0x134
    8b88ed30 8258c85a 8817b028 a0fa1de0 87d4b020 usbhub!UsbhHubWorker+0x50
    8b88ed44 82478fa0 86f667f8 00000000 87d4b020 nt!IopProcessWorkItem+0x23
    8b88ed7c 826254e0 86f667f8 8b885680 00000000 nt!ExpWorkerThread+0xfd
    8b88edc0 8249159e 82478ea3 80000000 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  gt72ubus+a0e1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: gt72ubus

    IMAGE_NAME:  gt72ubus.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4680fac5

    STACK_COMMAND:  .cxr 0xffffffff8b88e8c4 ; kb

    FAILURE_BUCKET_ID:  0x7E_gt72ubus+a0e1

    BUCKET_ID:  0x7E_gt72ubus+a0e1

    Followup: MachineOwner

    Gracias y Saludos !!!

    jueves, 25 de febrero de 2010 15:55