It seems one of the LM Control Software & Airspace Software combo fixed the issue. I didn't even uninstall the second installation, which wasn't working prior to one of the updates.
Though I think I may have found the events. I say 'may' but I'm relatively sure because this was on 11/24/2013 @ 1:44:25 PM then again at 1:46:24 PM. Then again at 1:48:40 PM, 1:48:59 PM, 1:50:59 PM. And then I obviously gave up. The exception code and Fault offset remain the same but the 'Faulting process id', start time, and Report Id change (obviously as these are time dependent).
Hopefully this helps to prevent this from happening again in future updates. --Mind you I say this because the software worked prior to the 1.0.9.0 update
Events:
Faulting application name: Airspace.exe, version: 1.0.9.0, time stamp: 0x521ac860
Faulting module name: Airspace.exe, version: 1.0.9.0, time stamp: 0x521ac860
Exception code: 0x80000003
Fault offset: 0x001ba920
Faulting process id: 0x2fbc
Faulting application start time: 0x01cee945325d3e31
Faulting application path: C:\Program Files (x86)\Leap Motion\Airspace\Airspace.exe
Faulting module path: C:\Program Files (x86)\Leap Motion\Airspace\Airspace.exe
Report Id: 708af19b-5538-11e3-8072-001fbc0192ef
Faulting package full name:
Faulting package-relative application ID: