que sigue despues de !analyze -v

Hash: SHA1

el analize ese está completo?

error 0x50 o problema de controladores o fallo de memoria RAM, pero el
ocntraldor completo no sale en lo que has puesto, de todas formas revisa
la memoria RAM con memtest por si las moscas.
Saludos / Fernando M.
MS MVP Windows - Shell/User
Fermu's Website - http://www.fermu.com
Fermu's Forum - http://fermu.notlong.com

gracias por tu respuesta, aqui lo pongo completo


icrosoft (R) Windows Debugger Version 6.5.0003.7
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) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Feb 8 16:37:44.796 2006 (GMT-7)
System Uptime: 0 days 0:29:15.493
Loading Kernel Symbols

Loading unloaded module list
...
Loading User Symbols
..Missing image name,
possible corrupt data.
.WARNING: Unknown_Module_83267504 overlaps win32k
WARNING: Unknown_Module_83267504 overlaps dxg
WARNING: Unknown_Module_83267504 overlaps ati2dvag
WARNING: Unknown_Module_83267504 overlaps ati2cqag
WARNING: Unknown_Module_83267504 overlaps atikvmag
WARNING: Unknown_Module_83267504 overlaps ati3duag
WARNING: Unknown_Module_83267504 overlaps ativvaxx
Unable to read LDR_DATA_TABLE_ENTRY at f98bd88b - NTSTATUS 0xC0000147

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffbff8, 0, 8054a51a, 0}

*** WARNING: Unable to verify timestamp for Unknown_Module_83267504
*** ERROR: Module load completed but symbols could not be loaded for
Unknown_Module_83267504
Probably caused by : Unknown_Image ( Unknown_Module_83267504+44d98749 )

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: ffffbff8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8054a51a, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:



OVERLAPPED_MODULE: Address regions for 'Unknown_Module_83267504' and
'win32k' overlap

READ_ADDRESS: ffffbff8

FAULTING_IP:
nt!ExFreePoolWithTag+23a
8054a51a 668b4efa mov cx,[esi-0x6]

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from ec4d8b00 to 804f9c37

STACK_TEXT:
efabdb14 ec4d8b00 89d84d89 ce3bfc75 71890974 nt!KeBugCheckEx+0x1b
WARNING: Frame IP not in any known module. Following frames may be wrong.
efabdb2c c7fffc4d 0001fc45 4d8b0000 8b098b0c 0xec4d8b00
efabdb30 0001fc45 4d8b0000 8b098b0c 0a89ec55
Unknown_Module_83267504+0x44d98749
efabdb34 4d8b0000 8b098b0c 0a89ec55 83ec7d8b 0x1fc45
efabdb38 8b098b0c 0a89ec55 83ec7d8b 758b08c7 0x4d8b0000
efabdb3c 0a89ec55 83ec7d8b 758b08c7 a5a5a508 Unknown_Module_83267504+0x7e31608
efabdb40 83ec7d8b 758b08c7 a5a5a508 fc4d83a5 0xa89ec55
efabdb44 758b08c7 a5a5a508 fc4d83a5 ec558bff Unknown_Module_83267504+0xc60887
efabdb48 a5a5a508 fc4d83a5 ec558bff 89104d8b 0x758b08c7
efabdb4c fc4d83a5 ec558bff 89104d8b e44d8b11
Unknown_Module_83267504+0x227f3004
efabdb50 ec558bff 89104d8b e44d8b11 8b204a89 0xfc4d83a5
efabdb54 89104d8b e44d8b11 8b204a89 5189ec55 0xec558bff
efabdb58 e44d8b11 8b204a89 5189ec55 00d0e918 Unknown_Module_83267504+0x5e9d887
efabdb5c 8b204a89 5189ec55 00d0e918 75ff0000 0xe44d8b11
efabdb60 5189ec55 00d0e918 75ff0000 dc458bec Unknown_Module_83267504+0x7f9d585
efabdb64 00d0e918 75ff0000 dc458bec e808488b 0x5189ec55
efabdb68 75ff0000 dc458bec e808488b 00019044 0xd0e918
efabdb6c dc458bec e808488b 00019044 00bb82b8 BROWSEUI!_pRawDllMain <PERF>
(BROWSEUI+0xc0000)
efabdb70 e808488b 00019044 00bb82b8 00b8c301 0xdc458bec
efabdb74 00019044 00bb82b8 00b8c301 eb800000 0xe808488b
efabdb78 00bb82b8 00b8c301 eb800000 ec75ff19 0x19044
efabdb7c 00b8c301 eb800000 ec75ff19 8bdc458b 0xbb82b8
efabdb80 eb800000 ec75ff19 8bdc458b 29e80848 0xb8c301
efabdb84 ec75ff19 8bdc458b 29e80848 b8000190 0xeb800000
efabdb88 8bdc458b 29e80848 b8000190 0100bb9d 0xec75ff19
efabdb8c 29e80848 b8000190 0100bb9d 0007b8c3 Unknown_Module_83267504+0x8b5d087
efabdb90 b8000190 0100bb9d 0007b8c3 4d8b8000 0x29e80848
efabdb94 0100bb9d 0007b8c3 4d8b8000 0d8964f4
Unknown_Module_83267504+0x34d98c8c
efabdb98 0007b8c3 4d8b8000 0d8964f4 00000000 0x100bb9d
efabdb9c 4d8b8000 0d8964f4 00000000 c95b5e5f 0x7b8c3
efabdba0 0d8964f4 00000000 c95b5e5f ff000cc2 0x4d8b8000
efabdba4 00000000 c95b5e5f ff000cc2 458be875 0xd8964f4


FOLLOWUP_IP:
Unknown_Module_83267504+44d98749
c7fffc4d ?? ???

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Unknown_Module_83267504+44d98749

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_Unknown_Module_83267504+44d98749

BUCKET_ID: 0x50_Unknown_Module_83267504+44d98749

Followup: MachineOwner


Te comento que esta misma pc me pasaba esto antes de cambiarle tarjeta
principal y memoria ram, de repente se apaga, se reinicia, crei que era la
ram antes de cambiar tarjeta principal, siguio el mismo problema y decidi
cambiar de tarjeta principal y ram, la tarjeta es Intel y la ram es Kingston.


Saludos..

Hash: SHA1

joy wrote:

gracias por tu respuesta, aqui lo pongo completo

utiliza verifier y revisa que drivers para versiones anteriores de winxp
tienes instalados, alguno de ellos puede ser el culpable... por que el
problema parece que lo provoca algún driver, pero yo por lo menos sigo
sin saber a ciencia cierta cual puede ser con la salida que pones...

Saludos
MS MVP Windows - Shell/User
Fermu's Website - http://www.fermu.com
Fermu's Forum - http://fermu.notlong.com/