UE 5.3 Crashes in a new project wit an "EXCEPTION_ACCESS_VIOLATION" error

Unreal Courses Ask
#1

Hello,
after a breake of learning to develop i thougt of starting again. So i sat down installed the newest UE version and opened a project based on the “ToonTanksProjectSetup”, and it crashed.
Then i thought “okay, “ToonTanksProjectSetup” was build on a UE4 version” so i made a new fresh Cpp project (Added nothing besides an empty map, a simple plane and one folder (only one per crash)), and after a few seconds in the editor it crashed again. At the moment I am a bit helpless because I tried some stuff and googelt but nothing helped till now. Maybe some of you knows an solution?
Happy to hear from anyone :grinning:

My error message:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
D3D12Core
dxgi
dxgi
dxgi
dxgi
dxgi
dxgi
dxgi
UnrealEditor_D3D12RHI!FD3D12Viewport::PresentChecked() [D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Viewport.cpp:638]
UnrealEditor_D3D12RHI!FD3D12Viewport::Present() [D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Viewport.cpp:709]
UnrealEditor_D3D12RHI!FD3D12CommandContextBase::RHIEndDrawingViewport() [D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Viewport.cpp:916]
UnrealEditor_RHI!FRHICommand<FRHICommandEndDrawingViewport,FRHICommandEndDrawingViewportString2069>::ExecuteAndDestruct() [D:\build++UE5\Sync\Engine\Source\Runtime\RHI\Public\RHICommandList.h:1245]
UnrealEditor_RHI!FRHICommandListBase::Execute() [D:\build++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:461]
UnrealEditor_RHI!FRHICommandListImmediate::ExecuteAndReset'::35’::<lambda_4>::operator()() [D:\build++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:772]
UnrealEditor_RHI!TGraphTask<TFunctionGraphTaskImpl<void __cdecl(void),0> >::ExecuteTask() [D:\build++UE5\Sync\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:1265]
UnrealEditor_Core!FNamedTaskThread::ProcessTasksNamedThread() [D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:758]
UnrealEditor_Core!FNamedTaskThread::ProcessTasksUntilQuit() [D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:649]
UnrealEditor_RenderCore!FRHIThread::Run() [D:\build++UE5\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:328]
UnrealEditor_Core!FRunnableThreadWin::Run() [D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:149]

What I tested so far:

  • Repairing UE via the Epic Store → Nothing found
  • Updating GPU drivers
  • Deleting UE and re installing it → Same issue
  • Installing a different UE 5.X Version → problems with the .NET files → downloading new ones did not help
  • Starting UE as admin → Same issue
  • Removed the writing protection in the UE folder → Same issue
  • Deinstalled UE via a deinstallation tool, and cleaning the registry after wards per CC Cleaner, rebooting, reinstallation on a non SSD drive → Same issue

System:
OS: Windows 11
Processor: AMD Ryzen 7 3700X
GPU: Geforce GTX 1070
RAM: 32GB
UE: 5.3.0

What I think it could be:
It could be an hardware thing, because of the graphics card. The card it self one card underneath the minimum requirements for UE5 (GTX 1080), but it would be od because bevor I completely remade my PC(Formatted the hard drives and went from Windows 10 to 11) the Editor runned smoothly.

#2

Are you saying that you now have it working after doing that?

I suppose you could be saying it worked before you did that. Although it doesn’t sound like you had UE5 installed then anyway.

You could try UE4 latest and see what happens.

It does look like a dx12 thing between the editor and your computer. That could be other things including other random applications running in the background that interfere with it or corruption of the OS for example.

I don’t know how well a 1080 would work with the UE5 editor but that could be an issue of course. Trying a newer GPU would solve that but you don’t have one to try. You could instead research it to see if anyone else has one working there.

#3

Could be driver related. Usually when you see a direct x issue, you need to check your drivers

#4

Yeah thought so too, so I updated them. I forgot to mention that.

#5

Hi,

I suppose you could be saying it worked before you did that.

Actually yes, I know it sounds wired but bevor that I even had an working Project.

I will test you’re tip with the UE4 version in the next day’s.
And on the next wednesday I can test a RTX 3070 ti, wich I can borrow from a firend for a few days. So I will give you an update on this, after I Tested the GPU. Thank you for your inputs :grinning_face_with_smiling_eyes:

#6

Noticed the video card there. I had a 1060 and had major issues but it worked. I now have a 3060ti which is nice.

Have you tried the 5.3.1 update that was released today. Is 5.2.0 working ok?

#8

So, I tested a few things. UE 5.2 does not work, it crashes after multiple attempts with this message:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
D3D12Core
dxgi
dxgi
dxgi
dxgi
dxgi
dxgi
dxgi
UnrealEditor_D3D12RHI
UnrealEditor_D3D12RHI
UnrealEditor_D3D12RHI
UnrealEditor_RHI
UnrealEditor_RHI
UnrealEditor_RHI
UnrealEditor_RHI
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_RenderCore
UnrealEditor_Core
UnrealEditor_Core
kernel32
ntdll

So it should be also a problem with dx12.

The newest 5.3.1 has the some problems, but with a few additional graphics glitches like glimmering of UI elements.

The leatest UE4 Version runns smoothly, without any issues.

Next week when I get the test GPU I will test the UE5 again. And if this dose not work, it has to be a problem rooted deeper. Like you mentioned “QueueButton” Until then, I at least are able to use the UE4 Version. Thank you both for your suggested solutions so far :+1:

#9

So last weekend I had time to install the borrowed GPU and have been testing it with UE5 ever since. And it completely solves my problem, no more errors and no more crashes. For me a new GPU solved the problem, thank you for your help :grinning:

1 Like
#10

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

Privacy & Terms