Author Topic: NEW Version: 19.2.2364 BSOD  (Read 14213 times)

0 Members and 1 Guest are viewing this topic.

Offline Be Secure

  • Long Time Avast User(9years.....) Security Enthusiast.
  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1908
Re: NEW Version: 19.2.2364 BSOD
« Reply #75 on: February 14, 2019, 05:49:35 AM »
My Vypr VPN still doesn't work, same Windows stop error 0x7F.  But - WhoCrashed said before that an Avast Firewall driver was probably causing the crash - whereas this time WhoCrashed claims a driver belonging to OpenVPN ("tap0901.sys") is the cause.

My Avast build is 19.2.4186.429, which I guess is the newly fixed version.  Upon everyone reporting back the good news of smooth sailing, I tried these steps:

Uninstalled my Vypr VPN service and app.
Installed the Avast Firewall component that I had uninstalled some days ago.
Manually initiated Avast to check for Program Updates and Virus Definition Updates.
Restarted Windows for extra good luck.
Reinstalled Vypr VPN, latest version (same version that originally participated in these crashes, though).
Attempted to connect to a VPN server:  BSOD.

I ran the Avast Support Tool again, in case anyone will want this.  Its file ID is UM5KX.
Best practices for resolving tap0901 issues:https://www.file.net/process/tap0901.sys.html
PC- Windows10 EDU 64Bit,avast! free 20.4.2410,uBlock Origin,NVT_OSA,GoogleChrome(64bit),CCleaner,Unchecky,ZAM Free,Shadow Defender.
Security Enthusiast

Offline chris..

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2390
Re: NEW Version: 19.2.2364 BSOD
« Reply #76 on: March 01, 2019, 08:45:18 PM »
hi,
After the emergency update (19.2.4186.429 and highter) my "Private Internet Access" vpn was working again.
Yesterday, there was an update of "PIA" and since the BSOD have gone back to my 2 W7 64bits OS (Still not on w10)
BSOD view:
Code: [Select]
ntoskrnl.exe+a1f69 NT Kernel & System 6.1.7601.24354 (win7sp1_ldr_escrow.190108-1700) C:\Windows\system32\ntoskrnl.exe I tried everything that allowed my vpn to work again 15 days ago (repair, re-installation of the vpn, authorization in the firewall,deactivating it,...) without success now.
The worst part is that even with the old version of the vpn, I still have the blue screens.

The only thing that works is to completely remove it (the firewall) by add/change in the UI
Is it the same as proposed by kwiq Here and I have to wait for next update ?
Why it was working fine until yesterday?

Offline Asyn

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 68721
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: NEW Version: 19.2.2364 BSOD
« Reply #77 on: March 02, 2019, 05:14:12 AM »
You could try the latest beta: https://forum.avast.com/index.php?board=15
Win8.1 [x64] - Avast PremSec 21.1.2444.B#2 [UI.595] - EEK - Firefox ESR 78.6.1 [NS/uBO/PB] - TB 78.6.1
Avast-Tools: Secure Browser 88.0 - Cleanup P 20.1 - SecureLine 5.9 - Driver Updater 20.2 - CCleaner 5.76
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline MrDJ

  • Jr. Member
  • **
  • Posts: 91
Re: NEW Version: 19.2.2364 BSOD
« Reply #78 on: March 02, 2019, 07:31:00 PM »
hi,
After the emergency update (19.2.4186.429 and highter) my "Private Internet Access" vpn was working again.
Yesterday, there was an update of "PIA" and since the BSOD have gone back to my 2 W7 64bits OS (Still not on w10)
BSOD view:
Code: [Select]
ntoskrnl.exe+a1f69 NT Kernel & System 6.1.7601.24354 (win7sp1_ldr_escrow.190108-1700) C:\Windows\system32\ntoskrnl.exe I tried everything that allowed my vpn to work again 15 days ago (repair, re-installation of the vpn, authorization in the firewall,deactivating it,...) without success now.
The worst part is that even with the old version of the vpn, I still have the blue screens.

The only thing that works is to completely remove it (the firewall) by add/change in the UI
Is it the same as proposed by kwiq Here and I have to wait for next update ?
Why it was working fine until yesterday?
oh dear. that doesnt sound good.
luckily for me since the emergency update my win 7 64bit is working as normal using nord vpn.

hope they sort it out soon for you Chris.