NOD32 vs Kaspersky

[KcN]

Thanks for the response all.

I think I'll go with NOD32. It's nice to have an all in one package, but
not at the expense of other things. I came in looking for an antivirus
program so I'll stick with a company that stands behind their core
technology... dealing with viruses.

 

[Brandon]

A solution to this problem was provided to me by Kaspersky's Support
team.

There is a registry entry that controls the load order of the
Kaspersky driver that causes this error.

The key is located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Klif

Inside of the Klif key is an entry named "Start" the default value is
1.

The possible values for the entry are 1,2, and 3.

The values define the order of driver load:

1. Boot
2. Automatic
3. Demand

Level "2" allows the driver to load after all main drivers have been
loaded.

Kaspersky asked that I try using value "2" by booting into safe mode
and changing the value. They said that this does not reduce
protection level at any rate, but can solve conflicts that can occur
with the IRP stack.

I followed their advice and changed the value from 1 to 2 and it fixed
the problem.