bad pool header, pantallazo azul windows 7

Página 1 de 1
edissonpk
edissonpk
ZoNeR@
ZoNeR@
 
Mensajes: 2
Registrado: Mar 22 Ene, 01:00

» Mar 22 Ene, 05:50

hola mi problema es que me aparece el pantallazo azul con el problema bad pool header, segui un tutorial y dejo la informacion del problema, pero no se como arreglarlo porque no entiendo muy bien.


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


Loading Dump File [C:\Windows\Minidump\012113-39265-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8281f000 PsLoadedModuleList = 0x82967810
Debug session time: Mon Jan 21 21:46:40.642 2013 (UTC - 5:00)
System Uptime: 0 days 4:02:03.640
*********************************************************************
* 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 *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 8540d000, The pool entry we were looking for within the page.
Arg3: 8540d300, The next pool entry.
Arg4: 08600000, (reserved)

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!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
*************************************************************************
*** ***
*** ***
*** 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!_POOL_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!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** 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: nt

FAULTING_MODULE: 8281f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: 8540d000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8bb55c9d to 8293e1b6

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9e1a7c68 8bb55c9d 8540d008 00000000 00000000 nt+0x11f1b6
9e1a7c84 8bb4f1ae 8540d008 82889783 859c0718 fltmgr+0x21c9d
9e1a7cb4 8bb58a25 859c0718 00000008 861d0e04 fltmgr+0x1b1ae
9e1a7cd4 8bb478af 8540d014 00000008 861d0e00 fltmgr+0x24a25
9e1a7cec 8bb4c89a 858f2ed8 00000008 857948c0 fltmgr+0x138af
9e1a7d00 8288cf2b 861d0e00 00000000 857948c0 fltmgr+0x1889a
9e1a7d50 82a2d66d 80000001 b813ce5b 00000000 nt+0x6df2b
9e1a7d90 828df0d9 8288ce1e 80000001 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc00d9


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+11f1b6
8293e1b6 cc int 3

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+11f1b6

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
Avatar de Usuario
Ayax
Administrador
Administrador
 
Mensajes: 10849
Registrado: Mar 21 Oct, 00:00

» Mar 22 Ene, 08:46

¿Has hecho algún cambio reciente en el sistema a raíz del cual creas que pueda venir el problema? (instalar, desinstalar un programa, etc.)

¿Tienes instalados todos los drivers de tu hardware? (chipset, tarjeta gráfica, tarjeta de red, tarjeta de sonido, etc.)

Saludos.
Imagen
SoftZone en Imagen
edissonpk
edissonpk
ZoNeR@
ZoNeR@
 
Mensajes: 2
Registrado: Mar 22 Ene, 01:00

» Mar 22 Ene, 21:37

hola
he mirado en la parte de instalar o desinstalar algún programa no.

estuve verificando los drivers y si tiene todos pero es que creo que no los instalaron bien o no están actualizados, porque estuve verificando y creo que es problema con el driver de sonido o de gráficos, porque siempre se reinicia cuando estoy viendo algún video.

si me pueden ayudar en esta parte porque no se como buscarlos e instalar los drivers de video y de sonido.
Avatar de Usuario
Ayax
Administrador
Administrador
 
Mensajes: 10849
Registrado: Mar 21 Oct, 00:00

» Mié 23 Ene, 09:35

¿Sabes si tu tarjeta gráfica está integrada en la placa base o es una tarjeta gráfica conectada a un puerto PCI-Express? Si está integrada, deberás descargar el driver desde la web del fabricante de tu placa base. Si es física, deberás descargar el driver desde la web de NVIDIA o AMD.

En el caso de la tarjeta de sonido y de red, lo más normal es que estén integradas en placa (salvo que tu PC sea muy antiguo) y por tanto debas descargar sus drivers desde la web del fabricante de tu placa base.

Saludos.
Imagen
SoftZone en Imagen
Página 1 de 1

Volver a Software