[Vpn-help] Bluescreen with Windows 7 64 bits with both 2.1.5-rc4 and 2.2.0-alpha9

Stuart Hall stuart at daern.org
Sat Nov 7 16:22:20 CST 2009


Yup, confirmed. I get exactly the same error from time to time and
Matthew has confirmed that there is a known issue that has been fixed
in the next (as yet unreleased) version of the application.

Sounds like the exact problem described in one of Matthew's earlier
emails, so I've got high hopes for the next release...

SH

Probably caused by : vfilter.sys ( vfilter+1114 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff98000004a16, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation
(only on chips which support this level of status)
Arg4: fffff800031980b6, address which referenced memory

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

On Sat, Nov 7, 2009 at 9:45 AM, Stian Jordet <liste at jordet.net> wrote:
> Stuart Hall skrev:
>>
>> I guess this is probably the normal issue with the Shrew drivers than
>> is apparently fixed in a later (as yet unreleased) version. You're
>> welcome to send me a minidump (please don't send a full one by email!)
>> and I'll run it through the debugger to confirm the cause of the
>> problem.
>>
>
> Thanks for confirming that it is a known (and probably fixed) issue! Here's
> my minidump :)
>
> Regards,
> Stian
>



More information about the vpn-help mailing list