Klim6.sys BSOD

[LuckyJosh]

--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 2.00
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.

This program does post-mortem crash dump analysis with the single click of a button.


To obtain technical support visit Resplendence Software - Contact and Support Form

To check if a newer version of this program is available, click here.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.


--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 8/11/2009 9:02:40 PM your computer crashed
This was likely caused by the following module: klim6.sys
Bugcheck code: 0xD4 (0xFFFFF88003E79098, 0x2, 0x0, 0xFFFFF80002E7A22B)
Error: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
Dump file: C:\Windows\Minidump\110909-26301-01.dmp
file path: C:\Windows\system32\drivers\klim6.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Lab Intermediate Network Driver

 

[H2SO4]

Are you asking a question or just marvelling?

 

[LuckyJosh]

Are you asking a question or just marvelling?

I didn't know I had to specify something. Yes I would like some help on this BSOD, are you able to help me? I would like to be able to stop this from occurring. I would rather not uninstall KIS 2010 unless absolutely necessary as I have another 276 days left on my license. It happens after Windows has passed the W7 Logo but before I get the login screen asking for my password

 

[H2SO4]

Are you asking a question or just marvelling?

I didn't know I had to specify something. Yes I would like some help on this BSOD, are you able to help me? I would like to be able to stop this from occurring. I would rather not uninstall KIS 2010 unless absolutely necessary as I have another 276 days left on my license. It happens after Windows has passed the W7 Logo but before I get the login screen asking for my password

It's always best to clarify what it is you're asking for, rather than just paste data. The point of including those data may not be as obvious to others.

Onwards to your issue...

Make sure you're running the latest build/version of KIS and test whether reinstalling it from scratch makes any difference. If not, and you continue to experience the exact same crash in the presence of the klim6.sys driver, submit the relevant minidumps (not the "WhoCrashed" problem reports) to Kaspersky, and include an explanatory note to say that you'd like them to offer guidance as to why their driver appears to be behaving in this manner on your machine - they may already have a solution, or be working on releasing one soon.

The OS noted the fact that the driver did not clean up after itself (before unloading), and that's a fatal flaw in a kernel-mode driver. If it's a bug, as opposed to some sort of environmental or configuration issue that a reinstall of KIS would hopefully rectify, then the only way to fix this is to work out the bugs in the driver's code and produce a new and better version of the driver.

Obviously, that last part can only be done by Kaspersky, hence the suggestion to submit a problem report to them. You paid for their software. You have a right to ask them why the product you paid for is exhibiting severe operational flaws on your machine.