Nudging layer with arrow keys makes part of canvas white

[peterjohnsen1905]

When I nudge a layer/image with the arrow keys, the image – or part of it – turns white. Making it impossible to see what's going on. Here was a lovely photo from a show, and all I did was hit the left arrow key for some nudging:

The image isn't erased og destroyed, it reappears if i hit Ctrl+T for free transform. I know this sounds like a computer problem rather than a program bug, but any advice would be appreciated. 
I made sure that Photoshop is allowed to use sufficient memory:

I am on Windows 10 with this these settings for graphics processor:

I've had this PC for a while and I haven't had the issue before. Our IT-dudes suggest rebooting the whole machine which I'd rather not. But it seems like the last resort – unless someone has a suggestion?
I'm on the newest verion of PS.

[Ged_Traynor]

@peterjohnsen1905 try enabling this option in preferences and restarting Photoshop to see if it helps, also do you have the latest Nvidia driver installed

[peterjohnsen1905]

@Ged_Traynor Thanks for the suggestion. Yeah the driver was updated very recently. I tried enabling 'Deactivate Native Canvas', and restarting, but it stille happens. 
Sometimes onli when using the left key, other times any direction.

[Ged_Traynor]

@peterjohnsen1905 one other thing to try, disable this option again in preferences and restart PS

[peterjohnsen1905]

@Ged_Traynor Tried it but no luck, but thanks for the tip.
It always seems to happen in files that have several artborads and many layers. Maybe it's just to much for the system, but everything shold be set up right to handle it. 

[Ged_Traynor]

@peterjohnsen1905 I've come across some other post that have reported similar issues to what you're experiencing

https://community.adobe.com/t5/photoshop-ecosystem-bugs/p-win-photoshop-shows-white-boxes-on-artboar...

https://community.adobe.com/t5/photoshop-ecosystem-discussions/artboards-not-displaying-correctly/m-...

[peterjohnsen1905]

Thanks @Ged_Traynor , seems like the exact same issue. But without a fix. Hope there's a solution somewhere.