Pantallazo azul (ntkrnlpa.exe)

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

Hola, ya he sufrido 3 pantallazos y he seguido los pasos del manual de softzone ( http://www.softzone.es/manuale...os-azules/ ) y os adjunto el log a ver is me podeis ayudar a evitarlo:

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

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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Mar 9 06:53:11.281 2010 (GMT+1)
System Uptime: 0 days 10:48:30.988
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, c06e7a30}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlpa.exe ( nt+6d6f0 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: c06e7a30, address which referenced memory

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!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a784394

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000

CURRENT_IRQL: 2

FAULTING_IP:
+ffffffffc06e7a30
c06e7a30 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to 805446f0

STACK_TEXT:
bacd3ac4 00000000 00000000 00000002 00000001 nt+0x6d6f0

STACK_COMMAND: kb

FOLLOWUP_IP:
nt+6d6f0
805446f0 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+6d6f0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

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

Saludos

Publicado: Viernes 12 Marzo 2010, 0:59

Haz un chkdsk /r desde la linea de comandos arrancando el sistema desde el CD de Windows

Si el problema persiste te recomiendo que hagas una reparación del sistema

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

gohuca escribió:

Haz un chkdsk /r desde la linea de comandos arrancando el sistema desde el CD de Windows

Si el problema persiste te recomiendo que hagas una reparación del sistema

Gracias gohuca, la reparacion del sistema se como se hace, pero puedes explicarme un poco como es eso de hacer un chkdsk /r desde la linea de comandos?

Saludos

Publicado: Viernes 12 Marzo 2010, 12:39

Arranca el sistema desde el cd de windows, eliges simbolo de sistema y pones el comando que te comento

De todas maneras mira esto que te ayudará:

Comandos de la consola de XP

Salu2

Gohuca

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

OK Gohuca, gracias, olo hago y os cuento

Publicado: Sábado 13 Marzo 2010, 13:39

Aquí estaremos esperando novedades al respecto

Salu2

Gohuca

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

He instalado la consola y he ejecutado el comando chkdsk /r, tras un alrgo rato me ha puesto que se ha encontrado y reparado uno o mas sectores defectuosos, o algo parecido. De momento no he sufrido mas pantallazos, seguiremos a la espera, muchas gracias.

Publicado: Lunes 15 Marzo 2010, 15:29

Esperemos que se haya solucionado. Si vuelves a tener el mismo problema comentaló y buscamos otras alternativas

Salu2

Gohuca

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

Bueno, pues parece que no ha funcionado, hoy me he encontrado el pc con otro pantallazo, pero el log parece diferente, os lo pego aqui:
De todos modos, esta noche probaré a hacer una reparacion de sistema con el cd del XP

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

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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Mar 16 20:39:39.312 2010 (GMT+1)
System Uptime: 0 days 3:37:43.009
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.......................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ebd2b7d8, 2, 1, ba5e819e}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image nvata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvata.sys
*** ERROR: Module load completed but symbols could not be loaded for nvata.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : nvata.sys ( nvata+1119e )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ebd2b7d8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: ba5e819e, address which referenced memory

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!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

MODULE_NAME: nvata

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4536c767

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
ebd2b7d8

CURRENT_IRQL: 2

FAULTING_IP:
nvata+1119e
ba5e819e ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to 80544718

STACK_TEXT:
bacd3b60 00000000 ebd2b7d8 00000002 00000001 nt+0x6d718

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvata+1119e
ba5e819e ?? ???

SYMBOL_NAME: nvata+1119e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: nvata.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

Haz una comprobación de tu disco duro con HDD Regenerator , porque me da que debe ser un error hardware.

Testea también la memoria RAM con memtest86+ .

Saludos.

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

Por partes:

Esta mañana intenté hacer una reparacion de sistema y casi la preparo parda.... arranque desde el cd de instalacion y le di a "Para instalar XP ahora, presione la tecla ENTRAR" pero empezo a copiar los archivos de instalacion y no me salio la nueva ventana con la opcion de reparar, tal y como muestra el siguiente manual:

http://www.softzone.es/manuale...ema-en-xp/

Asi que cancele la instalacion y ahora cuando arranco me salen 2 sistemas operativos a elegir, eso si, uno de ellos me pide el cd de instalcion para completarlo. Como hago para eliminar esta nueva opcion en el arranque? O mejor esto lo dejo para otro post, ok?

Por otra parte y respondiendo a Ayax:

HDD Regenerator y memtest86+ : donde los consigo? Son gratuitos?

Gracias y saludos

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

ronint4, elimina la entrada del arranque yendo a Inicio --> Ejecutar --> escribe msconfig --> pestaña BOOT.INI.

HDD Regenerator es un programa de pago, y memtest86+ es gratuito.

HDD Regenerator: http://www.dposoft.net/

memtest86+: http://www.memtest.org/#downiso

Deberás grabar cada uno de ellos en un CD y arrancar desde ellos.

Saludos.

Publicado: Jueves 18 Marzo 2010, 20:34

Tienes un manual de HDD Regenerator en SOFTzone Guiño

Salu2

Gohuca

ZoNeR@ EnGanChAUUuU Registrado: Apr 04, 2008 Mensajes: 785

Gracias a los dos, tengo noticias nuevas que no se si os serviran para saber que me esta pasando.

Para empezar, Ayax, en la pestaña de BOOT.INI. no veo el boton de eliminar.... Gracias por los enlaces, empezaré por el gratuito.... y luego ya veremos.

Gohuca: gracias por el enlace al manual.

Bueno, las novedades. Esta mañana, para descartar posibles fallos de software, me decidi a restaurar con Ghost una imagen que tengo del 11 de febrero, fecha en la que no tenia problemas, pues bien, en cuanto empieza a cargar la imagen sale un pantallazo azul. He probado con otra imagen de noviembre de 2009 y paso lo mismo, cuando llega la barra al 2-3% pantallazo al canto, lo he probado en 2-3 ocasiones y siempre pantallazo.

Alguna sugerencia?

Saludos y gracias de nuevo.

Publicado: Viernes 19 Marzo 2010, 11:06

Temo que es un problema de hardware.

Verifica como te hemos comentado el disco duro y la RAM

Salu2

Gohuca