Game crash detected - game is running fine

Tayra_Evenstar · July 2

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 · July 4

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

Game successfully unlaunched?

Kappachi · July 7

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 · July 15

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

vsrs_au · July 16

Me too.

KapiteinBoterham · July 19

barney2525 · August 8

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 · August 12

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 · August 18

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 · August 19

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

ZOS_Bill · August 20

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

Sarannah · August 24

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 · September 2

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 · September 2

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 · September 3

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

votan73 · September 3

@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 · September 4

@votan73

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

Kappachi · September 4

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 · November 7

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.