What went wrong?
The game crashes during the loading screen quite often. sometimes 3-4 times in 1 day.
the crashes are some that ive never seen in other games… ive had some crashes where my desktop wallpaper is removed. (yes the picture is gone and only a solid color is left.) and one that logged me out of windows lol. idk how this is even possible.
Sometimes the game will load the area but the entire screen except HP bars, item labels etc are all black. if i press alt+enter to change to windowed mode the game displays again but if i return to fullscreen or change areas the game crashes again.
I went through the crash logs you provided and you are having a wide variety of issues - mostly graphical but some not:
Grass special effects are crashing on certain maps
Failed to create agent because it is not close enough to the NavMesh
Dedicated video D3D11 device creation failed (error: 0x887a0004) - the game tried to run on the software based Microsoft Basic Render Driver. WTF?
d3d11: failed to create 2D texture shader resource view
Particle system meshes will only work with exactly one (1) sub mesh
TMPro.TextMeshProUGUI errors - graphical display of text.
NullReferenceException: Object reference not set to an instance of an object. - Countless repeats of various errors causing this
nvwgf2umx.dll caused an Access Violation - this is directly related to GPU drivers
Excessive system memory usage - there are a few logs that show your system is using 90%+ memory.
I then looked at the dxdiag report:
Your CPU is running at 3.8Ghz - as this is higher than standard spec I am assuming its overclocked.
You only have 8GB ram so this could explain memory issues especially if you are trying higher game settings.
The diagnostic section of the report is blank - end of the file - considering the errors JUST LE is having and your description of the game crashing to windows/causing windows level issues, this is impossible so I am assuming the report is incomplete or was unable to show diagnostics.
You havent provided the le_graphicsmanager.ini file so I have no idea what settings you are trying to use in-game.
Based on the information you have provided:
Your machine is behaving very strangely. Normally continual errors in LE can be attributed to a single error or at least type of errors - your setup is literally having almost every error that is possible for LE to have and that is most definitely not normal.
From the logs it looks like you are using the Standalone version of LE (not steam) so I recommend you do a full game reinstall to make 100% sure that your install is not messed up. Some (not all) of the errors you have, could point to a corrupted game install.
The errors in the logs point to more than half being graphical. I.e. its likely that reducing graphical settings will alleviate some of them issues/instability. Set the game to 1080p, 60fps framerate limited (in game), all special features disabled or on their lowest settings, all quality set to Very Low. This is the most stable graphical config.
It is also recommended based on the logs crashing on GPU dlls, that you do a reinstallation of your GPU drivers - very important - do not do an upgrade, do a CLEAN install (or use something like DDU). Upgrade installs do not always resolve GPU issues caused by problem driver files.
As there are no diagnostics in the dxdiag, I recommend that you View Reliability History on your system and see what Windows is reporting as causing problems and when this happens. It may provide some indication of other things that are happening on your system that needs dealing with.
The game attempted to run using the Microsoft Software based video renderer. This is bizarre and could indicate that there is some sort of issue with your GPU drivers/hardware to the point where windows tried a different renderer for the game - this should never happen. I have had a 1060 for 6 years now and I have NEVER EVER had this kind of thing happen and i have messed around with rendering engines and drivers many times.
Your system could be running out of memory. Using higher quality settings in LE can use GBs more ram - I have tested this and on a 16GB system, using ultra settings can use up to 12GB of system memory.
LE is currently unoptimised and can behave like a benchmark or system burn in unless its appropriately restricted by settings. Your CPU is reporting as overclocked so there could be some sort of instability because of the game state and your overclock. I do not know if you are also overclocking your GPU - again, LE can max out a GPU very easily and this on its own can cause instability. Any GPU overclock (even a small one) could potentially be involved here too.
Hey, thanks for the reply. lots of great info there.
CPU overclock has been stable for years now and havent had crashes etc in other demanding games.
ill try doing a DDU + reinstall of GPU drivers. (ive only been updating it for a while)
GPU has a slight overclock aswell, i will try with just stock values.
I have completely reinstalled LE now on the standalone version.
I went through some windows error logs and found a few odd errors.
Overclock. Yeah, normally I would agree but with things like LE that are beta and are generally unoptimised, things can get tricky. LE doesnt play nice if its not restricted and can run away with things. I have no idea how the Unity Game Engine handles itself on overclocked CPUs - i.e. if its prone to issues on beta / debug code. If you are certain on your CPU then ok, but I definitely would NOT overclock the GPU.
Looking at your settings, the 90fps foreground/background is definitely going to cause problems - I have a 1060 myself and from lots of testing over the years, its unlikely to be able to sustain 90fps and still be stable (i.e. not crash or do weird things). I can run at 90fps - even 100fps, but I am almost guaranteed crashing once or twice a play session. The issue here is that if LE maxes out the GPU and then hits a busy interaction (or loads a new map) there simply isnt enough headroom for the GPU to handle what LE is asking of it. Crashes happen when changing maps, freezes happen in maps with lots of effects/particles and big fps spikes/drops occur at similar times or when there are lots of mobs or minions.
The other issue with the GPU (and prehaps the overclock) is that LE can push hard enough without limits that it can easily overheat GPUs or draw too much power - especially older ones that may no longer be running as optimally as they did years ago. This obviously adds varying levels of instability that would be hard to predict.
I would definitely reduce this to 60fps. and there is no need for the background fps to be running as high, 30fps is more than adequate.
Windows errors - nvwgf2umx.dll - this is the GPU driver dll component that I saw in one of the crash logs. Basically just windows confirming a crash to GPU driver level. UnityPlayer.dll is the Unity Game engine giving up. This one tends to happen if the game itself crashed for whatever reason - sometimes this will show up on a graphical error - all depends on when in the code the error occurred.
Were there no other Windows events? Its usually unlikely for LE to be the only error report - check for things like updates etc - its always possible that something else my be throwing an error that affects something common in Windows that LE also needed/s.
Another thing to try. Make sure you are not running any other applications while testing LE. There are various known issues of other apps causing problems… Everything from Teamview/Citrix to old versions of keyboard and mouse software. Temporarily dont run anything else, just to see if its involved in some way.
I did a DDU uninstall of my GPU drivers and installed the latest ones. (there was one from 10/12 so pretty recent.)
changed my LE graphic settings to this. le_graphicsmanager.ini (488 Bytes)
(I wanted to keep my fps at my monitor refresh rate at least 75)
did a CHKDSK and found/fixed some errors.
Reduced overclock on GPU.
Been playing for about 3 hours straight now with no crashes, and the game feels a lot smoother. loading screens don’t freeze up so much either. (before it would sometimes show the “busy” cursor when loading)
I think it was the GPU drivers causing the problem, if theres no crashes today and tomorrow I guess that was it.
I looked again for some errors in the event log and found these. sorta the same type of errors all 1000 or 1005
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Last Epoch.exe because of this error.
Program: Last Epoch.exe
File:
The error value is listed in the Additional Data section.
User Action
Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
If the file still cannot be accessed and
It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
If the problem persists, restore the file from a backup copy.
Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
It could very well have been the GPU driver - its always possible and its amazing how many times someone has changed nothing but done a clean install and problems were gone.
75 fps. thats fine. The key is keeping LE under control enough to make sure your GPU doesnt max out all the time - short bursts to 100% in busy moments is fine.
CHkdsk. ok. Might want to just double check your harddrives too.
usoclient.exe - thats part of the Windows Update. If it doesnt keep happening and Windows Updates are working fine, then I wouldnt worry.
dwm.exe - this is potentially serious and why I suggested running SFC. Its the Windows Desktop Windows Manager and is an important part of hardware accelleration and the Windows GUI. It could be that it was having issues with your GPU driver too. Keep an eye on this - its not the kind of error you want to see continually happening.
The bad_module one… if you search for 0xe0464645, it shows dwm.exe and GPU driver crashing and causing windows to freeze. Again. hopefully this is resolved with the GPU driver update you did.
One thing I would recommend - if everything is working and seem stable without any more errors in the Event viewer then I would make a System Restore point just to have a safe known point to revert to if things go west again at a future date.
So i played on and off for around 8-10 hours now and i havent gotten a single crash!
Gonna say it was the GPU driver. No more application errors in event log either.
thanks Vapourfire! <3
