Dia atras habia planteado el problema , donde ocasionalmente em aparecía el
siguiente aviso:
Kernel_Stack_Inpage_Error
Esta última vez pude escribir el codigo que me arrojó que fue
STOP: 0X00000077(0XC000000,0XC000000E,0X00000000,0X00CF7000)
Pués , he seguido el consejode Tella , y he atrapado el archico dump con el
volcadode la memoria acuediendo a Uds para su interpretación.
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
Symbol search path is:
SRV*c:\websymbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Aug 25 20:38:23.265 2005 (GMT-3)
System Uptime: 0 days 2:37:32.956
Loading Kernel Symbols
Loading unloaded module list
...
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 77, {c000000e, c000000e, 0, cf7000}
Probably caused by : memory_corruption (
nt!MiMakeOutswappedPageResident+37e )
Followup: MachineOwner
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first and second arguments are 0, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c000000e, status code
Arg2: c000000e, i/o status code
Arg3: 00000000, page file number
Arg4: 00cf7000, offset into page file
Debugging Details:
ERROR_CODE: (NTSTATUS) 0xc000000e - Se ha especificado un dispositivo
inexistente.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x77_c000000e
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 805257b6 to 805371aa
STACK_TEXT:
f8baecf0 805257b6 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
f8baed60 804eb438 c03d2414 c03d2414 00000001
nt!MiMakeOutswappedPageResident+0x37e
f8baed8c 804eb337 00e8a7a0 00000000 82fbeb30 nt!MmInPageKernelStack+0xf3
f8baeda4 804e830b 82e8a800 80574128 00000000 nt!KiInSwapKernelStacks+0x16
f8baedac 80574128 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
f8baeddc 804efc81 804e8294 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+37e
805257b6 cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiMakeOutswappedPageResident+37e
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+37e
BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+37e
Followup: MachineOwner
PD. Entiendo que puede ser el disco , sus conectores , pero de la revisación
, nadaaaaaa
Espero sus comentarios .
pterodactiluss@i.com.uy
Leer las respuestas