NOD32 causes BSOD with new Flightkeeper

I am writing to alert you to a problem with NOD32 and the new release of FS Flightkeeper v2.7 ( a flight logbook program for Microsoft Flight Simulator).

When the installer for this utility tries to install some language DLL's, the computer crashes with a blue screen error. I was able to reproduce this on two different computers. The only way to successfully install is to disable AMON during the installation, and then create an exclusion for the FlightKeeper folder after installation.

The developer of the software was also able to reproduce this problem (http://www.molitor-home.de/FS/FLKeeper/default.asp)

I do not think NOD32 should cause blue screen crashes, so perhaps there is a problem that needs investigating?

This is the event log (WinXP - SP2):
The computer has rebooted from a bugcheck. The bugcheck was:
0x1000008e (0xc0000005, 0x00000008, 0x84f6eb4c, 0x00000000).

Graeme

 

What about setting AMON to scan files with default extensions only instead of all files? There are some applications that explicitly require this.

 

That might work, but my real point of making the post was that causing a blue screen crash is quite dramatic and probably not a desirable method of operation for a routine software installation.

I would merely ask that the NOD32 developers look into this problem to ascertain if their might be a way to prevent it occurring in the future.

Regards,
Graeme

 

It would be a good idea to email support about this problem, with all information you can have.