Getting SE_Lowx64.sys BSOD

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
Scorpion69
Posts: 8
Joined: Tue Jan 14, 2014 4:37 pm

Getting SE_Lowx64.sys BSOD

Post by Scorpion69 » Sat Jul 06, 2019 2:04 am

So I am running the latest version of SoftherVPN Server

Here is the thing I am doing transfers on my network NOT over the SofterherVPN

Any Suggestions here?

jeanwalsh
Posts: 1
Joined: Wed Jul 10, 2019 4:32 am

Re: Getting SE_Lowx64.sys BSOD

Post by jeanwalsh » Wed Jul 10, 2019 4:34 am

I wonder the same. Any idea?
"Learning never exhausts the mind."
happy wheels

Scorpion69
Posts: 8
Joined: Tue Jan 14, 2014 4:37 pm

Re: Getting SE_Lowx64.sys BSOD

Post by Scorpion69 » Sat Jul 13, 2019 2:47 am

I cant believe nobody else is having this issue, it seemed like it was a problem before....sombody reach out here and help please....

pfly
Posts: 1
Joined: Thu Nov 12, 2020 2:20 pm

Re: Getting SE_Lowx64.sys BSOD

Post by pfly » Thu Nov 12, 2020 2:44 pm

I am seeing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSODs on two different desktops running Win10 20H2 and SE Server latest version 4.34 Build 9745 rtm. I confirmed via windbg that the faulty driver is indeed SE_Lowx64.sys. I had seen similar BSODs occasionally on Win10 2004 also, so I don't believe this is a Win10 20H2 issue but rather an SE bug. Both desktops have ASUS Prime Z930-A motherboards with 32GB memory, one is an i9 and one an i5, using the onboard NIC. The BSOD occurs randomly at the point when a Client connects, either an SE Client or a regular SSTP client. I think SE is great software and I have used it for a number of years. But random BSODs is not something I can live with, so I have uninstalled for now from the desktops and am running SE instead in a virtual machine to minimize/control the impact when BSODs happen. I have a full MEMORY.DMP available from each desktop, plus a few minidumps. Developers/support team folks at SE - please let me know if you want access to the dumps so you can troubleshoot and fix this most annoying bug.

Post Reply