Apex legends crashing without error

---

@ThursdayLE wrote:
Error or no error. There is something wrong with this game.

---

This should be the answer.

I am sorry but the experimenting most of you are doing I understand are things you are able to handle the potential repercussions / revert any changes. However some of the things flying around as "fixes" shouldn't be mentioned and really need to be controlled. Letting this go on and random maybe not so educated individuals just messing with their CPU configurations is reckless and could end up in someones machine getting damaged if they happen to veer off course and experiment themselves.

Nobody should be disabling cores to get this game to run. If anything this type of troubleshooting needs to be addressed as "EXPERIMENTAL - TRY AT YOUR OWN RISK" or tbh if you can't explain why it worked, don't recommend it.

The snowball effect from tampering with the wrong stuff can very well lead to not playing any game at all. Not saying everyone here is uneducated, but, "assumptions make everyone look like an *."

Blueberry I don't want to tell you how to do your job but as a community manager you should recognize this could be problematic. I love this game just as much as you guys, I promise, I want more than anything to get this game running stably. It's killing me that I have a stacked discord right now, and I've got about 8 people that can't play more than maybe 1 game before game crashes. But i'd hate to see someone destroy their rig because they missed a few steps and clicked a few wrong buttons. 

I get that it's the internet and those things should be implied, "try at your own risk." But publishing random one off fixes into a sticky that honestly make little to no sense. I will say it again, it's reckless.

Best thing to do would be to wait out an answer from an engineer who designed this platform. Someone who understands how to optimize the product they built. Once again, I know it's killing everyone and they want to play. But if anything take this as my warning, be cautious with trying some of these randomly suggested "fixes" as there can be other parts of your machine / programs that could also be effected. If you do not understand what you are looking at. You probably should not touch it.

Love,

Random Concerned Apex Obsessed Gamer

**EDIT**

I also highly suggest anyone who has added anything like -high -threads etc...to their launch options to please do some research behind what these commands do. I get this is a different graphics engine and optimized different however these commands have been proven to be more harmful than they are effective multiple times. Actually I am positive there are even Valve/CSGO developers who have mentioned / explained those exact commands / subject and why they are harmful. A quick google search is all you need to do.

That is all I am trying to say. I honestly mean this in the kindest way possible. Everyone's attempt's to help others in the community have been valiant and shown what a great game and community this has already become. But please just be cautious and think before you speak - as other's might not be able to put out the fire that ensue's when you rub those two stones together. 

**EDIT #2**

For anyone who is wondering, yes, I have tried everything mentioned on these forums as well. Some of them I have tried knowing they would have absolutely no effect at all and it was just sheer luck. If you would like an example; My "streaming" / "secondary" rig runs my old am3+ setup before I upgraded into Ryzen. It is equipped with these specs -

• AMD FX 6300 - set to auto clocks - turbo boost enabled / CnQ enabled / APM enabled / C-States Disabled / Windows set to ultimate performance / All cores running
• GIGABYTE RX 570 4gb gaming edition - stock clocks - all wattman controlled / no msi afterburner etc. Attempted Driver sets 17.8.1 - 19.2.1
• GIGABYTE GA 970a DS3P Rev 2.1 Mobo - VRM's have a dedicated 120mm fan blowing directly onto them
• Corsair CX 750m 750W 80+ Bronze Certified PSU
• 2x 4gb ADATA DDR3 1600mhz - Dual Channel
• Evo 212 CPU Cooler
• I've tried total potato in game settings to nearly maxed for my hardware

Temps Monitored through HWINFO64 - CPU AVG = 36c SOCKET AVG=46c GPU AVG= 48C

Temps Monitored through AMD OVERDRIVE - Thermal Margin AVG = 39.2C (FARRRRRR from max temps)

With a practically stock bios and 0 cores disabled, 1920x1080, medium textures, trilinear filtering, full-screened, 4gb texture streaming, with spotify in the background: I ran the game solo last night for 5 hours with only 2 crashes. Today I haven't been able to make it through a game. 

My point being is some of these suggested fixes are random and may not work for you at all.