error irql_not_less_or_equal

09/04/2006 - 12:11 por Kaina | Informe spam
Hola a todos,
Hace ya un tiempo que recibo el típico pantallazo azul con
irql_not_less_or_equal. He estado buscando por internet las possibles causas
pero nada soluciona mi problema. Os adjunto el análisis con el windbg del
error, por si alguien me puede decir alguna cosa más sobre esto. Muchas
gracias

Microsoft (R) Windows Debugger Version 6.6.0003.5
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) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Apr 9 11:37:08.359 2006 (GMT+2)
System Uptime: 0 days 0:03:57.051
Loading Kernel Symbol

Loading User Symbols
Loading unloaded module list

*******************************************************************************
*
*
* Bugcheck Analysis
*
*

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 1c, 0, 804dc6fc}

Probably caused by : ntkrnlmp.exe ( nt!KiReadyThread+c1 )

Followup: MachineOwner


0: kd> !analyze -
*******************************************************************************
*
*
* 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: 00000008, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804dc6fc, address which referenced memory

Debugging Details:



READ_ADDRESS: 00000008

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiReadyThread+c1
804dc6fc 8b7b08 mov edi,[ebx+0x8]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804dc6fc to 804e0aac

STACK_TEXT:
80556248 804dc6fc badb0d00 00000001 00000286 nt!KiTrap0E+0x238
805562d0 804e17b6 82a0f988 00000000 805562e0 nt!KiReadyThread+0xc1
805562f0 804e2b00 8d4b9aba 00000043 80556418 nt!KiWaitTest+0xcd
805563fc 804e207d 80560f00 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x7a
80556428 804dcd22 80561300 00000000 00003b43 nt!KiTimerExpiration+0xb1
80556450 804dcc07 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80556454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiReadyThread+c1
804dc6fc 8b7b08 mov edi,[ebx+0x8]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiReadyThread+c1

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

FAILURE_BUCKET_ID: 0xA_nt!KiReadyThread+c1

BUCKET_ID: 0xA_nt!KiReadyThread+c1

Followup: MachineOwner

Preguntas similare

Leer las respuestas

#1 R.E Fernandez
09/04/2006 - 13:19 | Informe spam
email Siga el debate Respuesta Responder a este mensaje
Ads by Google
Help Hacer una preguntaRespuesta Tengo una respuesta
Search Busqueda sugerida