• Registrarse
  • Iniciar sesión


  • Página 1 de 3 123 ÚltimoÚltimo
    Resultados 1 al 10 de 24

    Reinicio aleatorio en windows 7

    Resumen del tema: Reinicio aleatorio en windows 7 - Hola a todos, Abro este tema porque estoy deseperado, tengo un pc de hace un año que se reinicia de forma aleatoria. Una veces empieza a ir lento y acaba reiniciandoes y otras reinicia sin ...

    1. #1
      Usuario Avatar de pepeluxo
      Registrado
      ago 2011
      Ubicación
      madrid
      Mensajes
      12

      Reinicio aleatorio en windows 7

      Hola a todos,

      Abro este tema porque estoy deseperado, tengo un pc de hace un año que se reinicia de forma aleatoria. Una veces empieza a ir lento y acaba reiniciandoes y otras reinicia sin avisar.
      El pc es un Packard Bell, con Windows 7 64bits, intel quad core q9400, 8gb.
      No encuentro la garantia para que me lo reparen y he hecho todo lo que he creido posible sin resultado, siendo:

      - Cambio de ventilador del procesador por uno más potente.
      - Dispositivos aparentemente correctos.
      - Testeo mediante herramientas de stress, todo correcto (temperatura, cpu, ventilador, etc)
      - Testeo de la memoria medianta memtes 4.20.
      - Analisis completos de virus, rootkit, spyware, etc mediante varios programas, incluido online.

      Lo último que he hecho es mirar el minidump mediante Debuggin tool for windows 64 bits, pero no sé interpretarlo, por si alguien puede echarme una mano.

      Muchas gracias.


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


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

      Symbol search path is: *** Invalid ***
      ****************************************************************************
      * Symbol loading may be unreliable without a symbol search path. *
      * Use .symfix to have the debugger choose a symbol path. *
      * After setting your symbol path, use .reload to refresh symbol locations. *
      ****************************************************************************
      Executable search path is:
      *********************************************************************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      *********************************************************************
      Unable to load image 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 (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS Personal
      Machine Name:
      Kernel base = 0xfffff800`0361b000 PsLoadedModuleList = 0xfffff800`03860670
      Debug session time: Fri Aug 12 18:25:22.643 2011 (UTC + 2:00)
      System Uptime: 0 days 0:00:10.016
      *********************************************************************
      * 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 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
      Mini Kernel Dump does not contain unloaded driver list
      *******************************************************************************
      * *
      * Bugcheck Analysis *
      * *
      *******************************************************************************

      Use !analyze -v to get detailed debugging information.

      BugCheck 124, {0, fffffa8008a44038, 0, 0}

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

      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      Unable to load image PSHED.dll, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for PSHED.dll
      *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      Probably caused by : hardware

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

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

      WHEA_UNCORRECTABLE_ERROR (124)
      A fatal hardware error has occurred. Parameter 1 identifies the type of error
      source that reported the error. Parameter 2 holds the address of the
      WHEA_ERROR_RECORD structure that describes the error conditon.
      Arguments:
      Arg1: 0000000000000000, Machine Check Exception
      Arg2: fffffa8008a44038, Address of the WHEA_ERROR_RECORD structure.
      Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
      Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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

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

      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************

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

      FAULTING_MODULE: fffff8000361b000 nt

      DEBUG_FLR_IMAGE_TIMESTAMP: 0

      BUGCHECK_STR: 0x124_GenuineIntel

      CUSTOMER_CRASH_COUNT: 1

      DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

      CURRENT_IRQL: 0

      STACK_TEXT:
      fffff880`031a86b0 fffffa80`08a44038 : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`08a44038 : nt+0x4b16cc
      fffff880`031a86b8 00000000`00000001 : 00000000`00000000 00000000`00000000 fffffa80`08a44038 00000000`00000000 : 0xfffffa80`08a44038
      fffff880`031a86c0 00000000`00000000 : 00000000`00000000 fffffa80`08a44038 00000000`00000000 00000000`00000000 : 0x1


      STACK_COMMAND: kb

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: hardware

      IMAGE_NAME: hardware

      BUCKET_ID: WRONG_SYMBOLS

      Followup: MachineOwner
      ---------
      Última edición por pepeluxo fecha: 15/08/11 a las 20:42:35

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

      Re: Reinicio aleatorio en windows 7

      Hola pepeluxo Bienvenido al Forospyware!

      El análisis de WinDBG es un poco inconcreto y podría deberse a cualquier cosa

      Si tienes más archivos en la carpeta Minidump, analízalos mejor con esta herramienta:
      • Descarga y descomprime el programa BlueScreenView.
      • Descarga y descomprime también el Parche de Idioma Español de BlueScreenView.
      • Pon el archivo del parche (BlueScreenView_lng) en la carpeta BlueScreenView junto a los demás archivos, y ejecuta BlueScreenView.exe.
      • En su menú Opciones> Modo del panel inferior> marca Sólo controladores encontrados en la pila.
      • Realiza una captura de pantalla de la ventana (maximizada plis) y nos la pegas en tu próxima respuesta --> ¿Cómo subir imágenes al Foro? *TUTORIAL*
      También, por favor, dinos el modelo de Packard Bell que es, y adjunta un reporte de Everest que nos dará una idea de lo que compone tu compu:
      • Descarga e instala Everest. Aunque como verás la versión 5.50 está descontinuada, sirve igual, o si prefieres Aida64 Extreme también nos vale
      • 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)
      Esperamos tus noticias Chao

    3. #3
      Usuario Avatar de pepeluxo
      Registrado
      ago 2011
      Ubicación
      madrid
      Mensajes
      12

      Re: Reinicio aleatorio en windows 7

      Hola Lucky!

      ante todo agradecerte la rápida respuesta.
      Los datos que me solicitas son:

      - Efectivamente existen varios minidump, había muchos más, pero están borrados.
      - Me he fijado en todos se ajustan a dos patrones, fallo en ntoskrnl.exe y fallo en ntoskrnl.exe y hal.dll, adjunto capturas del bluescreenview de los dos. Yo no había diferenciado que se produjerran fallos diferentes, todos me parece iguales;






      - El modelo del PC es Packard Bell ixtreme X6580 SP

      - El resumen del pc es:

      --------[ AIDA64 Extreme Edition ]--------------------------------------------------------------------------------------

      Versión AIDA64 v1.80.1450/es
      Módulo de rendimiento 2.7.380-x64
      Página Web http://www.aida64.com/
      Tipo de informe Informe rápido [ TRIAL VERSION ]
      Computadora PC-VALSAIN
      Generador Oscar
      Sistema operativo Microsoft Windows 7 Home Premium 6.1.7601 (Win7 RTM)
      Fecha 2011-08-17
      Hora 23:54


      --------[ Resumen ]-----------------------------------------------------------------------------------------------------

      Computadora:
      Tipo de computadora ACPI x64-based PC
      Sistema operativo Microsoft Windows 7 Home Premium
      Service Pack del sistema operativo [ TRIAL VERSION ]
      Internet Explorer 9.0.8112.16421 (IE 9.0)
      DirectX DirectX 11.0
      Nombre de la computadora PC-VALSAIN
      Nombre de usuario Pepeluxo
      Dominio de inicio de sesión [ TRIAL VERSION ]
      Fecha / Hora 2011-08-17 / 23:54

      Motherboard:
      Tipo de CPU QuadCore Intel Core 2 Quad Q9400, 2666 MHz (8 x 333)
      Nombre del motherboard Acer EG43M
      Chipset del motherboard Intel Eaglelake G43
      Memoria del sistema [ TRIAL VERSION ]
      DIMM1: GU342G0ALEPR692C6F 2 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
      DIMM2: GU342G0ALEPR692C6F [ TRIAL VERSION ]
      DIMM3: GU342G0ALEPR692C6F [ TRIAL VERSION ]
      DIMM4: GU342G0ALEPR692C6F [ TRIAL VERSION ]
      Tipo de BIOS AMI (08/31/09)
      Puerto de comunicación LGE Bluetooth TransPort (COM5)

      Monitor:
      Placa de video ATI Radeon HD 4600 Series (1024 MB)
      Placa de video ATI Radeon HD 4600 Series (1024 MB)
      Aceleradora 3D ATI Radeon HD 4650 (RV730)
      Monitor LG L1917S [19" LCD] (160365987)

      Multimedia:
      Placa de sonido ATI Radeon HDMI @ ATI RV710/730/740 - High Definition Audio Controller
      Placa de sonido Realtek ALC888 @ Intel 82801JB ICH10 - High Definition Audio Controller

      Almacenamiento:
      Controlador IDE Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26
      Controlador IDE Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A20
      Disco rígido Generic Mini SD Reader USB Device
      Disco rígido Generic USB CF Reader USB Device
      Disco rígido Generic USB MS Reader USB Device
      Disco rígido Generic USB SD Reader USB Device
      Disco rígido Generic USB xD/SM Reader USB Device
      Disco rígido WDC WD10EADS-22M2B0 ATA Device (931 GB, IDE)
      Disco rígido WDC WD10EADS-22M2B0 ATA Device (931 GB, IDE)
      Disco óptico HL-DT-ST DVDRAM GH40N ATA Device
      Estado SMART de los discos rígidos OK

      Particiones:
      C: (NTFS) [ TRIAL VERSION ]
      D: (NTFS) 931.5 GB (167.5 GB libre)
      E: (NTFS) 458.5 GB (450.2 GB libre)
      Tamaño total [ TRIAL VERSION ]

      Dispositivos de entrada:
      Teclado Microsoft USB Dual Receiver Wireless Keyboard (IntelliType Pro)
      Mouse Microsoft USB Dual Receiver Wireless Mouse (IntelliPoint)
      Mouse Mouse PS/2 de Microsoft

      Red:
      Dirección IP primaria [ TRIAL VERSION ]
      Dirección MAC primaria 00-25-11-A2-C5-81
      Placa de red Intel(R) 82567V-2 Gigabit Network Connection (192. [ TRIAL VERSION ])
      Placa de red VirtualBox Host-Only Ethernet Adapter (192. [ TRIAL VERSION ])
      Módem LGE Virtual Modem

      Periféricos:
      Impresora Brother DCP-130C USB Printer
      Impresora Fax
      Impresora Microsoft XPS Document Writer
      Controlador FireWire VIA OHCI Compliant IEEE 1394 Host Controller (PHY: VIA VT6307)
      Controlador USB1 Intel 82801JB ICH10 - USB Universal Host Controller
      Controlador USB1 Intel 82801JB ICH10 - USB Universal Host Controller
      Controlador USB1 Intel 82801JB ICH10 - USB Universal Host Controller
      Controlador USB1 Intel 82801JB ICH10 - USB Universal Host Controller
      Controlador USB1 Intel 82801JB ICH10 - USB Universal Host Controller
      Controlador USB1 Intel 82801JB ICH10 - USB Universal Host Controller
      Controlador USB2 Intel 82801JB ICH10 - USB2 Enhanced Host Controller
      Controlador USB2 Intel 82801JB ICH10 - USB2 Enhanced Host Controller
      Dispositivo USB ANT USB Stick 2
      Dispositivo USB Brother DCP-130C USB
      Dispositivo USB Compatibilidad con impresoras USB
      Dispositivo USB Dispositivo compuesto USB
      Dispositivo USB Dispositivo compuesto USB
      Dispositivo USB Dispositivo de almacenamiento USB
      Dispositivo USB Dispositivo de almacenamiento USB
      Dispositivo USB Dispositivo de entrada USB
      Dispositivo USB Dispositivo de entrada USB
      Dispositivo USB Microsoft Hardware USB Keyboard
      Dispositivo USB Microsoft Hardware USB Mouse
      Dispositivo USB Microsoft Mouse and Keyboard Detection Driver (USB)
      Dispositivo USB WinTV MiniStick

      DMI:
      DMI Fabricante del BIOS American Megatrends Inc.
      DMI Versión del BIOS P01-A1
      DMI Fabricante del sistema Acer
      DMI Nombre del sistema Aspire M5802/M3802
      DMI Versión del sistema
      DMI Número de serie del sistema [ TRIAL VERSION ]
      DMI Fabricante del motherboard Acer
      DMI Nombre del motherboard EG43M
      DMI Versión del motherboard
      DMI Número de serie del motherboard [ TRIAL VERSION ]
      DMI Fabricante del chasis Acer
      DMI Versión del chasis
      DMI Número de serie del chasis [ TRIAL VERSION ]
      DMI Identificador del chasis [ TRIAL VERSION ]
      DMI Tipo de chasis Desktop Case
      DMI Sockets de memoria Total / Libres 4 / 0



      --------[ Debug - Video BIOS ]------------------------------------------------------------------------------------------

      C000:0000 U.z...........................IBM............... 761295520......
      C000:0040 ................11/18/08 22:36..4................c..4c......K...
      C000:0080 PA.S.*..............113-AB93400-100-PC.RV730.PCI_EXPRESS.DDR2.RV
      C000:00C0 730PRO DDR2 128B 600E/500M DVI+HDMI+VGA
      C000:0100 .. ... ...(C) 1988-2005, ATI Technologies Inc. .ATOMB
      C000:0140 IOSBK-ATI VER011.016.000.015.000000.SAB93400.100.441189 .88047
      C000:0180 . .B66801\Config.h...$...ATOM..s.d...........K.........
      C000:01C0 ....PCIR............z.......ATI ATOMBIOS.Y\...............G...0.
      C000:0200 ....)....V..../..LP. .^..fPfQfRfSfUfVfW..................f......
      C000:0240 f.(....'.2.......&..&..&.......L&.`&..&..........DP. u.....od..d
      C000:0280 .......LP....n...f.......fP. .]...fXt.. f....)...f_f^f]f[fZfYfX
      C000:02C0 .........F.f3..F...F..R......DZ..........f......M.f.\.f.L.;.u...
      C000:0300 f.^.f.N............>...u.........{...f....e.....@.....B.........
      C000:0340 ....|..l..~......p.........f.............f..f..f...PMID..XL.....
      C000:0380 ..........q....l.f.........................fPfR.1f...f....fZfX.f
      C000:03C0 PfR.1f...f....fZfX...<....u..:&..u..G.....Ou..FG...MR.....5.....


      --------[ Debug - Unknown ]---------------------------------------------------------------------------------------------

      Monitor ID SNY8400: Monitor PnP genérico [NoDB]
      Monitor Model SONY TV
      Optical HL-DT-ST DVDRAM GH40N ATA Device


      ------------------------------------------------------------------------------------------------------------------------

      The names of actual companies and products mentioned herein may be the trademarks of their respective owners.


      - El resumen de los sensores;
      --------[ AIDA64 Extreme Edition ]--------------------------------------------------------------------------------------

      Versión AIDA64 v1.80.1450/es
      Módulo de rendimiento 2.7.380-x64
      Página Web http://www.aida64.com/
      Tipo de informe Informe rápido [ TRIAL VERSION ]
      Computadora PC-VALSAIN
      Generador Pepeluxo
      Sistema operativo Microsoft Windows 7 Home Premium 6.1.7601 (Win7 RTM)
      Fecha 2011-08-17
      Hora 23:59


      --------[ Sensor ]------------------------------------------------------------------------------------------------------

      Propiedades del sensor:
      Tipo de sensor ITE IT8720F (ISA A10h)
      Tipo de sensor de la GPU Diode (ATI-Diode)
      Nombre del motherboard Acer EG43M
      Intrusión detectada en el chasis Sí

      Temperaturas:
      Motherboard 46 °C (115 °F)
      CPU 35 °C (95 °F)
      CPU n.º 1 / núcleo n.º 1 52 °C (126 °F)
      CPU n.º 1 / núcleo n.º 2 48 °C (118 °F)
      CPU n.º 1 / núcleo n.º 3 50 °C (122 °F)
      CPU n.º 1 / núcleo n.º 4 47 °C (117 °F)
      Aux 55 °C (131 °F)
      diodo GPU (DispIO) 74 °C (165 °F)
      diodo GPU (MemIO) 73 °C (163 °F)
      WDC WD10EADS-22M2B0 (WD-WCAV53264531) [ TRIAL VERSION ]
      WDC WD10EADS-22M2B0 (WD-WCAV53370846) [ TRIAL VERSION ]

      Coolers:
      CPU 1383 RPM
      GPU 41%

      Valores de voltaje:
      Núcleo de la CPU 1.152 V
      +1.1 V 1.120 V
      +3.3 V 3.344 V
      +5 V 4.919 V
      +12 V [ TRIAL VERSION ]
      Puesta en espera +5 V 4.946 V
      Batería VBAT 3.152 V
      Debug Info F 01E8 FFFF FFFF 0000 0000
      Debug Info T 55 46 35
      Debug Info V 48 B8 72 B7 BF 46 D1 B8 C5



      --------[ Debug - Video BIOS ]------------------------------------------------------------------------------------------

      C000:0000 U.z...........................IBM............... 761295520......
      C000:0040 ................11/18/08 22:36..4................c..4c......K...
      C000:0080 PA.S.*..............113-AB93400-100-PC.RV730.PCI_EXPRESS.DDR2.RV
      C000:00C0 730PRO DDR2 128B 600E/500M DVI+HDMI+VGA
      C000:0100 .. ... ...(C) 1988-2005, ATI Technologies Inc. .ATOMB
      C000:0140 IOSBK-ATI VER011.016.000.015.000000.SAB93400.100.441189 .88047
      C000:0180 . .B66801\Config.h...$...ATOM..s.d...........K.........
      C000:01C0 ....PCIR............z.......ATI ATOMBIOS.Y\...............G...0.
      C000:0200 ....)....V..../..LP. .^..fPfQfRfSfUfVfW..................f......
      C000:0240 f.(....'.2.......&..&..&.......L&.`&..&..........DP. u.....od..d
      C000:0280 .......LP....n...f.......fP. .]...fXt.. f....)...f_f^f]f[fZfYfX
      C000:02C0 .........F.f3..F...F..R......DZ..........f......M.f.\.f.L.;.u...
      C000:0300 f.^.f.N............>...u.........{...f....e.....@.....B.........
      C000:0340 ....|..l..~......p.........f.............f..f..f...PMID..XL.....
      C000:0380 ..........q....l.f.........................fPfR.1f...f....fZfX.f
      C000:03C0 PfR.1f...f....fZfX...<....u..:&..u..G.....Ou..FG...MR.....5.....


      --------[ Debug - Unknown ]---------------------------------------------------------------------------------------------

      Monitor ID SNY8400: Monitor PnP genérico [NoDB]
      Monitor Model SONY TV
      Optical HL-DT-ST DVDRAM GH40N ATA Device


      ------------------------------------------------------------------------------------------------------------------------

      The names of actual companies and products mentioned herein may be the trademarks of their respective owners.


      Muchas gracias de nuevo, espero que no se me haya olvidado nada...

      Salu2!!!!!!!!!!!!!!!!!

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

      Re: Reinicio aleatorio en windows 7

      En 1er lugar, decirte que si el PC está en garantía, hagas buen uso de ella, ya que las bluescreens apuntan a componentes críticos de Windows (Kernel).

      Y dicho ésto hay 2 cositas que me llaman la atención:
      • 1) En el reporte de Aida64 aparece como que el PC es un Acer Aspire M5802/M3802. Y en la web de Packard Bell no aparece el modelo ixtreme X6580 SP Un lío, vamos...
      DMI Fabricante del sistema Acer
      DMI Nombre del sistema Aspire M5802/M3802
      • 2) La temperatura de la ATI -aunque habrá quien diga que es normal- yo la encuentro un poco elevada:
      diodo GPU (DispIO) 74 °C (165 °F)
      diodo GPU (MemIO) 73 °C (163 °F)
      Intenta hacer descender la temperatura realizando una limpieza interior, prestando especial atención en el ventilador de la tarjeta gráfica, es el del rectángulo rojo en la imagen:



      Pero sobretodo, ve con tiento a la hora de maniobrar en el interior del PC, por favor:
      • Hay que tener en cuenta que siempre hay que tomar precauciones cuando andamos manejando en una placa base, los circuitos de la mother son muy sensibles y cualquier golpe o descarga puede provocar la defunción de la misma
      • El pc debe estar apagado y desconectado de Corriente.
      • Debemos descargarnos de la posible electricidad estática acumulada en nuestro cuerpo tocando algo metálico por dos veces antes de acercar nuestras manos a la placa base.
      • En lo posible NO tocar el circuito impreso de la placa madre.
      • No forzar nunca, todos los elementos están estudiados para facilitar su extracción.
      Una vez realizada la limpieza, puedes observar la temperatura desde el Catalyst Control Center -que imagino debes tener- en su apartado Overdrive:



      Donde también puedes controlar las revoluciones del ventilador habilitando la casilla Enable Manual Fan Control.

      Saludos

    5. #5
      Usuario Avatar de pepeluxo
      Registrado
      ago 2011
      Ubicación
      madrid
      Mensajes
      12

      Re: Reinicio aleatorio en windows 7

      Hola Lucky!,

      El problema de la garantía es que no tengo el ticket, me lo regalaron para reyes y me lo han perdido, si no ya estaba en el Servicio técncio desde hace tiempo.
      Limpiaré la tarjeta de vídeo, pero lo tengo en un sitio donde no entra polvo y la verdad es que no se ensucia nada, de todas formas ya limpié todo cuando cambié el ventilador del procesador.
      El PC es un Pacard Bell, pero es verdad que muchos de lo componentes son Acer, hasta cuando arranca en la BIOS pone ACER.
      Yo también estuve mirando el modelo por si había algún bug de algún controlador de algún componente que solucionará el problema y no aparece por ningún lado.
      Creo que es porque fue una edición especial (8gb de RAM, dos discos de 1TB, etc).
      De todas formas creo que ACER compró a Packard Bell en 2008, por lo que seguramente el PC, de Packard Bell, sólo tendrá el logo de la caja.
      El modelo seguro que es ese porque todavía tiene colgando una etiqueta en un lateral.

      Muchas gracias, limpiaré el ventilado de la CPU y te cuento!

      Salu2!!

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

      Re: Reinicio aleatorio en windows 7

      Mmmm nop, la temperatura del CPU está bien:
      CPU 35 °C (95 °F)
      CPU n.º 1 / núcleo n.º 1 52 °C (126 °F)
      CPU n.º 1 / núcleo n.º 2 48 °C (118 °F)
      CPU n.º 1 / núcleo n.º 3 50 °C (122 °F)
      CPU n.º 1 / núcleo n.º 4 47 °C (117 °F)
      Además, he estado revisando los componentes, y la MotherBoard que monta ése PC mutante parece ser la Gigabyte GA-EG43M-S2H. Entonces se me ha ocurridoque la mejor manera de comprobar y descartar la tarjeta gráfica ATI Radeon HD 4600 como causante del problema, sería que la desmontes y conectes el monitor a la salida VGA ó DVI que integra la propia Mother:

      Entonces la compu trabajará con la gráfica integrada Intel, y si de esta manera NO se reproducen las Bluescreens, pues ya tendríamos a la culpable, me sigues?

      Esperando comentarios... Chao

    7. #7
      Usuario Avatar de pepeluxo
      Registrado
      ago 2011
      Ubicación
      madrid
      Mensajes
      12

      Re: Reinicio aleatorio en windows 7

      Buena idea!

      No se me había ocurrido, voy a conectar directamente el monitor a la placa.
      Si es sólo eso voy a tirar la tarjeta gráfica a tomar por c.........

      Bueno, ya te contaré, lo malo es que como es aleatorio puede tirarse unos días sin fallar... esperemos que no...

      Muchas gracias y salu2!

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

      Re: Reinicio aleatorio en windows 7

      Y éso es malo??

      Esperemos que se tire muchos días sin fallar jajajaj

    9. #9
      Usuario Avatar de pepeluxo
      Registrado
      ago 2011
      Ubicación
      madrid
      Mensajes
      12

      Re: Reinicio aleatorio en windows 7

      Hola Lucky!

      Lamentablemente parece que ese no era el problema .
      Hace una semana me empezó a ir lento, pero al final no se reinició.
      Hoy si lo ha hecho, con los mismo síntomas, empieza a ir lento hasta que se queda bloqueado y al rato se reinicia...

      Esta vez pone que el causante fue ntoskrnl.exe.

      Pongo el último minidump... estoy desesperado... ya creía que lo había solucionado y era la tarjeta gráfica...

      Si se te ocurre algo...



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


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

      Symbol search path is: *** Invalid ***
      ****************************************************************************
      * Symbol loading may be unreliable without a symbol search path. *
      * Use .symfix to have the debugger choose a symbol path. *
      * After setting your symbol path, use .reload to refresh symbol locations. *
      ****************************************************************************
      Executable search path is:
      *********************************************************************
      * Symbols can not be loaded because symbol path is not initialized. *
      * *
      * The Symbol Path can be set by: *
      * using the _NT_SYMBOL_PATH environment variable. *
      * using the -y <symbol_path> argument when starting the debugger. *
      * using .sympath and .sympath+ *
      *********************************************************************
      Unable to load image 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 (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS Personal
      Machine Name:
      Kernel base = 0xfffff800`03653000 PsLoadedModuleList = 0xfffff800`03898670
      Debug session time: Thu Sep 8 00:21:10.671 2011 (UTC + 2:00)
      System Uptime: 0 days 0:00:12.029
      *********************************************************************
      * 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 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
      Mini Kernel Dump does not contain unloaded driver list
      *******************************************************************************
      * *
      * Bugcheck Analysis *
      * *
      *******************************************************************************

      Use !analyze -v to get detailed debugging information.

      BugCheck 124, {0, fffffa8008a258f8, 0, 0}

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

      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      Unable to load image PSHED.dll, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for PSHED.dll
      *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      Probably caused by : hardware

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

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

      WHEA_UNCORRECTABLE_ERROR (124)
      A fatal hardware error has occurred. Parameter 1 identifies the type of error
      source that reported the error. Parameter 2 holds the address of the
      WHEA_ERROR_RECORD structure that describes the error conditon.
      Arguments:
      Arg1: 0000000000000000, Machine Check Exception
      Arg2: fffffa8008a258f8, Address of the WHEA_ERROR_RECORD structure.
      Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
      Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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

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

      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************
      *************************************************************************
      *** ***
      *** ***
      *** Your debugger is not using the correct symbols ***
      *** ***
      *** In order for this command to work properly, your symbol path ***
      *** must point to .pdb files that have full type information. ***
      *** ***
      *** Certain .pdb files (such as the public OS symbols) do not ***
      *** contain the required information. Contact the group that ***
      *** provided you with these symbols if you need this command to ***
      *** work. ***
      *** ***
      *** Type referenced: nt!_KPRCB ***
      *** ***
      *************************************************************************

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

      FAULTING_MODULE: fffff80003653000 nt

      DEBUG_FLR_IMAGE_TIMESTAMP: 0

      BUGCHECK_STR: 0x124_GenuineIntel

      CUSTOMER_CRASH_COUNT: 1

      DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

      CURRENT_IRQL: 0

      STACK_TEXT:
      fffff880`031c46b0 fffffa80`08a258f8 : 00000000`00000001 00000000`00000000 fffffa80`07c77ab0 fffffa80`08a258f8 : nt+0x4b16cc
      fffff880`031c46b8 00000000`00000001 : 00000000`00000000 fffffa80`07c77ab0 fffffa80`08a258f8 00000000`00000000 : 0xfffffa80`08a258f8
      fffff880`031c46c0 00000000`00000000 : fffffa80`07c77ab0 fffffa80`08a258f8 00000000`00000000 00000000`00000000 : 0x1


      STACK_COMMAND: kb

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: hardware

      IMAGE_NAME: hardware

      BUCKET_ID: WRONG_SYMBOLS

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

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

      Re: Reinicio aleatorio en windows 7

      En fin, ya puedes montar de nuevo la gráfica

      Ahora se trataría de comprobar el resto de componentes, realiza un ScanDisk a ambos discos:

      + Vimeo Vídeos by InfoSpyware
      ERROR: If you can see this, then Vimeo is down or you don't have Flash installed.


      De preferencia -si dispones del DVD de Seven- utiliza el método de ejecutarlo desde Reparar > Símbolo del Sistema.

      En tu próxima respuesta dinos si CHKDSK ha encontrado errores o sectores defectuosos por favor.

      Saludos

    Página 1 de 3 123 ÚltimoÚltimo