Ayuda para analizar pantallazo con el Windbg

Desde hace tiempo tengo pantallazos azules cuando estoy haciendo tareas
que exigen bastante al ordenador. (Compresion de video, trabajos grandes
con photoshop).
Creia que era la ram era la culpable, la analize con el memtest y con
otro programa (creo que es de microsoft), y lo cierto es que segun los
dos programas tenia muchos fallos. La cambie hace dos semanas y el
sistema es mucho mas estable que antes, pero en tareas fuertes suele dar
error a los 7 u 8 minutos.

Siguiendo las instrucciones que encontre en
http://www.multingles.net/docs/jmt/bsod.htm

he analizado el "memory dump" y quisiera que me ayudarais a entenderlo:


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) 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: Sat Apr 1 19:09:29.171 2006 (GMT+2)
System Uptime: 0 days 15:48:32.785
Loading Kernel Symbols
...
Loading User Symbols
...
Loading unloaded module list
...
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {d78feeb0, 2, 1, 804dc40c}

Probably caused by : ntoskrnl.exe ( nt!KiTimerListExpire+b1 )

Followup: MachineOwner


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: d78feeb0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804dc40c, address which referenced memory

Debugging Details:



WRITE_ADDRESS: d78feeb0

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerListExpire+b1
804dc40c 8903 mov [ebx],eax

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804dc40c to 804e187f

STACK_TEXT:
f78fee2c 804dc40c badb0d00 82a9d62b 02cef70c nt!KiTrap0E+0x233
f78fefa4 804dc378 82a9d62b 00000084 ffdff000 nt!KiTimerListExpire+0xb1
f78fefd0 804dbbd4 80559280 00000000 00379431 nt!KiTimerExpiration+0xaf
f78feff4 804db89e ba228d44 00000000 00000000 nt!KiRetireDpcList+0x46
f78feff8 ba228d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
804db89e 00000000 00000009 bb835675 00000128 0xba228d44


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiTimerListExpire+b1
804dc40c 8903 mov [ebx],eax

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTimerListExpire+b1

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

FAILURE_BUCKET_ID: 0xA_W_nt!KiTimerListExpire+b1

BUCKET_ID: 0xA_W_nt!KiTimerListExpire+b1

Followup: MachineOwner




A ver si me podeis echar una mano.

Gracias de antemano
Goiko5551