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