Game crash detected - game is running fine

Tayra_Evenstar

Since recently, after closing the game, the launcher shows a popup message stating the latest game launch failed. The game has been running with no issues, however. How do I get rid of this notification?

nankeenheron

I've been getting those too.
1) Quit game.
2) Launcher says (WTTE) "game launch failed".

Game successfully unlaunched?

Kappachi

I have been getting this every single time I close the game, it's not crashing, everything is normal. Ever since the new beta launcher

KapiteinBoterham

Same happens about 50% of the time after exiting the game. Tried a repair, still happens once in a while. The game runs normal.

Beilin_Balreis_Colcan

Me too.

KapiteinBoterham

barney2525

I'm not one to just jump on a band wagon.

well, yes I am.

Me Too. kinda weird that it triggers after successfully launching and playing the game, and then quitting normally.

DreamyLu

Ooooooooooohhhhhhhhhhh! I came to this forum to open a discussion about just that! So I'm not the only one?

I have uninstalled and re-installed the game, it didn't change anything. Since it's not preventing me from playing, I gave up on fixing that and now it's standard for me.

madman65

Yesterday I went into Zthenganaz in Wrothgar and the second I started fighting a single Ice Wrath, the ping went up and a few seconds later the same happened to me(game crash detected). I think the module for the dungeon is not fully loaded in the server and causes problems on our end. I may be wrong because I don`t know what happens on ESO end but I have seen in chat that modules are loading in.

Doctor_Demento

Add my name to that list. Been getting it for some time now.

ZOS_Bill

For those still encountering this error in the launcher basic crash troubleshooting and see if these steps will help out.

Sarannah

This has been happening since the latest launcher update. It is a false error, as the game is working fine and a repair isn't needed. This isn't player error, but a launcher issue.

Just ignore it.

PS: Normally when the game asks you to repair, run the repair. It is just in this instance where something is wrong and the error is received.

Kappachi

ZOS_Bill wrote: »

For those still encountering this error in the launcher basic crash troubleshooting and see if these steps will help out.

The game is not actually "Crashing" it is only that the launcher says it detected a game crash when we exit the game after playing through it 100% normally and having no issue with the game itself, though it creates the dialog we must press ok to every single time. A little annoying is all but our games are not actually "crashing".

votan73

It does not happen if you run the game briefly. I guess some internal things need to happen.
But you will find records in the event viewer. And the faulting offset is always the same.

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> 
  <EventID>1000</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2024-09-01T19:35:11.4062536Z" /> 
  <EventRecordID>48166</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="11352" ThreadID="13828" /> 
  <Channel>Application</Channel> 
  <Computer>**************</Computer> 
  <Security UserID="S-1-5-21-*" /> 
</System>
<EventData>
  <Data Name="AppName">eso64.exe</Data> 
  <Data Name="AppVersion">1.0.0.1</Data> 
  <Data Name="AppTimeStamp">66bd206f</Data> 
  <Data Name="ModuleName">d3d11.dll_unloaded</Data> 
  <Data Name="ModuleVersion">10.0.22621.3672</Data> 
  <Data Name="ModuleTimeStamp">4ac6f2bf</Data> 
  <Data Name="ExceptionCode">c0000005</Data> 
  <Data Name="FaultingOffset">000000000003d6c8</Data> 
  <Data Name="ProcessId">0x1ca4</Data> 
  <Data Name="ProcessCreationTime">0x1dafca0437b444c</Data> 
  <Data Name="AppPath">C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online\game\client\eso64.exe</Data> 
  <Data Name="ModulePath">d3d11.dll</Data> 
  <Data Name="IntegratorReportId">e9a24632-6c82-479d-9d94-00221ac77a28</Data> 
  <Data Name="PackageFullName" /> 
  <Data Name="PackageRelativeAppId" /> 
</EventData>
</Event>

ZOS_Bill

If you are still having issues, please go ahead and open a support ticket with customer support.

votan73

@ZOS_Bill No worries. I reported this as a /bug versions ago. It is either ignored by those reading the feedback or it is at position 5000+ in the back log already.

The game itself is doing fine.
And if you start the game without the launcher, as I do, there is nothing to click away.

/edit: Maybe my feedback was the reason the crash detector was added to the launcher. In this case: Sorry everyone.

ZOS_Bill

@votan73

Thank you for taking the time to send in this feedback to our dev team!

Kappachi

ZOS_Bill wrote: »

@votan73

Thank you for taking the time to send in this feedback to our dev team!

I did this as well but it's been a pretty long standing issue now. Ever since the new beta client was introduced I believe, and now that it's gone into production as the main client it's an issue every time with the launcher.

Doctor_Demento

It is STILL going on and it's November now. It is still NOT fixed and they have been aware of it for many months now. Please don't send me your suggested things to try ZOS. How about YOU fix it? YOU broke it. Thanks.

ImmortalElf13

Still having this problem in December. I've tried Repair several times. Still get the pop up

Kappachi

Same, still have this issue even on fresh clean reinstalls. It's a nonstop "issue" that doesn't neccessarily affect the game but it's being closed out normally and not "Crashing".

Knaxia

I thought my friend was the only one with that issue, but it happens to him on his PC, on my laptop and on my PC. So yep, still problematic it seems!

Weird that it's only on close, I guess the game actually crashes on close from something...

Of course if you have the launcher closed when the game is running, you won't have that issue.

BloodWolfe

I suddenly started getting this about a week ago. The first time I thought nothing of it and did the repair, but it's been happening maybe every other day and I noticed it only happens when I QUIT from within the game world but not if I click quit from the character selection screen (at least so far).

ESO is a fresh install from 2 weeks ago on my PC after doing a Windows 10 reinstall from scratch. The only thing different with my PC build is that I upgraded from my old RTX 3070 to a 9070 XT. Is this issue somehow related to AMD users maybe?

Seriously ZOS, going by this thread it is a long-standing issue, how is this not fixed? As above though, I NEVER saw this when using my Nvidia 3070 and this only started recently and with my Radeon 9070 XT. That or it's ram related? I realized I never had XMP enabled before when i thought I did, so I have XMP enabled now. So possibly related to one or both of those factors?