BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

Aspirant

BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

Hi!

I just tried to update my windows 10 version 1607 (OS Build 14936.1000) to insider prewiev build 14942 and got an BSOD. I managed to restore to my old version of windows. 

After a quick google search i found that it was caused by fsni64.sys 

That file seems to be from your programs.

I have freedom version 1.5.3284.0 installed and 

fs protection 16.5

Common Component Framework 2.74 build 256

CCF CUIF 10.11 build 116
CCF DAAS2 1.10 build 646
CCF Guts2 2.05 build 121
CCF Upstream 2.02 build 669
CCF Diagnostics 9.05 build 260
CCF Scanning 1.73 build 256.1036
CCF Network 1.04 build 214
CCF Reputation 2.1 build 1342

Any idea what i ausing this and how to fix it?

Thanks in advance. Niko

 

1 ACCEPTED SOLUTION

Accepted Solutions
F-Secure

Re: BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

Hi @Jauska

 

Yes, that's our driver that is causing the bluescreen. We need a bug report with Windows kernel dump to analyze the problem. The dump should be automatically created by Windows and collected by our Support Tool.

 

Ville

(F-Secure R&D)

 

4 REPLIES 4
Superuser

Re: BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

hello

did you try uninstall then clean (re)install ?

Aspirant

Re: BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

I deleted fs protection and updated windows (successfully). But when i tried to reinstall fs protection the bsod returned.
F-Secure

Re: BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

Hi @Jauska

 

Yes, that's our driver that is causing the bluescreen. We need a bug report with Windows kernel dump to analyze the problem. The dump should be automatically created by Windows and collected by our Support Tool.

 

Ville

(F-Secure R&D)

 

Aspirant

Re: BSOD Stop Code: DRVER_IRQL_NOT_LESS_OR_EQUAL What failed: fsni64.sys

I have sent a report now. SAFE_BUG-01416