The Level is blank besides the model, so I’m assuming it’s the model. I exported it from RC and have a 3070 GPU / AMD Ryzen 7 5800H processor, so my laptop can handle it. It was downsized in RC to 4k and 5m polygons, not even 39-40m, so not sure what is suddenly so demanding that UE5 has to crash within seconds of opening the Level.
If it’s relevant to the issue, I only get one texture and one normal map in my export, whereas others’ workflows seem to have several of each.
Hey there @jmoriarty16! Welcome to the community! The crash logs might be able to tell us what’s overflowing and where. Since your hardware doesn’t seem to be the issue, it could be drivers based, or maybe the 5 mil polys could be tripping something up. Is the mesh Nanite and are you working in DX12/DX11 or Vulkan?
It isn’t Nanite (yet), and after changing to DX11 it noticeably took longer to crash. In fact, it only crashed after loading in a Metahuman. I’m not sure whether it was just caved under the CPU demand, because that time it didn’t show a report box (but always does when it was crashing with DX12) so I’m assuming DX12 may have been the cause. I’ll follow up your response if it continues to crash indiscriminately.
The log was something like this;
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
D3D12Core
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_Core
UnrealEditor_RenderCore
UnrealEditor_Core
UnrealEditor_Core
kernel3
Hi, it is still happening despite trying DX11 and Vulcan instead. I’ve verified UE5, cleared up a ton of storage, made new levels, I literally don’t understand what else can I do. Nothing’s changed at this point so I don’t understand what’s causing the incessant crashing. I barely get a chance to change settings before the crash prevents a fix.
Could it be some external factor interfering with the import process like an automatic virus scanner in the background?
I’ve just tried that as well. Two factors of change during the time this started happening were installing AV software. So I uninstalled AVG and for Malwarebytes, I added a full exception to the UE5 folder/files. It’s still doing it. (:
The only other factor was when I first attempting to import a 3D model from RC. It got in the level and the crash happened shortly after, and has continued since. But that level and the model are now removed yet the crash continues.
We can go through a couple of things to reduce the project overhead to get it stable enough to be able to figure out what’s going on. It’s definitely looking like an environmental graphics issue in this case. So we’ll dig deeper in the environmental possibilities here.
If you’re using Game Ready drivers, swap them over to Studio drivers for more stability in UE.
Try restoring the default global settings in the Nvidia control panel, this sometimes corrects issues based on the settings forced here.
Are you using any overlays/GPU utilities or anything like Shadowplay, Rivatuner, or afterburner? They can also cause this.
I have a thread where I go through many ways to lower graphical overhead and fix a couple of GPU side issues. However, there’s a TON more possible answers littered through the post by other users.
This sometimes albeit rarely, stems from failed graphics driver installations over time. Both AMD and Nvidia offer their respective driver cleanup utilities, I usually recommend it as a last resort. After cleanup, a fresh install of the most recent drivers sometimes fixes it.
If you cannot get all the way into the project to be able to change some internals, see if you can use the -D3Ddebug argument and change the startup level to something like the built in minimal_default. This will get us a tiny bit more info.
I know I threw a ton at you there, but this is one of those issues that can be directly caused by the geometry at play but also could totally be environmental. The move to SM6 has been tumultuous.
Alright, I’ve followed everything here and I’m still getting persistent crashes. It happens without my large level being open first, if I start trying to do anything as simple as clicking stuff. Sometimes it happens sooner, sometimes later. I have a fresh installed UE5, fresh drivers, no corruption or verifying needed, global settings on, Shadowplay off, Studio Driver on, at this point it’s getting ridiculous that it still can’t handle anything for longer than 10 minutes.
Seems people on reddit are getting similar crashes with unreal regarding EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018
There are a couple of fixes (some to do with power settings, other with audio drivers). Guess it depends on hardware, but there are quite a few fixes that seem to work for people (and there are variants for ue5)
Perhaps if your hardware matches their case then you might find a solution?
If on windows do you have you power plan set to high performance and in nvidia control panel have you tried setting it to “Power management mode” = “Prefer maximum performance”
(some of my 3d aps like Maya like to crash after a while when the GPU would go to low power mode mid modelling causing problems)
This is a tough one, we’ve touched on most of the environmental issues that come up, and the nvwgf2umx error is usually purely graphical in nature. Is it still referencing the nvwgf2umx.dll for every error? (The memory location may change but that doesn’t matter since we have no frame of reference where they get assigned at runtime). There’s got to be something going on driver side if every project crashes in 5.0. Just hard to pinpoint where and why.
My fix for Ue5.1 was to install a custom installation of Nvidia Studio Drivers, and not install GForce experience, this is what worked for me. Nothing else worked except doing this for me.
Yep, same error. I’m going to try installing the drivers without GeForce Experience and see if that fixed it for me, then update.
No worries! I was going to bring info from Graeme’s post over here that night but I saw he already did so I just waited for your response. Fingers crossed!
Hi, quite remarkable that we worked out an unknown flaw there. It WAS Geforce causing the crashes. I’ve noticed now after not being on Unreal in a while that it isn’t crashing, and I have Geforce back. Was the issue identified by the team and resolved?
I’m glad it worked out for you! So the issue was indeed reported, but as of yet I don’t believe it’s known what portion of the GXP is conflicting. However reports from multiple users can help add more data to the issue and might provide insight, so feel free to submit your specs/information as well.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
