Access Violation - Media Texture

Having trouble finding an error. UE4 editor crashes on me when I run my game and execute a recent blueprint change but crash does not happen when I step through blueprint. How can I find culprit?

MachineId:2FB236494498CBDAFF7EB8BEB160B3A3
EpicAccountId:4f9c89767fa344bcb94145261e64a2bd

Access violation - code c0000005 (first/second chance not available)

“”

msvcr120
UE4Editor_MediaAssets!FMediaTextureResource::UpdateDeferredResource() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\mediaassets\private\assets\mediatextureresource.cpp:111]
UE4Editor_Engine!FDeferredUpdateResource::UpdateResources() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\engine\private\texturerendertarget.cpp:128]
UE4Editor_Renderer!RenderViewFamily_RenderThread() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\renderer\private\scenerendering.cpp:1542]
UE4Editor_Renderer!TGraphTask<FRendererModule::BeginRenderingViewFamily'::23’::EURCMacro_FDrawSceneCommand>::ExecuteTask() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\core\public\async\taskgraphinterfaces.h:779]
UE4Editor_Core!FTaskThread::ProcessTasks() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\core\private\async\taskgraph.cpp:539]
UE4Editor_Core!FTaskThread::ProcessTasksUntilQuit() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\core\private\async\taskgraph.cpp:340]
UE4Editor_RenderCore!RenderingThreadMain() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\rendercore\private\renderingthread.cpp:310]
UE4Editor_RenderCore!FRenderingThread::Run() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\rendercore\private\renderingthread.cpp:411]
UE4Editor_Core!FRunnableThreadWin::Run() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:74]

What version are you on?

Hi dsenter,

We haven’t heard back from you yet, so we’re resolving this post for tracking purposes. Please let us know if this is still an issue for you, and if so, in which version. We can continue assisting then. Thanks!