Hola buenos días:
tengo un portátil el cual al arrancarlo me sale la pantalla azul, he instalado el WinDbg y los datos que me da son los siguientes:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\092412-19484-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82a19000 PsLoadedModuleList = 0x82b624f0
Debug session time: Mon Sep 24 11:04:03.107 2012 (UTC + 2:00)
System Uptime: 0 days 0:00:22.167
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...........
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 84f4f850, Terminating object
Arg3: 84f4f9bc, Process image file name
Arg4: 82c31d60, Explanatory message (ascii)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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.
MODULE_NAME: wininit
FAULTING_MODULE: 00000000
DEBUG_FLR_IMAGE_TIMESTAMP: 0
PROCESS_OBJECT: 84f4f850
IMAGE_NAME: wininit.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8e8acc9c 82cf7139 000000f4 00000003 84f4f850 nt+0xdeeb4
8e8accc0 82c74cc4 82c31d60 84f4f9bc 84f4fac0 nt+0x2de139
8e8accf0 82c74c07 84f4f850 84f4f568 c0000005 nt+0x25bcc4
8e8acd24 82a571fa ffffffff c0000005 0009f824 nt+0x25bc07
8e8acd34 76e270b4 badb0d00 0009f7dc 00000000 nt+0x3e1fa
8e8acd38 badb0d00 0009f7dc 00000000 00000000 0x76e270b4
8e8acd3c 0009f7dc 00000000 00000000 00000000 0xbadb0d00
8e8acd40 00000000 00000000 00000000 00000000 0x9f7dc
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Bueno espero que puedan ayudarme.
Desde ya muchas gracias.
BSoD en portátil
¿Tienes problemas con el ordenador?, aquí te ayudamos a solucionarlos.
Responder
1 mensaje
• Página 1 de 1
Volver a “Taller de reparaciones”
Ir a
- Informatica
- ↳ Taller de reparaciones
- ↳ Hardware y periféricos
- ↳ Comunicaciones / Networking
- ↳ Componentes externos
- ↳ Dispositivos de almacenamiento
- ↳ Drivers y BIOS
- ↳ Microprocesadores
- ↳ Ordenadores
- ↳ Placas Base y Memorias
- ↳ Portatiles
- ↳ Tarjetas graficas
- ↳ Tarjetas multimedia
- ↳ Internet
- ↳ Movilidad
- ↳ Programación
- ↳ PHP
- ↳ Javascript
- ↳ Java
- ↳ C y C++
- ↳ Plataforma .NET
- ↳ HTML, DHTML y CSS
- ↳ Seguridad informática
- ↳ Sistemas operativos
- ↳ Linux
- ↳ Windows
- ↳ Otros
- ↳ Software de escritorio
- ↳ Ofimática
- ↳ Diseño gráfico
- ↳ Internet
- ↳ Navegadores
- ↳ Clientes de correo
- ↳ Mensajería instánea
- ↳ Diseño web
- ↳ Multimedia
- ↳ Taller informático
- Juegos
- ↳ Acción 3D
- ↳ Aventuras gráficas
- ↳ Deportes
- ↳ Estrategia
- ↳ Juegos en línea
- ↳ ROL
- ↳ Simuladores
- ↳ Videoconsolas
- Manuales
- ↳ Aplicaciones de escritorio
- ↳ Desarrollo
- ↳ Hardware
- ↳ Herramientas de diseño
- ↳ Sistemas operativos
- Mercadillo
- ↳ Compra
- ↳ Venta
- ↳ Intercambio
- MundoBIP
- ↳ Offtopic
- ↳ Sugerencias
- ↳ Pruebas
- ↳ Noticias
- ↳ Encuestas
- ↳ Quejas públicas