Ok, after some additional use, I've figured out that I don't think it's FXP any more. I think it was just a coincidence that the problem occurred at the correct time to make it appear that FXP was at fault.
Now I'm trying the fix listed in this MS KB article.
297684
I'll let you know how it turns out.