Pantallazo azul

hola a todos,

El otro día se me pegó un pantallazo azul un windows 2000 server y se me
reinició. Es un HP proliant en raid 5 con 3 discos en scsi. Desde que lo
montamos hace 6 meses no había dado el mas mínimo problema. Está bajo
dominio con terminal server instalado. En el visor de sucesos no veo nada
relevante. Pongo a continuación el informe de la herramienta windbg. ¿tendré
un fallo físico de hardware o tendré corrupta la librería RDPDD.dll como
parece indicarme como probable causa?

Gracias y un saludo


WARNING: Whitespace at end of path element

Microsoft (R) Windows Debugger Version 6.6.0003.5

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\Documents and Settings\ELOELO\Escritorio\c\MEMORY.DMP]

Kernel Complete Dump File: Full address space is available

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

WARNING: Dump file has been truncated. Data may be missing.

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

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



Executable search path is:

Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86
compatible

Product: LanManNt, suite: TerminalServer

Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b80

Debug session time: Wed May 31 11:38:09.541 2006 (GMT+2)

System Uptime: 1 days 16:24:33.625

Loading Kernel Symbols

...

Loading User Symbols

..

Loading unloaded module list

...

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {a228e000, 0, a07e7367, 1}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
MSVBVM60.DLL -

Probably caused by : RDPDD.dll ( RDPDD!OESendBrushOrder+85 )

Followup: MachineOwner

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by
try-except,

it must be protected by a Probe. Typically the address is just plain bad or
it

is pointing at freed memory.

Arguments:

Arg1: a228e000, memory referenced.

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: a07e7367, If non-zero, the instruction address which referenced the
bad memory

address.

Arg4: 00000001, (reserved)

Debugging Details:





READ_ADDRESS: a228e000 Nonpaged pool

FAULTING_IP:

RDPDD!OESendBrushOrder+85

a07e7367 f3a5 rep movsd

MM_INTERNAL_CODE: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 8046b063 to 8044c796

STACK_TEXT:

bd6d640c 8046b063 00000000 a228e000 00000000 nt!MmAccessFault+0x7dc

bd6d640c a07e7367 00000000 a228e000 00000000 nt!KiTrap0E+0xc7

bd6d64a4 a07e7458 a2018028 a228dfa8 a228dfd4 RDPDD!OESendBrushOrder+0x85

bd6d64d0 a07e40af a2018028 a228dfa8 a21f5594 RDPDD!OEReCacheBrush+0xce

bd6d64e8 a07e18ee a2018028 a21f5434 bd6d6508 RDPDD!OECheckBrushIsSimple+0xa1

bd6d650c a07e13bc a2018028 a21f5434 bd6d6558 RDPDD!OEEncodePatBlt+0x16

bd6d656c a0002d37 a20197a8 000000f0 00000000 RDPDD!DrvBitBlt+0x244

bd6d65b4 a0007450 a21f5434 bd6d6630 bd6d6608 win32k!GrePatBltLockedDC+0x1b0

bd6d6664 a000100c bd6d6700 0000f0f0 7ffde200
win32k!GrePolyPatBltInternal+0x17e

bd6d6704 8046835a 00000098 0012fb84 b5073236
win32k!NtGdiFlushUserBatch+0x1c3

bd6d6704 77f71963 00000098 0012fb84 b5073236 nt!KiSystemService+0x9a

0012fbd0 6a8b194c 010903bc 0101011b 010903bc GDI32!NtGdiGetAppClipBox+0xb

WARNING: Stack unwind information not available. Following frames may be
wrong.

0012fbe4 6a8b17a8 010903bc 00030036 0000000f
MSVBVM60!EVENT_SINK_AddRef+0x40dd

0012fc14 6a8b7050 00000000 00030036 0000000f
MSVBVM60!EVENT_SINK_AddRef+0x3f39

0012fcc0 6a8b18b4 0101011b 00030036 0012fd60 MSVBVM60!_vbaFreeObjList+0x987

0012fcdc 6a8b1774 010903bc 0012fd18 0012fd1c
MSVBVM60!EVENT_SINK_AddRef+0x4045

0012fd0c 6a8b08ab 010903bc 00030036 0000000f
MSVBVM60!EVENT_SINK_AddRef+0x3f05

0012fd68 77e4158f 00030036 0000000f 00000000
MSVBVM60!EVENT_SINK_AddRef+0x303c

0012fda4 77e3c1ca 00545ee8 0000000f 00000000 USER32!__ClientCharToWchar+0x38

001301c0 00000000 00000000 00000000 00000000 USER32!InternalEnumProps+0xbd



STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

RDPDD!OESendBrushOrder+85

a07e7367 f3a5 rep movsd

FAULTING_SOURCE_CODE:



SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: RDPDD!OESendBrushOrder+85

MODULE_NAME: RDPDD

IMAGE_NAME: RDPDD.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3e7b8771

FAILURE_BUCKET_ID: 0x50_RDPDD!OESendBrushOrder+85

BUCKET_ID: 0x50_RDPDD!OESendBrushOrder+85

Followup: MachineOwner