We have a Windows 2003 Enterprise SP2 server that crashed and the minidump shows the faulting process_name as vxpal.exe. I'm not a Veritas administrator or expert but I looked this up and it is a Veritas Provider Access Layer file. We're running V3.3.782 of Veritas Enterprise Administrator. Anybody have any ideas whether this is a know issue, what the root cause might be and any corrective action we could take?
Here is the dump file:
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8082d686, The address that the exception occurred at
Arg3: 808970ac, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!KiDispatchException+228
8082d686 8bbddcfdffff mov edi,dword ptr [ebp-224h]
TRAP_FRAME: 808970ac -- (.trap 0xffffffff808970ac)
ESP EDITED! New esp=8089740c
ErrCode = 00000000
eax=80897418 ebx=80897824 ecx=91de33b8 edx=00000000 esi=808977d0 edi=00000000
eip=8082d686 esp=80897120 ebp=808977b4 iopl=0 nv up ei pl nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
nt!KiDispatchException+0x228:
8082d686 8bbddcfdffff mov edi,dword ptr [ebp-224h] ss:0010:80897590=00000000
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x8E
PROCESS_NAME: vxpal.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: 808977d0 -- (.exr 0xffffffff808977d0)
ExceptionAddress: 00000000
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
LAST_CONTROL_TRANSFER: from 8088a262 to 8082d686
STACK_TEXT:
808977b4 8088a262 808977d0 00000000 80897824 nt!KiDispatchException+0x228
8089781c 8088a1fe 00000000 00000000 00000023 nt!CommonDispatchException+0x4a
80897824 00000000 00000023 00000023 047ede84 nt!KiExceptionExit+0x16e
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDispatchException+228
8082d686 8bbddcfdffff mov edi,dword ptr [ebp-224h]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710
SYMBOL_NAME: nt!KiDispatchException+228
FAILURE_BUCKET_ID: 0x8E_nt!KiDispatchException+228
BUCKET_ID: 0x8E_nt!KiDispatchException+228
Followup: MachineOwner
---------
