Seems to have found a workaround by using the i810 driver with 915resolution - can no longer replicate the bug when doing that.
Seems to have found a workaround by using the i810 driver with 915resolution - can no longer replicate the bug when doing that.