WinDbg BAD_POOL_HEADER


(Sebowaw) #1

Witam!

Od pewnego czasu mam dość poważny problem z lapkiem Samsung R540. Otóż pewnogo dnia komputer poważnie się zawiesił, pomogło tylko odłączenie od baterii/sieci. Następnie nie chciał się włączyć. W ogóle nie reagował. Zapalała się tylko kontrolka Power, a procesor i dysk nie reagował. Po jakichś 2-3 godzinach laptop się włączył jak gdyby nigdy nic. Następnie przy ponownym uruchomieniu problem z włączeniem się powtórzył, lecz znowu po jakimś czasie dało się go uruchomić. Teraz bardzo często pojawiają się BSOD. Na przykład uruchomieniu przeglądarki i chwilowym korzystaniu z sieci pojawia się BSOD "BAD_POOL_HEADER". Nie pamiętam w jakich okolicznościach ale pojawił się również "SYSTEM_SERVICE_EXPECTION". Do tego coś zaczął szwankować Kaspersky, ale po naprawie chyba wszytko z nim jest jak należy. Profilaktycznie wstawiam raport z WinDbg.

Powiedzcie mi co spowodowało problem. Moim skromnym bardzo laickim zdaniem jest to problem z RAMem, ale tak jak pisałem jestem bardzo ubogi o wiedzę informatyczną więc pytam się internetowych ekspertów co w trawie piszczy.

Pozdrawiam!

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\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 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16792.amd64fre.win7_gdr.110408-1633

Machine Name:

Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03450e50

Debug session time: Fri May 13 19:38:49.259 2011 (GMT+2)

System Uptime: 0 days 0:16:48.446

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\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

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 19, {20, fffff900c204a9e0, fffff900c204aa30, 2505009e}


***** 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***

******

*************************************************************************

*************************************************************************

******

******

***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***

******

*************************************************************************

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***

******

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Probably caused by : ntoskrnl.exe ( nt+70700 )


Followup: MachineOwner

---------


2: 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: 0000000000000020, a pool block header size is corrupt.

Arg2: fffff900c204a9e0, The pool entry we were looking for within the page.

Arg3: fffff900c204aa30, The next pool entry.

Arg4: 000000002505009e, (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!_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!_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_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***

******

*************************************************************************

*********************************************************************

* 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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************


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: fffff80003213000 nt


DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34


BUGCHECK_STR: 0x19_20


POOL_ADDRESS: fffff900c204a9e0 


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


CURRENT_IRQL: 0


LAST_CONTROL_TRANSFER: from fffff800033b66d3 to fffff80003283700


STACK_TEXT:  

fffff880`08f53ef8 fffff800`033b66d3 : 00000000`00000019 00000000`00000020 fffff900`c204a9e0 fffff900`c204aa30 : nt+0x70700

fffff880`08f53f00 00000000`00000019 : 00000000`00000020 fffff900`c204a9e0 fffff900`c204aa30 00000000`2505009e : nt+0x1a36d3

fffff880`08f53f08 00000000`00000020 : fffff900`c204a9e0 fffff900`c204aa30 00000000`2505009e 00000000`00000000 : 0x19

fffff880`08f53f10 fffff900`c204a9e0 : fffff900`c204aa30 00000000`2505009e 00000000`00000000 fffff880`08f54060 : 0x20

fffff880`08f53f18 fffff900`c204aa30 : 00000000`2505009e 00000000`00000000 fffff880`08f54060 fffff880`08f54050 : 0xfffff900`c204a9e0

fffff880`08f53f20 00000000`2505009e : 00000000`00000000 fffff880`08f54060 fffff880`08f54050 00000000`05161a06 : 0xfffff900`c204aa30

fffff880`08f53f28 00000000`00000000 : fffff880`08f54060 fffff880`08f54050 00000000`05161a06 fffff800`0328f700 : 0x2505009e



STACK_COMMAND: kb


FOLLOWUP_IP: 

nt+70700

fffff800`03283700 48894c2408 mov qword ptr [rsp+8],rcx


SYMBOL_STACK_INDEX: 0


SYMBOL_NAME: nt+70700


FOLLOWUP_NAME: MachineOwner


IMAGE_NAME: ntoskrnl.exe


BUCKET_ID: WRONG_SYMBOLS


Followup: MachineOwner

---------

(Kris-is) #2

http://forum.dobreprogramy.pl/ekran-smierci-tzw-blue-screen-t445558.html Tu masz chyba wszystkie błędy - wystarczy znaleźć dany typ błędu i sprawdzić możliwe jego powody i proponowane sposoby jego rozwiązania.


(Piotrkijak) #3

Do tesetu dysk twardy i ram. Ram sprawdzisz programem metest, natomiast dysk programem MHDD. Instrukcja: http://www.nirvanowiec.republika.pl/MHDD.html

http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm. Wydaje mi się, że właśnie to może być problem z ramem, skoro komp nie chciał się włączyć, bo komputer może startować z czarnym ekranem między innymi z powodu uszkodzonego ramu.