BSOD creating VPN

deadstick · 04 Jun 2017

This system is connected to a Netgear R7000 router and Xfinity TC8305 cable gateway handling my home network. I'm having a series of BSOD's in conjunction with my attempts to configure the OpenVPN capability on the router.

I made the appropriate settings in the router admin page and installed the OpenVPN client on this system. Installation appeared normal until I attempted to connect to the VPN from outside the home network. The client messages indicate a normal connection, but no files or directories appear. The client is trying to use port 12974 on the router, and a port check tool indicates it is closed. The router will not accept a port forwarding request on 12974, saying it's in use by another, unidentified, service. So: VPN apparently installed but not functional.

Now, in the course of trying to get the VPN to work, I've begun to get BSOD's that mention file ndis.sys. Various forums point to an old adapter driver as the culprit, but the driver is up to date. One more detail: After recovering from every BSOD, I get a Kaspersky box saying an application failed to load, and asking to forward a crash dump to them, but that forwarding always fails.

Dump attached. TIA...

Ztruker · 04 Jun 2017

The latest dump indicates a problem with Kaspersky:

Code:

BugCheck D1, {2000, 2, 1, fffff80c296119d3}
*** WARNING: Unable to verify timestamp for klwfp.sys
*** ERROR: Module load completed but symbols could not be loaded for klwfp.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

klwfp.sys is dated Mon Jun 13 05:29:14 2016.

See if there is a newer version of Kaspersky available. If not, uninstall it and run with the built-in Windows Defender which is what I, and many others here, use.

Also, it looks like you are overclocking the CPU from 2.3 to 2.4. Please remove all over clocking and/or over voltage, see if that makes a difference is Kaspersky doesn't resolve this.

deadstick · 05 Jun 2017

Thanks, Rich. Interesting to note that klwfp.sys as seen in File Manager is five days later than the timestamp you give; perhaps that has something to do with the "Unable to verify timestamp" error.

The overclocking item was a surprise: this is a bog-standard ASUS laptop, and any overclocking present must be the manufacturer's doing.

I'll monitor for a while and see if I can get the BSoD to happen without any VPN activity; if that happens I'll try an antivirus change.

rj