Windows 10: BSOD after establishing VPN connection - mrxsmb20.sys+bef3

Hello,

my BSOD is not 100% reproduce able but it happens when my VPN connection is established.
Sometimes it crashes imediatly into BSOD sometimes I can use it for a while befor my system crash.

I've already tried to finde a solution ... but know i give up.

Windows update, Bios update and Software did not change anything.

I hope you can help me.

The name of the VPN client is securepoint VPN
VPN-Client von Securepoint - Professionell und kostenlos

good luck

:)

 

Windows 10 - VPN needs pc restart to another connection

Hi all,

I have a problem here, after I establish a connection to vpn, I disconnect from it and when I try to establish a new connection it says: "The vpn connection was terminated due to a new network interface and could not be automatically re-established". The
only solution that I found is to reboot my pc but this is a little bit uncomfortable because it takes to long. If somebody knows why is this behaviour it would be great.

Thanks,

Alex

 

Windows 10 DNS-Server order when connected via LAN and establishing a VPN Connection

Hi Gil,

the internet Service Provider can't help me. It's Windows 10 related. Everytime when I establish a connection with Ethernet (LAN) to a network (does no matter which ISP), i get an IP and I can surf in the internet. But when I establish an VPN connection
on that Ethernet Connection, then my DNS will be set to the Ethernet Connection DNS-Server NOT to the VPN-Connection DNS-Server.

In this scenario my VPN-Connection gets a higher Metric as my Ethernet ( Cable bound LAN) connection.

Lan-Connection (Ethernet) Metric 5

VPN-Connection Metric 15

When I establish a WIFI connection to the same Router I can surf in the Internet. Then I establish an VPN-Connection an the DNS-Server will be set to the VPN-Connection configured DNS-Server.

In this scenario my VPN-Connection gets a lower Metric as my Wifi connection.

Wifi-Connection Metric 35

VPN-Connection Metric 25

Both Connections are preferred. So the connection with the better Metric wins.

It's not related to the ISP. He has nothing to do with the "automatic" Metric setting in my Windows 10 Client.

...

 

Hi supsuop,

Did you create a support ticket with their techs about the issue?

 

Hi,

the cause for the BSOD is definitely somthing with the VPN Client/Software:

Code: 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (2017-11-24 21:25:05) [Windows 10] CAUSED BY: mrxsmb20.sys * Longhorn SMB 2.0 Redirector (Windows System File) tap0901.sys [2016-04-21] * TAP-Win32 Adapter V9 or ExceptionCode: c0000005 (Access violation) PROCESS: System[/quote]
As axe wrote u should contact the support team. Updating the software and driver for the vpn setup would be a good idea too.

 

Thank you for your support. I have opened a Thread at the Forum by the producer of the software.

 

Yesterday I started to use the original OpenVPN client from Downloads and i had the same BSOD again..
i have uploaded the new dump.file

I do not think that the main problem is the TAP driver.

 

Latest dump indicates a problem with Avast:
Code: fffffb0c`967ee7f8 fffff805`60673140Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.sys *** ERROR: Module load completed but symbols could not be loaded for aswSP.sys aswSP+0x63140 fffffb0c`967ee8b8 fffff800`12293079Unable to load image \SystemRoot\system32\drivers\aswMonFlt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswMonFlt.sys *** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys aswMonFlt+0x3079[/quote] Suggest uninstalling Avast and running with Windows Defender for now, see if that helps resolve the problem. If so, you can then stay with Defender (what many of us here use) or try a different AV program.

 

Suggest uninstalling Avast and running with Windows Defender for now, see if that helps resolve the problem. If so, you can then stay with Defender (what many of us here use) or try a different AV program.[/quote] I will give it a try.
Can you tell me how you could read this message?
I use BlueScreenView to look into dmp file. But there ist nothing like "*** WARNING: Unable to verify timestamp".

 

You need to use windbg, part of the Windows Debugging toolkit.

See here for starting info and initial setup: WinDBG - Installing, configuring and debugging Crash Dumps in Windows 10

 

Hey, i have downloaded windbg preview for windows 10.
i am able to use "analyze -v" etc.
but i dont know where you get the informationen that avast was the problem.

I can't open the link that you send me.
http://192.168.1.2:31080
this is a privat adresse area. so it's impossible for me to connect to it.

 

The link Ztruker posted is a tutorial from this forum, I don't have experience with your kind of network setup and don't know any of the limits but I find it odd that you can't access a page from this forum.

Run the following commands:
Code: !thread; dps {limit} {base}[/quote]



Source: WinDBG - The Basics for Debugging Crash Dumps in Windows 10 BSOD Tutorials

 

My fault, it was a link to a database entry on my Apache server instead of the correct link to this forum, sorry.

Try this: How to Install and Configure WinDBG for BSOD Analysis

As far as learning how to use it, that's a separate issue, never ending really. You need to learn about commands like !thread and dps, !sysinfo, lmvm, etc.
You also need to take the time to learn to read event viewer logs and msinfo32.nfo data. It's not simple and is very time consuming.

 

The various k* commands for different outputs from stacks is also useful to know.