In our case, we discovered that code that was changing the system clock rate (SetSysClkRate()) led to the problem. Removing the call to SetSysClkRate() made the problem go away.
It seems like some of the code in WPILib must be making assumptions about the clock rate. You may want to avoid adjusting the clk rate.
