3.3.1 64-bit appcrash (Windows)

This happened in the middle of a mix, after 4 hours of (on and off) live mixing. Not faulting Cross here, but I do need help in finding out which Windows module is contributing to the crash itself. I suspect 32 and 64-bit miscommunication issues in these crashes.
Software Setup:
Windows 8.1, recently updated by Windows Update
Cross 3.3.1 64-bit (MIDI, standard Reloop Terminal Mix 4 mapping)
Reloop ASIO driver v1.15, 64-bit
Hardware Setup:
Samsung Ultra i5, 12GB RAM, Sandisk 250GB SSD
Reloop Terminal Mix 4
Wireless, bluetooth disabled
Scenario:
1. Loaded Cross
2. Waited 30 minutes until set start.
3. Set goes by without any problems (no FX juggling)
4. Cross goes idle for 1 hour as guest DJ performs
5. My second set starts (no FX juggling)
6. Appcrash occurs within 5 transitions (approximately 15 minutes into the set), message is "Cross has stopped working"
7. Hurriedly played the CDJ on standby (this is my usual setup: have a CD on standby JUST IN CASE), except that one of my friends pranked and swapped the inserted CD, so I ended up playing Earth Wind and Fire's "September"...this, in the middle of a techno set. Very very funny. Someone owes me big time.
What i noticed:
1. This is not a memory leak issue like v3.2.0, as I had task manager running (as I always do), and usage was between 350 and 400MB
2. No prior warnings from the Windows event log
3. No indication of hardware or module fault after crash.
From what I know, exception code 0x0000005 with other applications points to a driver issue. The only thing I can think of would be MIDI messages being sent too many times from the device, but that would've crashed Cross early on if so.
I will be using the 32-bit version in the meantime to find out if narrow down OS and Cross 64-bit issues. I am certain that this is not a Cross issue but some gremlin working in between the OS and Cross.
Help tracking down the cause would be really appreciated.
Software Setup:
Windows 8.1, recently updated by Windows Update
Cross 3.3.1 64-bit (MIDI, standard Reloop Terminal Mix 4 mapping)
Reloop ASIO driver v1.15, 64-bit
Hardware Setup:
Samsung Ultra i5, 12GB RAM, Sandisk 250GB SSD
Reloop Terminal Mix 4
Wireless, bluetooth disabled
Scenario:
1. Loaded Cross
2. Waited 30 minutes until set start.
3. Set goes by without any problems (no FX juggling)
4. Cross goes idle for 1 hour as guest DJ performs
5. My second set starts (no FX juggling)
6. Appcrash occurs within 5 transitions (approximately 15 minutes into the set), message is "Cross has stopped working"
7. Hurriedly played the CDJ on standby (this is my usual setup: have a CD on standby JUST IN CASE), except that one of my friends pranked and swapped the inserted CD, so I ended up playing Earth Wind and Fire's "September"...this, in the middle of a techno set. Very very funny. Someone owes me big time.
What i noticed:
1. This is not a memory leak issue like v3.2.0, as I had task manager running (as I always do), and usage was between 350 and 400MB
2. No prior warnings from the Windows event log
3. No indication of hardware or module fault after crash.
From what I know, exception code 0x0000005 with other applications points to a driver issue. The only thing I can think of would be MIDI messages being sent too many times from the device, but that would've crashed Cross early on if so.
I will be using the 32-bit version in the meantime to find out if narrow down OS and Cross 64-bit issues. I am certain that this is not a Cross issue but some gremlin working in between the OS and Cross.
Help tracking down the cause would be really appreciated.