Small update here: I've been able to repro this on a non-dev machine and can confirm it's related to garbage data in a render target texture. A short-term workaround is to open the console and enter "set motionblurintensity 0". I'll continue investigating a proper fix as I'm able.