Last Epoch Crashing on Launch

Crash Summary:
After completing the currently available story content I proceeded to the Monolith of Fate and attempted to enter an echo. A zone loading screen appeared and after sitting there for a while the game crashed.

Solutions attempted:

  • Disabled Steam overlay
  • Last Epoch > Properties > Local Files > Verify integrity of game files
  • Updated graphics card drivers
  • Updated DirectX
  • Disabled Nvidia GeForce Experience Overlay

Curent State:
At this point the game will begin to launch, hang on the Last Epoch splash screen before login and then crash both the game and the Steam client.

My most recent Player.log:

DxDiag:

After some fiddling and searching I changed my le_graphicsmanager.ini to this:

ConfigVersion = 2
MasterQuality = VeryLow
TerrainQuality = VeryLow
ShadowQuality = VeryLow
HBAO Quality = VeryLow
SetHX = VeryLow
Reflections = VeryLow
ScreenSpaceReflections = VeryLow
GrassDensity = Off
antialiasingMode = TAA
ColorGradingIntensity = Medium
Bloom = false
vertical Sync = Off
StreamerMode = false
LimitForegroundFPS = false
MaxForegroundFPS = 60
LimitBackgroundFPS = false
MaxBackgroundFPS = 60
SelectedMonitor = 0
ScreenMode = Windowed
Resolution = 1920x1080
DetailShadows = false

which got the game to launch to the login screen. I was able to login, select a character and then on the loading screen the game crashed with the following Player.log:

Did a full uninstall and reinstall and behavior remains unchanged.

–update–

Explored Windows Event Viewer and found faults like this:

Faulting application name: Last Epoch.exe, version: 2019.4.8.30749, time stamp: 0x5f2ac944
Faulting module name: nvwgf2umx.dll, version: 27.21.14.6589, time stamp: 0x605cd9e9
Exception code: 0xc0000005
Fault offset: 0x0000000000201979
Faulting process id: 0x2888
Faulting application start time: 0x01d72a494a1dfab6
Faulting application path: B:\SteamLibrary\steamapps\common\Last Epoch\Last Epoch.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_cc5a8fceed9bb371\nvwgf2umx.dll
Report Id: e5363023-7388-4daf-8a82-4752f5bb9b52
Faulting package full name: 
Faulting package-relative application ID:

–update again–

RAM check! It’s good, no errors detected.

Clean install of graphics card driver because, hey, last time we just upgraded it, why not do a full clean install again?

Let’s validate steam files again too because we re-installed so, we haven’t done this since

…

1 file failed to validate and will be reacquired! Powerful. Let’s validate again because I don’t trust anything anymore; All files successfully validated.

Made it past the splash page, logged in, and crashed on zone load.

Tried something new: I made a new character! Success, I loaded a zone. Let’s go back and try my other character now…

No dice, he’s bricked, game crashes.

Can we re-load the new character or will that one crash now too? That one still loads fine, so I guess it’s an issue with the character itself? Not sure how to debug going forward from here. I guess I can start a new play through but I’d like to see the end-game stuff with my sentinel.

–edit–

Here’s the sentinel’s save file:

Does anyone have any ideas of what I could try next?

This is something related to the driver. Did you try a DDU?

Hey, Welcome to the Forums…

You obviously have done a bug report before… :wink:

(Also, am assuming that you have updated to the latest game patch).

As I read your posts, there are 2 issues that I can chip in on…

Firstly, the corrupted savegames: Unfortunately the games current state does mean that it has instability & performance problems… With this comes the possiblity that savegame & other files can and do get sometimes corrupted when crashes happen.

There are people that are having exactly the same savegame corruptions who have found that that particular character will always crash the game if loaded… Some that have had lots of instability issues have even gotten to the point where it corrupts everything and even new characters start ok but end up corrupted…

Two options here…
One is to backup your Last Epoch folder before/after play to have something to fall back on… Dont use Steam Cloud Save if you can help it because it will just copy the corrupted files…
Two, if everything is getting corrupted no matter what you are doing then backup and delete the last Epoch folder and get Steam to re-verify files or re-install (not sure if the verify is enough) - this should clear the corrupted files and force the game to make new ones - which should then not be corrupted…

The second main thing is about the game crashing…

Obviously if there is a corruption somewhere, this needs to be dealt with and the above suggestion of manually removing the last epoch folder before a reinstall should help do this. I dont think a reinstall of the game will remove the corrupted files on its own.

As you know, LE is in beta so there are plenty of stability issues and they seem to be graphic and sometimes audio related… @greenpowa already suggested checking the graphic driver installation by doing a full driver uninstall… bit tedious but it will ensure that the driver is correctly installed and not corrupted itself.

Your dxdiag also shows audio drivers that are not on the WHQL lists - no I normally wouldnt worry about this but as LE can cause problems with audio, I would suggest checking this…

As to the graphics… You are already running the game on the very low setting - this tends to solve most peoples problems with instability. There is only one additional change I would suggest - enable a framerate limit… LE can run away with a GPU and max it to 100% usage very easily and it seems that a framerate limit helps to prevent this… I would set it to whatever your monitor can handle (or less if you can). THis is especially important regarding the high resolution you are running.

Another question… Are you running anything else at the same time when playing LE? as @greenpowa will attest to, there are issues with things like Teamviewer/Citrix and there is a possiblity that something else running could be involved in the instability issues.

1 Like

Alright tried some more things.

First I played with my save file, by removing all of my unlockedWaypointScenes I was able to load the character and wander around the beginning of the game, I progressed through a few zones and everything seemed to be working so I started playing around with adding more waypoints. What I found was any time I attempted to load the ā€œEnd of Timeā€ or ā€œCouncil Chambersā€ zones my game would crash. I verified that this happened both on load and from traveling through the Council Chambers portal in Last Refuge Outskirts.

Based on my other logs this seemed like most likely a graphical glitch occurring in those two zones and knowing my PC’s current state is kind of wonky I decided now was a good a time as any to reset windows and get a clean slate.

With a fresh faced Windows 10 install, shiny new Steam and Last Epoch installs, and definitely the right graphics card drivers things kicked off to a great start! I booted the game up and loaded the End of Time zone successfully! Finally, I attempt to enter the Monolith of Fate and an echo and succeed! Everything seems to be going swimmingly. I finished the zone, didn’t get a key to the arena, and logged out.

Here are my various logs and diagnostics after this play session. Best I can tell there was some mysterious issue locally that is resolved now that everything is clean, shiny, and new. There are still plenty of little complaints, but nothing crashing. Not the most useful but hopefully if something pops up again I can dig into what happened last time and try to figure out similarities.

Player.log:

Character save:

DxDiag:

P.S. I did add the framerate limit, so, for what that’s worth, I’m limiting my frame rate now!

I love peoples dedication to wanting to play a beta game… :wink:

Whatever the reason for now, I am glad you could get it stable and working… I hope it stays that way… Thanks for posting the before and after…

Dont forget to make backups just in case your savegames get borked again.

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