El Pc se me reinicia frecuentemente

23/08/2005 - 01:42 por Javier | Informe spam
Hago crossposting a microsoft.public.es.windwsxp porque me parece que
los dos grupos son adecuados.

Tengo Windows 2000 + SP4, actualizado con los parches para el sasser,
blaster y zotob, y utilizo el AVG antivirus.
Ultimamente se reinicia solo, todos los días. Guiándome por el artículo
de Jose Manuel Tella Llop
( www.multingles.net/docs/jmt/bsod.htm ),
he intentado analizar el volcado de memoria. Al analizar el minidump,
dice que parece un problema de win32k.sys. Se que esto puede ser un
problema de memoria, pero le he pasado el memtest86 durante unas horas y
no ha dado error. Lo pasaré más tiempo posteriormente. Cuando cambié el
tipo de volcado a kernel dump, cuando me dio el pantallazo, como tarda
más vi que ponía lo de win32k.sys. Al abrirlo con el WINDBG muestra lo
siguiente:


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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: a00645af, The address that the exception occurred at
Arg3: 00000000, Parameter 0 of the exception
Arg4: 245c8b00, Parameter 1 of the exception

Debugging Details:


*** ERROR: Symbol file could not be found. Defaulted to export symbols
for SHELL32.dll -
*** WARNING: Unable to verify checksum for persfw.exe
*** ERROR: Module load completed but symbols could not be loaded for
persfw.exe
Page 368 not present in the dump file. Type ".hh dbgerr004" for details
Page 368 not present in the dump file. Type ".hh dbgerr004" for details
Page b550 not present in the dump file. Type ".hh dbgerr004" for details
Page b550 not present in the dump file. Type ".hh dbgerr004" for details
Page 5f88 not present in the dump file. Type ".hh dbgerr004" for details
Page 5f88 not present in the dump file. Type ".hh dbgerr004" for details
Page 1a841 too large to be in the dump file.
Page 1a841 too large to be in the dump file.
Page b000 not present in the dump file. Type ".hh dbgerr004" for details
Page b000 not present in the dump file. Type ".hh dbgerr004" for details
Page 368 not present in the dump file. Type ".hh dbgerr004" for details
Page 368 not present in the dump file. Type ".hh dbgerr004" for details
Page b550 not present in the dump file. Type ".hh dbgerr004" for details
Page b550 not present in the dump file. Type ".hh dbgerr004" for details
Page 5f88 not present in the dump file. Type ".hh dbgerr004" for details
Page 5f88 not present in the dump file. Type ".hh dbgerr004" for details
Page 1a841 too large to be in the dump file.
Page 1a841 too large to be in the dump file.
Page b000 not present in the dump file. Type ".hh dbgerr004" for details
Page b000 not present in the dump file. Type ".hh dbgerr004" for details
Page 368 not present in the dump file. Type ".hh dbgerr004" for details
Page 368 not present in the dump file. Type ".hh dbgerr004" for details
Page b550 not present in the dump file. Type ".hh dbgerr004" for details
Page b550 not present in the dump file. Type ".hh dbgerr004" for details
Page 5f88 not present in the dump file. Type ".hh dbgerr004" for details
Page 5f88 not present in the dump file. Type ".hh dbgerr004" for details
Page 1a841 too large to be in the dump file.
Page 1a841 too large to be in the dump file.
Page b000 not present in the dump file. Type ".hh dbgerr004" for details
Page b000 not present in the dump file. Type ".hh dbgerr004" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace
referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

FAULTING_IP:
win32k!BuildHwndList+f
a00645af a0008b5c24 mov al,[245c8b00]

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 245c8b00

READ_ADDRESS: 245c8b00 Nonpaged pool

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x1E

LAST_CONTROL_TRANSFER: from 80866a1b to 80830999

STACK_TEXT:
bb314ba0 80866a1b bb314bbc 00000000 bb314c10
nt!Ki386CheckDelayedNpxTrap+0x5d
bb314c08 808669cd 01453708 bb314c2c 80856d5f nt!KiTrap0D+0x923
bb314c14 80856d5f 81672f48 e2a4eb58 00000000 nt!KiTrap0D+0x8d5
bb314c2c 80856cfa 808573c5 8162cd68 77592238 nt!RtlpSetSecurityObject+0xdf
bb314c84 a008e327 a039aa28 00000002 00000000 nt!RtlpSetSecurityObject+0x7a
bb314cd4 a008e506 00000000 00000000 77592238 win32k!_FindWindowEx+0x86
bb314d48 80865b91 00000000 00000000 0157f594 win32k!NtUserFindWindowEx+0x119
bb314d48 77e167ec 00000000 00000000 0157f594 nt!Dr_kitb_a+0x51
0157f5a4 77e22564 00000000 00000000 77592238 USER32!NtUserFindWindowEx+0xb
0157f5bc 775a7b4c 77592238 00000000 77c72be3 USER32!FindWindowW+0x12
WARNING: Stack unwind information not available. Following frames may be
wrong.
0157f99c 775cf940 00000001 0157f9b4 00000000 SHELL32!Shell_NotifyIconW+0x21
0157fd5c 0040d6cf 00000001 0157fd6c 000001e8 SHELL32!Shell_NotifyIcon+0xa0
79453a17 03e80824 c2000000 8b550004 565151ec persfw+0xd6cf
79453a1b c2000000 8b550004 565151ec 0875ff57 0x3e80824
79453a1f 8b550004 565151ec 0875ff57 50f8458d 0xc2000000
79453a23 565151ec 0875ff57 50f8458d ffffa0e8 0x8b550004
79453a27 0875ff57 50f8458d ffffa0e8 85f88bff 0x565151ec
79453a2b 50f8458d ffffa0e8 85f88bff 9a840fff 0x875ff57
79453a2f ffffa0e8 85f88bff 9a840fff 8b000345 0x50f8458d
79453a33 85f88bff 9a840fff 8b000345 45143035 0xffffa0e8
79453a37 9a840fff 8b000345 45143035 75ff5779 0x85f88bff
79453a3b 8b000345 45143035 75ff5779 83d6ff0c 0x9a840fff
79453a3f 45143035 75ff5779 83d6ff0c 0f000c7d 0x8b000345
79453a43 75ff5779 83d6ff0c 0f000c7d 03459685 0x45143035
79453a47 83d6ff0c 0f000c7d 03459685 00c0b900 0x75ff5779
79453a4b 0f000c7d 03459685 00c0b900 c13b0000 0x83d6ff0c
83d6ff0c 00000000 00182fa4 02d0000c bf650020 0xf000c7d


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
win32k!BuildHwndList+f
a00645af a0008b5c24 mov al,[245c8b00]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!BuildHwndList+f

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4047dcd6

FAILURE_BUCKET_ID: 0x1E_win32k!BuildHwndList+f

BUCKET_ID: 0x1E_win32k!BuildHwndList+f

Followup: MachineOwner


Lo de persfw se refiere al kerio personal firewall 2.1.5


¿Alguien tiene alguna idea o sabe lo que puedo hacer?


Gracias y un saludo

Preguntas similare

Leer las respuestas

#6 Javier
24/08/2005 - 20:16 | Informe spam
Antonio Núñez escribió:
Hola Javier, ¿has tenido alguna subida o bjada del fluido eléctrico en forma
de pico rápido?

Te lo comento porque a mí me pasó hace un par de años, el problema es que
trabajo con bdŽs y constantemente se me reiniciaba el equipo sin saber
cuándo iba a suceder. Las bdŽs quedaban abiertas, se corrompían los archivos
del S.O. y demás. La única solución que encontré fue empezar a desmontar el
PC por perifericos y tarjetas... El problema era que se había quemado el
modem analogico y estaba dando constantes problemas... Prueba tú eso.



Que yo sepa no, de todas formas ya probaré.

En estos dias he tenido mas reinicios con otro tipo de error:

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

Debugging Details:



WRITE_ADDRESS: ffffff89

FAULTING_IP:
win32k!BuildHwndList+37
a00645b7 105389 adc [ebx-0x77],dl

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 80868f3a to 8084a7c2

STACK_TEXT:
bb2bcbf8 80868f3a 00000001 ffffff89 00000000 nt!NtResetWriteWatch+0x104
bb2bcbf8 a00645b7 00000001 ffffff89 00000000 nt!LZNT1DecompressChunk+0x4e2
bb2bcc84 a008e327 a031a8b0 00000002 00000000 win32k!BuildHwndList+0x37
bb2bccd4 a008e506 00000000 00000000 77592238 win32k!_FindWindowEx+0x86
bb2bcd48 80865b91 00000000 00000000 0157f594 win32k!NtUserFindWindowEx+0x119
bb2bcd48 77e167ec 00000000 00000000 0157f594 nt!Dr_kitb_a+0x51
0157f5a4 77e22564 00000000 00000000 77592238 USER32!NtUserFindWindowEx+0xb
0157f5bc 775a7b4c 77592238 00000000 77c72be3 USER32!FindWindowW+0x12
WARNING: Stack unwind information not available. Following frames may be
wrong.
0157f99c 775cf940 00000001 0157f9b4 00000004 SHELL32!Shell_NotifyIconW+0x21
0157fd5c 0040d6cf 00000001 0157fd6c 000001e8 SHELL32!Shell_NotifyIcon+0xa0
79453a17 03e80824 c2000000 8b550004 565151ec persfw+0xd6cf
79453a1b c2000000 8b550004 565151ec 0875ff57 0x3e80824
79453a1f 8b550004 565151ec 0875ff57 50f8458d 0xc2000000
79453a23 565151ec 0875ff57 50f8458d ffffa0e8 0x8b550004
8b550004 001c0001 00046b76 000004aa 004f9020 0x565151ec
8b550008 00046b76 000004aa 004f9020 00000003 0x1c0001
8b55000c 00000000 004f9020 00000003 00000001 0x46b76


FOLLOWUP_IP:
win32k!BuildHwndList+37
a00645b7 105389 adc [ebx-0x77],dl

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!BuildHwndList+37

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4047dcd6

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_W_win32k!BuildHwndList+37

BUCKET_ID: 0x50_W_win32k!BuildHwndList+37

Followup: MachineOwner



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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {c0000005, 8086bbbd, 1, 484db1cd}

Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2cb )

Followup: MachineOwner


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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8086bbbd, The address that the exception occurred at
Arg3: 00000001, Parameter 0 of the exception
Arg4: 484db1cd, Parameter 1 of the exception

Debugging Details:



EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace
referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

FAULTING_IP:
nt!ExFreePoolWithTag+2cb
8086bbbd 188d4148508d sbb [ebp+0x8d504841],cl

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 484db1cd

WRITE_ADDRESS: 484db1cd Paged pool

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x1E

LAST_CONTROL_TRANSFER: from 80866a1b to 80830999

STACK_TEXT:
bafd6888 80866a1b bafd68a4 00000000 bafd68f8
nt!Ki386CheckDelayedNpxTrap+0x5d
bafd68f0 808669cd 80869d5b 01001414 ffffffff nt!KiTrap0D+0x923
bafd6914 809a7f53 a0200000 0000000a ffdff000 nt!KiTrap0D+0x8d5
bafd697c 80850fb8 00000000 00edabe0 bafd6d48 hal!KfLowerIrql+0x43
bafd6d48 80865b91 0000000a 03baff74 00000001 nt!PopApplyAttributeState+0x48
bafd6d48 7846287e 0000000a 03baff74 00000001 nt!Dr_kitb_a+0x51
03baff48 7755932f 0000000a 03baff74 00000001
ntdll!ZwWaitForMultipleObjects+0xb
03baffb4 7945438b 00000000 0012f168 02ca267c WINMM!timeThread+0x73
03baffec 00000000 7755927f 00000000 00000000 KERNEL32!BaseThreadStart+0x52


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+2cb
8086bbbd 188d4148508d sbb [ebp+0x8d504841],cl

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!ExFreePoolWithTag+2cb

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4047db83

FAILURE_BUCKET_ID: 0x1E_W_nt!ExFreePoolWithTag+2cb

BUCKET_ID: 0x1E_W_nt!ExFreePoolWithTag+2cb

Followup: MachineOwner






Saludos
email Siga el debate Respuesta Responder a este mensaje
Ads by Google
Help Hacer una pregunta AnteriorRespuesta Tengo una respuesta
Search Busqueda sugerida