New Member

Solved

forticlient 7.0.5 bluescreen bsod windows 10 NETIO.SYS or SYSTEM SERVICE EXCEPTION

Forum|Forum|3 years ago
May 24, 2022
8 replies
17833 views

Hallo, I have been noticed from some users of our network, that today and yesterday, some PCs with windows 10 started to show classic BSOD, and restart during normal use. Sometime it happens more than once a day.
PCs come from different brands, and hardware configurations, but are all windows 10 pro.
In the last days we have applied 7.0.5 update to all Forticlients. (7.0.3 previous ver.)
Any related recent known issue possible?

Thank you in advance.

Marco

Best answer by mrcmobile

Problem solved:

Symantec endpoint protection 14.3 was still installed on those PCs. Until FClient version 7.03 there were no problems. Both AV could share the same machine.
After updating to 7.05, BSOD started to affect only those PCs.
Note that we still own few PCs with Windows 7, and those are not affected. Symantec and Fclient 7.05 can still live together.

To avoid problem, I had to remove symantec endpoint 14.3 client from all PCs. It was already a sheduled job to do, but BSOD arrived earlier.

To answer to Bommi > it happens to all windows 10 versions. Same NETIO.SYS error.

PS: here they say both products could be installed:

https://www.fortinet.com/content/dam/fortinet/assets/alliances/dg-forticlient-symantec-endpoint-protection.pdf

A

Anonymous_User

New Member

Hello @mrcmobile ,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

Thanks,

Fortinet Community Team

bommi

New Member

Hello Marco,

can you tell us which version of windows 10 is shown when you use the "winver" command?

Is it the same windows 10 version for all endpoints with bsod?

Best Regards

Dominik

mrcmobileAuthorAnswer

New Member

Problem solved:

Symantec endpoint protection 14.3 was still installed on those PCs. Until FClient version 7.03 there were no problems. Both AV could share the same machine.
After updating to 7.05, BSOD started to affect only those PCs.
Note that we still own few PCs with Windows 7, and those are not affected. Symantec and Fclient 7.05 can still live together.

To avoid problem, I had to remove symantec endpoint 14.3 client from all PCs. It was already a sheduled job to do, but BSOD arrived earlier.

To answer to Bommi > it happens to all windows 10 versions. Same NETIO.SYS error.

PS: here they say both products could be installed:

https://www.fortinet.com/content/dam/fortinet/assets/alliances/dg-forticlient-symantec-endpoint-protection.pdf

Izzy

New Member

Currently we are having the same issue but we only have Forticlient running on our devices so when we moved to 7.0.5 we started to have this issue. We are not running any other third party AV software on our systems. Any one found a solution? We have ensured all updates to network drivers are up to date (recommended by Microsoft). Currently I am keeping users at 7.0.3 since it has not caused any issues with our current environment. I am currently testing 7.0.6 to see if this has been resolved.

Izzy

New Member

Adding to this, After upgrading to 7.0.6 we continue to have the same issue. With 7.0.3 we do not have the issue. Again we have win 10 devices which are also STIGed (did not mention before but could be relevant) they have windows defender and forticlient no other AV is installed. What I don't get is why the previous version work fine but the new ones have this issue. All sources I've seen thus far do not point to win defender causing problems with forticlient. I'll update when I get new results.

HewittVandegrift

New Member

Hey thanks for the super helpful reply. I'm not sure how I missed that thread. I haven't quite mastered the search function on here. I think I'll pass with him this time around. If i want any further guideline we will contact you here https://community.fortinet.com/t5/Fortinet-Forum/forticlient-7-0-5-bluescreen-bsod-windows-teatimeresults -10-NETIO-SYS-or-SYSTEM/td-p/212901

Thanks...

coregonus

New Member

We have the same problem with 7.0.5.0238. We have opened a TAC ticket. Will keep you updated if they have any solution to this. Does anybody has more information about this issue yet?

mrcmobileAuthor

New Member

any news from TAC support?

Thank you

marco

coregonus

New Member

Hello Marco

Yes, the TAC gave me a new FortiClient Interim build to test.

They have adjusted a few things, and I'm testing this version out right now.

I will let you know, if this resolved our bluescreen problem.

It would be helpful for Fortinet if you could open a TAC ticket as well and give them your logs. Only this way these problem cases are getting some importance.

coregonus

New Member

we are testing with 7.0.5.6095 right now. Until now we did not have any bluescreens yet. I hope this solved the problem.

mrcmobileAuthor

New Member

Today it did it again... Now on a virtual pc windows 10pro build 1909. On this VM there is no symantec client installed. Only Windows defender and Forticlient.
To temporary bypass problem, I have just unistalled Forticlient 7.0.5.0238. This evening I will update it to 21h2.
We need a solution from Fortinet. I can see that this trouble persist even with forticlient 7.06 > https://docs.fortinet.com/document/forticlient/7.0.6/windows-release-notes/991883/known-issues

bug id: 676424 NETIO.SYS causes blue screen of death on FortiClient endpoints

marco

Bestsoundbarblo

New Member

Hey thanks for the super helpful reply. I'm not sure how I missed that thread. I haven't quite mastered the search function on here. I think I'll pass with him this time around. If i want any further guideline we will contact you here
https://community.fortinet.com/t5/Fortinet-Forum /best-soundbar/forticlient-7-0-5-bluescreen-bsod-windows-10-NETIO-SYS-or-SYSTEM/td-p/212901

Malik_Shaffi

New Member

I totally agreed with you my problem is solved completely. https://community.fortinet.com/t5/Fortinet-Forum/forticlient-Tarde -7-0-5-bluescreen-bsod-windows-10-NETIO-SYS-or-SYSTEM/td-p/212901 Thankyou so much. Have a nice day to all…

anushty

New Member

To resolve BSOD BAD POOL CALLER, you need to remove your recently Installed hardware or software. In case you’ve installed some new hardware or software on your Windows 10/8/7 PC, it’s best that you remove them to fix this error. To delete a program in Windows 10, you can tap Start -> Settings -> Apps -> Apps & features, find the app that you like to uninstall, press it and choose the option of Uninstall. We hope that this method will help in fixing bad pool caller bsod error in no time. If it doesn't work then you can also go with updating drivers options. Just tap Windows + X keys on the keyboard altogether and select the option of Device Manager to open Device Manager on Windows 10. From here you can enlarge all the categories of devices and right-click the hardware for which you have installed a third-party driver, and press the option that states Update Driver.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded