Fortinet Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Juler
New Contributor

Windows 11 / Forticlient 7.0.2.0090 blue screen

forticlient 7.0.2.0090 hangs 98% of the time when connected, Windows 11 then gets an ndis.sys error and then reboots .

Occasionally, it also connects completely and hangs up a few seconds later

with the same error

 

Error sequence

Establishing a connection with a plant -> 98% -> Windows hangs -> error message Ndis.sys comes -> computer restarts

8 REPLIES 8
Siavesh
New Contributor

I have same error with Windows 10 / Forticlient 7.0.2.0090.
I got connected with the VPN server but when I pinging a IP address in the network I have connected with via VPN, I got the blue screen with the same ndis.sys error and then reboots.

 

Castun
New Contributor

Same.  It works fine on my home desktop, but my work laptop (where I need it the most) does not work.  I can connect just fine without issue 99% of the time, but as soon as I even ping an IP through the VPN it bluescreens.

warshad
Staff
Staff

 Hi,
 
Welcome to Fortinet community and Thank you for your post.
 
Have you tried a uninstall and clean reinstall of Forticlient on the host machine in question? Did you try to connect using web mode?
 
Hope to hear from you.
 
 
 
Waqas Arshad
Fortinet
Hary
New Contributor

Hi

 

I have the same problem with win 10. I uninstall and reinstall the client 3 times. I tested client v7.0 and also V6.2 and V5.6. Always the same problem with the blue screen.

 

SöHa
Rrrrrr
New Contributor

same problem.

windows10

forticlient 6.0.10.0297

98% and after blue screen(ndis.sys)

Us_er
New Contributor II

same problem.

windows11

forticlient 7.0.2

98% and after blue screen

Gaylord
New Contributor

Same issue. User upgraded to Windows 11 with existing Forticlient 7.0.1.0083 installation. ndis.sys bluescreens when attempting to connect SSL VPN, but IPsec VPN still worked.

Removed and reinstalled Forticlient, SSL still bluescreens the machine and now IPsec fails on first step.

Bluescreens appear to be really generic, as far as memory dumps go. "Caused By Address : ndis.sys+3989".

Gaylord

Of, and also tried VPN-only client, still bluescreens on SSL and IPsec won't connect. VPN-only client works fine for both VPN types on my personal Windows 11 machine.