[Vpn-help] BSOD on Vista Home Premium
Ivan Chou
ivan.chou2 at gmail.com
Tue Oct 27 11:38:51 CDT 2009
FWIW, the VPN client used to run well (albeit with a rare BSOD once
every week) on Vista 64-bit Home Premium with 2.1.4-rc-3. Starting
yesterday, I got the BSOD upon every bootup, with virtualnet.sys
instead of vfilter.sys. I resorted to a last known good config, and
made sure a Windows Update hadn't caused the issue. There were no
recent updates, so I'm really not sure what caused the change. A
fresh uninstall (making sure virtualnet.sys and vfilter.sys were
cleaned out) and re-install to 2.1.5-rc-4 made no difference.
Loading User Symbols
Loading unloaded module list
......
1: 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: fffffa600a60554a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffffa600a60554a, address which referenced memory
Debugging Details:
------------------
FAULTING_MODULE: fffff80002600000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ab9c0f7
READ_ADDRESS: fffffa600a60554a
CURRENT_IRQL: 0
FAULTING_IP:
virtualnet+554a
fffffa60`0a60554a 488b542420 mov rdx,qword ptr [rsp+20h]
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff8000265446e to fffff800026546d0
FAILED_INSTRUCTION_ADDRESS:
virtualnet+554a
fffffa60`0a60554a 488b542420 mov rdx,qword ptr [rsp+20h]
STACK_TEXT:
fffffa60`019c5d28 fffff800`0265446e : 00000000`0000000a
fffffa60`0a60554a 00000000`00000002 00000000`00000008 : nt+0x546d0
fffffa60`019c5d30 00000000`0000000a : fffffa60`0a60554a
00000000`00000002 00000000`00000008 fffffa60`0a60554a : nt+0x5446e
fffffa60`019c5d38 fffffa60`0a60554a : 00000000`00000002
00000000`00000008 fffffa60`0a60554a 00000000`00000104 : 0xa
fffffa60`019c5d40 00000000`00000002 : 00000000`00000008
fffffa60`0a60554a 00000000`00000104 00000000`00000000 :
virtualnet+0x554a
fffffa60`019c5d48 00000000`00000008 : fffffa60`0a60554a
00000000`00000104 00000000`00000000 00000000`00000000 : 0x2
fffffa60`019c5d50 fffffa60`0a60554a : 00000000`00000104
00000000`00000000 00000000`00000000 00000000`00000000 : 0x8
fffffa60`019c5d58 00000000`00000104 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 :
virtualnet+0x554a
fffffa60`019c5d60 00000000`00000000 : 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 : 0x104
STACK_COMMAND: kb
FOLLOWUP_IP:
virtualnet+554a
fffffa60`0a60554a 488b542420 mov rdx,qword ptr [rsp+20h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: virtualnet+554a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: virtualnet
IMAGE_NAME: virtualnet.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
More information about the vpn-help
mailing list