Usuario
Pantalla azul en windows 2003 Server.

Pregunta
-
Hola, buenos días. Uno de los servidores que tengo ha empezado a realizar reinicios automáticos y cada vez con más frecuencia. Añado el dump del último por si me podeis ayudar a averiguar la causa. (No he instalado nada de hard ni soft desde hace tiempo).
Gracias.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80866eb2, address which referenced memoryDebugging Details:
------------------***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Page 79e7c not present in the dump file. Type ".hh dbgerr004" for details
Page 79ee1 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.MODULE_NAME: nt
FAULTING_MODULE: 80800000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a90ad
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000CURRENT_IRQL: 0
FAULTING_IP:
nt!NtFreeVirtualMemory+f8d4
80866eb2 ff08 dec dword ptr [eax]DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 80866eb2 to 8088c9cb
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f5967898 80866eb2 badb0d00 00000001 00000000 nt!Kei386EoiHelper+0x28f3
f596792c 80867466 8a03e908 00000000 e2372100 nt!NtFreeVirtualMemory+0xf8d4
f5967944 8084f313 000004c0 c06d1f00 89f2f830 nt!NtFreeVirtualMemory+0xfe88
f5967978 808501e4 e2372100 00010000 00000000 nt!MmIsAddressValid+0x22fd
f59679bc 80850c35 00000000 da3e0000 c06d1f00 nt!MmIsAddressValid+0x31ce
f5967a6c 8085ea9e 00000001 da3e0000 c06d1f00 nt!MmIsAddressValid+0x3c1f
f5967af0 808592bc 00000000 da3e0000 00000000 nt!NtFreeVirtualMemory+0x74c0
f5967b2c 808b56db da3e0000 00000000 f5967c84 nt!NtFreeVirtualMemory+0x1cde
f5967bbc f719a6ce 89f32288 03620000 00010000 nt!CcFastCopyRead+0x159
f5967c14 f721fca2 89f32288 f5967c84 00010000 Ntfs+0x396ce
f5967c48 f722c8b3 00000003 00000000 f5967c7c fltmgr!FltGetIrpName+0x25a
f5967c9c 808f23b5 89f32288 f5967cd8 00010000 fltmgr!FltProcessFileLock+0x4e1
f5967d38 808897cc 00000640 00000000 00000000 nt!NtReadFile+0x2c5
f5967d64 7c82860c badb0d00 020de0bc 00000000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb64
f5967d68 badb0d00 020de0bc 00000000 00000000 0x7c82860c
f5967d6c 020de0bc 00000000 00000000 00000000 0xbadb0d00
f5967d70 00000000 00000000 00000000 00000000 0x20de0bc
STACK_COMMAND: kbFOLLOWUP_IP:
nt!NtFreeVirtualMemory+f8d4
80866eb2 ff08 dec dword ptr [eax]SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtFreeVirtualMemory+f8d4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrpamp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Todas las respuestas
-
Hola
es bueno que descargue este link http://oca.microsoft.com/en/windiag.asp para que verifique la memoria. Tambien es bueno que verifique el antivirus.
Saludos
Ramon Ant. Morillo Rodriguez MCITP: Enterprise Administrator Windows Server 2008 MCITP: Enterprise Messaging Administrator Microsoft Exchange 2007 A+ N+ S+ Dominican Republic