Applications calling wined3d_device_context_resolve_sub_resource() on a
deferred context would instead get this scheduled on the immediate context.
Worse, because the original call was intended for a deferred context, we'd do
this without taking the mutex required for immediate contexts, potentially
corrupting the command stream.