I have been running Vista x64 with SP1 installed since it was released and
last week I suddenly got a blue screen problem.

The blue screen says SYSTEM_SERVICE_EXCEPTION and reports error code 3B.
I have been able to track it down to soem problem with RASSSTP.SYS and the
crash occurs when the Secure Socket Tunneling Protocol Service is started
about 10-30 seconds after I logon and the desktop appears.

I have temporarily been able to get the computer into a working state by
disabling this service but the RAS Services doesn't run and I need them for
VPN connectivity.

The problem first occured last week after a reboot. I don't know if the
problem is related to some update that was installed at that point but I know
of only two pieces of software that I installed last week: New NVidia drivers
for Latutude D630 and the new Microsoft Virtual PC 2007 SP1. I have tried
uninstalling both of them but the problem is still there.

The device manager shows a set of WAN Miniport network adapters with
problems loading their driver, I assume this is caused by the disabled
services.



Anyone got tips on how to resolve this? I was looking to do some repair
installation or similar but the system restore points on my machine seems to
be broken also.

In some cases, after installing a SP or upgarde, you need to upgrade
hardware driver. Or troubleshooting collections may help.
Troubleshooting Vista Blue Screen and Stop Errors
Fixed Vista Blue Screen by installing BIOS on Dell computer · Vista
blue screen because of Catalyst 7.3 drivers · Vista blue screen because of
NVDIA driver ...
www.chicagotech.net/vista/vistabluescreen.htm


Troubleshooting Vista Blue Screen and Stop Errors
Fixed Vista Blue Screen by installing BIOS on Dell computer · Vista
blue screen because of Catalyst 7.3 drivers · Vista blue screen because of
NVDIA driver ...
www.chicagotech.net/vista/vistabluescreen.htm


--
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
"Per Salmi" <PerSalmi@xxxxxx> wrote in message
newsCDA7B67-837B-4DFF-AA1C-FC7D535A52B9@xxxxxx

>I have been running Vista x64 with SP1 installed since it was released and
> last week I suddenly got a blue screen problem.
>
> The blue screen says SYSTEM_SERVICE_EXCEPTION and reports error code 3B.
> I have been able to track it down to soem problem with RASSSTP.SYS and the
> crash occurs when the Secure Socket Tunneling Protocol Service is started
> about 10-30 seconds after I logon and the desktop appears.
>
> I have temporarily been able to get the computer into a working state by
> disabling this service but the RAS Services doesn't run and I need them
> for
> VPN connectivity.
>
> The problem first occured last week after a reboot. I don't know if the
> problem is related to some update that was installed at that point but I
> know
> of only two pieces of software that I installed last week: New NVidia
> drivers
> for Latutude D630 and the new Microsoft Virtual PC 2007 SP1. I have tried
> uninstalling both of them but the problem is still there.
>
> The device manager shows a set of WAN Miniport network adapters with
> problems loading their driver, I assume this is caused by the disabled
> services.
>
> Anyone got tips on how to resolve this? I was looking to do some repair
> installation or similar but the system restore points on my machine seems
> to
> be broken also.
>
>

I am not using Dell but I have similar issue BSOD upon connecting configured my VPN using SSTP. I tried to follow your advise by updating NVDIA drivers but there is no updated driver for my Forceware NIC. I did uninstall the driver using Guru3D in Safe Mode and re-install the NIC driver. However, I am still having BSOD issue.

Here is my dump file:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffffa80084de94c, 0, 24}

Probably caused by : afd.sys ( afd!AfdCreateConnection+1b1 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa80084de94c, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000024, Parameter 1 of the exception

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

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

FAULTING_IP:
+fffffa80084de94c
fffffa80`084de94c ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000024

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003832080
0000000000000024

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffa600c6c3580 -- (.trap 0xfffffa600c6c3580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000001 rcx=fffffa800aaa7d20
rdx=fffffffffdc3f50c rsi=fffffa600c6c36e0 rdi=fffffa600c6c36f0
rip=fffffa80084de94c rsp=fffffa600c6c3710 rbp=fffffa80082f7ab0
r8=0000000000000000 r9=0000000000000000 r10=623fbb010002007e
r11=fffffa800aaa7d64 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffffa80`084de94c ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003637e67 to fffff8000365e390

STACK_TEXT:
fffffa60`0c6c2d98 fffff800`03637e67 : 00000000`0000001e ffffffff`c0000005 fffffa80`084de94c 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0c6c2da0 fffff800`0365e1e9 : fffffa60`0c6c34d8 fffffa80`0aaa7d20 fffffa60`0c6c3580 fffffa80`07e71200 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`0c6c33a0 fffff800`0365cfe5 : 00000000`00000000 fffffa80`0aa36302 fffffa80`0a6a5c00 fffffa80`0aaa7d20 : nt!KiExceptionDispatch+0xa9
fffffa60`0c6c3580 fffffa80`084de94c : 00000000`00000000 fffffa60`0c6c3a00 00000000`00000000 fffffa60`0503af31 : nt!KiPageFault+0x1e5
fffffa60`0c6c3710 00000000`00000000 : fffffa60`0c6c3a00 00000000`00000000 fffffa60`0503af31 fffffa80`0595e370 : 0xfffffa80`084de94c
fffffa60`0c6c3718 fffffa60`0c6c3a00 : 00000000`00000000 fffffa60`0503af31 fffffa80`0595e370 00000000`00000000 : 0x0
fffffa60`0c6c3720 00000000`00000000 : fffffa60`0503af31 fffffa80`0595e370 00000000`00000000 00000000`00000000 : 0xfffffa60`0c6c3a00
fffffa60`0c6c3728 fffffa60`0503af31 : fffffa80`0595e370 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffa60`0c6c3730 fffffa60`0504e895 : fffffa80`0583a7b0 fffffa60`0c6c3ca0 fffffa80`0543cfb8 fffffa80`0543ce10 : afd!AfdCreateConnection+0x1b1
fffffa60`0c6c3860 fffff800`038e425a : fffffa80`0543ce10 fffffa80`0aa3bc90 fffffa80`0595e370 fffffa80`086e7210 : afd! ?? ::GFJBLGFE::`string'+0x80cd
fffffa60`0c6c39f0 fffff800`038fcf76 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`035145c0 : nt!IopXxxControlFile+0x5da
fffffa60`0c6c3b40 fffff800`0365de33 : 00000000`00000000 fffff683`ff7e5c50 00000000`0283f2f8 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffffa60`0c6c3bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

STACK_COMMAND: kb

FOLLOWUP_IP:
afd!AfdCreateConnection+1b1
fffffa60`0503af31 4881c4f8000000 add rsp,0F8h

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: afd!AfdCreateConnection+1b1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: afd

IMAGE_NAME: afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919ad7

FAILURE_BUCKET_ID: X64_0x1E_afd!AfdCreateConnection+1b1

BUCKET_ID: X64_0x1E_afd!AfdCreateConnection+1b1

Followup: MachineOwner

Never mind....I found the solution to my issue...

I reset my TCP/IP stack by using the following command

netsh int ip reset

after reboot, it resolved my BSOD issue upon connection using Vista VPN in SSTP.