Win2k3 SP2 - Minidump Help

One of our servers has began randomly getting stop errors(4 in the last 4 days, different times of day). Because it is in a remote location I cannot actually read the BSOD but I do have the minidumps. They all appear to be the same. It would appear to be a faulty driver based on the first paragraph. Is there anyway to narrow down which or is that just a friendly suggestion and could be something other than driver related. I am VERY new to looking through crash dumps so I am just looking for a little help/advice.

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

KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-zero, then this is the source of the problem.
The APC disable count is decremented each time a driver calls
KeEnterCriticalRegion, KeInitializeMutex, or FsRtlEnterFileSystem. The APC
disable count is incremented each time a driver calls KeLeaveCriticalRegion,
KeReleaseMutex, or FsRtlExitFileSystem. Since these calls should always be in
pairs, this value should be zero when a thread exits. A negative value
indicates that a driver has disabled APC calls without re-enabling them. A
positive value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the
machine -- especially unusual or non-standard drivers. Third party file
system redirectors are especially suspicious since they do not generally
receive the heavy duty testing that NTFS, FAT, RDR, etc receive.
This current IRQL should also be 0. If it is not, that a driver's
cancelation routine can cause this bugcheck by returning at an elevated
IRQL. Always attempt to note what you were doing/closing at the
time of the crash, and note all of the installed drivers at the time of
the crash. This symptom is usually a severe bug in a third party
driver.
Arguments:
Arg1: 00000000, The address of the APC found pending during exit.
Arg2: 0000ffff, The thread's APC disable count
Arg3: 00000000, The current IRQL
Arg4: 00000001

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


BUGCHECK_STR: 0x20_NULLAPC_KAPC_NEGATIVE

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8094c546 to 80827c83

STACK_TEXT:
b1f7ccac 8094c546 00000020 00000000 0000ffff nt!KeBugCheckEx+0x1b
b1f7cd44 8094c63f 00000000 00000102 00000000 nt!PspExitThread+0x64c
b1f7cd5c 8094c9dc 8b2c5ba8 00000000 00000001 nt!PspTerminateThreadByPointer+0x4b
b1f7cd70 b490791d 00000000 8b158380 00000010 nt!PsTerminateSystemThread+0x26
b1f7cd84 b4922245 00000000 8b2c5ba8 00000000 srv!SrvTerminateWorkerThread+0x57
b1f7cdac 80949b7c 01158380 00000000 00000000 srv!WorkerThread+0xa1
b1f7cddc 8088e092 b491b602 8b158380 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
srv!SrvTerminateWorkerThread+57
b490791d 5e pop esi

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: srv!SrvTerminateWorkerThread+57

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: srv

IMAGE_NAME: srv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48b558b6

FAILURE_BUCKET_ID: 0x20_NULLAPC_KAPC_NEGATIVE_srv!SrvTerminateWorkerThread+57

BUCKET_ID: 0x20_NULLAPC_KAPC_NEGATIVE_srv!SrvTerminateWorkerThread+57

Server 2k3 SP2, Runs IIS, DNS, is a DC, PC Anywhere v11, Symantec AV v9, Veritas Backup Exec v10. Any help you could lend would be helpful.

 

We've completed the steps in those articles. As soon as we finished uninstalling symatec and rebooted we got another BSOD with the same info.