hello I am running windows xp SP2 and I am getting this blue screen error and it shuts down. It seams to only come up when i am on the internet and so i checked the ethernet adapter in the device manager and it says it isnt installed correctly. So i uninstalled it and installed it again and im still getting the error. I logged the error here but its two big to send on here. I remember one line in the error message saying "BAD_POOL_CALL".
Blue screen error
- Thread starter Alex_W
- Start date
- Status
Route44
Posts: 12,015 +82
0x000000C2: BAD_POOL_CALLER
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.
Right now there isn't enough information to tell us what driver is the cause. So...
Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box.
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.
Right now there isn't enough information to tell us what driver is the cause. So...
Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box.
I debugged the error with WinDbg and this is what I got:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Alex\Desktop\blue screen error\blue screen error\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\websymbols*ttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Mar 22 22:14:04.137 2008 (GMT-4)
System Uptime: 0 days 0:01:50.844
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 2060004, 88d31688}
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+450c1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 02060004, Memory contents of the pool block
Arg4: 88d31688, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 88d31688 Nonpaged pool
FREED_POOL_TAG: TCPc
BUGCHECK_STR: 0xc2_7_TCPc
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb
STACK_TEXT:
bad038b8 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
bad03908 a98883f5 88d31688 00000000 bad03950 nt!ExFreePoolWithTag+0x2a3
bad03918 a9887c85 89d28008 89d2809c 89d2809c tcpip!TCPClose+0x16
bad03950 a983a0c1 890f2f18 89d28008 a98399cd tcpip!TCPDispatch+0x101
WARNING: Stack unwind information not available. Following frames may be wrong.
bad0395c a98399cd 890f2f18 89d28008 00000002 vsdatant+0x450c1
bad03990 a983a04a 890f2f18 89d28008 89d28008 vsdatant+0x449cd
bad039b4 a9839ee7 88c21680 a983a057 89d28008 vsdatant+0x4504a
bad039bc a983a057 89d28008 89061d68 89103e18 vsdatant+0x44ee7
bad039cc 80502909 88db6810 88a85538 88db680b vsdatant+0x45057
89103e18 890f2f18 00000000 890f2f18 00000000 nt!KiReadyThread+0x305
89103e1c 00000000 890f2f18 00000000 00000000 0x890f2f18
STACK_COMMAND: kb
FOLLOWUP_IP:
vsdatant+450c1
a983a0c1 c20c00 ret 0Ch
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: vsdatant+450c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vsdatant
IMAGE_NAME: vsdatant.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 473b79f9
FAILURE_BUCKET_ID: 0xc2_7_TCPc_vsdatant+450c1
BUCKET_ID: 0xc2_7_TCPc_vsdatant+450c1
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Alex\Desktop\blue screen error\blue screen error\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\websymbols*ttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Mar 22 22:14:04.137 2008 (GMT-4)
System Uptime: 0 days 0:01:50.844
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 2060004, 88d31688}
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+450c1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 02060004, Memory contents of the pool block
Arg4: 88d31688, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 88d31688 Nonpaged pool
FREED_POOL_TAG: TCPc
BUGCHECK_STR: 0xc2_7_TCPc
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb
STACK_TEXT:
bad038b8 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
bad03908 a98883f5 88d31688 00000000 bad03950 nt!ExFreePoolWithTag+0x2a3
bad03918 a9887c85 89d28008 89d2809c 89d2809c tcpip!TCPClose+0x16
bad03950 a983a0c1 890f2f18 89d28008 a98399cd tcpip!TCPDispatch+0x101
WARNING: Stack unwind information not available. Following frames may be wrong.
bad0395c a98399cd 890f2f18 89d28008 00000002 vsdatant+0x450c1
bad03990 a983a04a 890f2f18 89d28008 89d28008 vsdatant+0x449cd
bad039b4 a9839ee7 88c21680 a983a057 89d28008 vsdatant+0x4504a
bad039bc a983a057 89d28008 89061d68 89103e18 vsdatant+0x44ee7
bad039cc 80502909 88db6810 88a85538 88db680b vsdatant+0x45057
89103e18 890f2f18 00000000 890f2f18 00000000 nt!KiReadyThread+0x305
89103e1c 00000000 890f2f18 00000000 00000000 0x890f2f18
STACK_COMMAND: kb
FOLLOWUP_IP:
vsdatant+450c1
a983a0c1 c20c00 ret 0Ch
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: vsdatant+450c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vsdatant
IMAGE_NAME: vsdatant.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 473b79f9
FAILURE_BUCKET_ID: 0xc2_7_TCPc_vsdatant+450c1
BUCKET_ID: 0xc2_7_TCPc_vsdatant+450c1
Followup: MachineOwner
---------
Route44
Posts: 12,015 +82
As per your minidump read: Probably caused by : vsdatant.sys
If you google this you will find vsdatant.sys is a driver for Zone Alarm. Many people have experienced issues with this ZA driver.
1. Either update ZA or...
2. Go to their forums and post your issues with this driver and how it is causing crashes. They should have an answer there.
If you google this you will find vsdatant.sys is a driver for Zone Alarm. Many people have experienced issues with this ZA driver.
1. Either update ZA or...
2. Go to their forums and post your issues with this driver and how it is causing crashes. They should have an answer there.
- Status
