This error will be fixed in the next release this month. This happens to certain computers but shouldn't happen anymore in the next update as I was able to track the issue.
