Re: Game keeps crashing when playing Hero Showdown
@SteveZee I did change the DirectX 12 settings in the settings menu to disabled.
Forum Discussion
25 Replies
- Did that fix the problem at all? Changing DX12 to disabled i mean.
@SteveZee I have tried everything to solve this bug, but nothing helped. The weird thing was that my progression in battle scenarios was completely erased after the fifth crash. I do not know if you experience the same bug, but the game can crash in two ways. The first way is that your screen firstly starts to stutter then freezes and eventually you cannot do anything on your PC (even mouse movement is disabled). To solve this you have to restart your PC by holding the on/off-button. The second way my game crashes is by a forced closure of the game, so it simply turns off the application.
- Another option is to try and revert your GPU drivers back 2 or 3 versions. Maybe further. The other possibilities might be other applications running. You could try a clean boot. Make sure your motherboard drivers are up to date, etc etc.
Beyond that, what is the error specifically? Do you get this error message every time? And is it the same? - Nevermind i was able to DL the picture and view it.
It says "big picture mode must exit". I am not aware that Origin had a big picture mode at all. But STEAM does. Are you running BPM in steam at the same time? @SteveZee The error message in one of my screenshots some messages ago was only displayed one time and only at the first time my game crashed. The other times my game crashed I received no error messages, this makes it very hard to find the cause of this bug. The game now simply crashes without any error message.
- There are log files you can check
they are in
C:\ProgramData\Origin\Logs\
You can check client_log or any of the others for anything suspicious if it crashes again. Maybe it will clue you into the problem.
Beyond that, reverting to an older driver is a good option. - Is steam running w/ origins? If so, try exiting steam.
- You may have to have in game logging enabled. Goto origin, application settings,diagnostics and click in game logging. Then recreate the "crash" and upload the file.
- You can also check the event log. Recreate the error, and note the date and time of the error. Type event viewer in the windows search bar. Then open windows logs, then application logs. Scroll until you find the time frame of the error, and look for application crashes, errors, related to direct X. Note possible events surrounding that error. Like 30 seconds before it. It can flag a possible issue.
- Its along shot, but also check the IGOProxy_DX12 and IGOProxy64_DX12
in the log folder to make sure there are no errors or warnings listed. Only info and debug messages. - Yeah i hear ya. I just thought of something else. Are you running the game in windowed mode? If you are make sure the video settings are full screen mode and see if that helps.
@SteveZee Now I see that a specific error message has appeared several times since last week and this message showed up even more today and yesterday (the days I have been working to fix this). This is the error message:
Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Other error messages I received in this period of time:
1. MDM Session: OMA-DM message failed to be sent. Result: (Unknown Win32 Error code: 0x82ac0194).
2. A TCG Command has returned an error.
Desc: AuthenticateSession
Param1: 0x1
Param2: 0x60000001C
Param3: 0x900000006
Param4: 0x0
Status: 0x12
3. De vorige afsluiting van het systeem om 18:38:16 op 21-5-2018 is onverwacht gebeurd. (This one is in dutch, paste it in google and you will find the error message)@SteveZee I have noticed that this error message pops up multiple times when launching Star Wars Battlefront II:
Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.- I get tons of dcom errors. THose are fairly normal. Most of them are unrelated and permission oriented.
the MDM session is probably unrelated.
The TCG command seems to be associated with bit locker.
And the third one is about a previous shutdown that was unexpected. Have you ever gotten a bluescreen of death with this? If not, its probably not an issue.
Again, check the system TAB under event viewer to see about critical faults somewhere. If they are happening, then the kernel is faulting, but not critically and its probably DX that's crashing. So you, most likely, have a graphics issue. Its either the card thats failing, or you have a driver problem.
You could try to underclock your card and see if the problem goes away. If it does, then its probably overheating, or there is some kind of stress that makes it malfunction. And....from your client_log file i read this:
400 [2018-05-21 17:03:08.719] Event Origin::Services::SelfUpdateService::onCheckForUpdateComplete 9764 [Origin Autoupdater] No update available.
401 [2018-05-21 17:04:45.010] Event SetPresenceMessageHandler::OnMessage 6452 Jingle setting activity to STAR WARS™ Battlefront™ II;Origin.OFR.50.0002027;JOINABLE;;;1035052;;;Playing Hero Showdown on Naboo
0 [2018-05-21 17:31:57.475] Event Origin::Services::Logger::Init 3344 Logfile: C:\ProgramData\Origin/Logs/Client_Log
1 [2018-05-21 17:31:57.475] Event Origin::Services::Logger::Init 3344 Local time: ma mei 21 19:31:So the transition from "playing hero showdown on naboo" to Logfile: C:\Pro..... means that origins is rebooting several key services and files as it reloads again. Everytime you boot origins up, it starts from 0 in the log, then does basically the same steps everytime. My file is pretty much the same.
Now im not sure you made sure to check "in game logging" (origins, applications settings, diagnostics, origins in game logging), but if you haven't, and have the time, it might be a good idea to enable it, then upload client_log again like you did before after you reproduce the error.
So its likely its a crash that is unrelated to origins. Its certainly NOT cleanly closing out.And if you dont get any error messages, then its likely not the application thats faulting.
If you can, make sure in game logging is enabled, reproduce the error, and upload client_log. If you have the time. It would be interesteing to see if more information is logged. If not, dont worry about it.
AS i said before, its likely your graphics system.
Do you have a temp utility for your graphics card?
Does nvidia come with that? You should check the control panel for it. I know AMD does. If they do, make sure you check to see what temperature the cards getting to. Its a good idea to always know what temperature your card runs at for any game you play.
Feel free to list that readout and ill tell you if your cards overheating or not. The control panel should tell you though.
