DRIVER_IRQL_NOT_LESS_OR_EQUAL

Hola a tod@s de nuevo, reulta que anteriormente he puesto un post con el
mismo problema que ahora se encuentra en el asunto y parece que el ordenador
responde, y ahora me dispongo analizar el problema de otro ordenador con el
windbg y me aparece lo siguiente:


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


Loading Dump File [E:\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 Jun 22 14:20:18.062 2005 (GMT+2)
System Uptime: 0 days 0:02:22.638
Loading Kernel Symbols
..
Loading unloaded module list

Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8001, 2, 1, 8183e4db}

*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
CLASSPNP.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
PartMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for
ftdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for
VolSnap.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for sr.sys
Probably caused by : ACPI.sys ( ACPI+6cd9 )

Followup: MachineOwner


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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00008001, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8183e4db, address which referenced memory

Debugging Details:



WRITE_ADDRESS: 00008001

CURRENT_IRQL: 2

FAULTING_IP:
+ffffffff8183e4db
8183e4db 0018 add [eax],bl

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f99e7cd9 to 8183e4db

TRAP_FRAME: f9e644c4 -- (.trap fffffffff9e644c4)
ErrCode = 00000002
eax008001 ebxb77c80 ecx=f99ff280 edx000003 esi=f99ff280 edi83e4d8
eip83e4db esp=f9e64538 ebp=f9e64544 iopl=0 nv up ei ng nz na pe nc
cs08 ss10 ds23 es23 fs30 gs00 efl010282
8183e4db 0018 add [eax],bl ds:0023:00008001=??
Resetting default scope

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f9e64544 f99e7cd9 81b77c80 f9e64574 f9e64584 0x8183e4db
f9e64578 804e37f7 81b77c80 8183e4d8 8183e670 ACPI+0x6cd9
f9e64588 f9a72061 00007000 81847428 8183e670 nt!IopfCallDriver+0x31
f9e6459c f9a71d58 8183e670 81b7fb70 81847528
CLASSPNP!ClassCompleteRequest+0x402
f9e645cc f9a71e49 00009000 00009000 81847428
CLASSPNP!ClassCompleteRequest+0xf9
f9e645f0 804e37f7 81b7fab8 00000000 81bce4d8
CLASSPNP!ClassCompleteRequest+0x1ea
f9e64600 f9cb936c 81bacee8 8184754c f9e6463c nt!IopfCallDriver+0x31
f9e64610 804e37f7 81b7e020 81847428 81847570 PartMgr+0x36c
f9e64620 f99b21c6 00010000 81bd0170 819c47c0 nt!IopfCallDriver+0x31
f9e6463c 804e37f7 81bace30 81847428 81bce3e0 ftdisk+0x11c6
f9e6464c f9a5151a 81baca60 81baca60 f9e646b8 nt!IopfCallDriver+0x31
f9e6465c 804e37f7 81baca60 81847428 00000002 VolSnap+0x51a
f9e6466c f98a39cb 819c47c0 f9e64984 e12bec50 nt!IopfCallDriver+0x31
f9e646b8 f98a3800 f9e64984 81baca60 819c47c0 Ntfs+0x59cb
f9e64890 f98a16fe f9e64984 819c47c0 e12bec50 Ntfs+0x5800
f9e64970 f98a0fbf f9e64984 819c47c0 00000001 Ntfs+0x36fe
f9e64b20 804e37f7 81b8a658 819c47c0 81b7c810 Ntfs+0x2fbf
f9e64b30 f9942459 f9e64b5c 804e37f7 81b8a020 nt!IopfCallDriver+0x31
f9e64b38 804e37f7 81b8a020 819c47c0 00970000 sr+0x459
f9e64b48 804f5508 00000000 81abea60 81abea70 nt!IopfCallDriver+0x31
f9e64b5c 804f552f 81b8a020 81abea09 81abea78 nt!IopPageReadInternal+0xf4
f9e64b7c 804f5194 819505e8 81abea98 81abea78 nt!IoPageRead+0x1b
f9e64bf0 804ebace 065cb8c0 c5bf0000 c0316fc0 nt!MiDispatchFault+0x274
f9e64c40 804f7383 00000000 c5bf0000 00000000 nt!MmAccessFault+0x5bc
f9e64c80 80503db1 c5bf0000 00000000 80556618 nt!MmCheckCachedPageState+0x461
f9e64d2c 80503b65 81bc9298 80561440 81bcbb30 nt!CcPerformReadAhead+0x1f1
f9e64d74 804e426b 81bc9298 00000000 81bcbb30 nt!CcWorkerThread+0x147
f9e64dac 8057be15 81bc9298 00000000 00000000 nt!ExpWorkerThread+0x100
f9e64ddc 804fa4da 804e4196 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
ACPI+6cd9
f99e7cd9 8b4dfc mov ecx,[ebp-0x4]

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ACPI+6cd9

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d27

STACK_COMMAND: .trap fffffffff9e644c4 ; kb

FAILURE_BUCKET_ID: 0xD1_W_ACPI+6cd9

BUCKET_ID: 0xD1_W_ACPI+6cd9

Followup: MachineOwner


He observado que el problema ahora se encuentra o por lo menos me parece que
hace referencia al acpi.sys. Me gustaría que le echarais un ojo para ver si
me podrias decir como reolverlo.
P.D. El equipo esta recien formateado, con varios programas instalados entre
ellos juegos. He testeado la memoria y no me da errores. He actualizado los
drivers de la gráfica porque el error lo da normalmente mientras se juega con
el ordenador.
Un saludo y espero que me podais echar un cable. Gracias.