We're seeing a decent number of users report that their Windows computers will sporadically blue screen with a IRQL_NOT_LESS_OR_EQUAL error for covpnv64.sys. This has started happenings since we pushed out the 7.2.2 APM client update. Anyone else see something similar? The problem happens just as the VPN session is being established.
It has affected multiple types of laptops and Win10/11 clients.
Same issue described here except Driver Verifier is not involved.
I'm also experiencing BSOD with IRQL_NOT_LESS_OR_EQUAL error for covpnv64.sys on Windows 10 21H2, no Driver Verifier running. BigIP Edge Client 7221,2022,412,1126.
Here are the conditions for triggering the BSOD:
- PC put in sleep mode by closing lid while Edge Client is connected.
- When opening lid, waking the PC from sleep, BSOD occurs.
Was there ever a resolution or update to this?
We have been experiencing the same issue for the past month in our estate, though strangely it was prior to the rollout of 7.2.2.
220.127.116.11 fixed most issues but we have at least one user continue to have problems.
Support had a hot fix to resolve lingering issues which we haven't deployed yet. So expect most but not all crashes to be fixed in 18.104.22.168.
Let's have a look at the F5 components as installed to the client machine (typically: with using the CTU/f5winfo.ex - K12444): to avoid BSOD situation, let's ensure the covpn64.sys component originates from v22.214.171.124 (7221.X.Y.Z) or more recent. Any earlier version can cause BSOD.
We have upgraded to the latest edgeclient version 126.96.36.199, but still encountering the same problem. The bug ID tracker doesn't say a fix is there yet. https://cdn.f5.com/product/bugtracker/ID760395.html
I can suggest the following: have a look at the (software) version for the component covpn64.sys (by any means or with getting an f5Report). If it shows v7221 or more recent, I'd suggest you open a Support Ticket for investigation. If it still shows v7220 or earlier, I can suggest we first manually and thoroughly delete the F5 components (before we proceed again with deploying v188.8.131.52). To do that: pls run the CTU/f5wininfo.exe/f5uninstall.exe prgm as admin to uninstall the software. Then, run the same tool again (do feel free to discard the UAC), this time within the context of the usual user.