Backup Exec is rebooting the server

[sk8ology]

For a while when a backup failed (I can just assume this is causing it) the server would reboot. I did something (at least I thought I did) to stop this from happening. Well it's fricken happening again. Problem is this isn't the servers only function. Since I am not the first one in and the only IT guy at a large company, people are being affected by this.

Any ideas/suggestions??? Is there any additional information I can supply to better troubleshoot?

 

[steveot]

Have you looked at the memory dumps to see why its rebooting?

Do you Symantec Antivirus installed?

If so update the symevent files

 

[AllUserNamesAreTaken]

Try turning off System Failure - Automatically Restart in the Windows Startup and Recovery Options (Right click my Computer, properties, advanced tab, startup and recovery, settings)

 

[sk8ology]

I did the following recomendations. I also got the folling log from the mem dump.

One thing I neglected to state is; I am using a Maxtor One touch III as my backup device. This seems to be the problem after reading the dump log. I re-installed the one touch app and drivers, well see what happens.

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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Sat Sep 23 09:28:51.033 2006 (GMT-5)
System Uptime: 1 days 9:51:46.781
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {80000005, 0, 80000005, 0}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!CcCreateVacbArray+20 )

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

1: 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: 80000005, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80000005, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: 80000005

FAULTING_IP:
+ffffffff80000005
80000005 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0x50

PROCESS_NAME: OneTouch.exe

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from 82e8d170 to 80000005

FAILED_INSTRUCTION_ADDRESS:
+ffffffff80000005
80000005 ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f4230bb0 82e8d170 00000000 00000000 f4230be0 0x80000005
f4230bc0 809366e6 8224c020 82268328 82e8d170 0x82e8d170
f4230be0 80936a4c 82e8d170 82e8d228 c0100080 nt!CcCreateVacbArray+0x20
f4230c18 80936f27 00000000 00000000 00009801 nt!CmpFreeDelayItem+0xac
f4230c94 80936ff8 00e60ce8 c0100080 00e60c84 nt!NtLockRegistryKey+0x8f
f4230cf0 8092ed98 00e60ce8 c0100080 00e60c84 nt!NtDeleteKey+0x8a
f4230d30 80834d3f 00e60ce8 c0100080 00e60c84 nt!HvpFindFreeCellInThisViewWindow+0x7d
f4230d64 7c82ed54 badb0d00 00e60c4c 00000000 nt!ObpTraceDepth+0x3b
f4230d68 badb0d00 00e60c4c 00000000 00000000 0x7c82ed54
f4230d6c 00e60c4c 00000000 00000000 00000000 0xbadb0d00
f4230d70 00000000 00000000 00000000 00000000 0xe60c4c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CcCreateVacbArray+20
809366e6 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!CcCreateVacbArray+20

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42435e60

FAILURE_BUCKET_ID: 0x50_CODE_AV_BAD_IP_nt!CcCreateVacbArray+20

BUCKET_ID: 0x50_CODE_AV_BAD_IP_nt!CcCreateVacbArray+20

Followup: MachineOwner