BSOD (DUMP file included)

why did i get this bsod?

Your dump blame Kaspersky (klif.sys) and a WinMount software

-Remove WinMount

You are using an old version of Kaspersky
The kl1.sys and klif.sys BSODs were known issues in the older 11.0.1.xxx versions, update to 11.0.2.556(with patch b) by uninstalling the current version and download the latest one

-Uninstall completly Kaspersky
-Install new version
Product Updates

Code:

BugCheck A, {89f2aff8, ff, 1, 82c841ed}

*** WARNING: Unable to verify timestamp for WMDrive.sys
*** ERROR: Module load completed but symbols could not be loaded for WMDrive.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : WMDrive.sys ( WMDrive+860 )

well i did exactly that, i'm running the latest version of both KIS and Winmount, and my pc still crashes is it a conflict between the two? can i just prevent Kasper Antivirus from interfering with Winmount?

i attached the latest DUMP file, thx

bump

Latest dump blames your WinMount software (WMdrive.sys), Uninstall it

but i've been using it for some time know with no issues, could i have done something wrong that caused it to misbehave?

UnD3R0aTh said:

but i've been using it for some time know with no issues, could i have done something wrong that caused it to misbehave?

Check if a newer version of WinMount is available, if not you should remove it

ok i uninstalled Winmount, then googled around for an alternative, , i found "Rar Mount" (Rar Mount 3) however it also crashed my PC

here's the dump again, does it state "Rar Mount" only or is KIS somehow involved? i'm suspecting that KIS is the culprit behind all this!

The latest BSOD was caused by dokan.sys, probably from a software Dokan library, Uninstall it
Kaspersky has nothing to do with the BSODs now

Code:

dokan.sys    dokan.sys+bb90    0x96aa1000    0x96aafe00    0x0000ee00    0x495ada35    31/12/2008 06:34:29

indeed a new version is released and BSOD fixed, i think the recent windows update is what caused it to misbehave! thx :)