Simple piece of advice, applicable whenever you get these seemingly strange errors.

Make a brand new application that only tests the wrong behaiviour. Make sure that this is from scratch and uses none of your pre-built code.

If this Unit Test fails, then you know that the problem is with either your software or hardware.

If this Unit Test passes (ie behaives like it should), you know that there is something inside your code that is causing this.

This is all the more relevant since several other users cannot reproduce your error...this leads to the natural conclusion that something in your code, software, or hardware is mucking things up. I'm pretty sure that it's not going to be hardware related and a simple reinstall would take care of the software so in my eyes all signs point to something in your coding that isn't working right.