Automatic shutdown of the Server 2003

Server 2003 stops automatically without warning. There is no countdown and happens randomly. I was able to capture 3 of memory dump files, but I can't read it to understand what the problem is.

And here's one:

Microsoft (R) Windows debug 6.3.9600.17237 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [C:\Users\Evan\Downloads\Mini091014-03.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: * invalid *.
****************************************************************************
* Loading of the symbol may be unreliable without a symbol search path.           *
* Use .symfix to get the debugger to choose a symbol path.                   *
* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* with the help of the there when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack2) MP (4 procs) free x 86 compatible
Product: Server, suite: TerminalServer
Computer name:
Core = 0 x 80800000 PsLoadedModuleList = 0x808a8ee8
The debugging session: Wed Sep 10 14:57:54.514 2014 (UTC - 04:00)
System Uptime: 0 days 0:02:15.515
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* with the help of the there when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
...........
Loading user symbols
Loading unloaded module list
...

Summary of the symbol load error *.
Name of the module error
Ntoskrnl the system cannot find the specified file

You can solve most symbol related issues by turning the symbol loading diagnostics (! sym noisy) and repeating the command that caused the symbols to load.
You should also check that your symbol search path (.sympath) is correct.
WARNING: Unable to verify timestamp for hal.dll
ERROR: Module load completed but symbols can be loaded for hal.dll
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

Bugcheck 1000000A, {4ac, d0000002, 1, 80a613de}

The kernel symbols are FALSE. Correct symbols to do the analysis.

WARNING: Unable to verify timestamp for C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS
ERROR: Module load completed but symbols cannot be loaded for C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
Probably caused by: C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS (C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT + 17259)

Follow-up: MachineOwner
---------

2: kd >! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access an address pageable (or completely invalid) to a
application interrupt level (IRQL) that is too high.  It is usually
caused by drivers using a wrong address.
If a kernel debugger is available, download the stack trace.
Arguments:
Arg1: 000004ac, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000001, bit field:
bit 0: value 0 = read operation, 1 = write operation
bit 3: value 0 = not an enforcement operation, 1 = performance operation (only on chips that support this level of State)
Arg4: 80a613de, address memory

Debugging information:
------------------

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbols path and of loading symbol.

FAULTING_MODULE: 80800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 50346eff

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 808a8cf0
GetPointerFromAddress: unable to read from 808a8ce8
Unable to get nt! MmSpecialPoolStart
Unable to get nt! MmSpecialPoolEnd
Unable to get nt! MmPagedPoolEnd
Unable to get nt! MmNonPagedPoolStart
Unable to get nt! MmSizeOfNonPagedPoolInBytes
000004ac

CURRENT_IRQL: 0

FAULTING_IP:
HAL + 43de
80a613de f00fba2900 lock bts dword ptr [ecx], 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0XA

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers (dbg). 140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from 8081e23e to 80a613de

STACK_TEXT:
WARNING: Information not available stack unwind. Sequence of images may be wrong.
f4db5bcc 8081e23e 8af52e20 8955a4b8 8927efb0 hal + 0x43de
f4db5be4 808eca08 8955a4b8 895f0d88 00000000 nt + 0x1e23e
f4db5c0c 8094e1fe 8927eda8 8927eda8 8927efe8 nt + 0xeca08
f4db5c94 00000000 00000000 8927eda8 nt 8094e4dd + 0x14e1fe
f4db5cac 8094e82f 8927eda8 00000000 00000001 nt + 0x14e4dd
f4db5cd0 00000000 00000000 8a8e7628 nt f54ec259 + 0x14e82f
f4db5d40 8a8e7646 00000000 00000000 C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT + 0 e4604e58 x 17259
8088b 658 00000000 and 00000000 01d2f94c 0x8a8e7646 f4db5d54
f4db5d64 7c82845c badb0d00 01d2f93c 00000000 nt + 0x8b658
f4db5d68 badb0d00 00000000 00000000 0x7c82845c 01d2f93c
f4db5d6c 00000000 00000000 00000000 0xbadb0d00 01d2f93c
00000000 00000000 00000000 00000000 0x1d2f93c f4db5d70

STACK_COMMAND: kb

FOLLOWUP_IP:
C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT + 17259
f54ec259?              ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT + 17259

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT

NOM_IMAGE: C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Follow-up: MachineOwner
---------