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...
Forum Discussion
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
Spoiler
Spoiler
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:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 2/16/2019 2:23:38 AM
Event ID: 4689
Task Category: Process Termination
Level: Information
Keywords: Audit Success
User: N/A
Computer: Obscuro
Description:
A process has exited.
Subject:
Security ID:OBSCURO\[redacted]
Account Name:[redacted]
Account Domain:OBSCURO
Logon ID:0x5D09F
Process Information:
Process ID:0x107c
Process Name:C:\Program Files (x86)\Origin Games\Apex\r5apex.exe
Exit Status:0x64
Successful process terminations like when you alt+F4 or use task manager yields in general 0x0. However, in this case exit status showcases 0x64 which is an error related to semaphores.
I am not gonna go in details, but in short semaphores are another type of data type. Considering all of that it seems like a problem on a level of cooperation with OS itself, as error indicates system wide semaphores. Not sure how useful it is but trying to give my 2 cents.
Hardware info:
Spoiler
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
Which sections of event viewer should I be looking at for further information? As it stands Under Windows Logs > Application doesn't seem to log anything for the game (that I can see). But under Windows Logs > System I can see the services for the anticheat starting and stopping.
- under Windows Logs > Application you will find error marks that are not related to the r5apex.exe. With each such error there will be report detailing everything else, just check for the type of report it should be APPCRASH. You can also try to audit your system in order to check which processes are created and terminated at exact time of your crashing, and what is exit status for those processes
In my case I've never seen it log anything to the Application section of the event viewer. Which of course includes I've never seen an APPCRASH type of log flatout.
I have also seen someone saying something to the same effect in another thread a couple of days ago. When I googled the error mentioned I saw a help thread that mentioned that this could be caused by the Creators update that was pushed to Windows. Has anyone tried running this game on an earlier version of Windows 10/7, before the creators update to see if the crashes still persist? I think I might try it just to rule out whether or not it's the creators update that causes the crash for some rigs.
