If you are truly running the exact same code on two different machines and one runs it and the other does not, then logically you can't say it's bad code. It's just that your bridgeport/camsoft machine doesn't like it.
Again, I have seen these issues on and off over the years. Unfortunately they don't always resolve. I've actually seen motion hardware be ultimately identified as the root cause for interpolation errors of this sort.
Try XYR arcs as a last resort. I've also seen a linear shift in coordinate system resolve this type of problem. also try changing the arc radii by a few thousands. I've seen that work also.