Błąd bad pool caller


(Vaisala) #1

Mam kompa pentium P4 socket 478, plyta głowna Asrock.karta Radeon 9600, Sound blaster Audigy,HD Maxtor 160GB

Co jakis czas wystepuje u mnie bląd Bad Pool Caller.

Chcialem sie dowiedziec jak mozna ten dłąd usunąc,

Wyprobowalem wypiac karte grafiki i muzyki, ale nic to nie dało, dalej to samo.Zmieniłem dysk na inny i tez sie to dzieje.

Zmienilem wina z XP na 2000 i nie pomogło.

Czy ktos moze mi udzielic odpowiedzi jak usunąc ten blad??

Złączono Posta : 11.02.2007 (Nie) 8:41

Tresz blue screena jest taka

BAD POOL CALLER

STOP: 0x00000007C2

(0x00000007, 0x00000CD4, 0x024c0001, 0xFE17A618)


(Uzi) #2

Zajrzyj może ci to w czymś pomoże.

http://support.microsoft.com/default.aspx?scid=kb;pl;314492


(Vaisala) #3

czytałem juz to, ale nic z tego nie rozumiem.

Mam przeciez adres tego błędu.

Ale nie wiem co mam z tym zrobic.

Mysle ze problem leży raczej po stronie oprogramowania.

Dodatkowo dodam, ze wymienilem w kompie pamiec na nową.

Zasilacz na mocniejszy 400W.

Wiec raczej sprzet jest sprawny.


(Uzi) #4

Pamięci przetestuj jakims programikiem.Ewentualnie może ta nowa pamięć się gryzie?


(Vaisala) #5

Pamiec juz przetestowalem. Jest ok. Na starej pamieci tez sie to dzialo, ale miala bledy, wiec wywalilem ja i kupilem nową. A problem dalej pozostal.


(popula) #6

Przeinstaluj stery od karty graficznej. Przed nową instalacją przeczyść rejestr, najlepiej jv16.


(Vaisala) #7

Stery zmienialem.

Najpierw mailem oryginalne Ati, wywalilem je.

Potem Omega drivers, nie nie dalo, wywalilem je.

potem Dna drivers, dalej to samo, wywalilem je.

potam wywalilem cala karte i uzywalem tej z plyty glownej, ale dalej to samo, wiec wywalilem jej stery i znowu zalozylem radeona i strowniki z ati.


(popula) #8

W tej sytuacji specjalnie nie ma się co dziwić, że masz problemy. Takie wymiany bez odpowiedniego czyszczenia rejestru, muszą owocować skutkami ubocznymi. Miałem kiedyś taki komunikat. Walczyłem z nim długo. Dopiero gruntowne przeczyszczenie rejestru postawiło system na nogi. Użyj jv16 z funkcji “wyszukaj w rejestrze” i wpisz wszystkie nazwy poprzednio używanych sterowników.


(Vaisala) #9

Rejestr przeczyscilem i wykonalem calą pętlę od nowa. Po każdym odinstalowaniu sterownika czyszczenie rejestru. Ale nic to niestety nie dało. Czy macie moze jeszcze jakies pomysły??


(JNJN) #10

Może masz zainstalowany program Outpost firewall?


(Vaisala) #11

Nie.

Mam tylko Zone Alarma, i antywirusa Avira Antyvir.


(JNJN) #12

Spróbuj go odinstalować i zrobić po nim porządek i zobacz teraz?.


(popula) #13

(Vaisala) #14

Komputer nie ma ostatniej znanej dobrej konfiguracji.

Wiec tak opcja odpada.

Sterowniki mam firmwarowe.

Zadnego podkręcania.

A do czego moze mi posluzyc ten debuger o którym piszą na stronie Microsoftu, czy poprzez niego dojde jakie urządzenie wywołuje błąd??

Złączono Posta : 11.02.2007 (Nie) 11:35

Wkleje plik z log z Windbg.

Moze ktos wie jak to czytac.

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © 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 ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0

Debug session time: Sun Feb 11 08:41:13.046 2007 (GMT+1)

System Uptime: 0 days 9:53:16.746

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

* 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 ntoskrnl.exe, Win32 error 2

*** 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 C2, {7, cd4, 24c0001, fe17a618}

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

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

*** WARNING: Unable to verify timestamp for e10kx2k.sys

*** ERROR: Module load completed but symbols could not be loaded for e10kx2k.sys

*** WARNING: Unable to verify timestamp for portcls.sys

*** ERROR: Module load completed but symbols could not be loaded for portcls.sys

*** WARNING: Unable to verify timestamp for ks.sys

*** ERROR: Module load completed but symbols could not be loaded for ks.sys

*** WARNING: Unable to verify timestamp for sysaudio.sys

*** ERROR: Module load completed but symbols could not be loaded for sysaudio.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!PVOID ***

*** ***

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

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

*** WARNING: Unable to verify timestamp for wdmaud.sys

*** ERROR: Module load completed but symbols could not be loaded for wdmaud.sys

Probably caused by : e10kx2k.sys ( e10kx2k+dd46 )

Followup: MachineOwner



(Maciej Pomoc Techniczna) #15

Pobierz program WinThrust wlacz go (WinThrust to program uzywany do wytepiania bledow z niebieskim ekranem na windows 10 ktory usuwa zlosliwe dane z rejestru) gdy program zrobi swoje uzyj jakiegos avasya lub jakiegos innego antyvirusa i dan skanuj komputer czy cos w ten desen jezeli bedziesz mial jakiegos virusa pozbadz sie go ( Wtedy wszystko zalezy jaki virus ci wyskoczy) Jezeli Po tym wszystkim zrestartujesz komputer to powinno wszystko dzialac.