Windows 2003 crashes after successful VPN connection

July 15, 2007

Hi,

I have a windows 2003 server, which is also a VPN server. Everytime after I

have connected via remote, it crashes.

It then gives a stop error when it reboot

0x000000d1 (0x00000006, 0xd0000002, 0x00000000, 0xf75683de)

I ran a dumpchk and got the following; Any help appreciated.

thanks

Jin

Microsoft ® Windows Debugger Version 6.6.0007.5

Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:

SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free

x86 compatible

Product: LanManNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp2_gdr.070304-2240

Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8

Debug session time: Sun Jul 15 23:49:08.641 2007 (GMT+8)

System Uptime: 0 days 2:08:34.043

Loading Kernel Symbols

......................................................................................................................

Loading User Symbols

Loading unloaded module list

..........

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

*

* Bugcheck Analysis

*

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {6, d0000002, 0, f712d3de}

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

baspxp32.sys

Probably caused by : baspxp32.sys ( baspxp32+13de )

Followup: MachineOwner

---------

2: kd>

2: kd> !analyze -v

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

*

* Bugcheck Analysis

*

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 00000006, memory referenced

Arg2: d0000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: f712d3de, address which referenced memory

Debugging Details:

------------------

READ_ADDRESS: 00000006

CURRENT_IRQL: 2

FAULTING_IP:

baspxp32+13de

f712d3de f6460605 test byte ptr [esi+6],5

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: f78ee8ac -- (.trap fffffffff78ee8ac)

ErrCode = 00000000

eax=8903f872 ebx=b1414afe ecx=00000005 edx=00000028 esi=00000000 edi=80854211

eip=f712d3de esp=f78ee920 ebp=f78ee92c iopl=0 nv up ei pl nz na po nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202

baspxp32+0x13de:

f712d3de f6460605 test byte ptr [esi+6],5

ds:0023:00000006=??

Resetting default scope

LAST_CONTROL_TRANSFER: from f712d3de to 80836de5

STACK_TEXT:

f78ee8ac f712d3de badb0d00 00000028 f7537000 nt!KiTrap0E+0x2a7

WARNING: Stack unwind information not available. Following frames may be

wrong.

f78ee92c f712eb14 89e4f000 8659e7f0 00000035 baspxp32+0x13de

f78ee960 f712c854 89e4f000 00000035 8a0acab0 baspxp32+0x2b14

f78ee988 f71ffab4 89e4f030 8895ee70 00000082 baspxp32+0x854

f78ee9b0 b98a1a5b 8a08e870 8895ee70 87fd60b0 NDIS!ndisMSendX+0x1cf

f78ee9d8 b98a0b95 88808c38 8895ee70 87fd60b0 tcpip!ARPSendData+0x1a9

f78eea04 b98b27af 87fd60c4 f78eea02 00000001 tcpip!ARPTransmit+0x112

f78eea88 b98c289c 86c70c98 8903f872 00000014 tcpip!IPForwardPkt+0x765

f78eeb10 b98b19d8 89c83968 8903f872 8903f872 tcpip!DeliverToUserEx+0x534

f78eeba4 f758d11a 86c70c98 8903f886 00000013 tcpip!IPRcvPacket+0x6e1

f78eebe8 f758d1c1 0cabb1e5 86c3eed8 8903f864 wanarp!WanReceiveCommon+0x164

f78eec20 f722a605 0cabb1e5 00000000 86d07540 wanarp!WanNdisReceivePacket+0x6d

f78eec74 ba2d1369 8a03f648 f78eecb4 00000001

NDIS!ethFilterDprIndicateReceivePacket+0x209

f78eeca8 ba2d1625 02c61888 86c3eed8 86c61888 ndiswan!IndicateRecvPacket+0x2d0

f78eecdc ba2d1aee 86c61888 8903f808 0000002c ndiswan!ProcessPPPFrame+0x193

f78eecf8 ba2cf533 86c4bb90 8903f808 89ef8f10 ndiswan!ReceivePPP+0x7b

f78eed1c f7223b54 00000001 85ddd52c 0000002c

ndiswan!ProtoWanReceiveIndication+0x106

f78eed3c ba2b48b5 f78eed64 000a6130 00000001 NDIS!NdisMWanIndicateReceive+0x4f

f78eed70 f720b013 89bdfdec 0000002c f78eedac

raspptp!CallProcessRxPackets+0x141

f78eed80 8082db08 89bdfdec 00000000 8a3978d0 NDIS!ndisWorkItemHandler+0xe

f78eedac 80920833 89bdfdec 00000000 00000000 nt!ExpWorkerThread+0xeb

f78eeddc 8083fe9f 8082da4b 00000000 00000000 nt!PspSystemThreadStartup+0x2e

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

baspxp32+13de

f712d3de f6460605 test byte ptr [esi+6],5

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: baspxp32+13de

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: baspxp32

IMAGE_NAME: baspxp32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 40f2dd68

FAILURE_BUCKET_ID: 0xD1_baspxp32+13de

BUCKET_ID: 0xD1_baspxp32+13de

Followup: MachineOwner

---------

2: kd> lmvm baspxp32

start end module name

f712c000 f7138b00 baspxp32 (no symbols)

Loaded symbol image file: baspxp32.sys

Image path: \SystemRoot\system32\DRIVERS\baspxp32.sys

Image name: baspxp32.sys

Timestamp: Tue Jul 13 02:50:16 2004 (40F2DD68)

CheckSum: 0001B833

ImageSize: 0000CB00

Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

July 16, 2007

Re: Windows 2003 crashes after successful VPN connection

You may try these:

1.. Microsoft® Online Crash Analysis.

2.. Use the File Signature Verification tool,.

3.. Use Device Manager to roll back to a previous version of the driver.

4.. Disable the driver identified in the Stop message or any newly installed drivers.

Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net

How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

"Jin" <Jin@discussions.microsoft.com> wrote in message news:3C25EEA3-4F57-45F2-B9C3-6054D441E8AB@microsoft.com...

Hi,

I have a windows 2003 server, which is also a VPN server. Everytime after I

have connected via remote, it crashes.

It then gives a stop error when it reboot

0x000000d1 (0x00000006, 0xd0000002, 0x00000000, 0xf75683de)

I ran a dumpchk and got the following; Any help appreciated.

thanks

Jin

Microsoft ® Windows Debugger Version 6.6.0007.5

Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:

SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free

x86 compatible

Product: LanManNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp2_gdr.070304-2240

Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8

Debug session time: Sun Jul 15 23:49:08.641 2007 (GMT+8)

System Uptime: 0 days 2:08:34.043

Loading Kernel Symbols

.......................................................................................................................

Loading User Symbols

Loading unloaded module list

.........