Possible fx-6300 fixes (alternative to turning off 2 cores)

I've done some search in the game directory and found something that solved my problem (atleast for the moment 10 games played w/out crash) without turning off 2 cores of the fx-6300 by bios setting.

Be mindfull that it may not work (maybe that 10 games are lucky) but it can be worth a try.

-Go to ("C:\Program Files (x86)\Origin Games\Apex")

-search for a "bin" folder

-There's only one file inside (dxsupport.cfg)

-make a backup of this file.

-Now open "dxsupport.cfg" inside the bin folder

Search for this section:

"9"
{
"name" "CPU Level"
"min_phys_processor_count" "1"
"max_phys_processor_count" "3"
"min_log_processor_count" "1"
"max_log_processor_count" "3"
"min_clockspeed" "0"
"max_clockspeed" "65535"
"cpu_level" "0"
}

"10"
{
"name" "CPU Level"
"min_phys_processor_count" "2"
"max_phys_processor_count" "3"
"min_log_processor_count" "4"
"max_log_processor_count" "65535"
"min_clockspeed" "2880"
"max_clockspeed" "65535"
"cpu_level" "1"
}

Modify the section to:

"9"
{
"name" "CPU Level"
"min_phys_processor_count" "1"
"max_phys_processor_count" "2"
"min_log_processor_count" "1"
"max_log_processor_count" "3"
"min_clockspeed" "0"
"max_clockspeed" "65535"
"cpu_level" "0"
}

"10"
{
"name" "CPU Level"
"min_phys_processor_count" "3"
"max_phys_processor_count" "6"
"min_log_processor_count" "4"
"max_log_processor_count" "65535"
"min_clockspeed" "2880"
"max_clockspeed" "65535"
"cpu_level" "1"
}

- close and save

For me it worked

I have an FX-6300 and GTX-1050 2gb; 8gb ram

L4mbooo
7 years ago
Sup guys. I had the same problem, just figured out how to solve it for me. Changed resolution to the lowest (720p), capped fps to 60 and turned anti-aliasing off (yeah, the graphics looks like ps1 but you can actually play the game wow). Tried every single solution on this planet, but only this one worked, would be very happy if it helps someone. 🙂
AMD fx-6350
r9 380x 4 gb
P.S. Just turned anti-aliasing back on and it looks like the game is running just fine, been playing for 4 hours straight now.
P.P.S. And also low all your graphics settings to the ground ,of course.

13 Replies

7JG26Godman
7 years ago
What does this do exactly? I don't want to mess around with code not knowing how and what it affects
IIIAmerIII
7 years ago
Classic "I changed some random * and after a ridiculously low sample size I can determine that yep it totally fixed all my problems"
DanielHsn
7 years ago
Looks like the fx-6300 conflicts between the cpu_level 0 and cpu_level 1 of this cfg file, I changed the values so it just load the cpu_level 1
These cpu-level configurations can be related to the files inside the "cfg" folder
From what i see, this processor changes from cpu_level 0 to cpu_level 1 midgame causing conflict since it have 3 "cores" and some "logic cores"
Deactivating 2 cores make it only Hits only the cpu_level 0 configuration removing conflict
This fix should make it hit only the cpu_level 1 configuration
you can find treads about this file with most source engine like cs:go and tf2 games
Since this game uses a modified souce engine
The file looks is like a guide for the game to detect the system it being played on and use the correct ekv files
But we're modifying some game files, so i don't know the effect on easyanticheat.
I have no problems for the moment playing with the modified dxsupport file
7JG26Godman
7 years ago
Boy I wish a developer had a look at your post, what you are saying could be extremely relevant to the problem... I however have no idea what you are talking about and therefore cannot test this for myself
thewarrioroflos
7 years ago
gonna try this out

@IIIAmerIII wrote:
Classic "I changed some random * and after a ridiculously low sample size I can determine that yep it totally fixed all my problems"
dude hundreds of people are doing random * to fix the problem, there is bound to be one who finds the solution but if people like you act passive aggressive like this guess what? they will never share it with the rest of us and we'll be left to rely on ea meaning we're screwed
ZoloftAndMe
7 years ago
Didn't work for me. Sadly
IIIAmerIII
7 years ago
I don't think it's unreasonable to ask people to do more than 10 games of testing before they announce they've found the holy grail.
7JG26Godman
7 years ago
Ive gone over 12 hours straight of gametime no crashing, until it finally crashed. A few days of testing is needed to be absolutely sure of any meaningful changes
FTWraith
7 years ago
Just throwing this out there,I have not crashed since Sunday (at least 20 hours of gametime)
I had this same issue,
Step 1. Restart your game completely, when you start back up do not alt-tab. if you ever do alt-tab, restart your game completely. I have not crashed since i started this.

Step 2. Change all video settings back to default (you can keep fullscreen enabled and vsync disabled.)
I have a $500 prebuilt potato from microcenter and at default settings I get 100 fps.

Try these and I bet you won't crash anymore
KonradTen
7 years ago
This does not solve the POPCNT problem. This does not fix the problem of CPU support.