If you can reproduce this on some machines, but not on others, all using the same code... that is very strange.
As I said, the error message does seem to suggest that something funny is going on when interacting with the device. I haven't written a lot of pure DirectX code, but from what little I've written as well as debugging through some weird issues in SlimDX once, I do remember it was a little finicky.
Can you boil this down to a small program that you can pass around, then paste the code for that? Also, if you've got hardware that you can 100% reproduce this on, it might be a good idea to grab the code for MonoGame, build it, then attach a debugger to your program and see if you can get any insights.
Sorry you're having such a strange issue... things like this are extra frustrating