It looks like this was a case of stack corruption, I suspect it either happens _extremely_ rarely, was connected to a driver issue, or is fixed. It may be some combination of all 3. :)
It looks like this was a case of stack corruption, I suspect it either happens _extremely_ rarely, was connected to a driver issue, or is fixed. It may be some combination of all 3. :)