IRQ_NOT_LESS_OR_EQUAL

[#1]

As soon as FortiClient Installations procedures wants to install the Fortidrv Miniport for this WLAN-Controller, there is a blue screen with IRQ_NOT_LESS_OR_EQUAL under Windows XP SP2. When I disengage the Intel-WLAN device it works, as soon as I engage it, Blue screen. I use the actual available driver from Intel and the latest available FortiClient. Without FortiClient the Intel-Device works without problems. Anyone of you can give me a hint how to get them out of the Hardware-Manager? Regards

[vanc]

Do you have other VPN software or firewall software installed? Maybe there is some kind of conflicts. After BSOD, your Windows will generate a dump file. Can you post the dump files under c:\Windows\minidump here? One is enough.

[#3]

No, I don' t have other VPN software but pc-cillin. I guess my Core Duo processor might causing in this issue......thanks for that vanc. And i will come back to you with my minidump file later.

[#4]

I don' t think it is the Core Duo. We have several Core Duo perfectly working in combination with FC and even UMTS software. No problem what soever. My guess is that you are using a 1.6 version of the FC. Regards, Eric

[AKrause]

Same problem here. Hardware is a IBM Thinkpad T60. Intel PRO/Wireless 3945ABG Driver_IRQL_NOT_LESS_OR_EQUAL NDIS.sys With activating the WLAN-Adapter the BSOD appears. regards, Andreas

[vanc]

PC-Cilin has a low level network filtering driver for email scanning. It maybe the reason for the crash. FortiClient has a standard NDIS Intermediate driver which attaches to every network interface for packet inspection and manipulation (VPN). A minidump file will help Fortinet to know where is the crash.

[#7]

I can confirm this problem was re-created on a brand new Siemens 7110 laptop using 3.0 229. Disable the Intel Wireless then FortiClient installs. Activate the Wireless immediate BSOD. Clearly a FC problem

[vanc]

Intel' s new driver for Pro/Wireless card introduced a new OID which collides with FortiClient' s virtual adapter. When FortiClient issues a query to this OID, Intel driver processed it without proper buffer checking and caused the blue screen. Fortinet introduced a fix for this problem and a interrim build is ready. Tested on HP Pavillion Laptop (T2300) with Intel Pro/Wireless 3945ABG and latest intel driver. Crash fixed. Please ask support for FortiClient 3.0 build 294. If you don' t want a interim build, you can still use the release build 229. But you need to copy two drivers from build 294 after installation and move to the PC with 229. The driver is under c:\Windows\system32\drivers, one is fortidrv.sys and another one ft_vnic.sys. The drivers should be digitally signed by Fortinet. You can verify by right click on the files and select Properties. The dialog will present a " Digital Signatures" tab. The driver version should be 3.0.75.