Server 2003 STD SP2 Crashes at same time everyday, minidump points to SymSnap.sys

Windows Server 2003 Standard w/ SP2
Symantec Backup Exec v. 11d
/NOEXECUTE=OPTOUT is set in the boot.ini

We have a server that has started crashing every night at the same approximate time (within 20 minutes). This is about the same time that the Symantec backups kick-off too. This started after a set of Microsoft updates were installed on a Friday night, and it has crashed every night since. The mini dump that gets generated every night is virtually identical and posted below. We have performed a successful MEMTest about 4 months ago with no errors. I would prefer to find a work around to not have to reinstall Symantec Backup exec, but any help would be greatly appreciated.

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


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

Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070304-2240
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Tue Jul 29 21:16:50.995 2008 (GMT-7)
System Uptime: 0 days 23:57:46.125
Loading Kernel Symbols
................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {b69114a2, 1, f7234482, 0}

Unable to load image SymSnap.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SymSnap.sys
*** ERROR: Module load completed but symbols could not be loaded for SymSnap.sys

Could not read faulting driver name
Probably caused by : SymSnap.sys ( SymSnap+10482 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: b69114a2, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: f7234482, If non-zero, the instruction address which referenced the bad memory
      address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  b69114a2

FAULTING_IP:
SymSnap+10482
f7234482 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  dmadmin.exe

CURRENT_IRQL:  1

TRAP_FRAME:  b69102ec -- (.trap 0xffffffffb69102ec)
ErrCode = 00000002
eax=b69114a2 ebx=000000a8 ecx=e9272ca0 edx=b69105fc esi=e9272ca1 edi=b69114a2
eip=f7234482 esp=b6910360 ebp=b6910380 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
SymSnap+0x10482:
f7234482 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8085eced to 80827c63

STACK_TEXT:  
b691025c 8085eced 00000050 b69114a2 00000001 nt!KeBugCheckEx+0x1b
b69102d4 8088c798 00000001 b69114a2 00000000 nt!MmAccessFault+0xb25
b69102d4 f7234482 00000001 b69114a2 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
b691035c e9272ca0 b69105e0 f7234419 b69105fc SymSnap+0x10482
b6910380 f7234106 e5929e78 e5929ec8 e7d20758 0xe9272ca0
b691060c f7233440 e5929ec8 e7f57c74 e7f57c7c SymSnap+0x10106
b6910610 e5929ec8 e7f57c74 e7f57c7c e7f57c80 SymSnap+0xf440
b6910614 e7f57c74 e7f57c7c e7f57c80 e7d20678 0xe5929ec8
b6910618 e7f57c7c e7f57c80 e7d20678 e7f57c98 0xe7f57c74
b691061c e7f57c80 e7d20678 e7f57c98 b6910678 0xe7f57c7c
b6910620 e7d20678 e7f57c98 b6910678 00000000 0xe7f57c80
b6910624 e7f57c98 b6910678 00000000 f7233722 0xe7d20678
b6910628 b6910678 00000000 f7233722 e7d20678 0xe7f57c98
b691062c 00000000 f7233722 e7d20678 e7f57c70 0xb6910678


STACK_COMMAND:  kb

FOLLOWUP_IP:
SymSnap+10482
f7234482 ??              ???

SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SymSnap

IMAGE_NAME:  SymSnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42f3b382

SYMBOL_NAME:  SymSnap+10482

FAILURE_BUCKET_ID:  0x50_W_SymSnap+10482

BUCKET_ID:  0x50_W_SymSnap+10482

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


Start Free Trial