Re: Constant Crashes With No Message

we literally have the same exact problem.. i dont understand it either.. my build could run this game and warzone at the same time... so its def on their end... its so frustrating man... cant even grind ranked atm because of it... glad yet not glad to see im not the only one

I've opened the .dmp files with WinDbg and all of them point to the same thing (except one really old .dmp file that is not related to these crashes), something AMD related.. I don't even have an amd processor or gpu.

Do You play with unlocked fps? I have limited my fps to 141 (I have a monitor with g-sync and 144hz) and since then I haven't had any crashes.

Maybe try it out.

Also I have read here on the forum that game above certain fps count is unstable. 

Like I said, this is virtually troubleshoot-proof. It's a recurring issue and we've already tried all of the common solutions present on these boards. It's a specific issue which comes up after hotfixing the game and it always coincides with the reintroduction of more than one map to the map rotation. The only solution I haven't dabbled with is disabling six cores in windows just to play Apex Legends. There is probably a solution possible in the game's code, as the beginning of seasons and the beginning of events runs without a hitch when a single map is put up to offer.

@nohmu replied before i could.. there is nothing we havent tried... nothing lol short of reinstalling windows which ummm no aint nobody got time for that :D

I've been having the exact same issue as you guys.

After trying basically everything, I started in depth monitoring my PC while playing, and found a crash pattern at around 2800-2900 CPU memory usage. 

So I started digging deeper and I ran into a forum thread where a dev adressed an issue similar to ours, he suspected the CPU.

I then decided to try downclocking my CPU, from 4.8GHz to 4.6GHz, re-enable XMP instead of a ram OC preset I was running, and I haven't crashed since I tried these changes.

I assume this has something to do with the amount of data the CPU recieves from the game, and if the CPU is OC'd to it's limit, it can't comprehend the amount it recieves, and so it crashes.

It's worth mentioning that I didn't have any crashing issues BEFORE the reintroduction of olympus, and before that I haven't had any issues since they hotfixed an issue back in s7. (Also around the reintroduction of worlds edge I believe)

I remember several people having crashing problems around that time too.

I hope it works for you guys as well, if anything it's worth trying.. If your CPU is overclocked that is.

I think we get the same issue, I don't know why r5apex.exe call the AmdPowerXpressRequestHighPerformance function and get the exception, there is no AMD device in my PC. My PC is build by Intel I7-10700 and Nvidia RTX3080

@NotQuinnenill give this shot bro ty for posting this.. i havent tried this at all.. and my cpu was oced to the max lol... so hopefully this works ty again ill let u know either way

@NotQuinnen Hey just posting an update as requested and i have to say thank you firstly for posting your fix.. as it allowed me to notice that when i over clocked my pc i oc'd too much to begin with.. but i am happy to say that since underclocking from 5.0 to 4.6 i havent had a single crash since.. thank you again and hopefully it remains fixed.

@nohm Exactly. I remember the constant crashes in Season 3 - I played very little that time, because Apex crashed almost every match. I think Season 6 was very similar too, if I remember correctly.

It's the same now, and I'm getting sick of hearing "have you tried XY already?". I changed my drive, tweaked XMP settings, underclocked my CPU and GPU, etc. - doesn't matter, game keeps crashing.

The issue is clearly on Respawn's end, because if the problem was with my PC, then 1: I could have solved it already somehow (I really tried everything!), and 2: it would persist through seasons, and not come and go with updates.

I hope they fix this sh*t soon, because, once again, I'm unable to play the game due to constantly crashing.