We have a 2000 machine that sometimes reboots. Windbg prints the following results from the minidump. We think it's an "error with disk hardware" as indicated in the printout, but we want more information. We have several machines running with the same processor and OS that do not reboot.

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


Loading Dump File [C:\TEB\Mini092705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\winnt\system32
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e1b8
Debug session time: Tue Sep 27 06:54:08.633 2005 (GMT-4)
System Uptime: not available
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, 44f6000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+2b9 )

Followup: MachineOwner
---------

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: 044f6000, offset into page file

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'CTDHW2Kd' and 'VGA.dll' overlap

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x77_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

LAST_CONTROL_TRANSFER: from 8044045e to 80440d9e

STACK_TEXT:
f405bd50 8044045e c02ff8d8 00000019 00000001 nt!MiMakeOutswappedPageResident+0x2b9
f405bd7c 80464390 816e1c00 00000000 00000000 nt!MmInPageKernelStack+0x10e
f405bd90 80464355 00000000 00000000 00000000 nt!KiInSwapKernelStacks+0x2f
f405bda8 80455a16 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x80
f405bddc 80469bb2 804642d5 00000000 00000000 nt!PspSystemThreadStartup+0x69
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+2b9
80440d9e b102 mov cl,0x2

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+2b9

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3ee6c002

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+2b9

BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+2b9

Followup: MachineOwner
---------