Forums Últimos mensajes - Powered by IBM
 
Tags Palabras claves

Siguen los problemas de cuelgues

07/06/2005 - 14:00 por FJTL | Informe spam
Ayuda Hacer una pregunta
Hace unos días puso un hilo sobre cuelgues (pantallazos azules) con mensajes
que hacían referencia a unha impresora de Macromedia FlashPaper. Como no se
solucionaban decidí formatear e instalar todo otra vez. Los problemas
seguían, asíq ue quité uno de los módulos de memoria ram (tengo dos de 512
Mb) y volví a formatear e reinstalar. Todo parecía ir bien pero hace un
momento volvió a saltar la pantalla azul y en eventos aparece este error:

Tipo de suceso: Error
Origen del suceso: System Error
Categoría del suceso: (102)
Id. suceso: 1003
Fecha: 07/06/2005
Hora: 13:57:18
Usuario: No disponible
Equipo: FRAN
Descripción:
Código de error 1000008e, parámetro 1 c000001d, parámetro 2 f811c5d5,
parámetro 3 f8950d64, parámetro 4 00000000.

Para obtener más información, vea el Centro de ayuda y soporte técnico en
http://go.microsoft.com/fwlink/events.asp.
Datos:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 31 64 2c 20 00001d,
0038: 66 38 31 31 63 35 64 35 f811c5d5
0040: 2c 20 66 38 39 35 30 64 , f8950d
0048: 36 34 2c 20 30 30 30 30 64, 0000
0050: 30 30 30 30 0000


Espero ayuda.
Gracias.
Francisco.
email Siga el debateRespuesta 14 respuestasRespuesta Tengo una respuesta

Preguntas similare

Mostrar todos los temas similares

Leer las respuestas

#11 FJTL
07/06/2005 - 19:51 | Informe spam
En el dump de hoy no sale nada. Aparece un error que dice Win32 error 193.
¿?
Francisco.

"JM Tella Llop [MVP Windows]" escribió en el mensaje
news:
Si saca un dump... saldrá directamente el culpable :-)

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.



"fermu" wrote in message
news:%
Hash: SHA1

FJTL wrote:
Probaremos a ver.
Por cierto, en la pantalla azul aparecía referenciado el archivo
hidusb.sys.
¿Quiere decir algo?.
Gracias.




Si, quiere decir bastante, que dispositivos USB tienes en el sistema?
Alguno de ellos es el culpable

Saludos
Fernando M.
Fermu's Website - http://www.fermu.com




Respuesta Responder a este mensaje
#12 JM Tella Llop [MVP Windows]
07/06/2005 - 20:01 | Informe spam
El primero, nuestro amigo Norton..el segundo un casque de lo sdriver de
red ¿todos los dirvers de tarjetas de red o wireless los tienes
certificados? y el ultimo, le faltan los simbolos... ¿estabas conectado
cuando sacasque el analisis?

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:
Bueno, pues no va la cosa.
He abierto el archivo dump y nada. no sale nada.
He abierto uno anterior (de ayer) y dice:

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {c5c19c31, 1, 80668aa4, 0}



Could not read faulting driver name

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

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

Probably caused by : hardware ( SYMEVENT+b124 )

Followup: MachineOwner



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: c5c19c31, memory referenced.

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

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

address.

Arg4: 00000000, (reserved)

Debugging Details:





Could not read faulting driver name

WRITE_ADDRESS: c5c19c31

FAULTING_IP:

nt!LZNT1FindMatchStandard+49

80668aa4 09897df88b3f or [ecx+0x3f8bf87d],ecx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

MISALIGNED_IP:

nt!LZNT1FindMatchStandard+49

80668aa4 09897df88b3f or [ecx+0x3f8bf87d],ecx

LAST_CONTROL_TRANSFER: from 80668819 to 80668aa4

STACK_TEXT:

f7c592c4 80668819 da830000 00000000 da840000
nt!LZNT1FindMatchStandard+0x49

f7c59300 80668bd1 80668a5b da830000 da831000 nt!LZNT1CompressChunk+0xae

f7c59330 806676a1 da830000 80668a5b 86376000
nt!RtlCompressBufferLZNT1+0x5b

f7c59358 f76ab031 00000002 da830000 00010000 nt!RtlCompressBuffer+0x4a

f7c59528 f769bcf6 f7c5991c 85220008 e163d0d0 Ntfs!NtfsPrepareBuffers+0xbfe

f7c59710 f769cae9 f7c5991c 85220008 e163d0d0 Ntfs!NtfsNonCachedIo+0x20e

f7c5990c f769cc97 f7c5991c 85220008 0110070a Ntfs!NtfsCommonWrite+0x1949

f7c59a80 804e37f7 861a6580 85220008 8639d918 Ntfs!NtfsFsdWrite+0xf3

f7c59a90 f773f3ca 804e8a39 00000000 f7c59b48 nt!IopfCallDriver+0x31

f7c59aa0 804e37f7 860ccc38 85220008 f7c59af8 sr!SrWrite+0xaa

f7c59ab0 b2efb124 00000000 f7c59af8 862909a8 nt!IopfCallDriver+0x31

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

f7c59b48 804ee6a6 862a770a f7c59b70 f7c59c04 SYMEVENT+0xb124

f7c59c24 804ed331 e276c5c0 e276c600 e276c600
nt!MiFlushSectionInternal+0x38b

f7c59c60 804eed68 852857c0 e276c5c0 00000170 nt!MmFlushSection+0x1b5

f7c59ce8 804ed178 00010000 00000000 00000001 nt!CcFlushCache+0x372

f7c59d2c 804e4f1d 863bfaa8 80561440 863c5da8 nt!CcWriteBehind+0xdc

f7c59d74 804e426b 863bfaa8 00000000 863c5da8 nt!CcWorkerThread+0x126

f7c59dac 8057be15 863bfaa8 00000000 00000000 nt!ExpWorkerThread+0x100

f7c59ddc 804fa4da 804e4196 00000000 00000000
nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16



FOLLOWUP_IP:

SYMEVENT+b124

b2efb124 ?? ???

SYMBOL_STACK_INDEX: b

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SYMEVENT+b124

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner





En otro también de ayer dice esto otro:



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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 84fa322a, b268d874, 0}

Probably caused by : Npfs.SYS ( Npfs!NpCreateNewNamedPipe+174 )

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: 84fa322a, The address that the exception occurred at

Arg3: b268d874, 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:

+ffffffff84fa322a

84fa322a 0000 add [eax],al

TRAP_FRAME: b268d874 -- (.trap ffffffffb268d874)

ErrCode = 00000002

eax800709a ebx000044 ecx•b50003 edx•b40002 esi0085f7
edi€4e6b9c

eip„fa322a esp²68d8e8 ebpc46704e iopl=0 nv up ei pl nz na po cy

cs08 ss10 ds23 es23 fs30 gs00 efl010207

84fa322a 0000 add [eax],al ds:0023:3800709a=??

Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 84fa322a

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

6346704e 00000000 00000000 00000000 00000000 0x84fa322a



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

FOLLOWUP_IP:

Npfs!NpCreateNewNamedPipe+174

f7b77888 4e dec esi

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Npfs!NpCreateNewNamedPipe+174

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b86

FAILURE_BUCKET_ID: 0x8E_Npfs!NpCreateNewNamedPipe+174

BUCKET_ID: 0x8E_Npfs!NpCreateNewNamedPipe+174

Followup: MachineOwner



En uno de antes de ayer dice:



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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.



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: b2bd686c, Trap Frame

Arg4: 00000000

Debugging Details:



***** Kernel symbols are WRONG. Please fix symbols to do analysis.



MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

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: b2bd686c -- (.trap ffffffffb2bd686c)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx=0a980001 edx=0a970000 esi000008
edi€4e72c4

eip000000 esp²bd68e0 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

STACK_TEXT:

b2bd68dc 00000000 00000800 00000800 b2bd6928 0x0



STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner



¡no me aclaro!

Gracias.

Francisco.




"FJTL" escribió en el mensaje
news:
No he podido contestar antes porque fui a trabajar. Acabo de llegar y me
pongo.
Respecto a los dispositivos USB tengo el ratón, la impresora (Epson 1200)
y el scanner (HP scanjet 3570c).
Estoy bajando el Debugging Tools y analizaré los archivos, a ver qué
sale.
En cuanto sepa algo lo posteo.
Gracias de nuevo a ambos.
Francisco.

"fermu" escribió en el mensaje
news:%
Hash: SHA1

JM Tella Llop [MVP Windows] wrote:
Si saca un dump... saldrá directamente el culpable :-)





Si, si de hecho se lo he aconsejado, (he referenciado tu articulo en un
post precedente), pero tampoco creo, que tanga tantos dispostivos USB
conectados al sistema, es cuestión de desconectarlos y probar
(quizás hasta sea más rapido...)
Saludos
Fernando M.
Fermu's Website - http://www.fermu.com








Respuesta Responder a este mensaje
#13 FJTL
07/06/2005 - 20:21 | Informe spam
Lo del Norton... pues lo tengo hace tiempo, pero claro, nada en esta vida es
seguro. Sé que tú no usas antivirus pero yo no me atrevo a quitarlo, aunque
si insistes... ;-))
Los drivers de red son los de XP. Vamos, que hice una instalación limpia y
la red funcionó sin más, así que no creo que sea.
Lo de los símbolos... sí estaba conectado porque tengo una conexión por
cable de esas permanentes. O sea, que al encender el ordenador ya está
conectado. De hecho la carpeta Websymbols se ha llenado de subcarpetas...
En cualquier caso, volveré a poner el módulo de memoria que había quitado;
desinstalaré el Norton, y rezaré.
Gracias de nuevo.
Francisco.



"JM Tella Llop [MVP Windows]" escribió en el mensaje
news:%
El primero, nuestro amigo Norton..el segundo un casque de lo sdriver
de red ¿todos los dirvers de tarjetas de red o wireless los tienes
certificados? y el ultimo, le faltan los simbolos... ¿estabas
conectado cuando sacasque el analisis?

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:
Bueno, pues no va la cosa.
He abierto el archivo dump y nada. no sale nada.
He abierto uno anterior (de ayer) y dice:

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {c5c19c31, 1, 80668aa4, 0}



Could not read faulting driver name

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

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

Probably caused by : hardware ( SYMEVENT+b124 )

Followup: MachineOwner



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: c5c19c31, memory referenced.

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

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

address.

Arg4: 00000000, (reserved)

Debugging Details:





Could not read faulting driver name

WRITE_ADDRESS: c5c19c31

FAULTING_IP:

nt!LZNT1FindMatchStandard+49

80668aa4 09897df88b3f or [ecx+0x3f8bf87d],ecx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

MISALIGNED_IP:

nt!LZNT1FindMatchStandard+49

80668aa4 09897df88b3f or [ecx+0x3f8bf87d],ecx

LAST_CONTROL_TRANSFER: from 80668819 to 80668aa4

STACK_TEXT:

f7c592c4 80668819 da830000 00000000 da840000
nt!LZNT1FindMatchStandard+0x49

f7c59300 80668bd1 80668a5b da830000 da831000 nt!LZNT1CompressChunk+0xae

f7c59330 806676a1 da830000 80668a5b 86376000
nt!RtlCompressBufferLZNT1+0x5b

f7c59358 f76ab031 00000002 da830000 00010000 nt!RtlCompressBuffer+0x4a

f7c59528 f769bcf6 f7c5991c 85220008 e163d0d0
Ntfs!NtfsPrepareBuffers+0xbfe

f7c59710 f769cae9 f7c5991c 85220008 e163d0d0 Ntfs!NtfsNonCachedIo+0x20e

f7c5990c f769cc97 f7c5991c 85220008 0110070a Ntfs!NtfsCommonWrite+0x1949

f7c59a80 804e37f7 861a6580 85220008 8639d918 Ntfs!NtfsFsdWrite+0xf3

f7c59a90 f773f3ca 804e8a39 00000000 f7c59b48 nt!IopfCallDriver+0x31

f7c59aa0 804e37f7 860ccc38 85220008 f7c59af8 sr!SrWrite+0xaa

f7c59ab0 b2efb124 00000000 f7c59af8 862909a8 nt!IopfCallDriver+0x31

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

f7c59b48 804ee6a6 862a770a f7c59b70 f7c59c04 SYMEVENT+0xb124

f7c59c24 804ed331 e276c5c0 e276c600 e276c600
nt!MiFlushSectionInternal+0x38b

f7c59c60 804eed68 852857c0 e276c5c0 00000170 nt!MmFlushSection+0x1b5

f7c59ce8 804ed178 00010000 00000000 00000001 nt!CcFlushCache+0x372

f7c59d2c 804e4f1d 863bfaa8 80561440 863c5da8 nt!CcWriteBehind+0xdc

f7c59d74 804e426b 863bfaa8 00000000 863c5da8 nt!CcWorkerThread+0x126

f7c59dac 8057be15 863bfaa8 00000000 00000000 nt!ExpWorkerThread+0x100

f7c59ddc 804fa4da 804e4196 00000000 00000000
nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16



FOLLOWUP_IP:

SYMEVENT+b124

b2efb124 ?? ???

SYMBOL_STACK_INDEX: b

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SYMEVENT+b124

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner





En otro también de ayer dice esto otro:



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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 84fa322a, b268d874, 0}

Probably caused by : Npfs.SYS ( Npfs!NpCreateNewNamedPipe+174 )

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: 84fa322a, The address that the exception occurred at

Arg3: b268d874, 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:

+ffffffff84fa322a

84fa322a 0000 add [eax],al

TRAP_FRAME: b268d874 -- (.trap ffffffffb268d874)

ErrCode = 00000002

eax800709a ebx000044 ecx•b50003 edx•b40002 esi0085f7
edi€4e6b9c

eip„fa322a esp²68d8e8 ebpc46704e iopl=0 nv up ei pl nz na po cy

cs08 ss10 ds23 es23 fs30 gs00 efl010207

84fa322a 0000 add [eax],al ds:0023:3800709a=??

Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 84fa322a

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

6346704e 00000000 00000000 00000000 00000000 0x84fa322a



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

FOLLOWUP_IP:

Npfs!NpCreateNewNamedPipe+174

f7b77888 4e dec esi

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Npfs!NpCreateNewNamedPipe+174

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b86

FAILURE_BUCKET_ID: 0x8E_Npfs!NpCreateNewNamedPipe+174

BUCKET_ID: 0x8E_Npfs!NpCreateNewNamedPipe+174

Followup: MachineOwner



En uno de antes de ayer dice:



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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.



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: b2bd686c, Trap Frame

Arg4: 00000000

Debugging Details:



***** Kernel symbols are WRONG. Please fix symbols to do analysis.



MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

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: b2bd686c -- (.trap ffffffffb2bd686c)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx=0a980001 edx=0a970000 esi000008
edi€4e72c4

eip000000 esp²bd68e0 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

STACK_TEXT:

b2bd68dc 00000000 00000800 00000800 b2bd6928 0x0



STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner



¡no me aclaro!

Gracias.

Francisco.




"FJTL" escribió en el mensaje
news:
No he podido contestar antes porque fui a trabajar. Acabo de llegar y me
pongo.
Respecto a los dispositivos USB tengo el ratón, la impresora (Epson
1200) y el scanner (HP scanjet 3570c).
Estoy bajando el Debugging Tools y analizaré los archivos, a ver qué
sale.
En cuanto sepa algo lo posteo.
Gracias de nuevo a ambos.
Francisco.

"fermu" escribió en el mensaje
news:%
Hash: SHA1

JM Tella Llop [MVP Windows] wrote:
Si saca un dump... saldrá directamente el culpable :-)





Si, si de hecho se lo he aconsejado, (he referenciado tu articulo en un
post precedente), pero tampoco creo, que tanga tantos dispostivos USB
conectados al sistema, es cuestión de desconectarlos y probar
(quizás hasta sea más rapido...)
Saludos
Fernando M.
Fermu's Website - http://www.fermu.com












Respuesta Responder a este mensaje
#14 JM Tella Llop [MVP Windows]
07/06/2005 - 20:27 | Informe spam
EL primer casque estaba clarisimo: antivirus (por cierto, segun estadisticas
del centro de diagnostico de Microsoft, son los antivirus los que mas
pantallas azules provocan: siempre aconsejan tener el ultimo motor de los
fabricantes)

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:
Lo del Norton... pues lo tengo hace tiempo, pero claro, nada en esta vida
es seguro. Sé que tú no usas antivirus pero yo no me atrevo a quitarlo,
aunque si insistes... ;-))
Los drivers de red son los de XP. Vamos, que hice una instalación limpia y
la red funcionó sin más, así que no creo que sea.
Lo de los símbolos... sí estaba conectado porque tengo una conexión por
cable de esas permanentes. O sea, que al encender el ordenador ya está
conectado. De hecho la carpeta Websymbols se ha llenado de subcarpetas...
En cualquier caso, volveré a poner el módulo de memoria que había quitado;
desinstalaré el Norton, y rezaré.
Gracias de nuevo.
Francisco.



"JM Tella Llop [MVP Windows]" escribió en el mensaje
news:%
El primero, nuestro amigo Norton..el segundo un casque de lo sdriver
de red ¿todos los dirvers de tarjetas de red o wireless los tienes
certificados? y el ultimo, le faltan los simbolos... ¿estabas
conectado cuando sacasque el analisis?

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:
Bueno, pues no va la cosa.
He abierto el archivo dump y nada. no sale nada.
He abierto uno anterior (de ayer) y dice:

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {c5c19c31, 1, 80668aa4, 0}



Could not read faulting driver name

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

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

Probably caused by : hardware ( SYMEVENT+b124 )

Followup: MachineOwner



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: c5c19c31, memory referenced.

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

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

address.

Arg4: 00000000, (reserved)

Debugging Details:





Could not read faulting driver name

WRITE_ADDRESS: c5c19c31

FAULTING_IP:

nt!LZNT1FindMatchStandard+49

80668aa4 09897df88b3f or [ecx+0x3f8bf87d],ecx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

MISALIGNED_IP:

nt!LZNT1FindMatchStandard+49

80668aa4 09897df88b3f or [ecx+0x3f8bf87d],ecx

LAST_CONTROL_TRANSFER: from 80668819 to 80668aa4

STACK_TEXT:

f7c592c4 80668819 da830000 00000000 da840000
nt!LZNT1FindMatchStandard+0x49

f7c59300 80668bd1 80668a5b da830000 da831000 nt!LZNT1CompressChunk+0xae

f7c59330 806676a1 da830000 80668a5b 86376000
nt!RtlCompressBufferLZNT1+0x5b

f7c59358 f76ab031 00000002 da830000 00010000 nt!RtlCompressBuffer+0x4a

f7c59528 f769bcf6 f7c5991c 85220008 e163d0d0
Ntfs!NtfsPrepareBuffers+0xbfe

f7c59710 f769cae9 f7c5991c 85220008 e163d0d0 Ntfs!NtfsNonCachedIo+0x20e

f7c5990c f769cc97 f7c5991c 85220008 0110070a Ntfs!NtfsCommonWrite+0x1949

f7c59a80 804e37f7 861a6580 85220008 8639d918 Ntfs!NtfsFsdWrite+0xf3

f7c59a90 f773f3ca 804e8a39 00000000 f7c59b48 nt!IopfCallDriver+0x31

f7c59aa0 804e37f7 860ccc38 85220008 f7c59af8 sr!SrWrite+0xaa

f7c59ab0 b2efb124 00000000 f7c59af8 862909a8 nt!IopfCallDriver+0x31

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

f7c59b48 804ee6a6 862a770a f7c59b70 f7c59c04 SYMEVENT+0xb124

f7c59c24 804ed331 e276c5c0 e276c600 e276c600
nt!MiFlushSectionInternal+0x38b

f7c59c60 804eed68 852857c0 e276c5c0 00000170 nt!MmFlushSection+0x1b5

f7c59ce8 804ed178 00010000 00000000 00000001 nt!CcFlushCache+0x372

f7c59d2c 804e4f1d 863bfaa8 80561440 863c5da8 nt!CcWriteBehind+0xdc

f7c59d74 804e426b 863bfaa8 00000000 863c5da8 nt!CcWorkerThread+0x126

f7c59dac 8057be15 863bfaa8 00000000 00000000 nt!ExpWorkerThread+0x100

f7c59ddc 804fa4da 804e4196 00000000 00000000
nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16



FOLLOWUP_IP:

SYMEVENT+b124

b2efb124 ?? ???

SYMBOL_STACK_INDEX: b

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SYMEVENT+b124

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner





En otro también de ayer dice esto otro:



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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 84fa322a, b268d874, 0}

Probably caused by : Npfs.SYS ( Npfs!NpCreateNewNamedPipe+174 )

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: 84fa322a, The address that the exception occurred at

Arg3: b268d874, 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:

+ffffffff84fa322a

84fa322a 0000 add [eax],al

TRAP_FRAME: b268d874 -- (.trap ffffffffb268d874)

ErrCode = 00000002

eax800709a ebx000044 ecx•b50003 edx•b40002 esi0085f7
edi€4e6b9c

eip„fa322a esp²68d8e8 ebpc46704e iopl=0 nv up ei pl nz na po cy

cs08 ss10 ds23 es23 fs30 gs00 efl010207

84fa322a 0000 add [eax],al ds:0023:3800709a=??

Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to 84fa322a

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:

6346704e 00000000 00000000 00000000 00000000 0x84fa322a



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

FOLLOWUP_IP:

Npfs!NpCreateNewNamedPipe+174

f7b77888 4e dec esi

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Npfs!NpCreateNewNamedPipe+174

MODULE_NAME: Npfs

IMAGE_NAME: Npfs.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b86

FAILURE_BUCKET_ID: 0x8E_Npfs!NpCreateNewNamedPipe+174

BUCKET_ID: 0x8E_Npfs!NpCreateNewNamedPipe+174

Followup: MachineOwner



En uno de antes de ayer dice:



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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.



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: b2bd686c, Trap Frame

Arg4: 00000000

Debugging Details:



***** Kernel symbols are WRONG. Please fix symbols to do analysis.



MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

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: b2bd686c -- (.trap ffffffffb2bd686c)

ErrCode = 00000000

eaxÀ00009a ebx000044 ecx=0a980001 edx=0a970000 esi000008
edi€4e72c4

eip000000 esp²bd68e0 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

STACK_TEXT:

b2bd68dc 00000000 00000800 00000800 b2bd6928 0x0



STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner



¡no me aclaro!

Gracias.

Francisco.




"FJTL" escribió en el mensaje
news:
No he podido contestar antes porque fui a trabajar. Acabo de llegar y
me pongo.
Respecto a los dispositivos USB tengo el ratón, la impresora (Epson
1200) y el scanner (HP scanjet 3570c).
Estoy bajando el Debugging Tools y analizaré los archivos, a ver qué
sale.
En cuanto sepa algo lo posteo.
Gracias de nuevo a ambos.
Francisco.

"fermu" escribió en el mensaje
news:%
Hash: SHA1

JM Tella Llop [MVP Windows] wrote:
Si saca un dump... saldrá directamente el culpable :-)





Si, si de hecho se lo he aconsejado, (he referenciado tu articulo en
un
post precedente), pero tampoco creo, que tanga tantos dispostivos USB
conectados al sistema, es cuestión de desconectarlos y probar
(quizás hasta sea más rapido...)
Saludos
Fernando M.
Fermu's Website - http://www.fermu.com
















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