Crashing on some load screens and during game

Technical Support
1

Edit: added dxdiag file
Hello,
I had a few crashes before the most current patch but now it happens at least once an hour. It most often happens on a load screen but also happens during gameplay (and even once standing in the end of time). I don’t seem to have a crashlog in …/LocalLow/EleventhHourGames/LastEpoch. I will attach the files in there and the windows Event Viewer information as well.

le_graphicsmanager.ini (482 Bytes)
Player.log (168.8 KB)
Player-prev.log (228.1 KB)
DxDiag.txt (107.3 KB)
Event viewer text:
Faulting application name: Last Epoch.exe, version: 2019.4.23.19969, time stamp: 0x60519ea2
Faulting module name: UnityPlayer.dll, version: 2019.4.23.19969, time stamp: 0x6051a069
Exception code: 0xc0000005
Fault offset: 0x0000000000dfab0e
Faulting process id: 0x398
Faulting application start time: 0x01d7a5dd2aed881d
Faulting application path: D:\Steam\steamapps\common\Last Epoch\Last Epoch.exe
Faulting module path: D:\Steam\steamapps\common\Last Epoch\UnityPlayer.dll
Report Id: 63c745f6-caa2-4bdb-918a-8ad3c9b896ec
Faulting package full name:
Faulting package-relative application ID:

I’ve tried everything I can think of

Uninstall and reinstall
DDU tool to uninstall and reinstall graphics drivers
Reduced graphical Settings

Thanks.

1 Like
2

Hey there… Welcome to the forums…

Sorry you are having hassles…

Seems like you have done the usual things and your system specs etc should not be having the known performance issues - at least not at the resolution & in-game settings you are using…

From the dxdiag diagnostic section:

  • You have two Bluescreen crashes - the dxdiag file doesnt have any information as to what the underlying cause is - please can you look at “View Reliability History” on your system and see if you can find these Bluescreens and see what the causes were - no computer should be having Bluescreens unless you know exactly why they happened and have sorted it.

  • Last Epcoh has crashed on the UnityPlayer a few times and other it seems to have the AppHang error (just timedout and didnt specifically crash). The player.log has more information that the devs might be able to work but you have already done the two things I recommend (verify the game files & GPU drivers) when seeing the UnityPlayer.dll crash.

  • There is an error with Last Epoch referring to fmodstudio.dll - this has something to do with Unity Sound and I dont think I have seen this error before… Are you running any applications that could be doing something with sound while trying to play LE? Are you streaming or recording during play? Have you installed FMOD on your machine for something else?

Assuming the above issues dont provide a solution… we have to think out of the box to figure this out or at least find something that is involved here…

Are you running any other applications while trying to play LE? ANything at all… There are known third party apps (like Teamviewer/Citrix) that mess with the Unity Game engine so anything you are running is worth investigating…

3

Hey vapourfire,

Thank you for the detailed response. About your questions:

As far as the fmodstudio.dll goes, I did a quick file search and the only place it appears to be is in the Last Epoch folder. I can’t find it anywhere else on my PC. To my knowledge I’ve never installed FMOD directly or indirectly through any other program.

As for other running programs. Just the normal lot. I don’t stream but I will often have twitch and discord open, but I’ve closed them both to ensure it isn’t somehow related to the crash. As for background programs we’ve got Steam, Aqua Computer Service (for my watercooling), MSI Afterburner, Logitech Ghub. That’s all I can think of.

Finally… the blue screens. I did not recognize them as blue screens at the time, but they both happened while I was playing the game. The screen became very artifacted, frozen, and a very repetitive sound played for a few seconds before my PC restarted. Here is what the reliability history had to say about them:

Source
Windows

Summary
Shut down unexpectedly

Date
‎9/‎6/‎2021 11:49 AM

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 403
Parameter 2: ffffe7813af5fee0
Parameter 3: 81000005031c0319
Parameter 4: ffffe780ee24ef80
OS version: 10_0_19042
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19042.2.0.0.768.101
Locale ID: 1033

Source
Windows

Summary
Shut down unexpectedly

Date
‎9/‎4/‎2021 11:32 PM

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: a
Parameter 1: ffff8e4080000080
Parameter 2: 2
Parameter 3: 0
Parameter 4: fffff803684a79b4
OS version: 10_0_19042
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19042.2.0.0.768.101
Locale ID: 1033

At the same time as one of the blue screens and more concerning because I have no idea what it is but is listed as a hardware error:

Source
Windows

Summary
Hardware error

Date
‎9/‎4/‎2021 11:32 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 124
Parameter 1: 0
Parameter 2: ffff890a20b2ca40
Parameter 3: baa00000
Parameter 4: 90150
OS version: 10_0_19042
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19042.2.0.0.768.101
Locale ID: 1033

4

Ok…

FMOD… hmm… will have to keep that in mind/on the backburner for now - as I said, I havent seen anyone else with that particular error before so I dont want to ignore it…

Other apps… Other than Aqua, I run the same ones so nothing immediately concerning there… Ghub is really crap compared to the old one, but it doesnt seem to be causing issues that I can see…

Bluescreens… was hoping the logs would have a reference to an offending dll or driver file - that would give some indication of where to start looking…

The LiveKernel 124 even that you found is helpful as it provides something to work from… Unfortunately its usually hardware related… I am looking at it independently of LE - i.e. trying to find out what the LiveKernel event 124 could mean…

After consolidating the hundreds of google results, the issues could be anything from:

  1. Overheating/thermals on both the CPU or GPU or other components.
  2. CPU or GPU Failure - apparenlty 124 usually refers to the CPU - not always but more often than not
  3. Memory issues - incorrectly configured XMP or faulty memory
  4. Hardware driver issues- e.g. GPU driver problesm, any device drivers on your machine that is not installed or incorrect - even something like USB.
  5. BIOS updates
  6. Overclocking settings
  7. Incorrect harddrive configurations in BIOS
  8. …

Basically it seems that 124 is a hardware related error of some kind and the only way to establish exactly what hardware is involved seems to be through trial and error & monitoring.

Your description of the artifacts etc, seems to indicate to me that its likely the GPU first crashing… but I cannot be sure…

I would suggest:

  • Physically check your machine - make sure things like fans are running properly, cables are properly seated and there is no obvious issue like something touching a motherboard component it shouldnt, things are clean etc…

  • Check that your machine bios is correctly setup for your memory / make sure you dont have any overclocks running

  • Make sure your bios is up to date, and all your devices drivers etc are up to date and correctly installed in device manager.

  • Run some independent stress tests on your machine while monitoring your system components (clocks/thermals/usage etc) and see if these errors happen without running LE… Running things like Prime95 (CPU test)/Furmark (GPU test) or other benchmarks (Heaven, Cinebench etc) in a looped fashion should highlight any hardware based issues - in fact, they should do so much easier than LE ever could.

LE does have performance related issues and does stress systems unneccessarily but by using the dedicated stress tests, you take it out of the equation as a possible cause - yes, it is still possible that LE has a bug that your systme just doesnt like but considering the level of errors you are getting its best to try and test without LE involved.

5

So I did a BIOS update and reinstalled all my drivers. I also did some googling as you did on the 124 error. I’ve tested my system quite a bit over the past months for stability. A few months ago I was getting crashes in warzone and what seemed to be the issue was my RAM. When I ran the XMP profile at 3600 I’d get problem but if I lowered it to 3200 I’d seem to be okay. I tested my memory heavily and it passed all tests, so I thought perhaps it was the memory controller on my 3700x. A few weeks ago I upgraded to the 5800x and set my XMP profile back to it’s default of 3600.

Today I lowered it back to 3200 and I haven’t crashed at all. I think it must be related to the RAM but I’m at a loss because it passes all tests. It might be time to try some new sticks. I’m still not convinced it’s the RAM… but if I need to run it at 3200 then well I’ll just do that for now.

Thank you for your help Vapourfire! Have a good one.

6

Ok then… glad you managed to find some stability again…

RAM overclocking can be tricky as it involves a lot of different factors that need to be just right…

The 5800X ram spec from AMD indicates a maximum of 3200Mhz DDR4 - but obviously this can and is overclocked through simple BIOS XMP configs provided the RAM & Motherboard is capable of handling it…

Your memory passing all tests just means its working at stock (assuming you got 3200 - if its less then its already overclocked and is probably doing quite well considering) - it all depends on the silicon lottery as to how well this memory can be overclocked and if the motherboard auto OC (like your MSI Tomahawks A-XMP OC MODE) can correctly match the voltage & clock speeds your RAM needs to handle an overclock…

You might find that you can find a stable config through manual memory overclocking but honestly it could probably be that your memory isnt capable of any additional overclock - that is very possible… It may even be that your 5800x itself is much more picky with OC settings when it comes to RAM speeds and it might not like overclocked memory.

To be honest, I have never really cared for OC settings - I prefer stability & longevity over performance… Most of the time I find that the added few fps or quicker unzip time just isnt relevant… If I need something faster, I buy something that is faster at stock… Some people have the exact polar opposite idea and have to redline everything to get the most bang for their buck but not me… I’d rather know my system will run an extra few years without blue smoke coming out the back one day… :wink:

1 Like
7

I normally just overclock for fun. 99% of the rest of the time I run an undervolt on both my CPU and GPU to keep temperatures down. (I live in the desert). Though I’ve always had XMP enabled on all my PC’s before, I’ve manually dropped the frequency and in testing I can’t even find a difference between 3200 and 3600. So at least for now, crisis averted.

1 Like
8

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