Bf1 crash after enabling Origin in-game overlay [ Edited ]

[Sellis97]

Hi! After enabling Origin in-game overlay to report cheaters (why is this the only way..) my Bf1 crashed mid game. Event log is below. It's in Finnish because there isn't a way to output the log file in English. I will disable it for now and see if my game crashes again. I am not sure if this event log will help at all but atleast it's something. 

Spoiler

Lokinimi: Application
Lähde: Application Error
Päivä: 10.7.2017 2.38.58
Tapahtumatunnus:1000
Tehtäväluokka: (100)
Taso: Virhe
Avainsanat: Perinteinen
Käyttäjä: -
Tietokone: Ville
Kuvaus:
Viallisen sovelluksen nimi: bf1.exe, versio: 1.0.50.17863, aikaleima: 0x593ec790
Viallisen moduulin nimi: bf1.exe, versio: 1.0.50.17863, aikaleima: 0x593ec790
Poikkeuskoodi: 0xc0000005
Virhepoikkeama: 0x0000000004745f59
Viallisen prosessin tunnus: 0x272c
Viallisen sovelluksen käynnistysaika: 0x01d2f8fe596a73e7
Viallisen sovelluksen polku: C:\Program Files (x86)\Origin Games\Battlefield 1\bf1.exe
Viallisen moduulin polku: C:\Program Files (x86)\Origin Games\Battlefield 1\bf1.exe
Raportin tunnus: c052863b-6d32-47cb-a81a-b450d66bc108
Viallisen paketin koko nimi:
Viallisen paketin suhteellinen sovellustunnus:
Tapahtuman Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-09T23:38:58.540517400Z" />
<EventRecordID>3320</EventRecordID>
<Channel>Application</Channel>
<Computer>Ville</Computer>
<Security />
</System>
<EventData>
<Data>bf1.exe</Data>
<Data>1.0.50.17863</Data>
<Data>593ec790</Data>
<Data>bf1.exe</Data>
<Data>1.0.50.17863</Data>
<Data>593ec790</Data>
<Data>c0000005</Data>
<Data>0000000004745f59</Data>
<Data>272c</Data>
<Data>01d2f8fe596a73e7</Data>
<Data>C:\Program Files (x86)\Origin Games\Battlefield 1\bf1.exe</Data>
<Data>C:\Program Files (x86)\Origin Games\Battlefield 1\bf1.exe</Data>
<Data>c052863b-6d32-47cb-a81a-b450d66bc108</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[EA_Archi]

Hello @Sellis97 

I am really sorry for those troubles with Origin in-game. Can you try to perform Clean GPU instillation, as described in this article here and let us know the outcome? 

Cheers,

Archi

[Sellis97]

The outcome is the same.

Origin's in-game overlay has been notorious for causing crashes at-least for Battlefield series. I remember first time stumbling on this when I was playing Battlefield 4. I have been systematically disabling the overlay for all Battlefield games and all the crashes are gone for me.

I suggest a complete overhaul for Origin's in-game overlay to fix these problems. Build it from scratch and make it 100% safe to use. I know it's a big thing to ask but these problems have been around for YEARS and still they aren't fixed. The problem isn't in our hardware but in the coding of the overlay itself. 

Look at Steam's in-game ui/overlay. (shift+tab). It's perfect but only the web browser can be buggy sometimes but at-least it never crashes the whole game. I don't mean copy the whole system that they are using but the only thing I am asking is to separate the overlay from the game. If the overlay crashes, make it so that the game doesn't crash with it. Like make the overlay a separate instance from the game. 

[EA_Archi]

Hello @Sellis97 and thanks you for reporting back on this. I know how frustrating some of those issues can be. And all your constructive feedback is truly appreciated.  Maybe there is a third-party software on your PC, which prevents overlay from  working properly? Can you try to load your system, using Clean Boot and try to launch Origin again? 

Cheers,

Archi

[Sellis97]

I highly doubt that but I can try. I like to keep my PC always clean from bloatware and 3rd party software unless they are really essential like system monitoring tools or benchmarking tools. But they are never running when I play games for obvious reasons. If I enable the origin in-game logging in Troubleshooting where does it save the log file? I can try to find the root cause by using the logger.