Crash with KVM hardware driver

Crashes happen several times a day during copy/move operation.
Please help. Its causing serious interruption.
I'm sending minidumps to crashdumps@gpsoft.com.au.

I just found the conflicting 3rd party program, after all the days of crashes.
It is KVM hardware driver and software. (http://download.j5create.com/driver/JUC700_Wormhole_Windows_Driver/download.php)
Anyway, the KVM software works fine, while dopus crashes. Could you fix it?

I'm confused by what you're reporting here.

The crash dump did not show that Opus was copying any files at the time of the crash, unless the details are obscured by the Dropbox plugin (which we don't have source or debug symbols for, so we can't see below it in a stack trace).

This was the thread which crashed, where we can only see Windows and Dropbox code in scope:

The rest of the Opus process looked like it was idle, waiting for input. It's possible the thread that stack screenshot is from was doing a file copy and the Dropbox shell extension has installed a file copy hook which causes it to get involved. If that is the case then I would try uninstalling Dropbox to see if the problem remains.

I don't know why a KVM driver would have any interaction with Opus at all? I can't see any indication of that in the dump you sent us. Or are there two separate issues here?

These are the other non-Windows, non-Opus modules which the dump shows are loaded into the process:

If a KVM driver is crashing things, you will probably need to talk to the people who make the driver, as drivers should not have that kind of effect on user-level code unless they have a bug in them, and work at a lower level than Opus is directly involved with.

I just sent two new crash dumps to crashdumps@gpsoft.com.au
The new dumps are from the other machine connected with KVM cable, in which Dropbox is not installed. They should be more helpful than the last dump I sent in February.

Both of those look like memory heap corruptions. Unfortunately, that makes it difficult to say where the cause is.

The two crashes are in different places, where something is freeing memory, which usually means the thing crashing is just a victim of something else that went wrong.

(It's like something leaving a banana peel on the ground, and we get a snapshot of the code that trips over the peel some time later, not the code that dropped the peel.)

We can't tell from the crash dumps if the cause of the crash is in Opus or in a third party component, but these are the non-Opus and non-Windows components loaded in each of the crashes:

C:\Program Files\Common Files\microsoft shared\OFFICE14\Cultures\OFFICE.ODF
C:\Program Files\ESTsoft\ALZip\AZCTM.dll
C:\Program Files\MCT Corp\MagicLink\Driver\Utility\DMHK.DLL
C:\Program Files\MCT Corp\MagicLink\Driver\Utility\MlftUI2.dll
C:\Program Files\Microsoft Office\Office14\1042\GrooveIntlResource.dll
C:\Program Files\Microsoft Office\Office14\GROOVEEX.DLL
C:\Windows\DSCnpPolicy.dll
C:\Windows\ExtModuleManager.dll
C:\Windows\softcamp\sds\DSEDCon.dll
C:\Windows\softcamp\sds\DSSCIcon.dll
C:\Windows\softcamp\sds\DSShell2.dll
C:\Windows\softcamp\sds\DSTermpr.dll
C:\Windows\softcamp\sds\Rijndael.dll
C:\Windows\softcamp\vsd\DSInfo.dll
C:\Windows\softcamp\vsd\DSTransData.dll
C:\Windows\softcamp\vsd\swahmain.DLL
C:\Windows\softcamp\vsd\SWConnCtrl.dll
C:\Windows\softcamp\vsd\swmonapi.dll
C:\Windows\softcamp\vsd\SWOutlook.dll
C:\Windows\softcamp\vsd\SWOVIcon.dll
C:\Windows\softcamp\vsd\swsfctrl.dll
C:\Program Files\Adobe\Acrobat 11.0\Acrobat Elements\ContextMenuShim.dll
C:\Program Files\Beyond Compare 4\BCShellEx.dll
C:\Program Files\Common Files\microsoft shared\OFFICE14\Cultures\OFFICE.ODF
C:\Program Files\Common Files\Microsoft Shared\OFFICE14\msoshext.dll
C:\Program Files\EditPlus 3\eppshell.dll
C:\Program Files\ESTsoft\ALSee\ASSHLExt5004.dll
C:\Program Files\ESTsoft\ALSee\Lfcmp15u.dll
C:\Program Files\ESTsoft\ALSee\Lffax15u.dll
C:\Program Files\ESTsoft\ALSee\Lfjbg15u.dll
C:\Program Files\ESTsoft\ALSee\Lfpdf15u.dll
C:\Program Files\ESTsoft\ALSee\Lftif15u.dll
C:\Program Files\ESTsoft\ALSee\Ltclr15u.dll
C:\Program Files\ESTsoft\ALSee\Ltdis15u.dll
C:\Program Files\ESTsoft\ALSee\Ltfil15u.dll
C:\Program Files\ESTsoft\ALSee\LTIMGEFX15U.DLL
C:\Program Files\ESTsoft\ALSee\Ltimgutl15u.dll
C:\Program Files\ESTsoft\ALSee\Ltkrn15u.dll
C:\Program Files\ESTsoft\ALZip\AZCTM.dll
C:\Program Files\MCT Corp\MagicLink\Driver\Utility\DMHK.DLL
C:\Program Files\MCT Corp\MagicLink\Driver\Utility\MlftUI2.dll
C:\Program Files\Microsoft Office\Office14\1042\GrooveIntlResource.dll
C:\Program Files\Microsoft Office\Office14\GROOVEEX.DLL
C:\Program Files\Penta Security Systems\DSP\BG_CertViewer.dll
C:\Program Files\Penta Security Systems\DSP\FileUtility\bin\filemenu.dll
C:\Program Files\Penta Security Systems\DSP\pinfilter.dll
C:\Program Files\Penta Security Systems\DSP\secfold.dll
C:\Program Files\Penta Security Systems\DSP\selkey.dll
C:\Program Files\Penta Security Systems\DSP\ssa.dll
C:\Program Files\Penta Security Systems\DSP\wiper.dll
C:\Program Files\SQISoft\ssbridge4\FMContextMenu.dll
C:\Windows\DSCnpPolicy.dll
C:\Windows\dsinfo.dll
C:\Windows\dsipcag.dll
C:\Windows\DSTransData.dll
C:\Windows\ExtModuleManager.dll
C:\Windows\NEWGENCNI\EXPOINT\EPShEx.dll
C:\Windows\scbase.dll
C:\Windows\SCEventhandlerDataCtrl.dll
C:\Windows\softcamp\sdk\SC_AddIn_SW_CmdCtrl.dll
C:\Windows\softcamp\sdk\SCAI_CheckLogin.dll
C:\Windows\softcamp\sdk\SCAI_CSLnkLogUtil.dll
C:\Windows\softcamp\sdk\SCAI_CustomPrintMark.dll
C:\Windows\softcamp\sdk\SCAI_ExportDocFileWithURL.dll
C:\Windows\softcamp\sdk\SCAI_MKShortCut.dll
C:\Windows\softcamp\sdk\SCAI_OwnerChangeMsgCtrl.dll
C:\Windows\softcamp\sdk\SCAI_PKILoginUtil.dll
C:\Windows\softcamp\sdk\SCAI_SecuDrvNameapceCtrl.dll
C:\Windows\softcamp\sdk\SCAI_SWLoginErrMsgCtrl.dll
C:\Windows\softcamp\sdk\SCAI_VSDVW_ExToolbar.dll
C:\Windows\softcamp\sdk\SCAICommon.dll
C:\Windows\softcamp\sdk\SCPolicy.dll
C:\Windows\softcamp\sdk\scsa\SC_AddIn_DSOptimization.dll
C:\Windows\softcamp\sdk\scsa\SC_AddIn_KB_DSMSOAddIn.dll
C:\Windows\softcamp\sdk\scsa\SC_AutoSaveCtrl.dll
C:\Windows\softcamp\sdk\scsa\SCAI_OldVSDDiskMvSlave.dll
C:\Windows\softcamp\sdk\SCUser.dll
C:\Windows\softcamp\sds\dsbsdata.dll
C:\Windows\softcamp\sds\DSBSInfo.dll
C:\Windows\softcamp\sds\DSBSStAg.dll
C:\Windows\softcamp\sds\dscagent.dll
C:\Windows\softcamp\sds\DSCodec.dll
C:\Windows\softcamp\sds\DSComm.dll
C:\Windows\softcamp\sds\DSCommPacket.dll
C:\Windows\softcamp\sds\DSEDCommon.dll
C:\Windows\softcamp\sds\DSEDCon.dll
C:\Windows\softcamp\sds\dshdinfo.dll
C:\Windows\softcamp\sds\DSLang.dll
C:\Windows\softcamp\sds\DSSCIcon.dll
C:\Windows\softcamp\sds\DSShell.dll
C:\Windows\softcamp\sds\DSShell2.dll
C:\Windows\softcamp\sds\DSTermpr.dll
C:\Windows\softcamp\sds\dsxccode.dll
C:\Windows\softcamp\sds\DSXDCode.dll
C:\Windows\softcamp\sds\Rijndael.dll
C:\Windows\softcamp\sds\SCMsgBox.dll
C:\Windows\softcamp\sds\XecureCrypto.dll
C:\Windows\softcamp\vsd\langmgr.dll
C:\Windows\softcamp\vsd\swahmain.DLL
C:\Windows\softcamp\vsd\SWConnCtrl.dll
C:\Windows\softcamp\vsd\SWDataCtrl.dll
C:\Windows\softcamp\vsd\SWEncCtrl.dll
C:\Windows\softcamp\vsd\swmonapi.dll
C:\Windows\softcamp\vsd\SWOutlook.dll
C:\Windows\softcamp\vsd\SWOVIcon.dll
C:\Windows\softcamp\vsd\swsfctrl.dll
C:\Windows\softcamp\vsd\SWUtilCtrl.dll
C:\Windows\softcamp\vsd\VsdMenu.dll

(It's also possible that the problem was caused by a component which was no longer loaded at the time of the crash, so this list is not exclusive.)

  1. If it was just these two dumps, I would investigate whether Softcamp was involved. But I went back and checked the original dump and found it was not present, so it is most likely innocent and can be ignored.

  2. The MCT Corp / MagickLink KVM drivers are loaded into all three crash dumps, so it's possible they are involved, as you suspected above.

  3. The ESTsoft ALZip shell extension is also loaded into all three crash dumps. It might be worth a try to disable that to see if it is involved, in case we are focusing on the wrong thing.

If the crash is only happening when either of those components is in use then I think the problem is on one of those components, with one of them doing something which corrupts the memory heap. If so, that is not something that we would be able to fix on our side, other than by trying to prevent the components from being loaded. It would need to be fixed in the component that is causing the problem.

Thanks for your kind reply...