Me acaba de dar otro error (continúa de hilo anterior)

Ah!!! Que va a ir poniendo cosas. Espero a que acabe ;-))
Siento mi ignorancia.
Francisco.


"JM Tella Llop [MVP Windows]" escribió en el mensaje
news:

Npfs.SYS
Algo relacionado con la red es como si hay restos en el stack IP de
algun componente que intenta (por ejemplo) actualizarte el software desde
remoto...

netstat -bv

(en una consola de comandos) puede que te de informacion...

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"FJTL" wrote in message
news:%

Y esta vez no es el Norton (ya está desinstalado y reiniciado).

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, f83de848, 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: f83de848, 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: f83de848 -- (.trap fffffffff83de848)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx960002 edx950001 esi000008
edi€4e6b9c

eip000000 espø3de8bc ebpc46704e iopl=0 nv up ei pl zr na po cy

cs08 ss10 ds23 es23 fs30 gs00 efl010247

00000000 ?? ???

Resetting default scope

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 00000000

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

f83de8b8 00000000 00000800 00000800 f83de904 0x0



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

FOLLOWUP_IP:

Npfs!NpCommonCreateNamedPipe+1c1

f87f8beb ebb0 jmp Npfs!NpCommonCreateNamedPipe+0x173 (f87f8b9d)

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



¿¿¿¿????

¿Se me ha cascado el ordenador?. ¿Algún programa de diagnósticos?.

Francisco.




"FJTL" escribió en el mensaje
news:

Pues eso, que otro error. Supongo que está claro que es el Norton... ¿o
no?.

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {90, ffdff120, 0, 0}

Unable to load image SAVRT.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for SAVRT.SYS

*** ERROR: Module load completed but symbols could not be loaded for
SAVRT.SYS

Probably caused by : SAVRT.SYS ( SAVRT+33af4 )

Followup: MachineOwner



kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

A device driver attempting to corrupt the system has been caught. This
is

because the driver was specified in the registry as being suspect (by
the

administrator) and the kernel has enabled substantial checking of this
driver.

If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and
0xA will

be among the most commonly seen crashes.

Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.

Typically the code is 0x1001 (deadlock detected) and you can

issue a '!deadlock' KD command to get more information.

Arguments:

Arg1: 00000090, A driver switched stacks. The current stack is neither a
thread

stack nor a DPC stack. Typically the driver doing this should be

on the stack obtained from `kb' command.

Arg2: ffdff120

Arg3: 00000000

Arg4: 00000000

Debugging Details:





BUGCHECK_STR: 0xc4_90

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from e295e33a to ef519af4

TRAP_FRAME: fbeccbe8 -- (.trap fffffffffbeccbe8)

ErrCode = 00000000

eaxá09a088 ebx000000 ecxá272260 edxâ95e008 esiá24007f
edi00007f

eip=ef519af4 esp=fbeccc5c ebp000000 iopl=0 nv up ei pl nz na pe nc

cs08 ss10 ds23 es23 fs30 gs00 efl010202

SAVRT+0x33af4:

ef519af4 ?? ???

Resetting default scope

STACK_TEXT:

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

fbeccc58 e295e33a fbecccb0 e295e008 ef525392 SAVRT+0x33af4

00010202 00000000 00000000 00000000 00000000 0xe295e33a



FOLLOWUP_IP:

SAVRT+33af4

ef519af4 ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+33af4

MODULE_NAME: SAVRT

IMAGE_NAME: SAVRT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41ba0a1f

STACK_COMMAND: .trap fffffffffbeccbe8 ; kb

FAILURE_BUCKET_ID: 0xc4_90_SAVRT+33af4

BUCKET_ID: 0xc4_90_SAVRT+33af4

Followup: MachineOwner



Francisco.

Campo Valor
Propiedades del sensor
Tipo de sensor ITE IT8712F (ISA 290h)
Nombre de la Placa Base Asus A7V600 / A7V880 / A7V8X-X / K8N / SK8N

Temperaturas
Placa base 44 °C (111 °F)
Procesador 54 °C (129 °F)
Seagate ST340810A 41 °C (106 °F)
Seagate ST340014A 40 °C (104 °F)

Ventiladores
Procesador 3649 RPM

Valores de voltaje
Núcleo CPU 1.65 V
+3.3 V 3.30 V
+5 V 4.95 V
+12 V 13.31 V
Puesta en espera +5 V 5.03 V

Francisco.


"FJTL" escribió en el mensaje
news:

El netstat dice:

Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Francisco>netstat -bv

Conexiones activas

Proto Dirección local Dirección remota Estado PID
TCP fran:1033 localhost:1052 ESTABLISHED 1048

¿¿¿???
Francisco.

"JM Tella Llop [MVP Windows]" escribió en el mensaje
news:

Npfs.SYS
Algo relacionado con la red es como si hay restos en el stack IP de
algun componente que intenta (por ejemplo) actualizarte el software desde
remoto...

netstat -bv

(en una consola de comandos) puede que te de informacion...

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"FJTL" wrote in message
news:%

Y esta vez no es el Norton (ya está desinstalado y reiniciado).

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, f83de848, 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: f83de848, 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: f83de848 -- (.trap fffffffff83de848)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx960002 edx950001 esi000008
edi€4e6b9c

eip000000 espø3de8bc ebpc46704e iopl=0 nv up ei pl zr na po cy

cs08 ss10 ds23 es23 fs30 gs00 efl010247

00000000 ?? ???

Resetting default scope

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 00000000

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

f83de8b8 00000000 00000800 00000800 f83de904 0x0



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

FOLLOWUP_IP:

Npfs!NpCommonCreateNamedPipe+1c1

f87f8beb ebb0 jmp Npfs!NpCommonCreateNamedPipe+0x173 (f87f8b9d)

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



¿¿¿¿????

¿Se me ha cascado el ordenador?. ¿Algún programa de diagnósticos?.

Francisco.




"FJTL" escribió en el mensaje
news:

Pues eso, que otro error. Supongo que está claro que es el Norton... ¿o
no?.

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {90, ffdff120, 0, 0}

Unable to load image SAVRT.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for SAVRT.SYS

*** ERROR: Module load completed but symbols could not be loaded for
SAVRT.SYS

Probably caused by : SAVRT.SYS ( SAVRT+33af4 )

Followup: MachineOwner



kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

A device driver attempting to corrupt the system has been caught. This
is

because the driver was specified in the registry as being suspect (by
the

administrator) and the kernel has enabled substantial checking of this
driver.

If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and
0xA will

be among the most commonly seen crashes.

Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.

Typically the code is 0x1001 (deadlock detected) and you can

issue a '!deadlock' KD command to get more information.

Arguments:

Arg1: 00000090, A driver switched stacks. The current stack is neither
a thread

stack nor a DPC stack. Typically the driver doing this should be

on the stack obtained from `kb' command.

Arg2: ffdff120

Arg3: 00000000

Arg4: 00000000

Debugging Details:





BUGCHECK_STR: 0xc4_90

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from e295e33a to ef519af4

TRAP_FRAME: fbeccbe8 -- (.trap fffffffffbeccbe8)

ErrCode = 00000000

eaxá09a088 ebx000000 ecxá272260 edxâ95e008 esiá24007f
edi00007f

eip=ef519af4 esp=fbeccc5c ebp000000 iopl=0 nv up ei pl nz na pe nc

cs08 ss10 ds23 es23 fs30 gs00 efl010202

SAVRT+0x33af4:

ef519af4 ?? ???

Resetting default scope

STACK_TEXT:

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

fbeccc58 e295e33a fbecccb0 e295e008 ef525392 SAVRT+0x33af4

00010202 00000000 00000000 00000000 00000000 0xe295e33a



FOLLOWUP_IP:

SAVRT+33af4

ef519af4 ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+33af4

MODULE_NAME: SAVRT

IMAGE_NAME: SAVRT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41ba0a1f

STACK_COMMAND: .trap fffffffffbeccbe8 ; kb

FAILURE_BUCKET_ID: 0xc4_90_SAVRT+33af4

BUCKET_ID: 0xc4_90_SAVRT+33af4

Followup: MachineOwner



Francisco.

Dice todo ésto:
Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Francisco>netstat -bv

Conexiones activas

Proto Dirección local Dirección remota Estado
PID
TCP fran:1033 localhost:1052 ESTABLISHED 1048
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1033 localhost:1051 ESTABLISHED 1048
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1033 localhost:1036 ESTABLISHED 1048
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1034 localhost:1038 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1034 localhost:1046 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1034 localhost:1047 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1034 localhost:1039 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1035 localhost:1048 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1036 localhost:1033 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1037 localhost:1049 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1038 localhost:1034 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1039 localhost:1034 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1046 localhost:1034 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1047 localhost:1034 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1048 localhost:1035 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
[CLI.exe]

TCP fran:1049 localhost:1037 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1051 localhost:1033 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1052 localhost:1033 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1081 news.terra.es:nntp ESTABLISHED 1640
No se puede obtener información de propiedad
TCP fran:1083 msnews.microsoft.com:nntp ESTABLISHED
1640
No se puede obtener información de propiedad
TCP fran:1077 msnews.microsoft.com:nntp TIME_WAIT 0
TCP fran:1080 news.terra.es:nntp TIME_WAIT 0
TCP fran:1082 news.x-privat.org:nntp TIME_WAIT 0

C:\Documents and Settings\Francisco>netstat -bv

Francisco

Ese "cli.exe" no es de windows y tiene muy mala pinta.. ¿de quien es?

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"FJTL" wrote in message
news:

Dice todo ésto:
Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Francisco>netstat -bv

Conexiones activas

Proto Dirección local Dirección remota Estado PID
TCP fran:1033 localhost:1052 ESTABLISHED 1048
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1033 localhost:1051 ESTABLISHED 1048
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1033 localhost:1036 ESTABLISHED 1048
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1034 localhost:1038 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1034 localhost:1046 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1034 localhost:1047 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1034 localhost:1039 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll

c:\windows\assemblyativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e08
9_0437e919\system.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1035 localhost:1048 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1036 localhost:1033 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1037 localhost:1049 ESTABLISHED 1848
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1038 localhost:1034 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1039 localhost:1034 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1046 localhost:1034 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1047 localhost:1034 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1048 localhost:1035 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
[CLI.exe]

TCP fran:1049 localhost:1037 ESTABLISHED 1048
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[CLI.exe]

TCP fran:1051 localhost:1033 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1052 localhost:1033 ESTABLISHED 1848
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\ws2_32.dll
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
C:\WINDOWS\system32\KERNEL32.dll
[cli.exe]

TCP fran:1081 news.terra.es:nntp ESTABLISHED 1640
No se puede obtener información de propiedad
TCP fran:1083 msnews.microsoft.com:nntp ESTABLISHED 1640
No se puede obtener información de propiedad
TCP fran:1077 msnews.microsoft.com:nntp TIME_WAIT
0
TCP fran:1080 news.terra.es:nntp TIME_WAIT 0
TCP fran:1082 news.x-privat.org:nntp TIME_WAIT 0

C:\Documents and Settings\Francisco>netstat -bv

Francisco

No. No es elevada como para producir casques aleatorios.

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"FJTL" wrote in message
news:%23$4$

Campo Valor
Propiedades del sensor
Tipo de sensor ITE IT8712F (ISA 290h)
Nombre de la Placa Base Asus A7V600 / A7V880 / A7V8X-X / K8N / SK8N

Temperaturas
Placa base 44 °C (111 °F)
Procesador 54 °C (129 °F)
Seagate ST340810A 41 °C (106 °F)
Seagate ST340014A 40 °C (104 °F)

Ventiladores
Procesador 3649 RPM

Valores de voltaje
Núcleo CPU 1.65 V
+3.3 V 3.30 V
+5 V 4.95 V
+12 V 13.31 V
Puesta en espera +5 V 5.03 V

Francisco.


"FJTL" escribió en el mensaje
news:

El netstat dice:

Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Francisco>netstat -bv

Conexiones activas

Proto Dirección local Dirección remota Estado PID
TCP fran:1033 localhost:1052 ESTABLISHED
1048

¿¿¿???
Francisco.

"JM Tella Llop [MVP Windows]" escribió en el
mensaje news:

Npfs.SYS
Algo relacionado con la red es como si hay restos en el stack IP de
algun componente que intenta (por ejemplo) actualizarte el software
desde remoto...

netstat -bv

(en una consola de comandos) puede que te de informacion...

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"FJTL" wrote in message
news:%

Y esta vez no es el Norton (ya está desinstalado y reiniciado).

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, f83de848, 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: f83de848, 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: f83de848 -- (.trap fffffffff83de848)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx960002 edx950001 esi000008
edi€4e6b9c

eip000000 espø3de8bc ebpc46704e iopl=0 nv up ei pl zr na po cy

cs08 ss10 ds23 es23 fs30 gs00 efl010247

00000000 ?? ???

Resetting default scope

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 00000000

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

f83de8b8 00000000 00000800 00000800 f83de904 0x0



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

FOLLOWUP_IP:

Npfs!NpCommonCreateNamedPipe+1c1

f87f8beb ebb0 jmp Npfs!NpCommonCreateNamedPipe+0x173 (f87f8b9d)

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



¿¿¿¿????

¿Se me ha cascado el ordenador?. ¿Algún programa de diagnósticos?.

Francisco.




"FJTL" escribió en el mensaje
news:

Pues eso, que otro error. Supongo que está claro que es el Norton...
¿o no?.

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {90, ffdff120, 0, 0}

Unable to load image SAVRT.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for SAVRT.SYS

*** ERROR: Module load completed but symbols could not be loaded for
SAVRT.SYS

Probably caused by : SAVRT.SYS ( SAVRT+33af4 )

Followup: MachineOwner



kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

A device driver attempting to corrupt the system has been caught. This
is

because the driver was specified in the registry as being suspect (by
the

administrator) and the kernel has enabled substantial checking of this
driver.

If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and
0xA will

be among the most commonly seen crashes.

Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.

Typically the code is 0x1001 (deadlock detected) and you can

issue a '!deadlock' KD command to get more information.

Arguments:

Arg1: 00000090, A driver switched stacks. The current stack is neither
a thread

stack nor a DPC stack. Typically the driver doing this should be

on the stack obtained from `kb' command.

Arg2: ffdff120

Arg3: 00000000

Arg4: 00000000

Debugging Details:





BUGCHECK_STR: 0xc4_90

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from e295e33a to ef519af4

TRAP_FRAME: fbeccbe8 -- (.trap fffffffffbeccbe8)

ErrCode = 00000000

eaxá09a088 ebx000000 ecxá272260 edxâ95e008 esiá24007f
edi00007f

eip=ef519af4 esp=fbeccc5c ebp000000 iopl=0 nv up ei pl nz na pe nc

cs08 ss10 ds23 es23 fs30 gs00 efl010202

SAVRT+0x33af4:

ef519af4 ?? ???

Resetting default scope

STACK_TEXT:

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

fbeccc58 e295e33a fbecccb0 e295e008 ef525392 SAVRT+0x33af4

00010202 00000000 00000000 00000000 00000000 0xe295e33a



FOLLOWUP_IP:

SAVRT+33af4

ef519af4 ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+33af4

MODULE_NAME: SAVRT

IMAGE_NAME: SAVRT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41ba0a1f

STACK_COMMAND: .trap fffffffffbeccbe8 ; kb

FAILURE_BUCKET_ID: 0xc4_90_SAVRT+33af4

BUCKET_ID: 0xc4_90_SAVRT+33af4

Followup: MachineOwner



Francisco.