7 years ago
Crashing to Desktop No Error
Product: Apex Legends Platform:PC Please specify your platform model. PC AMD or Nvidia Model Number GTX 1060 3GB Enter RAM memory size in GB 16 What is your gamertag/PSN ID/EA Account name? cool...
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number R9 290
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? Jexthis
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)? Lifeline
Which Legends were your squad mates using (if applicable)? Wraith, Bloodhound
Where did the issue occur? start of dropship
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. almost always crashes when I am dropmaster it seems
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. seems to be from becoming dropmaster
Did your squad mates also experience the issue? No
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) Many diffrent days before this but also today. 2.16ish
How often does the bug occur? Occasionally I wanna say 10% up to 33%
how severe is your issue? yeah
What happens when the bug occurs? The game "crashes" to desktop.
What should be happening instead? The game doesn't crash randomly
Steps: How can we find the bug ourselves? Due to the random nature all I'm doing is playing the game. Thus steps to repo can't be given.
Game crashes to desktop with no error. Been happening on and off pretty much since launch. Normally atleast once a day for me. No error message is given and last I time I checked nothing was logged in the event viewer. Not really sure what else to do at this point.
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number GTX 970
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? EZForEnce
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible: Moxerific, 500DaysOfAutumn
Which Legend were you playing (if applicable)? Wraith
Which Legends were your squad mates using (if applicable)? Wraith, Bloodhound
Where did the issue occur? 2 Squads Remaining
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Runoff
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. I was running to get positioned for the final fight
Did your squad mates also experience the issue? No
How many matches had you played in a row before the issue occurred? 5 or 6? Not sure
When did this happen? (dd.mm.yy hh:mm) 15.02.19 1:15 AM
How often does the bug occur? About once daily
how severe is your issue? High
What happens when the bug occurs? The game suddenly closes with no error message
What should be happening instead? The game doesn't crash randomly
Steps: How can we find the bug ourselves? Unknown
Looking through Event Viewer in Windows, going to Windows Logs > System I see a few instances sourcing from Service Control and FilterManager in which the service "EasyAntiCheatSys" is mentioned. The first instance of this service (Source: Service Control Manager) is of the service being installed into the system at 10:41 PM 14.02.19, when I first booted the game up on this occasion. At the exact same time, FilterManager reports the event "File System Filter 'EasyAntiCheatSys' (6.1, 2019-01-24T02:26:48.000000000Z) has successfully loaded and registered with Filter Manager."
Then, at 1:08:33AM 15.02.19, the Event "File System Filter 'EasyAntiCheatSys' (Version 6.1, 2019-01-24T02:26:48.000000000Z) unloaded successfully." occurs. (Source is from FilterManager)
Following this is Service Control Manager at 1:10:29 AM 15.02.19, saying that it has once again installed the EasyAntiCheatSvs in the system, with FilterManager once again saying it is successfully loaded and registered, as though I had just booted the game up. Then at 1:12:37AM 15.02.19, the event "File System Filter 'EasyAntiCheatSys' (Version 6.1, 2019-01-24T02:26:48.000000000Z) unloaded successfully." occurs (Source: FilterManager), This lines up with the time period when my game closed, and is the only record I can find in the Event Viewer that would show any sort of closing/crashing activity related to Apex.
Just crashed again. Checked the event viewer nothing logged in the Application section for the time of crash but in the windows logs > System. At the time of crash Service Control Manager logged "The Application Experience service entered a running state."
Regarding your concern with EasyAnticheat and how it successfully loads and unloads, it is behaving like it is supposed to be due to parent process (r5apex.exe in this case) being the one which crashes. after extensive search i concluded that eac isnt a problem in this case, if you are experiencing bad_module_info in event viewer. Gonna post my findings here soon
Day 3 - Log 1
Same issue here. Game CTD's at any random moment, however predominantly at initial jump. Someone with exact same setup except mobo and ram has no issues at all.
Event viewer gives bad_module_info with no further information regarding nature of error.
All of the findings and taken actions in spoiler tag, so that it doesn't take up all page
Tried measures:
-Resetting OC's
-disabling core 5&6
-reinstalling vc++ redists
-new windows profile
-disabling all unnecessary services
-overlays in everything are disabled
-compatibility mode win 7&8
-admin privileges to origin and apex
-fullscreen optimization off
-fps_max & several other commands coming to experience with source engine
-temp local cleanup of origin
-reinstalling both origin and apex
-playing with video settings (from default to min possible)
-fullscreen/windowed/borderless
-checking my cpu and gpu temps during gameplay (within norm)
-disabling everything in sound control except headset (3.5 mm jack so no correlation to another common usb headset problem)
-from services only thing running is windows essential services + origin + realtek hd + amd radeon
-warming up hardware and gpu by playing 5-10 mins at training
-defender off
-DVR off
Detailed description:
-Game CTD's almost every match, with higher frequency during evenings for eastern hemisphere ( server overloads? )
Actions leading to CTD:
-Jumping from ship
-Relinquishing jumpmaster privileges
-on exact moment you drop to the ground
-random moments when you play
-refilling shield (haven't encountered CTD when refilling health though)
-right after everyone selected legends
-using sights
-during some ultimates
-pathfinder Q (sound cue played on hitting wall, however CTD'edwith a freeze few secs before)
-using wraith's portal ( considering all of that could it be related to unoptimized shader swap? But still believe that it is software compatibility issue )
Additional remarks:
-average CPU GPU loads are within specs
-hardware temps within specs (had benchmarks run successfully 20-30 C higher)
-even though this build is budget tight it is capable of running most of AAA games (low-mid settings) without any issue (Kinda laughable that i can play RE2:remastered, or Fortnite (if you are worried about cpu overload of 64+ people on the server) on decent settings, but cant play Apex on lowest possible)
-cant be due to source engine (Dota 2 maxed out, CSGO maxed out, TF2 was once at a time maxed out)
-Number of different builds with same problems doesn't correlate to your statement about our rigs being problematic (Example i provided once again same build for main components just different mobo and ram, his game runs perfectly, mine crashes almost every game)
-he also has defender, DVR, Gamebar, and Cortana off'ed! (Gonna test gamebar + cortana as well,might be conflicts from there) -- doesn't help
-the game drops framerates every second game if not resetting video settings and changing them back (could game be resetting to default automatically?)
One of the Russian sites that i visited during searching for this problem highlighted bad_module_info being a problem for people who upgraded from win 7 as we have traces of older version calls in our systems (could it be issue?) If you wondering guy with the same set up as me updated from win 7, and i did clean install of win 10.
I suggest creating one megathread to collect all information regarding this issue, mainly one topic, as hoping between different threads for possible solution on 1 of them is quite annoying considering how hectic everything is. I will try to delve deeper into the system in order to pinpoint exact process at fault.
After auditing my system during crash I found following:
Hardware info:
My rig:
FX-6300 3.5 GHz (no OC)
Sapphire r7 260x 2GB (factory OC'ed)
Ripjaws X 8GB (1866 MHZ dual channel no OC)
1TB HDD (WD Black series)
Win 10 Pro (1803 - x64)
Guy who doesnt crash at all:
AMD FX-6300 Hexa-Core 3.5GHz
SAPPHIRE Radeon R7 260X OC 2GB
Kingston 6GB DDR3
Toshiba 1TB SATA ASRock N68-VS3 FX
Microsoft Windows 10 Pro x64