Infinite Loop of Errors in Fusion 8.2 build 2

I started randomly getting infinite loop errors when I recently upgraded to Fusion 8.2 build 2. I am on a Windows 10 Professional system with a 6-core Xeon processor and an Nvidia Quadro K2200 GPU. This doesn't crash the software, but it does make it unusable.

I haven't been able to identify any particular pattern that is causing this to happen, but I have noticed it most often when connecting the output of a Tracker node into the foreground of a Merge node.

I've attached an image with some of the error boxes spread out to give you an idea of what I'm seeing. Also, I'm happy to provide an error log if Fusion generates one.

I'm also getting this same kind of error, I haven't been able to pin point the root of the issue either. I have been stitching multiple DNG sequences together and its like out of know where it just freaks out and the only way i can really reset the issue is to reboot my tower. I can only close the program by using the task manager.

For all you techs out there from BM I'm using:
Fusion 8.2 build 2 lite
Dual Xeon 8 core CPU
64gb of memory
A Quadro K4000 and a Gforce 980TI
windows 10 pro.

Thanks for any help you can pass along

Yep, had the same random error popping up regularly with FStudio8 (beta and official releases). Sent error reports via reseller and was told BMD had it as high priority. Over a month later I've heard nothing.
Gone back to FS7 as FS8 was too unreliable.
BMD really need to work on these fixes faster AND communicate with their customers as to progress. I have no idea what's going on, or whether a new release has been available with a fix?

I do miss the Eyeon days when you got prompt replies from actual tech support in the company.

Weird, the only people reporting these have Quadro and 2011 CPUs. Anyone else notice this or have a counter example?

How much RAM is installed and how much is being utilized? Are you using Simultaneous Branching (Preferences/Memory)? It looks like a null pointer is being returned in code when not expected, this can happen when memory allocation fails. Are you using any non standard tools or fuses?

I also sent something to support a while ago regarding logging and product features and have heard nothing, not even a confirmation.