Without a log the only thing we can tell you is to turn on framelock
Is this what you need?
[03:35:55.550 N] Honorbuddy v2.5.11769.750 started.
[03:37:39.883 N] Logging in...
[03:37:41.098 N] T: 5247181477031336170 H: 243364633
[03:37:43.197 D] System.IO.FileLoadException: Could not load file or assembly 'RemoteASM, Version=2.5.11769.750, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'RemoteASM, Version=2.5.11769.750, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda'
at GreyMagic.ExternalProcessMemory.Init(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm)
at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits)
at Honorbuddy.MainWindow.HandleSuccess()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].