Pantalla azul IRQL_NOT_LESS_OR_EQUAL

*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+13583 )

IMAGE_NAME: klif.sys

klif.sys

Hola a :
Ultimamente he observado que los ordenadores con los que trabajo sulen
mostrar el error que indico en el asunto, y no consigo eliminarlo. Por eso
he
estado mirando por internet la información que hay al respecto y he
llegado
al articulo que ha escrito José Manuel Tella en la dirreción
http://www.multingles.net/docs/jmt/bsod.html, que me ha parecido
superinteresante, y me puesto manos a la obra para ver si consigo
resolverlos
he probado con uno de los ordenadores y el informe que me genera el windbg
es
el siguiente:


Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Apr 20 16:11:42.267 2005 (GMT+2)
System Uptime: 0 days 6:09:42.856
Loading Kernel Symbols
...
Loading unloaded module list
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {99be4b14, 2, 0, 804eb245}

*** ERROR: Module load completed but symbols could not be loaded for
klif.sys
Probably caused by : klif.sys ( klif+13583 )

Followup: MachineOwner


kd> .reload
Loading Kernel Symbols
...
Loading unloaded module list
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
kd> .reload
Loading Kernel Symbols
...
Loading unloaded module list
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
kd> analyze -v
Couldn't resolve error at 'nalyze -v'
kd> hh.dbgerr001
^ Syntax error in 'hh.dbgerr001'
kd> hh
^ Syntax error in 'hh'
kd> kd> !analyze -v
Numeric expression missing from '> !analyze -v'
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address
at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 99be4b14, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804eb245, address which referenced memory

Debugging Details:


*** ERROR: Module load completed but symbols could not be loaded for
klif.sys

READ_ADDRESS: 99be4b14 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiDeletePte+15b
804eb245 8b420c mov eax,[edx+0xc]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804f0e20 to 804eb245

TRAP_FRAME: fac4ba5c -- (.trap fffffffffac4ba5c)
ErrCode = 00000000
eaxffc961 ebxÀ300018 ecxffedcb edx™be4b08 esic48678
edi003045
eip€4eb245 esp=fac4bad0 ebp=fac4baf4 iopl=0 nv up ei pl nz na pe
nc
cs08 ss10 ds23 es23 fs30 gs00
efl010202
nt!MiDeletePte+0x15b:
804eb245 8b420c mov eax,[edx+0xc]
ds:0023:99be4b14=????????
Resetting default scope

STACK_TEXT:
fac4baf4 804f0e20 c0300018 c0006000 00000000 nt!MiDeletePte+0x15b
fac4bbb8 80501253 00001000 01bfffff 00000000
nt!MiDeleteVirtualAddresses+0x1c5
fac4bbfc 80582e8e 01aa9da0 ffaa9b28 ffaa9d70
nt!MmCleanProcessAddressSpace+0x25b
fac4bca4 8057a46a 00000000 ffaa9b28 00000000 nt!PspExitThread+0x680
fac4bcc4 80582d13 ffaa9b28 00000000 fac4bd64
nt!PspTerminateThreadByPointer+0x52
fac4bcf0 f97e0583 00000000 00000000 0012fe00 nt!NtTerminateProcess+0x118
WARNING: Stack unwind information not available. Following frames may be
wrong.
fac4bd64 7c91eb94 badb0d00 0012fdf8 00000000 klif+0x13583
0012feec 00000000 00000000 00000000 00000000 0x7c91eb94


FOLLOWUP_IP:
klif+13583
f97e0583 8d4c2408 lea ecx,[esp+0x8]

SYMBOL_STACK_INDEX: 6

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: klif+13583

MODULE_NAME: klif

IMAGE_NAME: klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f8bb7d9

STACK_COMMAND: .trap fffffffffac4ba5c ; kb

FAILURE_BUCKET_ID: 0xA_klif+13583

BUCKET_ID: 0xA_klif+13583

Followup: MachineOwner


he observado que hace referencia con frecuencia al klif.sys que al parecer
es un driver, pero no se si es el causante, ni a que pertenece. Espero
quero
alguien me pueda hechar una mano y orientarme para poder resover las tan
temidas pantallas azules que me traen por la calle de la amargura.

Un saludo para Por cierto he probado si era problema de la memoria,
he actualizado drivers, actualizado BIOS (por si acaso), cambiado
memorias,
cambiado gráficas. Excepto formatear de casi todo. Lo de formatear porque
me
huele que el error se va mantener.

Hash: SHA1

Nacho wrote:

> *** ERROR: Module load completed but symbols could not be loaded for klif.sys
> Probably caused by : klif.sys ( klif+13583 )

> IMAGE_NAME: klif.sys
>

Al karpesky, pertenece al karpesky, actualiza tu motor de antivirus... o
utiliza otro, desactiva la función residente y comprueba si los
pantallazos azules remiten,

A parte hay un error stop 0x0a
**/Soluciones posibles 0x0A 0x01E y errores 0x50 a DETENER
http://support.microsoft.com/?kbid3169&sd=RMVP

El artículo de la kb, incide en el tema del antivirus
Saludos
Fernando M. / Registered Linux User #367696
Fermu's Website - http://www.fermu.com

>klif.sys

blanco y en botella = antivirus ;-)

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"Nacho" wrote in message
news:
> Hola a :
> Ultimamente he observado que los ordenadores con los que trabajo sulen
> mostrar el error que indico en el asunto, y no consigo eliminarlo. Por eso
> he
> estado mirando por internet la información que hay al respecto y he
> llegado
> al articulo que ha escrito José Manuel Tella en la dirreción
> http://www.multingles.net/docs/jmt/bsod.html, que me ha parecido
> superinteresante, y me puesto manos a la obra para ver si consigo
> resolverlos
> he probado con uno de los ordenadores y el informe que me genera el windbg
> es
> el siguiente:
>
>
> Microsoft (R) Windows Debugger Version 6.4.0007.2
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\MEMORY.DMP]
> Kernel Complete Dump File: Full address space is available
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 2600.xpsp_sp2_gdr.050301-1519
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
> Debug session time: Wed Apr 20 16:11:42.267 2005 (GMT+2)
> System Uptime: 0 days 6:09:42.856
> Loading Kernel Symbols
> ...
> Loading unloaded module list
> ..
> Loading User Symbols
> PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck A, {99be4b14, 2, 0, 804eb245}
>
> *** ERROR: Module load completed but symbols could not be loaded for
> klif.sys
> Probably caused by : klif.sys ( klif+13583 )
>
> Followup: MachineOwner
>
>
> kd> .reload
> Loading Kernel Symbols
> ...
> Loading unloaded module list
> ..
> Loading User Symbols
> PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
> kd> .reload
> Loading Kernel Symbols
> ...
> Loading unloaded module list
> ..
> Loading User Symbols
> PEB is paged out (Peb.Ldr = 7ffd900c). Type ".hh dbgerr001" for details
> kd> analyze -v
> Couldn't resolve error at 'nalyze -v'
> kd> hh.dbgerr001
> ^ Syntax error in 'hh.dbgerr001'
> kd> hh
> ^ Syntax error in 'hh'
> kd> kd> !analyze -v
> Numeric expression missing from '> !analyze -v'
> kd> !analyze -v
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> IRQL_NOT_LESS_OR_EQUAL (a)
> An attempt was made to access a pageable (or completely invalid) address
> at an
> interrupt request level (IRQL) that is too high. This is usually
> caused by drivers using improper addresses.
> If a kernel debugger is available get the stack backtrace.
> Arguments:
> Arg1: 99be4b14, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 804eb245, address which referenced memory
>
> Debugging Details:
>
>
> *** ERROR: Module load completed but symbols could not be loaded for
> klif.sys
>
> READ_ADDRESS: 99be4b14 Nonpaged pool
>
> CURRENT_IRQL: 2
>
> FAULTING_IP:
> nt!MiDeletePte+15b
> 804eb245 8b420c mov eax,[edx+0xc]
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> BUGCHECK_STR: 0xA
>
> LAST_CONTROL_TRANSFER: from 804f0e20 to 804eb245
>
> TRAP_FRAME: fac4ba5c -- (.trap fffffffffac4ba5c)
> ErrCode = 00000000
> eaxffc961 ebxÀ300018 ecxffedcb edx™be4b08 esic48678
> edi003045
> eip€4eb245 esp=fac4bad0 ebp=fac4baf4 iopl=0 nv up ei pl nz na pe
> nc
> cs08 ss10 ds23 es23 fs30 gs00
> efl010202
> nt!MiDeletePte+0x15b:
> 804eb245 8b420c mov eax,[edx+0xc]
> ds:0023:99be4b14=????????
> Resetting default scope
>
> STACK_TEXT:
> fac4baf4 804f0e20 c0300018 c0006000 00000000 nt!MiDeletePte+0x15b
> fac4bbb8 80501253 00001000 01bfffff 00000000
> nt!MiDeleteVirtualAddresses+0x1c5
> fac4bbfc 80582e8e 01aa9da0 ffaa9b28 ffaa9d70
> nt!MmCleanProcessAddressSpace+0x25b
> fac4bca4 8057a46a 00000000 ffaa9b28 00000000 nt!PspExitThread+0x680
> fac4bcc4 80582d13 ffaa9b28 00000000 fac4bd64
> nt!PspTerminateThreadByPointer+0x52
> fac4bcf0 f97e0583 00000000 00000000 0012fe00 nt!NtTerminateProcess+0x118
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> fac4bd64 7c91eb94 badb0d00 0012fdf8 00000000 klif+0x13583
> 0012feec 00000000 00000000 00000000 00000000 0x7c91eb94
>
>
> FOLLOWUP_IP:
> klif+13583
> f97e0583 8d4c2408 lea ecx,[esp+0x8]
>
> SYMBOL_STACK_INDEX: 6
>
> FOLLOWUP_NAME: MachineOwner
>
> SYMBOL_NAME: klif+13583
>
> MODULE_NAME: klif
>
> IMAGE_NAME: klif.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 3f8bb7d9
>
> STACK_COMMAND: .trap fffffffffac4ba5c ; kb
>
> FAILURE_BUCKET_ID: 0xA_klif+13583
>
> BUCKET_ID: 0xA_klif+13583
>
> Followup: MachineOwner
>
>
> he observado que hace referencia con frecuencia al klif.sys que al parecer
> es un driver, pero no se si es el causante, ni a que pertenece. Espero
> quero
> alguien me pueda hechar una mano y orientarme para poder resover las tan
> temidas pantallas azules que me traen por la calle de la amargura.
>
> Un saludo para Por cierto he probado si era problema de la memoria,
> he actualizado drivers, actualizado BIOS (por si acaso), cambiado
> memorias,
> cambiado gráficas. Excepto formatear de casi todo. Lo de formatear porque
> me
> huele que el error se va mantener.