Windows XP Blue Screen

HI all,

I have AT&T Version 6.4.0.3000 - August 10, 2005, installed.

Whenever i get diconnected from braodband from home due to any reason, i get blue screen. The dump error shows as below. I usually use Ethernet connected to connect to my official network. When i use USB connection, that pathetic. I get another type of blue screen error. Information mentioned below

When i use Ethernet i get following error, at the time of sudden disconnect from internet.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini060107-01.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 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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu May 31 21:40:57.491 2007 (GMT+5)
System Uptime: 0 days 0:56:23.358
*********************************************************************
* 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 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
............
Unable to load image abvpn2k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for abvpn2k.sys
*** ERROR: Module load completed but symbols could not be loaded for abvpn2k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b91a37db, 999e4728, 0}

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

***** 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 ***
*** ***
*************************************************************************
Probably caused by : abvpn2k.sys ( abvpn2k+77db )

Followup: MachineOwner
---------

At the time of USB connection i get



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


Loading Dump File [C:\WINDOWS\Minidump\Mini052507-01.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 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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri May 25 22:15:33.031 2007 (GMT+6)
System Uptime: 2 days 11:03:11.911
*********************************************************************
* 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 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
..................................................
Unable to load image NDIS.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 0, 0}

***** 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 abvpn2k.sys
*** ERROR: Module load completed but symbols could not be loaded for abvpn2k.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.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!_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 vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : abvpn2k.sys ( abvpn2k+4205 )

Followup: MachineOwner
---------

 

Reply

Thanks

the link which you provided guide me through the installer to check the dump logs. Is the same link u talking about to change the symbol ?

Thanks in Advance !

 

I have done till step 3 . i have this data in notepad

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini060107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers


I did'nt get step 4.. can u please explain ..

 

oh ... thanks ...

its below

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini060107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.051011-1528
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu May 31 21:40:57.491 2007 (GMT+5)
System Uptime: 0 days 0:56:23.358
Loading Kernel Symbols
...........................................................................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*** ERROR: Module load completed but symbols could not be loaded for abvpn2k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b91a37db, 999e4728, 0}

Probably caused by : abvpn2k.sys ( abvpn2k+77db )

Followup: MachineOwner
---------

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b91a37db, The address that the exception occurred at
Arg3: 999e4728, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
abvpn2k+77db
b91a37db 83782c01 cmp dword ptr [eax+2Ch],1

TRAP_FRAME: 999e4728 -- (.trap 0xffffffff999e4728)
.trap 0xffffffff999e4728
ErrCode = 00000000
eax=00000000 ebx=86e07438 ecx=870fa02e edx=ffffd30f esi=870fa02e edi=870fa01a
eip=b91a37db esp=999e479c ebp=999e47f4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
abvpn2k+0x77db:
b91a37db 83782c01 cmp dword ptr [eax+2Ch],1 ds:0023:0000002c=????????
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: vsmon.exe

LAST_CONTROL_TRANSFER: from 00000000 to b91a37db

STACK_TEXT:
999e47f4 00000000 870fa01a 00000000 00000001 abvpn2k+0x77db


STACK_COMMAND: kb

FOLLOWUP_IP:
abvpn2k+77db
b91a37db 83782c01 cmp dword ptr [eax+2Ch],1

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: abvpn2k

IMAGE_NAME: abvpn2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42ceecb2

SYMBOL_NAME: abvpn2k+77db

FAILURE_BUCKET_ID: 0x8E_abvpn2k+77db

BUCKET_ID: 0x8E_abvpn2k+77db

Followup: MachineOwner
---------

eax=00000000 ebx=86e07438 ecx=870fa02e edx=ffffd30f esi=870fa02e edi=870fa01a
eip=b91a37db esp=999e479c ebp=999e47f4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
abvpn2k+0x77db:
b91a37db 83782c01 cmp dword ptr [eax+2Ch],1 ds:0023:0000002c=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
999e47f4 00000000 870fa01a 00000000 00000001 abvpn2k+0x77db
start end module name
804d7000 806fd000 nt ntkrnlmp.exe Wed Oct 12 05:48:01 2005 (434C5639)
806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 11:29:09 2004 (41107B2D)
97836000 97860180 kmixer kmixer.sys Wed Jun 14 14:17:45 2006 (448FCD31)
9803f000 98042680 avpnnic avpnnic.sys Thu Mar 20 02:14:26 2003 (3E78D6AA)
9839b000 9839df60 SYMREDRV SYMREDRV.SYS Tue Aug 09 02:15:11 2005 (42F7C457)
99063000 99077400 wdmaud wdmaud.sys Wed Jun 14 14:30:44 2006 (448FD03C)
99210000 9921ed80 sysaudio sysaudio.sys Wed Aug 04 11:45:54 2004 (41107F1A)
992f8000 9930a000 pdlndldl pdlndldl.sys Wed Sep 07 00:07:54 2005 (431DE202)
99a19000 99a1bd00 vstor2 vstor2.sys Tue Nov 14 02:13:11 2006 (4558D8DF)
99a1d000 99a6e480 srv srv.sys Mon Aug 14 16:04:39 2006 (44E051BF)
99ccf000 99cdc000 pdlndoem pdlndoem.sys Wed Sep 07 00:07:50 2005 (431DE1FE)
99d63000 99d66100 mdmxsdk mdmxsdk.sys Thu Oct 06 05:28:05 2005 (4344688D)
99d67000 99d84580 appnapi appnapi.sys Tue Sep 06 23:08:50 2005 (431DD42A)
99d85000 99d95670 pdlnemap pdlnemap.sys Wed Sep 07 00:08:11 2005 (431DE213)
99d96000 99da7000 pdlndtdl pdlndtdl.sys Wed Sep 07 00:07:48 2005 (431DE1FC)
99da7000 99dbb000 pdlndsdl pdlndsdl.sys Wed Sep 07 00:07:46 2005 (431DE1FA)
99dbb000 99dcd000 pdlndqll pdlndqll.sys Wed Sep 07 00:07:42 2005 (431DE1F6)
99dcd000 99de2000 pdlndlpb pdlndlpb.sys Wed Sep 07 00:07:39 2005 (431DE1F3)
99de2000 99e09220 pdlncfwk pdlncfwk.sys Wed Sep 07 00:07:08 2005 (431DE1D4)
99e0a000 99e1c5c0 pdlnacom pdlnacom.sys Wed Sep 07 00:08:44 2005 (431DE234)
99e1d000 99f571a0 appn appn.sys Tue Sep 06 23:08:24 2005 (431DD410)
99f58000 99f70c20 llc2 llc2.sys Tue Sep 06 23:06:19 2005 (431DD393)
99f71000 99fa0d20 AppnBase AppnBase.sys Tue Sep 06 23:06:10 2005 (431DD38A)
99fa1000 99fb8580 vmx86 vmx86.sys Tue Nov 14 01:59:48 2006 (4558D5BC)
99fc1000 99fc4d00 vmnetuserif vmnetuserif.sys Tue Nov 14 02:10:06 2006 (4558D826)
9a009000 9a035400 mrxdav mrxdav.sys Wed Aug 04 11:30:49 2004 (41107B91)
9a036000 9a058080 RDPWD RDPWD.SYS Fri Jun 10 05:22:39 2005 (42A8D647)
9a059000 9a05b1a0 pdlnebas pdlnebas.sys Wed Sep 07 00:06:47 2005 (431DE1BF)
9a08d000 9a08f8a0 klognt klognt.sys Tue Sep 06 22:53:54 2005 (431DD0AA)
9a0b9000 9a0bc1e0 pdlnemsg pdlnemsg.sys Wed Sep 07 00:06:48 2005 (431DE1C0)
9a0d1000 9a0e6580 irda irda.sys Wed Aug 04 11:30:50 2004 (41107B92)
9c0e7000 9c1bc700 dump_iastor dump_iastor.sys Thu Oct 13 00:37:10 2005 (434D5EDE)
9c1d5000 9c1d9b80 agnwifi agnwifi.sys Fri Apr 30 02:49:16 2004 (40917154)
9c1dd000 9c1e2b00 vmnetbridge vmnetbridge.sys Tue Nov 14 02:10:07 2006 (4558D827)
9c1e5000 9c1e9b20 AegisP AegisP.sys Thu Dec 15 21:01:20 2005 (43A18C48)
9c46c000 9c46de00 nstrcnt nstrcnt.sys Tue Sep 06 22:50:58 2005 (431DCFFA)
9c6b7000 9c6c6900 Cdfs Cdfs.SYS Wed Aug 04 11:44:09 2004 (41107EB1)
9da15000 9da16a80 pdlncbas pdlncbas.sys Wed Sep 07 00:06:57 2005 (431DE1C9)
9fe59000 9fec7a00 mrxsmb mrxsmb.sys Fri May 05 15:11:42 2006 (445B1DD6)
9ff6f000 9ff99a00 rdbss rdbss.sys Fri May 05 15:17:55 2006 (445B1F4B)
a014d000 a016ed00 afd afd.sys Wed Aug 04 11:44:13 2004 (41107EB5)
a029f000 a02e2440 vsdatant vsdatant.sys Thu Feb 16 06:44:59 2006 (43F3D213)
a0328000 a0330000 pdlnctdl pdlnctdl.sys Wed Sep 07 00:07:23 2005 (431DE1E3)
a0360000 a0368000 Smapint Smapint.sys Wed Dec 04 19:28:05 2002 (3DEE09ED)
a0370000 a0376000 TDSMAPI TDSMAPI.SYS Mon Oct 24 15:03:31 2005 (435CAA6B)
a03cd000 a03d5880 Fips Fips.SYS Sat Aug 18 07:01:49 2001 (3B7DC585)
a04de000 a0505c00 netbt netbt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
a0572000 a0592f00 ipnat ipnat.sys Thu Sep 30 03:58:36 2004 (415B3714)
a0593000 a05d2ec0 SYMTDI SYMTDI.SYS Tue Aug 09 02:14:50 2005 (42F7C442)
a062a000 a0681d80 tcpip tcpip.sys Thu Apr 20 17:21:47 2006 (444775D3)
a072c000 a073e400 ipsec ipsec.sys Wed Aug 04 11:44:27 2004 (41107EC3)
a07ab000 a07b3700 netbios netbios.sys Wed Aug 04 11:33:19 2004 (41107C27)
a081b000 a0820000 Tppwrif Tppwrif.sys Tue Nov 30 13:08:22 2004 (41AC236E)
a0823000 a0829000 TSMAPIP TSMAPIP.SYS Fri Jun 28 09:29:23 2002 (3D1BDF1B)
a09bf000 a09c7700 wanarp wanarp.sys Wed Aug 04 11:34:57 2004 (41107C89)
a0a0f000 a0a17900 msgpc msgpc.sys Wed Aug 04 11:34:11 2004 (41107C5B)
a0d27000 a0d282e0 EGATHDRV EGATHDRV.SYS Mon Aug 23 21:52:04 2004 (412A19AC)
a0f00000 a0f04020 TPHKDRV TPHKDRV.SYS Tue Jul 05 11:27:04 2005 (42CA2130)
a0f18000 a0f1f880 Npfs Npfs.SYS Wed Aug 04 11:30:38 2004 (41107B86)
a0f28000 a0f2ca80 Msfs Msfs.SYS Wed Aug 04 11:30:37 2004 (41107B85)
a1170000 a1181440 naveng naveng.sys Fri Mar 16 10:04:29 2007 (45FA1E55)
a11a7000 a1275820 navex15 navex15.sys Fri Mar 16 10:44:23 2007 (45FA27AF)
a1298000 a129ad00 ANC ANC.SYS Mon Mar 22 10:38:44 2004 (405E74DC)
a13a8000 a13bb000 Savrtpel Savrtpel.sys Sat Jun 18 03:28:42 2005 (42B34792)
a13bb000 a13d7cc0 SYMEVENT SYMEVENT.SYS Wed Jul 20 07:40:15 2005 (42DDB287)
a13d8000 a142d000 savrt savrt.sys Sat Jun 18 03:28:41 2005 (42B34791)
a2043000 a2048200 vga vga.sys Wed Aug 04 11:37:06 2004 (41107D0A)
a2e03000 a2e09180 HIDPARSE HIDPARSE.SYS Wed Aug 04 11:38:15 2004 (41107D4F)
a2f9b000 a2f9c780 IBMBLDID IBMBLDID.sys Thu Jan 12 21:03:21 2006 (43C676C1)
a2f9d000 a2f9e280 ShockMgr ShockMgr.SYS Mon Jun 20 08:48:00 2005 (42B63568)
a3051000 a305f100 usbhub usbhub.sys Wed Aug 04 11:38:40 2004 (41107D68)
a433e000 a433f400 PMEMNT PMEMNT.SYS Thu Sep 30 21:21:09 1999 (37F386ED)
a65b2000 a65b3080 RDPCDD RDPCDD.sys Sat Aug 18 02:16:56 2001 (3B7D82C0)
a65b8000 a65b9080 mnmdd mnmdd.SYS Sat Aug 18 02:27:28 2001 (3B7D8538)
a65c0000 a65c1080 Beep Beep.SYS Sat Aug 18 02:17:33 2001 (3B7D82E5)
a65c2000 a65c3f00 Fs_Rec Fs_Rec.SYS Sat Aug 18 02:19:37 2001 (3B7D8361)
a7926000 a79dc000 hsx_cnxt hsx_cnxt.sys Wed Dec 07 00:50:41 2005 (4395E489)
a79dc000 a7ad3000 hsx_dpv hsx_dpv.sys Wed Dec 07 00:51:27 2005 (4395E4B7)
a7ad3000 a7b0d000 hsxhwazl hsxhwazl.sys Wed Dec 07 00:50:47 2005 (4395E48F)
a7b0d000 a7b32580 AEAudio AEAudio.sys Wed Jun 08 02:23:44 2005 (42A60958)
a7b33000 a7b62000 ADIHdAud ADIHdAud.sys Tue Jan 31 20:49:33 2006 (43DF8005)
a7eca000 a7ecc900 Dxapi Dxapi.sys Sat Aug 18 02:23:19 2001 (3B7D843F)
a82b9000 a82be770 pdlnslea pdlnslea.sys Wed Sep 07 00:08:16 2005 (431DE218)
a82c1000 a82c9000 pdlndint pdlndint.sys Wed Sep 07 00:07:30 2005 (431DE1EA)
a82c9000 a82cde10 pdlnepkt pdlnepkt.sys Wed Sep 07 00:06:52 2005 (431DE1C4)
a82d1000 a82d6960 anydlc anydlc.sys Tue Sep 06 23:39:54 2005 (431DDB72)
a8c35000 a8c3c580 Modem Modem.SYS Wed Aug 04 11:38:04 2004 (41107D44)
a8ccb000 a8cd3cd0 pdlnafac pdlnafac.sys Wed Sep 07 00:09:09 2005 (431DE24D)
a8cdb000 a8ce9440 pdlnsx25 pdlnsx25.sys Wed Sep 07 00:08:36 2005 (431DE22C)
a8ceb000 a8cf8490 pdlnsv25 pdlnsv25.sys Wed Sep 07 00:08:29 2005 (431DE225)
a8cfb000 a8d09870 pdlnshay pdlnshay.sys Wed Sep 07 00:08:26 2005 (431DE222)
a8d0b000 a8d15000 pdlnatdl pdlnatdl.sys Wed Sep 07 00:07:22 2005 (431DE1E2)
a8d1b000 a8d274a0 pdlnecfg pdlnecfg.sys Wed Sep 07 00:06:55 2005 (431DE1C7)
a8e35000 a8e3f000 pdlnatcm pdlnatcm.sys Wed Sep 07 00:07:20 2005 (431DE1E0)
b8fe4000 b9005700 portcls portcls.sys Wed Mar 17 00:28:17 2004 (40574E49)
b9006000 b9053d60 btaudio btaudio.sys Tue Apr 25 11:14:04 2006 (444DB724)
b9054000 b9087200 update update.sys Wed Aug 04 11:28:32 2004 (41107B08)
b9088000 b90b8100 rdpdr rdpdr.sys Wed Aug 04 11:31:10 2004 (41107BA6)
b90b9000 b90cf680 ndiswan ndiswan.sys Wed Aug 04 11:44:30 2004 (41107EC6)
b90d0000 b919bb80 btkrnl btkrnl.sys Tue Apr 25 11:11:15 2006 (444DB67B)
b919c000 b91c5b80 abvpn2k abvpn2k.sys Sat Jul 09 02:44:26 2005 (42CEECB2)
b91c6000 b91e8680 ks ks.sys Wed Aug 04 11:45:20 2004 (41107EF8)
b91e9000 b9214600 SynTP SynTP.sys Wed Feb 15 03:34:56 2006 (43F25408)
b9215000 b9237e80 USBPORT USBPORT.SYS Wed Aug 04 11:38:34 2004 (41107D62)
b9238000 b92aacc0 ar5211 ar5211.sys Wed Dec 21 23:49:09 2005 (43A99C9D)
b92d8000 b92fd000 HDAudBus HDAudBus.sys Sat Jan 08 06:37:15 2005 (41DF3243)
b92fd000 b9310780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 11:37:04 2004 (41107D08)
b9311000 b9494000 ati2mtag ati2mtag.sys Sat Mar 25 09:38:43 2006 (4424C24B)
b94b0000 b94b2280 rasacd rasacd.sys Sat Aug 18 02:25:39 2001 (3B7D84CB)
b9a64000 b9a6d480 NDProxy NDProxy.SYS Sat Aug 18 02:25:30 2001 (3B7D84C2)
b9a74000 b9a82b80 drmk drmk.sys Wed Aug 04 11:37:54 2004 (41107D3A)
b9a94000 b9a9df00 termdd termdd.sys Wed Aug 04 11:28:52 2004 (41107B1C)
b9aa4000 b9aafd00 raspptp raspptp.sys Wed Aug 04 11:44:26 2004 (41107EC2)
b9ab4000 b9abe200 raspppoe raspppoe.sys Wed Aug 04 11:35:06 2004 (41107C92)
b9ac4000 b9ad0880 rasl2tp rasl2tp.sys Wed Aug 04 11:44:21 2004 (41107EBD)
b9ad4000 b9adf200 tshd4_kern_i386 tshd4_kern_i386.sys Tue Nov 21 04:49:41 2006 (4562380D)
b9d60000 b9d67000 nscirda nscirda.sys Wed Aug 04 11:30:49 2004 (41107B91)
b9d68000 b9d6da00 mouclass mouclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
b9d70000 b9d76000 kbdclass kbdclass.sys Wed Aug 04 11:28:32 2004 (41107B08)
b9d78000 b9d7e800 usbehci usbehci.sys Wed Aug 04 11:38:34 2004 (41107D62)
b9d80000 b9d85000 usbuhci usbuhci.sys Wed Aug 04 11:38:34 2004 (41107D62)
ba1e5000 ba1e5740 PQNTDrv PQNTDrv.SYS Fri Aug 10 15:29:11 2001 (3B73B06F)
ba1f0000 ba1f2c00 irenum irenum.sys Wed Aug 04 11:30:45 2004 (41107B8D)
ba932000 ba932d00 dxgthk dxgthk.sys Sat Aug 18 02:23:12 2001 (3B7D8438)
ba981000 ba98a180 csiidecoder_kern_i386 csiidecoder_kern_i386.sys Tue Nov 21 04:49:43 2006 (4562380F)
ba991000 ba999580 srs_sscfilter srs_sscfilter.sys Tue Nov 21 04:49:46 2006 (45623812)
ba9a1000 ba9af080 redbook redbook.sys Wed Aug 04 11:29:34 2004 (41107B46)
ba9b1000 ba9bd180 cdrom cdrom.sys Wed Aug 04 11:29:52 2004 (41107B58)
ba9c1000 ba9cb380 imapi imapi.sys Wed Aug 04 11:30:12 2004 (41107B6C)
ba9d1000 ba9dde00 i8042prt i8042prt.sys Wed Aug 04 11:44:36 2004 (41107ECC)
ba9e1000 ba9e9d00 intelppm intelppm.sys Wed Aug 04 11:29:19 2004 (41107B37)
baa11000 baa1b000 hcmon hcmon.sys Tue Nov 14 02:09:38 2006 (4558D80A)
bac2a000 bac2e580 ptilink ptilink.sys Sat Aug 18 02:19:53 2001 (3B7D8371)
bac32000 bac36880 TDI TDI.SYS Wed Aug 04 11:37:47 2004 (41107D33)
bac3a000 bac3ec80 rasirda rasirda.sys Sat Aug 18 02:21:29 2001 (3B7D83D1)
bac42000 bac49d00 wowhd_kern_i386 wowhd_kern_i386.sys Tue Nov 21 04:49:42 2006 (4562380E)
bac4a000 bac52000 atmeltpm atmeltpm.sys Tue May 17 19:50:06 2005 (4289FD96)
bac72000 bac77500 TDTCP TDTCP.SYS Wed Aug 04 11:28:52 2004 (41107B1C)
bace5000 bace7800 VMNET VMNET.SYS Thu Dec 16 13:43:19 2004 (41C1439F)
bace9000 baceb580 vmnetadapter vmnetadapter.sys Thu Dec 16 13:43:25 2004 (41C143A5)
baced000 bacf0c80 mssmbios mssmbios.sys Wed Aug 04 11:37:47 2004 (41107D33)
bacfd000 bacff580 ndistapi ndistapi.sys Sat Aug 18 02:25:29 2001 (3B7D84C1)
bad11000 bad13780 ibmpmdrv ibmpmdrv.sys Fri Nov 11 11:26:12 2005 (4374327C)
bad15000 bad18700 CmBatt CmBatt.sys Wed Aug 04 11:37:39 2004 (41107D2B)
badfd000 bae17580 Mup Mup.sys Wed Aug 04 11:45:20 2004 (41107EF8)
bae18000 bae44a80 NDIS NDIS.sys Wed Aug 04 11:44:27 2004 (41107EC3)
bae45000 baed1480 Ntfs Ntfs.sys Wed Aug 04 11:45:06 2004 (41107EEA)
baed2000 baee8780 KSecDD KSecDD.sys Wed Aug 04 11:29:45 2004 (41107B51)
baee9000 baefaf00 sr sr.sys Wed Aug 04 11:36:22 2004 (41107CDE)
baefb000 baf1a780 fltMgr fltMgr.sys Mon Aug 21 14:44:57 2006 (44E97991)
baf1b000 baf46d80 dac2w2k dac2w2k.sys Sat Aug 18 02:22:13 2001 (3B7D83FD)
bafe7000 bafffe00 adpu160m adpu160m.sys Wed May 30 14:48:22 2001 (3B14BADE)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 19:17:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 11:30:51 2004 (41107B93)
bf9d5000 bfa18000 ati2dvag ati2dvag.dll Sat Mar 25 09:39:04 2006 (4424C260)
bfa18000 bfa57000 ati2cqag ati2cqag.dll Sat Mar 25 08:21:27 2006 (4424B02F)
bfa57000 bfa8d000 atikvmag atikvmag.dll Sat Mar 25 08:57:05 2006 (4424B889)
bfa8d000 bfd17120 ati3duag ati3duag.dll Sat Mar 25 09:20:52 2006 (4424BE1C)
bfd18000 bfe2c100 ativvaxx ativvaxx.dll Sat Mar 25 09:13:42 2006 (4424BC6E)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 13:26:56 2004 (411096C8)
f744f000 f7466480 atapi atapi.sys Wed Aug 04 11:29:41 2004 (41107B4D)
f7467000 f747e800 SCSIPORT SCSIPORT.SYS Wed Aug 04 11:29:39 2004 (41107B4B)
f747f000 f7493f00 Shockprf Shockprf.sys Wed Nov 30 12:28:27 2005 (438D4D93)
f7494000 f74b9700 dmio dmio.sys Wed Aug 04 11:37:13 2004 (41107D11)
f74ba000 f74d8880 ftdisk ftdisk.sys Sat Aug 18 02:22:41 2001 (3B7D8419)
f74d9000 f74f6480 pcmcia pcmcia.sys Wed Aug 04 11:37:45 2004 (41107D31)
f7517000 f7521d80 surroundhp_kern_i386 surroundhp_kern_i386.sys Tue Nov 21 04:49:42 2006 (4562380E)
f7567000 f7571f80 agpCPQ agpCPQ.sys Wed Aug 04 11:37:42 2004 (41107D2E)
f7577000 f7581580 agp440 agp440.sys Wed Aug 04 11:37:40 2004 (41107D2C)
f7587000 f7591800 amdagp amdagp.sys Wed Aug 04 11:37:42 2004 (41107D2E)
f7597000 f75a7a80 pci pci.sys Wed Aug 04 11:37:45 2004 (41107D31)
f75a8000 f75d5d80 ACPI ACPI.sys Wed Aug 04 11:37:35 2004 (41107D27)
f75f7000 f75ffc00 isapnp isapnp.sys Sat Aug 18 02:28:01 2001 (3B7D8559)
f7607000 f7611500 MountMgr MountMgr.sys Wed Aug 04 11:28:29 2004 (41107B05)
f7617000 f7623c80 VolSnap VolSnap.sys Wed Aug 04 11:30:14 2004 (41107B6E)
f7627000 f7634e80 aic78xx aic78xx.sys Fri May 11 01:53:40 2001 (3AFAF8CC)
f7637000 f763f180 ql10wnt ql10wnt.sys Sat Aug 18 02:22:14 2001 (3B7D83FE)
f7647000 f7650e00 ql1240 ql1240.sys Sat Aug 18 02:22:14 2001 (3B7D83FE)
f7657000 f7664780 aic78u2 aic78u2.sys Fri May 11 01:53:41 2001 (3AFAF8CD)
f7667000 f766ff80 ultra ultra.sys Sat Aug 18 02:22:19 2001 (3B7D8403)
f7677000 f7680d80 ql1080 ql1080.sys Sat Aug 18 02:22:18 2001 (3B7D8402)
f7687000 f7692f80 ql1280 ql1280.sys Sat Aug 18 02:22:16 2001 (3B7D8400)
f7697000 f76a2100 ql12160 ql12160.sys Sat Aug 18 02:22:18 2001 (3B7D8402)
f76a7000 f76afe00 disk disk.sys Wed Aug 04 11:29:53 2004 (41107B59)
f76b7000 f76c3200 CLASSPNP CLASSPNP.SYS Wed Aug 04 11:44:26 2004 (41107EC2)
f76c7000 f76cfb80 PxHelp20 PxHelp20.sys Wed Oct 18 23:03:53 2006 (45366581)
f76d7000 f76e1080 sisagp sisagp.sys Wed Aug 04 11:37:42 2004 (41107D2E)
f76e7000 f76f1500 viaagp viaagp.sys Wed Aug 04 11:37:42 2004 (41107D2E)
f76f7000 f7701700 alim1541 alim1541.sys Wed Aug 04 11:37:40 2004 (41107D2C)
f7707000 f770d200 PCIIDEX PCIIDEX.SYS Wed Aug 04 11:29:40 2004 (41107B4C)
f770f000 f7713900 PartMgr PartMgr.sys Sat Aug 18 07:02:23 2001 (3B7DC5A7)
f7717000 f771ba80 sparrow sparrow.sys Fri Dec 08 23:10:58 2000 (3A311D2A)
f771f000 f7725780 asc asc.sys Sat Aug 18 02:21:58 2001 (3B7D83EE)
f7727000 f772b380 mraid35x mraid35x.sys Sat Aug 18 02:22:11 2001 (3B7D83FB)
f772f000 f7733880 i2omp i2omp.sys Wed Aug 04 11:30:49 2004 (41107B91)
f7737000 f773ef80 symc8xx symc8xx.sys Fri Dec 08 23:10:59 2000 (3A311D2B)
f773f000 f7745ee0 sym_hi sym_hi.sys Tue Mar 20 11:21:22 2001 (3AB6EFDA)
f7747000 f774e7e0 sym_u3 sym_u3.sys Tue Mar 20 11:06:17 2001 (3AB6EC51)
f774f000 f7754c00 ABP480N5 ABP480N5.SYS Sat Aug 18 02:21:59 2001 (3B7D83EF)
f7757000 f775c780 asc3350p asc3350p.sys Sat Aug 18 02:22:01 2001 (3B7D83F1)
f775f000 f7763ee0 dpti2o dpti2o.sys Wed Mar 21 00:37:16 2001 (3AB7AA64)
f7767000 f776daa0 perc2 perc2.sys Mon Apr 23 16:21:37 2001 (3AE40939)
f776f000 f7775560 hpn hpn.sys Mon Apr 23 16:21:37 2001 (3AE40939)
f778f000 f7793080 raspti raspti.sys Sat Aug 18 02:25:32 2001 (3B7D84C4)
f77df000 f77e3500 watchdog watchdog.sys Wed Aug 04 11:37:32 2004 (41107D24)
f7897000 f789a000 BOOTVID BOOTVID.dll Sat Aug 18 02:19:09 2001 (3B7D8345)
f789b000 f789d480 compbatt compbatt.sys Sat Aug 18 02:27:58 2001 (3B7D8556)
f789f000 f78a2700 BATTC BATTC.SYS Sat Aug 18 02:27:52 2001 (3B7D8550)
f78a3000 f78a5d80 ACPIEC ACPIEC.sys Sat Aug 18 02:27:55 2001 (3B7D8553)
f78a7000 f78aaa80 cpqarray cpqarray.sys Sat Aug 18 02:22:05 2001 (3B7D83F5)
f78ab000 f78ae200 aha154x aha154x.sys Sat Aug 18 02:21:59 2001 (3B7D83EF)
f78af000 f78b2f80 symc810 symc810.sys Fri Dec 08 23:10:59 2000 (3A311D2B)
f78b3000 f78b6980 dac960nt dac960nt.sys Sat Aug 18 02:22:13 2001 (3B7D83FD)
f78b7000 f78b9f00 amsint amsint.sys Sat Aug 18 02:22:01 2001 (3B7D83F1)
f78bb000 f78bea00 asc3550 asc3550.sys Sat Aug 18 02:21:56 2001 (3B7D83EC)
f78bf000 f78c2e80 ini910u ini910u.sys Sat Aug 18 02:22:07 2001 (3B7D83F7)
f78c3000 f78c6680 cbidf2k cbidf2k.sys Sat Aug 18 02:22:06 2001 (3B7D83F6)
f78d3000 f78d6280 ndisuio ndisuio.sys Wed Aug 04 11:33:10 2004 (41107C1E)
f7987000 f7988b80 kdcom kdcom.dll Sat Aug 18 02:19:10 2001 (3B7D8346)
f7989000 f798a100 WMILIB WMILIB.SYS Sat Aug 18 02:37:23 2001 (3B7D878B)
f798b000 f798c480 aliide aliide.sys Sat Aug 18 02:21:54 2001 (3B7D83EA)
f798d000 f798ea00 cmdide cmdide.sys Sat Aug 18 02:21:51 2001 (3B7D83E7)
f798f000 f7990380 toside toside.sys Sat Aug 18 02:21:52 2001 (3B7D83E8)
f7991000 f7992500 viaide viaide.sys Wed Aug 04 11:29:42 2004 (41107B4E)
f7993000 f7994580 intelide intelide.sys Wed Aug 04 11:29:40 2004 (41107B4C)
f7995000 f7996700 dmload dmload.sys Sat Aug 18 02:28:15 2001 (3B7D8567)
f7997000 f7998e00 cd20xrnt cd20xrnt.sys Sat Aug 18 02:22:04 2001 (3B7D83F4)
f7999000 f799a580 perc2hib perc2hib.sys Mon Apr 23 16:21:37 2001 (3AE40939)
f79fb000 f79fd000 i2omgmt i2omgmt.SYS Wed Aug 04 11:30:50 2004 (41107B92)
f79ff000 f7a00280 USBD USBD.SYS Sat Aug 18 02:32:58 2001 (3B7D8682)
f7a01000 f7a02100 swenum swenum.sys Wed Aug 04 11:28:41 2004 (41107B11)
f7a4f000 f7a4fd00 pciide pciide.sys Sat Aug 18 02:21:49 2001 (3B7D83E5)
f7a50000 f7a50d80 OPRGHDLR OPRGHDLR.SYS Sat Aug 18 02:27:55 2001 (3B7D8553)
f7a6b000 f7a6bb80 Null Null.SYS Sat Aug 18 02:17:39 2001 (3B7D82EB)
f7a6f000 f7a6fc00 audstub audstub.sys Sat Aug 18 02:29:40 2001 (3B7D85BC)
f7b09000 f7bde700 iaStor iaStor.sys Thu Oct 13 00:37:10 2005 (434D5EDE)

Unloaded modules:
97809000 97836000 e1e5132.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a65ba000 a65bc000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
97836000 97861000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
98f4d000 98f78000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba253000 ba254000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
99033000 99040000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
98fa0000 98fc3000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
990f0000 990fe000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
9cc0d000 9cc0f000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b92ab000 b92d8000 e1e5132.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a2e67000 a2e6b000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a2e0b000 a2e10000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

yeah i have zone alarm.. but thats a customized one and very minimally used for my company firewall policies.. i doubt i can unintall that.. well i wil try to re-install and check if that works... it's not giving problem wot other colleague of mine with same configuration Laptop... will keep u updated....

thanks a lot for your help ...

 

Hi, ayaduka. Welcome to Windows BBS!

Here's another angle to investigate.

I Googled abvpn2k.sys and came up with only 22 results.

In one of those results, a person stated (in post #190) about abvpn2k.sys,

However, the poster did not identify the firewall he was referring to.

While I have ZoneAlarm Pro installed and running on my computer, abvpn2k.sys does not exist anywhere on my computer (as far as I can tell). I searched with Windows XP's native Search utility and didn't find the file.

Therefore, I wonder if you have (or had) another firewall installed on your computer. If so, then there may be a firewall conflict that is causing your BSODs.

If you had another firewall installed on your computer and you uninstalled it before installing ZoneAlarm, perhaps the uninstall did not remove all parts of the old firewall.

Perhaps you can locate the abvpn2k.sys file on your computer. If so,

• Right-click on the filename
• Select "Properties "

Perhaps the information about abvpn2k.sys displayed there will tell us what vendor the file belongs to.

EDIT: By the way, the filename abvpn2k.sys makes me wonder if the file is part of Virtual Private Network (VPN) software on your computer. If so, then perhaps your ZoneAlarm is improperly configured to work with your VPN software.

 

One of the Google results states that abvpn2k.sys belongs to AT&T Global Net Firewall.

 

Hi, Pete. Thanks.

I knew what you picked up on. That is why I pursued the abvpn2k.sys angle (since I run ZoneAlarm Pro and didn't locate the abvpn2k.sys file on my computer)... and also added my EDIT above.

ZoneAlarm Pro has an "Advanced" setting for "Allow VPN protocols" and the version of ZoneAlarm that ayaduka is using might have a similar setting.

 

Hi, peterdiva. Welcome to Windows BBS!

Thanks! I assume the result you are referring to is here.

Looks like ayaduka might make some progress with this info.

 

Hi again, ayaduka.

I'm sorry about cluttering this thread with so many of my posts, but I can't get this off my mind until I post the following.

If you indeed have ZoneAlarm and the AT&T Global Net Firewall (or some other software firewall) running at the same time, then you need to know...

Running two or more software firewalls concurrently is commonly discouraged because the firewalls tend to "fight" each other for control over network traffic [which may be the cause of your "Blue Screens of Death" (BSODs)].

You should be sure you don't also have Windows XP's native firewall active while using another firewall. Click on the "KB889740" link below for details.

According to Microsoft's Knowledge Base article, KB889740,

Therefore, it appears (to me) you have the following two options. (Option 2 might be the better choice in your case.) Read the information in the last section of this message for leads on another possibly better avenue to investigate.

==============

OPTION 1:

Follow PeteC's suggestion and

• disconnect from the Internet (as a precaution),
• shut down your ZoneAlarm firewall (by right-clicking on the ZoneAlarm icon in your tool tray and selecting "Shutdown ZoneAlarm "),
• uninstall your ZoneAlarm firewall, and then
• reboot (restart) your computer.

Then configure your AT&T Global Net Firewall to conform to your company's policies.

==============

OPTION 2:

If ZoneAlarm was customized/installed by your company (and you or your Internet Service Provider installed the AT&T Global Network Client/Firewall), then your better choice might be to deactivate the AT&T Global Net Firewall component and use just ZoneAlarm instead. (EDIT: In this case, you might want to make sure ZoneAlarm is configured to "allow VPN protocols" as I mentioned in a post above.)

==============

(EDIT: I removed information from this section after further research described in the section below.)

==============

I found a 10-page AT&T Global Network Client Version History (v6versionhistory.pdf) (FTP link to attglobal.net). It appears your version is rather old and several fixes/enhancements have been applied since August 10, 2005. The latest AT&T Global Network Client version is "Version 6.9 "“ January 15, 2007" (according to the document).

NOTE: You will need to have the Adobe Reader (or another PDF-compatible reader) installed on your computer to be able to view .PDF documents.

Here are all the references to "Zone Labs" (producer of ZoneAlarm) in that AT&T Global Network Client Version History document...

*Since it appears the AT&T Global Network Client might use Zone Labs software components (including vsmon.exe) in its own firewall, you might actually have only one active firewall after all. Therefore, your best course of action might be to simply upgrade your AT&T Global Network Client software.

According to this AT&T Global Network Client download page (HTTPS link to help.attbusiness.net), the latest English AT&T Global Network Client is Version 7.0.1 - May 24, 2007. Older v6.x versions (but newer than your version) of AT&T Global Network Client are also apparently available from that download page.

The following potentially helpful .PDF documents can also be downloaded from the AT&T Global Network Client download page (HTTPS link to help.attbusiness.net):

• User´s Guide for v6.x AT&T Global Network Client for Windows (usersguide.pdf) (FTP link to attglobal.net)
  (The Table of Contents is quoted in my EDIT below.)
• Upgrade User´s Guide for the AT&T Global Network Client for Windows (upgradeusersguide.pdf) (FTP link to attglobal.net)

I suggest you consult with your company's IT System Administrator before performing any of these possible courses of action.

I hope this helps! Please keep us informed about your progress.


EDIT: I downloaded the User´s Guide for v6.x AT&T Global Network Client for Windows and discovered the AT&T Global Network Client's firewall apparently IS "powered by Zone Labs ". (Click on the attached thumbnail image below.)

Here is the text from the table of contents.