After a long hiatus, Formula One is back with a brand new entry, F1 22, available for PC and consoles. The game was met with favorable reviews from both players and media outlets worldwide. On the other hand, the PC version of Formula One 22 is plagued with problems and faults such as the Ego Dumper Error, a crash when playing the game, the inability to use DLSS and ray tracing, a crash at launch, and the error code AKEX-JHXX-KDKM-BAVE, amongst others. I have assembled a list of issues that PC players have reported, along with the solutions and workarounds that they have found for each.
What is F1 22?
F1 22 is a racing video game developed by Codemasters and published by EA Sports. It is the fifteenth installment in Codemasters’ F1 series of video games. The 2022 Formula One and Formula 2 championships are officially licensed to be represented in this video game. The video game was made available for download on July 1, 2022, for Microsoft Windows, the PlayStation 4, PlayStation 5, Xbox One, and Xbox Series X/S. Additionally, it would make its premiere on the Electronic Arts Origin platform, which serves as their primary platform and is playable on the EA Desktop app as well as the Epic Games Store. Previously, PC players had access to only one platform, which was Steam.
How to Fix F1 22 Error Code AKEX-JHXX-KDKM-BAVE Step by step Solutions
Problem with F1 22:
The most recent installment in the series is numbered F1 22. Despite the fact that F1 21 debuted a single-player campaign, the developers decided not to include one this year. However, in order to justify the new entry, they included a new mode; however, this mode does not appear to really add anything to the game.
Like previous F1 games, F1 22 has been designed with portability in mind. Despite this, users of F1 22 on the PC are claiming a variety of defects and problems, including the EEgo Dumper error, an in-game crash, the inability to use DLSS and ray tracing, a crash upon launch, the error code AKEX-JHXX-KDKM-BAVE, and other problems. The following is a list of faults that PC players are encountering, along with potential solutions and workarounds to these issues.
Steam configuration tweaks:
Another option that could work is to seek F1 22 within the Steam folder that is stored on their PC. After that, players will discover a DirectX file that has been given the name F1 22 dx12.exe. By right-clicking on the icon, users can grant the device administrator access and set the device’s situation config to 50. It is an excellent fix, however, there is a possibility that it will not work all of the time.
Hardware issues:
It’s possible that the problem is with the device itself, rather than the USB port that the wheels are connected to. It is recommended that players test them out in other racing games to check if they are functional. If this is not the case, then the issue lies with the hardware.
However, if the wheels operate on other games but not F1 22, fans can try switching around the USB ports to see if the game will identify the device when it is plugged into a different USB input. This is an option only if the wheels work on other games.
Reinstall the drivers for all of the devices:
One of the simplest and, at times, most effective remedies is to delete and then reinstall the device’s wheel drivers. The way to accomplish this for players is to first uninstall the drivers from the Control Panel, restart the computer, and then reinstall them. This will almost certainly resolve the problem by allowing the game to identify the input device.
Experimenting with the in-game settings:
There’s a good chance that the game’s Force Feedback was disabled by default, so make sure to check those settings. Therefore, in order to switch force feedback on or off, players will need to travel to the main settings page of the game. Once there, they will find an option to do so under the heading “Generic settings.”
This is the only approach that will work to fix the Force Feedback problem in F1 22. As a final resort, players might try reinstalling the game and checking it again after doing so. However, if they have tried everything, the best course of action is to wait for the developers to release a patch that will address the problem.
