[Hilo anterior] A ver que pasa con los cuelgues.

El sistema tiene instaladoWXP + SP2 limpio. Automáticamente instaló las
actualizaciones. Instaló el scanner.
De repente se congeló con el monitor en negro. No hay información de error.
Tuve que reiniciar "en bruto".
Francisco.

"FJTL" escribió en el mensaje
news:%

Tal y como me recomendó JM, he instalado una nueva versión de WXP en otra
partición,. listo para hacer las pruebas que sea menester.
Por ahora voy a hacer varias cosas a ver si "salta" el sistema.
Informaré.
Francisco.

Loading Dump File [E:\WINDOWS\Minidump\Mini061105-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*E:\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 Jun 11 17:09:25.859 2005 (GMT+2)

System Uptime: 0 days 0:00:26.421

Loading Kernel Symbols

...

Loading unloaded module list

..

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, bacc386c, 0}

Probably caused by : Npfs.SYS ( Npfs!NpCommonCreateNamedPipe+1c1 )

Followup: MachineOwner



kd> g

^ No runnable debuggees error in 'g'

kd> .restart

Loading Dump File [E:\WINDOWS\Minidump\Mini061105-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*E:\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 Jun 11 17:09:25.859 2005 (GMT+2)

System Uptime: 0 days 0:00:26.421

Loading Kernel Symbols

...

Loading unloaded module list

..

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, bacc386c, 0}

Probably caused by : Npfs.SYS ( Npfs!NpCommonCreateNamedPipe+1c1 )

Followup: MachineOwner



kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

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.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: c0000005, The exception code that was not handled

Arg2: 00000000, The address that the exception occurred at

Arg3: bacc386c, Trap Frame

Arg4: 00000000

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:

+0

00000000 ?? ???

TRAP_FRAME: bacc386c -- (.trap ffffffffbacc386c)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx=0cd60001 edx=0cd50000 esi000008
edi€4e6b9c

eip000000 esp=bacc38e0 ebpc46704e iopl=0 nv up ei pl zr na pe cy

cs08 ss10 ds23 es23 fs30 gs00 efl010243

00000000 ?? ???

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 00000000

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

bacc38dc 00000000 00002000 00002000 bacc3928 0x0



STACK_COMMAND: .trap ffffffffbacc386c; dds @$csp ; kb

FOLLOWUP_IP:

Npfs!NpCommonCreateNamedPipe+1c1

f7b4fbeb ebb0 jmp Npfs!NpCommonCreateNamedPipe+0x173 (f7b4fb9d)

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Npfs!NpCommonCreateNamedPipe+1c1

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b86

FAILURE_BUCKET_ID: 0x8E_Npfs!NpCommonCreateNamedPipe+1c1

BUCKET_ID: 0x8E_Npfs!NpCommonCreateNamedPipe+1c1

Followup: MachineOwner





Francisco

"FJTL" escribió en el mensaje
news:%

Tal y como me recomendó JM, he instalado una nueva versión de WXP en otra
partición,. listo para hacer las pruebas que sea menester.
Por ahora voy a hacer varias cosas a ver si "salta" el sistema.
Informaré.
Francisco.