Error 2003 Server : Error del sistema: sistema detenido

Descarga las últimas debugging tools o cambia la ruta de acceso a los
símbolos ya que no los estás cargando bien.

A parte, en lugar de usar mini-dump, configura el sistema para que haga un
dum completo (kernel) para poder sacar luego más información con las
debugging tools

Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"ARKANO" escribió en el mensaje
news:
Llevo varias semanas que el sistema me cierra la sesión al realizar
busquedas desde el explorador de ficheros, al volver a iniciar la
sesión me da el siguiente código de error:

El motivo facilitado por el usuario SERVIDOR\Administrador para el
último apagado inesperado del equipo es el siguiente: Error del
sistema: sistema detenido
Código de motivo: 0x805000f
Id. de error:
Cadena de control del error: 0x00000050 (0xfffffff0, 0x00000000,
0x808925cf, 0x00000000)
Comentario: 0x00000050 (0xfffffff0, 0x00000000, 0x808925cf,
0x00000000)

Además uno de los volumenes raid empieza a comprobar la paridad.

El fichero de errores me facilita la siguiente información:

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Administrador\Escritorio
\WER9a34.dir00\Mini040108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/
download/symbols
Executable search path is:
Map \WINDOWS\system32tkrnlpa.exe:
Image region 800:8e000 does not fit in mapping
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs)
Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Tue Apr 1 20:54:50.437 2008 (GMT+2)
System Uptime: 0 days 0:06:31.066
Map \WINDOWS\system32tkrnlpa.exe:
Image region 800:8e000 does not fit in mapping
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Loading Kernel Symbols
...
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffff0, 0, 808925cf, 0}

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

*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************


Probably caused by : ntkrnlpa.exe ( nt+925cf )

Followup: MachineOwner


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

Debugging Details:


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

*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************



MODULE_NAME: nt

FAULTING_MODULE: 80800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45ec0a19

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffffff0

FAULTING_IP:
nt+925cf
808925cf ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 8085eced to 80827c63

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
f7902bdc 8085eced 00000050 fffffff0 00000000 nt+0x27c63
f7902c54 8088c798 00000000 fffffff0 00000000 nt+0x5eced
f7902c6c 808925cf badb0d00 fffffff6 00000019 nt+0x8c798
f7902d2c 808c6dd5 fffffff6 00000000 808a46c0 nt+0x925cf
f7902d48 808c7dba e2abd3b0 e29b76b0 f7902d80 nt+0xc6dd5
f7902d58 80814841 e2abd3b0 00000000 8a3933f0 nt+0xc7dba
f7902d80 8088043d 00000000 00000000 8a3933f0 nt+0x14841
f7902dac 80949b7c 00000000 00000000 00000000 nt+0x8043d
f7902ddc 8088e062 80880352 00000001 00000000 nt+0x149b7c
00000000 00000000 00000000 00000000 00000000 nt+0x8e062


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+925cf
808925cf ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt+925cf

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


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

Debugging Details:


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

*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************



MODULE_NAME: nt

FAULTING_MODULE: 80800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45ec0a19

READ_ADDRESS: fffffff0

FAULTING_IP:
nt+925cf
808925cf ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 8085eced to 80827c63

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
f7902bdc 8085eced 00000050 fffffff0 00000000 nt+0x27c63
f7902c54 8088c798 00000000 fffffff0 00000000 nt+0x5eced
f7902c6c 808925cf badb0d00 fffffff6 00000019 nt+0x8c798
f7902d2c 808c6dd5 fffffff6 00000000 808a46c0 nt+0x925cf
f7902d48 808c7dba e2abd3b0 e29b76b0 f7902d80 nt+0xc6dd5
f7902d58 80814841 e2abd3b0 00000000 8a3933f0 nt+0xc7dba
f7902d80 8088043d 00000000 00000000 8a3933f0 nt+0x14841
f7902dac 80949b7c 00000000 00000000 00000000 nt+0x8043d
f7902ddc 8088e062 80880352 00000001 00000000 nt+0x149b7c
00000000 00000000 00000000 00000000 00000000 nt+0x8e062


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+925cf
808925cf ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt+925cf

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


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

Debugging Details:


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

*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************
*************************************************************************
***
***
***
***
*** Your debugger is not using the correct symbols
***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full type information.
***
***
***
*** Certain .pdb files (such as the public OS symbols) do not
***
*** contain the required information. Contact the group that
***
*** provided you with these symbols if you need this command to
***
*** work.
***
***
***
*** Type referenced: nt!_KPRCB
***
***
***
*************************************************************************



MODULE_NAME: nt

FAULTING_MODULE: 80800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45ec0a19

READ_ADDRESS: fffffff0

FAULTING_IP:
nt+925cf
808925cf ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 8085eced to 80827c63

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
f7902bdc 8085eced 00000050 fffffff0 00000000 nt+0x27c63
f7902c54 8088c798 00000000 fffffff0 00000000 nt+0x5eced
f7902c6c 808925cf badb0d00 fffffff6 00000019 nt+0x8c798
f7902d2c 808c6dd5 fffffff6 00000000 808a46c0 nt+0x925cf
f7902d48 808c7dba e2abd3b0 e29b76b0 f7902d80 nt+0xc6dd5
f7902d58 80814841 e2abd3b0 00000000 8a3933f0 nt+0xc7dba
f7902d80 8088043d 00000000 00000000 8a3933f0 nt+0x14841
f7902dac 80949b7c 00000000 00000000 00000000 nt+0x8043d
f7902ddc 8088e062 80880352 00000001 00000000 nt+0x149b7c
00000000 00000000 00000000 00000000 00000000 nt+0x8e062


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+925cf
808925cf ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt+925cf

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


Por mas vueltas que le doy no consigo dar con el problema.

Alguna sugerencia ????

Gracias por adelantado