none
pantallazo azul windows 7 x64 (ntoskrnl.exe)

    Question

  • estaba navegando por net, escuchando musica y por MSN. cuando de pronto se puso azul la pantalla y me salio este error (descripcion mas abajo). mi notebook es nuevo tiene un mes o dos solamente y la verdad no entiendo por que paso esto.

    mi notebook es un Asus;

    Intel® HD Graphics (Core i3)

    Report Date:            4/27/2011
    Report Time[hr:mm:ss]:        2:1:3
    Driver Version:            8.15.10.2302
    Operating System:        Windows 7  Service Pack 1(6.1.7601)
    Default Language:        Spanish (Chile)
    DirectX* Version:        10.0
    Physical Memory:        2924 MB
    Minimum Graphics Memory:    32 MB
    Maximum Graphics Memory:    1270 MB
    Graphics Memory in Use:        75 MB
    Processor:            Intel64 Family 6 Model 37 Stepping 5
    Processor Speed:        2527 MHz
    Vendor ID:            8086
    Device ID:            0046
    Device Revision:        18

    *   Accelerator Information   *
    Accelerator in Use:        Intel(R) HD Graphics
    Video BIOS:            1930.0
    Current Graphics Mode:        1366 by 768

    *   Devices Connected to the Graphics Accelerator   *
    Active Notebook Displays: 1

    *    Built-in Display    *
    Monitor Name:            Generic PnP Monitor
    Display Type:            Digital
    Gamma Value:            2,2
    DDC2 Protocol:            Supported

    Maximum Image Size:
    Horizontal:            13,78 pulgadas
    Vertical:            07,48 pulgadas

    Monitor Supported Modes:
    1366 by 768 (60 Hz)

    Display Power Management Support:
    Standby Mode:            Not Supported
    Suspend Mode:            Not Supported
    Active Off Mode:        Not Supported

    Raw EDID:
    00 FF FF FF FF FF FF 00 30 E4 50 02 00 00 00 00
    00 14 01 03 80 23 13 78 0A C2 D5 9C 60 55 9E 26
    19 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
    01 01 01 01 01 01 3E 1C 56 A0 50 00 16 30 30 20
    35 00 59 C2 10 00 00 19 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 FE 00 4C
    47 20 44 69 73 70 6C 61 79 0A 20 20 00 00 00 FE
    00 4C 50 31 35 36 57 48 32 2D 54 4C 45 41 00 FD

     

    DESCRIPCION DEL PROBLEMA: (alguien tiene idea como resolver esto??? =s)

    Creado por uso BlueScreenView

    Archivo de volcado Hora del fallo Cadena de comprobación de error Código de comprobación de error Parámetro 1 Parámetro 2 Parámetro 3 Parámetro 4 Causado por controlador Causado por dirección Descripción Nombre Companía Versión Proceso Computer Name Full Path Processors Count Major Version Minor Version Dump File Size
    042711-23462-01.dmp 27-04-2011 1:34:36 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02f69909 fffff880`093e1a50 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+80640 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) x64
    C:\Windows\Minidump\042711-23462-01.dmp 4 15 7601

    374.248

    Wednesday, April 27, 2011 5:18 AM

Answers

  • Creo que he podido solucionarlo, claro despues de leer e investigar un poco por la net. sacando por descarte encontre que programa era el responsable del BSD, por ay lei que la mayoria de estos problemas se dan por la poca compatibilidad del windows 7 hacia aplicaciones anteriores, y busque por la pagina del autor el programa y vi que era version 32x, segun see deberia correr sin problemas en mi version 64x, pero tambien lei que algunos programas de 32x pueden ser incompatibles con versiones posteriores, por los controladores del programa mismo. tengo mi windows actualizado a full, asi que no sabia por que ocurria el problema. me descargue el programa updatestar que busca los programas de la pc e indica las actualizaciones mas reciente de estos, a mi sorpresa indicaba que tenia programas desactualizados del sistema, siendo que en mi pc indicaba tener las ultimas versiones, los descargue e reinstale y ay me marco en el programa que tenia las ultimas versiones, supongo que se instalaron mal o se dañaron por algun motivo por eso no marcaban como actualizadas. reinicie la pc y abri el programa que me generaba el problema y ya no sale la famosa pantallita molesta =).  dejo esto por si a alguien le pueda servir, ya que di vuelta mucho tiempo por alguna solucion. dejo los pasos a seguir que me sirvieron:

     

    1) ir a updatestar y descargar el programa

    2) instalarlo y correr el programa

    3) actualizar los componentes del sistema que se marquen como desactualizados

    descargarlos e instalarlos, ojo!! aunque tengan instalada la ultima version en su pc y en el programa muestre que necesitan actualizarce... volver a instalarla, en mi caso decia que tenia instalada la version 1.1 de netframework xD, siendo que tenia instalada la version 4.

    4) reinstalar y fin del suplicio =D

     

    imagen del programa desactualizado:

     

    Uploaded with

    salu2:

    Tuesday, May 03, 2011 5:20 PM

All replies

  • Hola, analízalo siguiendo este artículo y déjanos los resultados:
    http://www.multingles.net/docs/jmt/bsod.htm
    Wednesday, April 27, 2011 1:05 PM
    Moderator
  • Hola, analízalo siguiendo este artículo y déjanos los resultados:
    http://www.multingles.net/docs/jmt/bsod.htm

    espero que sea esto lo que me pedias...

     

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


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

    Symbol search path is: SRV*d:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e48e90
    Debug session time: Sun May  1 22:46:47.422 2011 (UTC - 4:00)
    System Uptime: 0 days 0:32:20.968
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1904fb, fffff8800979ec58, fffff8800979e4b0, fffff880014d0527}

    Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

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

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

    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff8800979ec58
    Arg3: fffff8800979e4b0
    Arg4: fffff880014d0527

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


    EXCEPTION_RECORD:  fffff8800979ec58 -- (.exr 0xfffff8800979ec58)
    ExceptionAddress: fffff880014d0527 (Ntfs!NtfsFindPrefixHashEntry+0x00000000000001fe)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff8800979e4b0 -- (.cxr 0xfffff8800979e4b0)
    rax=fffff8a002e18000 rbx=0030007700790038 rcx=0000000000000688
    rdx=0000000000000004 rsi=fffff8a000302390 rdi=fffffa800351c350
    rip=fffff880014d0527 rsp=fffff8800979ee90 rbp=0000000000005000
     r8=000000001fb22f44  r9=0000000000000000 r10=0000000000000003
    r11=fffff8800979eed8 r12=fffff8800979f190 r13=fffff8800979f440
    r14=0000000000000344 r15=0000000000000f44
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    Ntfs!NtfsFindPrefixHashEntry+0x1fe:
    fffff880`014d0527 44394310        cmp     dword ptr [rbx+10h],r8d ds:002b:00300077`00790048=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  downloader.exe

    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_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:  0000000000000000

    EXCEPTION_PARAMETER2:  ffffffffffffffff

    READ_ADDRESS:  ffffffffffffffff

    FOLLOWUP_IP:
    Ntfs!NtfsFindPrefixHashEntry+1fe
    fffff880`014d0527 44394310        cmp     dword ptr [rbx+10h],r8d

    FAULTING_IP:
    Ntfs!NtfsFindPrefixHashEntry+1fe
    fffff880`014d0527 44394310        cmp     dword ptr [rbx+10h],r8d

    BUGCHECK_STR:  0x24

    LAST_CONTROL_TRANSFER:  from fffff880014cefd2 to fffff880014d0527

    STACK_TEXT: 
    fffff880`0979ee90 fffff880`014cefd2 : fffffa80`02f09b90 fffffa80`0351c350 fffff8a0`00302390 fffff800`02c9a201 : Ntfs!NtfsFindPrefixHashEntry+0x1fe
    fffff880`0979efc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsFindStartingNode+0x452


    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+1fe

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Ntfs

    IMAGE_NAME:  Ntfs.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

    STACK_COMMAND:  .cxr 0xfffff8800979e4b0 ; kb

    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+1fe

    BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+1fe

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

    Monday, May 02, 2011 4:38 AM
  • Hola, analízalo siguiendo este artículo y déjanos los resultados:
    http://www.multingles.net/docs/jmt/bsod.htm

    espero que sea esto lo que me pedias...

     

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


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

    Symbol search path is: SRV*d:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e48e90
    Debug session time: Sun May  1 22:46:47.422 2011 (UTC - 4:00)
    System Uptime: 0 days 0:32:20.968
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1904fb, fffff8800979ec58, fffff8800979e4b0, fffff880014d0527}

    Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

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

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

    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff8800979ec58
    Arg3: fffff8800979e4b0
    Arg4: fffff880014d0527

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


    EXCEPTION_RECORD:  fffff8800979ec58 -- (.exr 0xfffff8800979ec58)
    ExceptionAddress: fffff880014d0527 (Ntfs!NtfsFindPrefixHashEntry+0x00000000000001fe)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff8800979e4b0 -- (.cxr 0xfffff8800979e4b0)
    rax=fffff8a002e18000 rbx=0030007700790038 rcx=0000000000000688
    rdx=0000000000000004 rsi=fffff8a000302390 rdi=fffffa800351c350
    rip=fffff880014d0527 rsp=fffff8800979ee90 rbp=0000000000005000
     r8=000000001fb22f44  r9=0000000000000000 r10=0000000000000003
    r11=fffff8800979eed8 r12=fffff8800979f190 r13=fffff8800979f440
    r14=0000000000000344 r15=0000000000000f44
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    Ntfs!NtfsFindPrefixHashEntry+0x1fe:
    fffff880`014d0527 44394310        cmp     dword ptr [rbx+10h],r8d ds:002b:00300077`00790048=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  downloader.exe

    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_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:  0000000000000000

    EXCEPTION_PARAMETER2:  ffffffffffffffff

    READ_ADDRESS:  ffffffffffffffff

    FOLLOWUP_IP:
    Ntfs!NtfsFindPrefixHashEntry+1fe
    fffff880`014d0527 44394310        cmp     dword ptr [rbx+10h],r8d

    FAULTING_IP:
    Ntfs!NtfsFindPrefixHashEntry+1fe
    fffff880`014d0527 44394310        cmp     dword ptr [rbx+10h],r8d

    BUGCHECK_STR:  0x24

    LAST_CONTROL_TRANSFER:  from fffff880014cefd2 to fffff880014d0527

    STACK_TEXT: 
    fffff880`0979ee90 fffff880`014cefd2 : fffffa80`02f09b90 fffffa80`0351c350 fffff8a0`00302390 fffff800`02c9a201 : Ntfs!NtfsFindPrefixHashEntry+0x1fe
    fffff880`0979efc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsFindStartingNode+0x452


    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+1fe

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Ntfs

    IMAGE_NAME:  Ntfs.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

    STACK_COMMAND:  .cxr 0xfffff8800979e4b0 ; kb

    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+1fe

    BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefixHashEntry+1fe

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


    Es muy peligrosos usar programas como el downloader o P2P en la maquina real...

    Saludos :)

    Monday, May 02, 2011 7:39 AM
  • Creo que he podido solucionarlo, claro despues de leer e investigar un poco por la net. sacando por descarte encontre que programa era el responsable del BSD, por ay lei que la mayoria de estos problemas se dan por la poca compatibilidad del windows 7 hacia aplicaciones anteriores, y busque por la pagina del autor el programa y vi que era version 32x, segun see deberia correr sin problemas en mi version 64x, pero tambien lei que algunos programas de 32x pueden ser incompatibles con versiones posteriores, por los controladores del programa mismo. tengo mi windows actualizado a full, asi que no sabia por que ocurria el problema. me descargue el programa updatestar que busca los programas de la pc e indica las actualizaciones mas reciente de estos, a mi sorpresa indicaba que tenia programas desactualizados del sistema, siendo que en mi pc indicaba tener las ultimas versiones, los descargue e reinstale y ay me marco en el programa que tenia las ultimas versiones, supongo que se instalaron mal o se dañaron por algun motivo por eso no marcaban como actualizadas. reinicie la pc y abri el programa que me generaba el problema y ya no sale la famosa pantallita molesta =).  dejo esto por si a alguien le pueda servir, ya que di vuelta mucho tiempo por alguna solucion. dejo los pasos a seguir que me sirvieron:

     

    1) ir a updatestar y descargar el programa

    2) instalarlo y correr el programa

    3) actualizar los componentes del sistema que se marquen como desactualizados

    descargarlos e instalarlos, ojo!! aunque tengan instalada la ultima version en su pc y en el programa muestre que necesitan actualizarce... volver a instalarla, en mi caso decia que tenia instalada la version 1.1 de netframework xD, siendo que tenia instalada la version 4.

    4) reinstalar y fin del suplicio =D

     

    imagen del programa desactualizado:

     

    Uploaded with

    salu2:

    Tuesday, May 03, 2011 5:20 PM
  • Hola acaba de instalar el win7 64 bit encima de otro igual y la ora de reiniciar se pone en apagando.....casi media hora, he buscado por que me ha salido pantalla azul y he encontrado esto:

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


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

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`08789c32?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00235022?
    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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e4d670
    Debug session time: Thu Jul 19 15:00:49.140 2012 (UTC + 3:00)
    System Uptime: 0 days 0:19:06.968
    *********************************************************************
    * 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000009F, {4, 258, fffffa800674cb50, fffff80000b9c3d0}

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

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_ETHREAD                                   ***
    ***                                                                   ***
    *************************************************************************
    Implicit thread is now fffffa80`0674cb50
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_ETHREAD                                   ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_ETHREAD                                   ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_TRIAGE_9F_PNP                             ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_TRIAGE_PNP_DEVICE_COMPLETION_QUEUE                 ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_TRIAGE_PNP_DEVICE_COMPLETION_REQUEST                ***
    ***                                                                   ***
    *************************************************************************

    Thursday, July 19, 2012 2:17 PM

  • *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+8207a )

    Followup: MachineOwner

    Espero una respuesta o una ayuda por favor, gracias y salu2 mi correo es mmario66@yahoo.com

    Thursday, July 19, 2012 2:23 PM

  • *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+8207a )

    Followup: MachineOwner

    Espero una respuesta o una ayuda por favor, gracias y salu2 mi correo es mmario66@yahoo.com

    No has configurado los simbolos. Es necesario para que el informe sea mas completo.

    Revisa este articulo mio: http://multingles.net/docs/jmt/bsod.htm

    Un saludo,


    Jose Manuel Tella Llop news://jmtella.com

    Thursday, July 19, 2012 6:10 PM