Error Message

A crash dump analysis should show similar output as the following:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffffad98780b182, The address that the exception occurred atArg3: fffffad9861729e0, Exception Record AddressArg4: fffffad9861723f0, Context Record AddressDebugging Details:------------------EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: vxio+7a182fffffad9`8780b182 f6400402        test    byte ptr [rax+4],2EXCEPTION_RECORD:  fffffad9861729e0 -- (.exr 0xfffffad9861729e0)ExceptionAddress: fffffad98780b182 (vxio+0x000000000007a182)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 0000000000000004Attempt to read from address 0000000000000004CONTEXT:  fffffad9861723f0 -- (.cxr 0xfffffad9861723f0)rax=0000000000000000 rbx=fffffadfdb799010 rcx=fffffad98780b17erdx=fffffad987791000 rsi=fffffadfdb799010 rdi=fffffadd6c153530rip=fffffad98780b182 rsp=fffffad986172c00 rbp=fffffadd6c153530 r8=fffffad9878482f4  r9=fffffad986172bf0 r10=0000000000000027r11=0000000000000015 r12=0000000000000001 r13=0000000000000006r14=fffffadd34bdd000 r15=fffffad98802d600iopl=0         nv up ei ng nz na po nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286vxio+0x7a182:fffffad9`8780b182 f6400402        test    byte ptr [rax+4],2 ds:002b:00000000`00000004=??Resetting default scopePROCESS_NAME:  SystemCURRENT_IRQL:  0ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  0000000000000004READ_ADDRESS:  0000000000000004 FOLLOWUP_IP: vxio+7a182fffffad9`8780b182 f6400402        test    byte ptr [rax+4],2BUGCHECK_STR:  0x7EDEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCELAST_CONTROL_TRANSFER:  from fffffad98780b502 to fffffad98780b182STACK_TEXT:  fffffad9`86172c00 fffffad9`8780b502 : fffffadf`db799010 00000000`00000000 fffffad9`86172cd0 00000000`00000001 : vxio+0x7a182fffffad9`86172c50 fffffad9`877c5dc8 : fffffadf`db799010 fffffadf`de1c2850 00000000`00000000 00000000`00000001 : vxio+0x7a502fffffad9`86172cb0 fffffad9`877c64b3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vxio+0x34dc8fffffad9`86172d30 fffff800`0124a972 : fffffad9`bbf65040 00000000`00000080 fffffad9`bbf65040 fffffad9`88033680 : vxio+0x354b3fffffad9`86172d70 fffff800`01020226 : fffffad9`8802b180 fffffad9`bbf65040 fffffad9`88033680 00000000`000493e0 : nt!PspSystemThreadStartup+0x3efffffad9`86172dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  vxio+7a182FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: vxioIMAGE_NAME:  vxio.sysDEBUG_FLR_IMAGE_TIMESTAMP:  4adffeaeSTACK_COMMAND:  .cxr 0xfffffad9861723f0 ; kbFAILURE_BUCKET_ID:  X64_0x7E_vxio+7a182BUCKET_ID:  X64_0x7E_vxio+7a182

Pending updates in the replicator log (SRL) which have not been written to the diskgroup are handled during RVG recovery. If the RVG recovery code, while handling such pending updates, finds an IO error on the diskgroup, then a bug check error (0x7e) will occur.

A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.

Veritas Technologies LLC currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

Applies To

Windows Server 2003 / 2008
SFW / SFW-HA 5.1 SP1 & 6.0
VVR Replication