PDA

View Full Version : Bad_pool_caller BSoD(s)


Edmachine
07-29-08, 08:46 AM
Hello, I'm having some trouble with my PC. It poops out a BSoD every once in a while (up to 4-5 times a day!), and it is really annoying.
The error is, as stated in the title, BAD_POOL_CALLER.
The dump file contains this:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini072708-02.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 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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul 27 16:25:33.375 2008 (GMT+3)
System Uptime: 0 days 0:37:56.093
************************************************** *******************
* 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 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
***PAGE STRETCH***
Loading User Symbols
Loading unloaded module list
...............
The call to LoadLibrary(ext) failed, Win32 error 0n2
"The system cannot find the file specified."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
"The system cannot find the file specified."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(ext) failed, Win32 error 0n2
"The system cannot find the file specified."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
"The system cannot find the file specified."
Please check your debugger configuration and/or network access.
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Bugcheck code 000000C2
Arguments 00000007 00000cd4 02060005 893a3a30

ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
bacf78b4 8054b583 000000c2 00000007 00000cd4 nt+0x22f33
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
bacf7904 b70ccae3 893a3a30 00000000 bacf794c nt+0x74583
bacf7914 b70cc44d 88a00e00 88a00e94 88a00e94 tcpip+0xaae3
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
bacf794c b68a00c1 8a5135b8 88a00e00 b689f9cd tcpip+0xa44d
bacf7950 8a5135b8 88a00e00 b689f9cd 8a5135b8 vsdatant+0x450c1
bacf7954 88a00e00 b689f9cd 8a5135b8 88a00e00 0x8a5135b8
bacf7958 b689f9cd 8a5135b8 88a00e00 00000002 0x88a00e00
bacf795c 8a5135b8 88a00e00 00000002 88a00e94 vsdatant+0x449cd
bacf7960 88a00e00 00000002 88a00e94 8a5135b8 0x8a5135b8
bacf7964 00000000 88a00e94 8a5135b8 bacf7c44 0x88a00e00

It says something about the symbols. What could it mean? I hope I don't get a BSoD while posting this :P.

Please help, thanks in advance :).


P.S. Operating system: XP

Zefram
07-29-08, 12:46 PM
The debug file would point to the Internet portion of the O/S which had fault in it.

tcpip.sys is the system responsible for your internet connectivity.

And you're using XP SP3, there's known problems for SP3 with AMD systems.
Full system configurations would be much more helpful ;)

Edmachine
07-29-08, 01:30 PM
Gigabyte GA-EP35-DS3
Intel Core2Duo E6850 3.00GHz
2GB of OCZ RAM, DDRII, 800Mhz, Titanium series
Asus 8800GT 512MB (if that's what you meant with system configuration...)
And I have XP Service Pack 3.
Forgot to mention, that I have already tested my memory with MemTest, no errors.
Graphics drivers are updated (CUDA, so I can use F@H). Is there any way to fix this?

EDIT: Actually, the only times when I get BSoD, are when I use the Internet. Sometimes in games, but I use BitComet then... So, there's something wrong with the tcpip.sys?

Zefram
07-29-08, 02:13 PM
EDIT: Actually, the only times when I get BSoD, are when I use the Internet. Sometimes in games, but I use BitComet then... So, there's something wrong with the tcpip.sys?

Hmm, then my initial post suggesting the internet connectivity might had something to do with this is somewhat accurate

Test the theory then. Disconnect from internet, play games, watch movies, benchmark, etc....... and test for bluescreen. If there's none, then we already isolated and identify that the internet connectivity had something to do with it.

If it is, we need to isolate whether its a specific O/S, or driver related problems. Try updating your onboard Realtek 8111B Gigabit Lan driver (DOWNLOAD HERE (ftp://210.51.181.211/cn/nic/PCIE_Install_5698_0725.zip))

Plus update your antivirus and scan your PC for virus or spywares. TCPIP.sys is a viable target since its connected to the internet. :fighty:

Edmachine
07-29-08, 03:11 PM
I just updated the driver. But, seeing if that was the problem will be hard, because, there are no certain conditions for the BSoD (except, probably, Internet connection). And when, or if, I'll get a BSoD, I'll 'leave the Internet' for a day or two. And, if even then I get a BSoD, I'll post about it here. And the dump.

EDIT: Got a BSoD. Now, I am going to un-plug my Ethernet cable from my PC. And play games, run F@H... browse web with my laptop...
An opportunity to continue writing my website :P.

EDIT2: Haven't got a BSoD so far. Did a benchmark (got ~11000 3DMark06 Points), played some games... nothing happens. Going to plug in the Ethernet cable.

EDIT3: Yup, 15 minutes after plugging in the cable, guess what, it poops out a BSoD... so, I am 95% sure it's the Internet. Did a virus and spyware scan earlier, cleared all the threats. Help?

Zefram
08-04-08, 06:43 AM
There is a Discussion on TechSpot (external Link) forum (http://www.techspot.com/vb/topic108142.html). This good chap is having the same problem as yours.

He ended up reverting to SP2, but still the problem persist.

In the end, they suggested that he tested on a different windows partition, and there are no post after that........... which sounds to me that reinstalling windows helps to fix this issues :fighty:

Edmachine
08-04-08, 07:14 AM
I am going to try reverting back to SP2, but can you tell me how to do it? Just download SP2 and install?

Zefram
08-04-08, 09:36 AM
I am going to try reverting back to SP2, but can you tell me how to do it? Just download SP2 and install?

Supposedly when you install SP3, windows would keep a uninstall options so that you could remove SP3 and move back to SP2 easily.
This could be found under Control Panel > Add/Remove Program

However, if the SP3 is slipstreamed (integrated into the CD), or you choose not to keep old data (the checkbox for this came out when you install SP3), then there's not way to uninstall SP3 and revert back to previous service packs.

I believe if you re-downloaded SP2, it wont install. :fighty: