UE 4.15.2 Crashing on Startup

Development Platform & Builds
, , , ,
1

When I attempt to launch UE it crashes with a crash report:

When I first installed UE, I installed it on a different D:// than the OS C:// drive.

UE was working completely fine the week before. I tried uninstalling everything, VS2017/2015, UE, and any SDKs and reinstalling everything onto the C:// drive which still hasn’t worked either.

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

nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvapi64
nvapi64
GFSDK_Aftermath_Lib
GFSDK_Aftermath_Lib
UE4Editor_D3D11RHI!FD3DGPUProfiler::PushEvent() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11rhi.cpp:570]
UE4Editor_D3D11RHI!FD3D11DynamicRHI::RHIPushEvent() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\windows\d3d11rhi\private\d3d11device.cpp:251]
UE4Editor!`FEngineLoop::Tick'::`10'::EURCMacro_BeginFrame::DoTask() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\launch\private\launchengineloop.cpp:2915]
UE4Editor!TGraphTask<`FEngineLoop::Tick'::`10'::EURCMacro_BeginFrame>::ExecuteTask() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\public\async\taskgraphinterfaces.h:883]
UE4Editor_Core!FNamedTaskThread::ProcessTasksNamedThread() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\async\taskgraph.cpp:954]
UE4Editor_Core!FNamedTaskThread::ProcessTasksUntilQuit() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\async\taskgraph.cpp:701]
UE4Editor_RenderCore!RenderingThreadMain() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:325]
UE4Editor_RenderCore!FRenderingThread::Run() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:459]
UE4Editor_Core!FRunnableThreadWin::Run() [d:\build\++ue4+release-4.15+compile\sync\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]
2

Hey Mythixxx,

There is an answer you may find helpful here, as your issue sounds similar and you have the exact same callstack as the user from this thread. Essentially they had to roll back thier updated drivers, and this may help your issue too

Cheers!

3

I’m not sure if this would have solved it because I didn’t get a chance to try it, I went ahead and did a fresh install of Windows 10 and everything got fixed perfectly. I think my issue had something to do with installing things separately on two separate hard drives. Lucky for me it took me just about 20 mins to get it all up and running again.