I am trying to get a handle on an odd issue I am experiencing with our DFS folders and Symantec AV.
If we copy from \\domain\dfs\share1 to \\domain\dfs\share2 everything works without issue. If however we move data between the same folders the server instantly reboots.
The following are two excerts from mini dumps we recovered after the server reboots
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(c8c.1258): Access violation - code c0000005 (first/second chance not available)
eax=00000001 ebx=00000000 ecx=01bf5648 edx=69583548 esi=01bd72b0 edi=80090006
eip=65930a03 esp=06ddf7b8 ebp=06ddff40 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010206
Unable to load image D:\program files\sav\SymProtectStorag
e.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SymProtectStorage.dll
*** ERROR: Module load completed but symbols could not be loaded for SymProtectStorage.dll
*** WARNING: Unable to verify timestamp for mssmbios.sys
Unable to load image fltmgr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltmgr.sys
Unable to load image \??\C:\Program Files\Symantec\SYMEVENT.SY
S, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
Unable to load image Mup.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Mup.sys
Probably caused by : SYMEVENT.SYS ( SYMEVENT+7652 )
Occasionally after the reboot we received a stop code 0x00000035 which a quick google points us at Microsoft KB http://support.microsoft.com/kb/906866
Having made the changes and reboot we still get the same error messages. We tried to disable all Symantec services however this still caused the same error.
Any advice anyone has on this would be greatly appreciated as its causing us a number of issues when we are working on the network.
Posting this to the Symantec forums was useless and I really need to try and get some understanding as to why this happns on my network.