My server started just started to give me the BSOD. I checked the dump file and got this


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


Loading Dump File [f:\mini030805-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is: d:\i386
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Tue Mar 8 16:07:24.375 2005 (GMT-5)
System Uptime: 0 days 0:00:45.093
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................
Loading unloaded module list
...
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c02017c0, c00000a3, 805f07b4, 713860}

Probably caused by : memory_corruption ( nt!MiAddRangeToCrashDump+6d )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c02017c0, lock type that was held (value 1,2,3, or PTE address)
Arg2: c00000a3, error status (normally i/o status code)
Arg3: 805f07b4, current process (virtual address for lock type 3, or PTE)
Arg4: 00713860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc00000a3 - {Drive Not Ready} The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed.

BUGCHECK_STR: 0x7a_c00000a3

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 8052caaf to 80543ac9

STACK_TEXT:
fef1bbcc 8052caaf 0000007a c02017c0 c00000a3 nt!MiAddRangeToCrashDump+0x6d
fef1bbf4 805092ac 8100a9c8 c02017c0 805f07b4 nt!MmInSwapProcess+0x269
fef1bc78 804f4c21 00000001 805f07b4 c02017c0 nt!NtYieldExecution+0xe0
fef1bcd4 804e2dfc 00000000 805f07b4 00000000 nt!CcPinFileData+0x22e
fef1bcec 00000000 00000000 19bde3b8 fef1bdcc nt!strncpy+0x88


FOLLOWUP_IP:
nt!MiAddRangeToCrashDump+6d
80543ac9 5d pop ebp

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiAddRangeToCrashDump+6d

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 40b53739

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7a_c00000a3_nt!MiAddRangeToCrashDump+6d

BUCKET_ID: 0x7a_c00000a3_nt!MiAddRangeToCrashDump+6d

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

IS this a memory error or a hard drive error. THanks so very much for any help you can provide.

If I'm not mistaken, its a RAM issue. Check the event log for errors that might point you in the right direction.