Cross 1.71 Random single glitch while mixing, ruins a mix

Hey guys,
I've been encouraged by a certain beta tester to report this issue.
When I am mixing, sometimes I get a single glitch on what is a completely random track. It ruins any mix that I am in.
I can lift the needle and go back to the part that skipped, and I can reproduce it everytime.
The track itself is not flawed, in fact I can load another track, then load the one that was skipping, and it will be fine.
I am using an i7-2630QM machine, Win7 x32, Ecler EVO5 mixer. I've also had this problem when using an RME Fireface 800 and my Core2 T9300 laptop.
This bug has been going on since I started using Cross, but I figured I just needed to get a faster machine, so I did. Then I figured it was because I was running low latencies, but I have increased to 128 samples. My machine is optimized for audio, and DPC latency is very low, WiFi off, etc.
This is really frustrating because I've tried everything there is to try, and I'm convinced this is a software bug in the track loading process somewhere. Because it happens with random tracks, never the same one twice, it's not possible for me to narrow it down to certain tracks causing a problem.
I hope someone cares enough to investigate this problem, as it's driving me nuts and I have spend countless hours optimizing my setup and countless money making sure I have what should be the most solid and reliable setup.
I've been encouraged by a certain beta tester to report this issue.
When I am mixing, sometimes I get a single glitch on what is a completely random track. It ruins any mix that I am in.
I can lift the needle and go back to the part that skipped, and I can reproduce it everytime.
The track itself is not flawed, in fact I can load another track, then load the one that was skipping, and it will be fine.
I am using an i7-2630QM machine, Win7 x32, Ecler EVO5 mixer. I've also had this problem when using an RME Fireface 800 and my Core2 T9300 laptop.
This bug has been going on since I started using Cross, but I figured I just needed to get a faster machine, so I did. Then I figured it was because I was running low latencies, but I have increased to 128 samples. My machine is optimized for audio, and DPC latency is very low, WiFi off, etc.
This is really frustrating because I've tried everything there is to try, and I'm convinced this is a software bug in the track loading process somewhere. Because it happens with random tracks, never the same one twice, it's not possible for me to narrow it down to certain tracks causing a problem.
I hope someone cares enough to investigate this problem, as it's driving me nuts and I have spend countless hours optimizing my setup and countless money making sure I have what should be the most solid and reliable setup.