Foro de InfoSpyware - Foro de Hijackthis - Foro de Virus

Hola espero me puedan auxiliar en la interpretación de la información que anexo: recientemente mi maquina se reinicia, recupre el sistema e instale kaspersky internet security (versión de evalaución), sin embargo continua reiniciandose, el reporte menciona que la probable causa es.
Probably caused by : klif.sys ( klif+2d19 )

Pero no sé interpretarlo me podrían ayudar agradezco su ayuda
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini100509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16830.x86fre.vista_gdr.090302-1506
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Oct 5 08:31:06.829 2009 (GMT-7)
System Uptime: 0 days 0:04:47.517
Loading Kernel Symbols
.................................................. .................................................. ...............................
Loading User Symbols
Loading unloaded module list
....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, a297ba80, 0}

Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+2d19 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: a297ba80, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

FAULTING_IP:
+0
00000000 ?? ???

TRAP_FRAME: a297ba80 -- (.trap 0xffffffffa297ba80)
ErrCode = 00000010
eax=b3ff6008 ebx=b3ff6008 ecx=aa7d44cc edx=aa7d450c esi=a297bb7c edi=b3fec4c8
eip=00000000 esp=a297baf4 ebp=a297bafc iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: avp.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 00000000 to 00000000

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffa297bb04

STACK_COMMAND: dds A297BB04-0x20 ; kb

STACK_TEXT:
a297bae4 00000010
a297bae8 00000000
a297baec 00000008
a297baf0 00010206
a297baf4 00000012
a297baf8 00dcb5e9
a297bafc a297bb5c
a297bb00 89dc3d19 klif+0x2d19
a297bb04 85772878
a297bb08 a297bb7c
a297bb0c 8405ac18
a297bb10 ae206540
a297bb14 b3fec4c8
a297bb18 00400120
a297bb1c 85772a60
a297bb20 85772930
a297bb24 8405abb8
a297bb28 a297bbd0
a297bb2c 00000000
a297bb30 aa7da840
a297bb34 00000006
a297bb38 00000001
a297bb3c 15dc938e
a297bb40 00000000
a297bb44 00000000
a297bb48 00000001
a297bb4c b3fec4c8
a297bb50 85772878
a297bb54 ae206540
a297bb58 00000196
a297bb5c a297bbb8
a297bb60 80761843 fltmgr!FltpPerformPreCallbacks+0x2e5


FOLLOWUP_IP:
klif+2d19
89dc3d19 ?? ???

SYMBOL_NAME: klif+2d19

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: klif

IMAGE_NAME: klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4981a5cb

FAILURE_BUCKET_ID: 0x8E_klif+2d19

BUCKET_ID: 0x8E_klif+2d19

Followup: MachineOwner
---------

0: kd> lmvm klif
start end module name
89dc1000 89e00000 klif T (no symbols)
Loaded symbol image file: klif.sys
Image path: \SystemRoot\system32\DRIVERS\klif.sys
Image name: klif.sys
Timestamp: Thu Jan 29 04:49:15 2009 (4981A5CB)
CheckSum: 0003C405
ImageSize: 0003F000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0