• Registrarse
  • Iniciar sesión


  • Resultados 1 al 2 de 2

    Pantalla azul DRIVER_POWER_STATE_FAILURE, no logro identificar el driver que falla

    Resumen del tema: Pantalla azul DRIVER_POWER_STATE_FAILURE, no logro identificar el driver que falla - Estimados Tengo un pequño problemita con mi portatil Lenovo G470 y agradeceria si alguien me puede ayudar. Me arroja blue screen DRIVER_POWER_STATE_FAILURE periodicamente, pero no logro identificar que driver ocasiona el problema. El siguiente es ...

    1. #1
      Usuario Avatar de carrascofd
      Registrado
      ene 2013
      Ubicación
      Argentina
      Mensajes
      3

      Pantalla azul DRIVER_POWER_STATE_FAILURE, no logro identificar el driver que falla

      Estimados

      Tengo un pequño problemita con mi portatil Lenovo G470 y agradeceria si alguien me puede ayudar.
      Me arroja blue screen DRIVER_POWER_STATE_FAILURE periodicamente, pero no logro identificar que driver ocasiona el problema.

      El siguiente es el analisis del MEMORY.DMP con WinDbg:


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


      Loading Dump File [C:\Windows\MEMORY.DMP]
      Kernel Summary Dump File: Only kernel address space is 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+ *
      *********************************************************************
      *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
      Windows 7 Kernel Version 7600 MP (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS
      Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
      Machine Name:
      Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c59e70
      Debug session time: Thu Jan 17 12:08:25.852 2013 (UTC - 3:00)
      System Uptime: 0 days 0:59:08.022
      *********************************************************************
      * 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+ *
      *********************************************************************
      *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
      Loading Kernel Symbols
      ...............................................................
      ................................................................
      .............................
      Loading User Symbols

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

      Use !analyze -v to get detailed debugging information.

      BugCheck 9F, {3, fffffa8005cbfa00, fffff80000b9c4d8, fffffa8006e1ea20}

      ***** 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!_DEVICE_OBJECT ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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_POWER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IO_STACK_LOCATION ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_DEVICE_OBJECT ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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 : ntkrnlmp.exe ( nt!wcsncat_s+1defb )

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

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

      DRIVER_POWER_STATE_FAILURE (9f)
      A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
      Arguments:
      Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
      Arg2: fffffa8005cbfa00, Physical Device Object of the stack
      Arg3: fffff80000b9c4d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
      Arg4: fffffa8006e1ea20, The blocked IRP

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

      ***** 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!_DEVICE_OBJECT ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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_POWER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IO_STACK_LOCATION ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_IRP ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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!_DEVICE_OBJECT ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** 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 ***
      *** ***
      *************************************************************************

      ADDITIONAL_DEBUG_TEXT:
      You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

      MODULE_NAME: nt

      FAULTING_MODULE: fffff80002a1d000 nt

      DEBUG_FLR_IMAGE_TIMESTAMP: 503f857d

      DRVPOWERSTATE_SUBCODE: 3

      DEVICE_OBJECT: fffffa8005cbfa00

      DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

      BUGCHECK_STR: 0x9F

      CURRENT_IRQL: 0

      LAST_CONTROL_TRANSFER: from fffff80002afafd3 to fffff80002a8d5c0

      STACK_TEXT:
      fffff800`00b9c488 fffff800`02afafd3 : 00000000`0000009f 00000000`00000003 fffffa80`05cbfa00 fffff800`00b9c4d8 : nt!KeBugCheckEx
      fffff800`00b9c490 fffff800`02a99702 : fffff800`00b9c5d8 fffff800`00b9c5d8 00000000`00000001 00000000`00000000 : nt!wcsncat_s+0x1defb
      fffff800`00b9c530 fffff800`02a989c6 : fffff800`02c3c700 00000000`0003786b 00000000`00000000 00000000`00000000 : nt!ExReleaseResourceAndLeavePriorityRegion+0xba
      fffff800`00b9c5a0 fffff800`02a995de : 00000008`42c9565d fffff800`00b9cc18 00000000`0003786b fffff800`02c09fe8 : nt!KeRemoveQueueEx+0xb66
      fffff800`00b9cbf0 fffff800`02a98d37 : 00000001`d9f8e7c2 00000001`0003786b 00000001`d9f8e73c 00000000`0000006b : nt!ExEnterPriorityRegionAndAcquireResourceShared+0x1f6
      fffff800`00b9cc90 fffff800`02a95d9a : fffff800`02c06e80 fffff800`02c14c40 00000000`00000002 fffff880`00000000 : nt!KeRemoveQueueEx+0xed7
      fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KeUpdateSystemTime+0x47a


      STACK_COMMAND: kb

      FOLLOWUP_IP:
      nt!wcsncat_s+1defb
      fffff800`02afafd3 cc int 3

      SYMBOL_STACK_INDEX: 1

      SYMBOL_NAME: nt!wcsncat_s+1defb

      FOLLOWUP_NAME: MachineOwner

      IMAGE_NAME: ntkrnlmp.exe

      BUCKET_ID: WRONG_SYMBOLS

      Followup: MachineOwner




      Tambien analizé los minidump con el BlueScreenView marcando Sólo controladores encontrados en la pila.
      Este me arroja como causante del problema al controlador ntoskrnl.exe

      Espero alguien me pueda ayudar a solucionar este problema que me esta volviendo loco.

      Desde ya muchas gracias.
      Saludos.
      Fernando.

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

      Re: Pantalla azul DRIVER_POWER_STATE_FAILURE, no logro identificar el driver que fall

      Hola Fernando Bienvenido al Forospyware!

      Puedes subirnos una captura de pantalla de Bluescreenview? --> ¿Cómo subir imágenes al Foro? *TUTORIAL*

      Y también un reporte de Aida64, por favor:


      • Descarga e instala Aida64.
      • Vas a Computadora > Resumen (clic derecho) > Informe rápido > Texto sin formato.
      • También, vas a Computadora > Sensor (clic dcho.) > Informe rápido > Texto sin formato.
      • Copias y pegas los resultados en tu próxima respuesta (la parte final de Debug PCI no hace falta en ninguno de los 2 informes, ahórratela)


      Si el PC es portátil
      o de marca, dinos la idem y el modelo.

      Saludos