OpenVPN 2.3.4 Crashes with latest TAP Driver

[carthickeyan]

Hi

I have installed OpenVPN client and server 2.3.4 on my Windows 7 32 Bit Enterprise edition systems. I have uninstalled the default TAP Driver and installed the one which I have built using Python script ( note no code changes been done). When I connect the OpenVPN client to the server I am observing frequent BSOD on NDIS.SYS with the below signatures. I have tried with previous version of OpenVPN and observed the same errors. Kindly guide me what could be the issue. I am planning to build TAP Driver with WIN8.1 WDK.

If Driver verifier is disabled I am not observing BSOD. But Driver verifier is enabled for TAP Driver automatically.

MODULE_NAME: ndis

FAULTING_MODULE: 8280e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78937

BUGCHECK_STR: 0xc9_24c

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 24c

FAULTING_IP:
ndis!TrFilterDprIndicateReceiveComplete+1a36
84e9f6c4 8bff mov edi,edi

FOLLOWUP_IP:
ndis!TrFilterDprIndicateReceiveComplete+1a36
84e9f6c4 8bff mov edi,edi

IRP_ADDRESS: 86194008

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER: from 82b44f03 to 828ecbfc

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a8a6fb28 82b44f03 000000c9 0000024c 84e9f6c4 nt!KeBugCheckEx+0x1e
a8a6fb48 82b472cd 84e9f6c4 a8a6fb80 84e9f6c4 nt!PoSetHiberRange+0xdd08
a8a6fb60 82b47414 0000024c 84e9f6c4 00000103 nt!PoSetHiberRange+0x100d2
a8a6fbd0 82b45620 0000024c 86194008 00000103 nt!PoSetHiberRange+0x10219
a8a6fc00 82b44e5f 92443a14 924439b0 00000000 nt!PoSetHiberRange+0xe425
a8a6fc14 82b3f6d4 92443a14 00000000 93e9ab20 nt!PoSetHiberRange+0xdc64
a8a6fc38 82844bd5 00000000 86194008 9247d960 nt!PoSetHiberRange+0x84d9
a8a6fc4c 82a38be9 93e9ab20 86194008 86194078 nt!IofCallDriver+0x1b
a8a6fc6c 82a7e978 9247d960 93e9ab20 00000001 nt!NtSetEvent+0x2c1
a8a6fd08 8284b8c6 9247d960 000000a0 00000000 nt!NtWriteFile+0x6ee
a8a6fd34 77da70f4 badb0d00 0022f2e0 00000000 nt!ZwYieldExecution+0xb86
a8a6fd38 badb0d00 0022f2e0 00000000 00000000 ntdll!KiFastSystemCallRet
a8a6fd3c 0022f2e0 00000000 00000000 00000000 0xbadb0d00
a8a6fd40 00000000 00000000 00000000 00000000 0x22f2e0


STACK_COMMAND: .bugcheck ; kb

SYMBOL_NAME: ndis!TrFilterDprIndicateReceiveComplete+1a36

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ndis.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

Thank You,
Regards,

Karthikeyan Palanisamy

[cron2]

Hi,

something in the build of your tap driver went wrong - which is why it's crashing your system (blue screen).

Nobody will be able to answer *what* went wrong, though, I'm afraid - none of the developers build drivers on 8.1, we use old and trusted build systems (my TAP driver extentions have been done on WinXP, I think Samuli builds the official drivers on Win7). Since the old NDIS version is deprecated by Microsoft, it might well be that there is something in the 8.1 WDK that just breaks our driver.

Since we have a new NDIS6 driver - see https://github.com/OpenVPN/tap-windows6 - which uses the up-to-date API, it doesn't seem useful to invest time to debug why the old driver does not bild on Win8.1

What are you trying to achieve anyway? I'm a bit curious, because building the TAP driver is so much hassle that nobody does it without having a really good reason.

gert

[carthickeyan]

Hi Gert,

Thanks for your reply.

we would like to enable NDIS630 and NDIS640 for WIN8 and WIN8.1 respectively. The current TAP Driver supports only NDIS61.

Hence we are building TAP driver with WIN8.1 WDK.

Thank You,
Regards,

Karthikeyan Palanisamy

[dkaehny]

Hi,

i had the same problems, Windows 7 64 bit and Asus Mainboard with Realtek chip, dont know if this matter. Anyhow after playing around with my G DATA antivirus and firewall it looks like the problem is somewhere else. Then I read this thread about this TAP Driver and take a look at the network connection using the TAP network adapter, and finally I found the problem in my case. Open the properties of the network connection using the TAP network adapter, and remove the unneeded ticks of the elements that this connection will use, like in my case from Shrew Soft, VMWare, Virtual-PC, and finally AVM VPN. After that no blue screens anymore.

Hope could help somebody with that.

dkaehny