Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
kolawale_FTNT wrote:
Wondering if your FortiClient installation conflicts with other third-party software. Consider raising a support ticket if you have not already done so. An output of the FortiClient_Diagnostic_Tool will be useful. So is any kernel memory dump file from the BSoD. Post the ticket number once you have one. In the meantime, FortiSniff2 is used by Application Firewall. If you are not using this feature, you can request from the Support Engineer how to shut it down.
Thanks, I have raised a ticket, and it is now escalated to L2 support. We are currently testing the new installations with new drivers they have sent us. I guess it is more serious than just random Windows error, but we are very happy with the support so far.
I'm having BSOD's (Error: Page fault in nonpaged area - fortisniff2.sys) as well with FortiClient 5.2.1.0605 on Windows 8.1, but not in relation to sleep mode.
It has occurred when:
- Using TeamViewer
- Browsing LinkedIn on Firefox
BL97Ih wrote:I'm having BSOD's (Error: Page fault in nonpaged area - fortisniff2.sys) as well with FortiClient 5.2.1.0605 on Windows 8.1, but not in relation to sleep mode.
It has occurred when:
- Using TeamViewer
- Browsing LinkedIn on Firefox
We also have Teamviewer as a part of baseline installation. But I haven't used it when it BSODed. No Firefox btw. Hm.
Had quite a lot of this on Windows 7 starting with the 5.2.1 FortiClient. Teamviewer installed but not used in months. Doesn't appear to be related to any common activities either - just at random.
I had this error come up rebooting a system after installation of 5.2.1.0605. It was an HP 6500 desktop. It wasn't until hitting the Accept key on registration that the issue occurred (BSOD), then rebooting got the BSOD repeatedly before hitting the Windows login gui.
Safe mode, removed Forticlient, installed latest NIC driver (Broadcom/HP), installed FortiClient, issue resolved.
danielkr
I had a similar problem on my Macintosh 10.9 using FCT 5.2.1
Removing and reinstalling resolved the blue screens.
It also seemed to related to registration to the Fortigate.
FGT-60E; FGT-90D; FGT-100E; FGT-600D; FGT-1000D; FGT-3000D; FGT-VM on Azure
FAZ-3000D; FWB-VM on Azure; FAZ on Azure; FAC-VM
April 2024 and i have the same problem. Verion 7.0.11
vaya problema , si ya paso en un equipo, espero no suceda en otros mas. y no se ha resuelto , formateamos el equipo recuperamos y luego se vuelve a instalar y con la incertidumbre de que vuelva a ocurrir , no pudede ser.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1713 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.