Solutions to the error with reference to the atidxx64.dll file in Windows 10, 8.7
Mostly an error indicating the problematic file atidxx64.dll appears in games. Players of Final Fantasy XIV, Call of Duty Ghosts, Battlefield 4, Genshin Impact were at risk, but no one is immune from it, they can appear in almost any game. As we found out, the problem lies in the ATI Radeon video drivers (mostly), but there are other, less common reasons. It is interesting that the error can appear both at a random moment in time, and strictly after a certain interval. Someone writes that he is thrown out of the game after 30 minutes, others – after 45 minutes, and for some the error pops up only when the application is closed. Despite the variety of spawn conditions, we have solutions that can work.
What the error might look like:
Fault Module Name: atidxx64.dll
Atidxx64.dll caused an Access Violation (0xc0000005)
Unhandled exception at 0x000007FEF41FAE4D (atidxx64.dll)
How to fix atidxx64.dll error?
Considering that the file described now belongs to the video card drivers, the most logical solution would be to try to work with it. We have real-life examples where this worked, albeit with slightly different procedures. Plus, we found out that the problem may be in the connection of equipment, game files,
Updating / rolling back video card drivers
Atidxx64.dll is directly related to the video card drivers. It seems that some of their versions are more susceptible to this kind of error, which means that a clean reinstallation has a good chance of restoring the correct operation of games.
How to do it:
- Right-click on Start and select “Device Manager”.
- Expand the “Video adapters” list and double-click on Radeon (it can be either a discrete or an integrated video card).
- Go to the “Driver” tab and click “Delete”.
- Go to the support page AMD and indicate the model of your video card.
- Download the file and install the drivers.
After removing the video drivers, the system will work with large visual delays, and this is normal. To minimize the time for such unpleasant behavior, the drivers can be loaded in advance.
Important! There are known cases when only a specific version of the video driver can work. You may need to try this procedure several times. For example, only version 17.4.2 helped someone.
It is known that the error can appear in the opposite situation – after a recent video card software update. If so, it is worth trying to rollback the driver to an earlier version. Fortunately, this is not difficult to do.
- We press the combination Win + X and select “Device Manager”.
- In the “Video adapters” block, right-click on the Radeon card and select “Properties”.
- Go to the “Drivers” tab and click on the “Rollback” button.
- Click on the required button to start the procedure.
Failure of older technologies like AMD’s Mantle API
Starting with Radeon Software Adrenalin 2019 Edition 19.5.1 of 2019, the company has deprecated the Mantle API. Previously, great hopes were placed on her, but he did not gain popularity. Forced support for 6 years has been completed. Today, some users are still using drivers so old that they have an unsupported API for 2 years. This is evidenced by several user reports. The solution will be a clean installation or update of drivers, not necessarily up to the current state (if there are any “contraindications” to this), but at least up to 19.5.1 and newer.
Another recommendation is to uninstall Omega Driver. This is an unofficial set of drivers for ATI Radeon and NVIDIA. More precisely, these are not just other, but rather modified versions of the drivers. Yes, they really were worthy of attention in their time, as they offered many additional settings and functions. This software has not been officially supported since 2012, but remains relevant for older video cards. It looks like this is one of the possible causes of the atidxx64.dll file error. You will have to abandon such software in order to fix the error.
Replacing the new atidxx64.dll file with the old one
One of the solutions to the problem, which is also aimed at the driver, and this is not surprising, given that the file belongs to them. The bottom line is to try to update the software, but keep the old file atidxx64.dll or atidxx32.dll.
How to do it:
- Go to the C: Windows System32 folder.
- Copy the file atidxx64.dll to another folder.
- Installing a new driver.
- Go back to the same folder and copy the old file with the replacement here, but it’s better to save the new dll somewhere. You may need to unlock it with Unlocker or boot into Safe Mode.
- Checking the result.
If the effect is not followed, you can try to roll back the driver to the previous version and install a new file atidxx64.dll. In other words, perform the reverse procedure.
Additional solutions to the problem
Despite the fact that the first mentions of the error with the atidxx64.dll file began to appear even more than 6 years ago, there is still a very vague idea of the nature of the origin of the failure. There are a number of cases in which users performed completely different actions and this helped them. We have no choice but to list what there are already positive reviews on the forums.
Other things to try:
- Run the game with administrator rights… To do this, hold down Alt and press Enter, go to the “Compatibility” tab and check the box with admin privileges.
- Disable anti-aliasing in the game… This is to some extent related to the problem of drivers, but for some it was enough to do only such an action.
- Check the quality of the loops… It is worth disassembling the system unit or laptop case and check the quality of the RAM connection, as well as the SATA cables. Simply by correcting them, the error can go away forever.
- Switch to a different version DirectX… The procedure is performed in the game settings or in the configuration files. If you’re currently using DirectX 12, you can try 11 and vice versa.
- Delete file configuration… It looks like after deleting the PROFSAVE_profile file or similar (the name depends on the game), the problem goes away. True, along with it, the graphics and control settings also fly off, but it is easy to fix it manually. For example, for Battlefield 4, the path looks like C: Users Administrator Documents Battlefield 4 settings. Something similar for other games.
We are already silent about the methods that first come to mind: reinstall the game, update Windows, check system files, reinstall Visual C ++. All of this can be tried too if all else fails. They are not included in this atidxx64.dll fix only because we have not seen real confirmation of the effectiveness of the methods. However, this does not mean that they really did not give effects. So far, this is all we can offer.