Atidxx64.dll Download

[Glendora Starr]

MiniToolOEM program enable partners like hardware / software vendors and relative technical service providers to embed MiniTool software with their own products to add value to their products or services and expand their market.

What is atidxx64.dll? Some people find this atidxx64.dll crash error when they attempt to access or open the program that includes atidxx64.dll. So, why does that happen? And how to get rid of this error? In this article on MiniTool Website, you will find a series of solutions for that.

What is atidxx64.dll? It is a Dynamic Link Library file used to ensure components run smoothly on your PC. Some people may receive some related error messages, such as atidxx64.dll missing, atidxx64.dll not found, or atidxx64.dll crashing error.

Those errors commonly occur on programs used with atidxx64.dll when the file is missing or corrupted. You may accidentally delete the file or some virus or malware infiltrations damage the system files.

MiniTool ShadowMaker is designed for data backup and file syncing. It has many advanced features to help improve the backup and syncing experience. This tool provides a 30-day free trial version for you and get that by clicking the button.

I was last able to play BF4 okay on 4/30. Logging in today (5/3), I barely get a minute in before BF4 crashes with faulting module atidxx64.dll. Sometimes, the game crashes before it has finished loading. The game seems to run fine on the Test Range and empty servers.

I have tried using the latest 14.4 driver and the beta 14.4, but was using an earlier driver just fine a few days ago, and tried rolling back to it in between. I have also updated my Realtek driver to R273, to no effect.

I have the same problem as you, it started a few days ago. I connect to a server, it loads up, and not even a minute passes and it crashes. I haven't installed any updates in the past few days ( except some firefox updates ).

If the problem only began after updating your graphics driver then try reverting to a previous driver (again choosing 'clean install)

If using Mantle drivers on AMD and crashing in X64 version then: Go to C:\Users\Administrator\Documents\Battlefield 4\settings and delete the file "PROFSAVE_profile" (or you could just move it somewhere else on your PC for safekeeping).This will also reset keybindings and graphics settings so you will need to do them again when you launch the game.

Not sure what went right, but between more installs of 13.12 and 14.4 between cleanings with AMDCleanupUtility, turning off antialiasing, and even mistakenly clearing out an old PROFSAVE_profile from an older folder, I'm not crashing at the moment.

I have the exact same problem and narrowed it down to antialiasing. Game works with it switched off, but does this mean I can never have it switched on again? I think graphics at a distance look really crumby with it turned off. It's much harder to make out enemies at range. Surely antialiasing isn't now permanently borked for a lot of users?

Still happening 5 months later, and I have ot agree the lack of AA is kind of ruining the experience, can anyone comment is it only on certain types of AMD/ATI cards? or even further that Nvidia doesn't have the issue since it doesn't appear it's important enough for people to fix in updates either driver or game side..

It was fine for me till the latest patch and then atidxx64.dll errors in my Event Viewer > Application logs. I surfed the web for literally DAYS trying to fix the game crashing the moment i start a match. I updated to latest ATI graphics drivers, updated Punkbuster, did origin repair, deleted Ati raptr profile, tried 32 bit version of bf4, unchecked cloud sync in Origin, unchecked origin in game in Origin settings. Turning off Antialaising worked. OMFG (Thanks for taking the time to post suggestion)

I have been having a problem for a while now where I'll be creating something in Unity and both of my monitors will go black. Usually this only happens when I am working in Unity or Blender but it has occasionally happened when playing games. I've tried several "black screen of death" fixes such as checking for virtual monitors and plugging my monitor into the motherboard's HDMI output vs. the GPU's. A few days ago I was sick of dealing with this so I reformatted my hard drive and installed the newest AMD drivers for my card. I still get the same results but now when running Unity I only get the BSoD every once and a while. Sometimes when running Unity it just crashes and I submit an error report. A Unity customer service rep contacted me from one of the error reports I submitted and said that there was an issue with the atidxx64.dll file which is part of the AMD driver. I have the most recent driver (and have been having this problem with previous ones) and a fresh install so there can be no complications with previous installs. I'm pretty stuck at this point and don't know what to do from here and I'd appreciate any help!

I had been having a similar issue for the last 10 months with my 580. Under-clocking 5% made the issue very rare. I assumed that my old psu was likely to blame but last week i built a new machine keeping the 580. Everything was fine until Windows Update... the problem returned...

Funny, I've also had the issue for the last 10 months or so. It started shortly after I got my card and I wonder if it was the updated driver that caused it. What made you think the PSU could be the cause?

my old pc had a 550w psu and reaching 6 years old. I've seen similar crashes when installing a gfx card on a prebuilt pc ie hp where they only have a 300-400w psu. There's enough power to run the card normally but under load there may be times where it's being starved for juice.

I would try uninstalling the manually installed drivers first and then check for updates with windows. Logically, this should work if you're experiencing the same issue. I had originally thought it was an update for windows causing it and I'm on a fresh system anyway that's why i just reinstalled.

for almost two weeks I am facing with sporadically crashes in DCS. The first one was after a long mission with the A-10C II at the NTTR map ten days ago, the second one in a Su-33 at the Syria map about one hour ago.

After the first mission I checked the dcs.log and crash.log and found some issues with the graphics driver (access violation by atidxx64.dll). At this time i still used the old 19.12.1 AMD driver. So I changed to the new recommended driver (20.9.1). But also with this I had a crash for the same cause.

I will try. But normally I clean these both folders everytime I change something in the DCS or Radeon settings (also when I install a new graphics driver). Windows 10, yeah I know, I am a little paranoid with these upgrades because there is a lot of issue reports every time Microsoft is "blessing" us with one of these upgrades, so I do it so rarely as possible. But I also will do it and hopefully it will resolve this problem. Thank you very much for your fast help.

I have deleted the fxo and metashaders2 folder, upgraded my Windows 10 to version 20H2 (2004 wasn't offered anymore) but it crashed again, Su-33, Syria map, same mission.This time neither a .trk file nor a .crash file was written, only the dcs.log file (attached). It crashed to desktop without any error message.

I disabled "Enhanced Sync" both at Global and DCS profile within the Radeon settings, deleted the fxo and the metashaders2 folders again, started the game, flew the same mission as before (Syria map, Su-33). More than 1 hour later I finished the mission by landing on the Kuznetsov with the last drop of fuel, folded the wings, rolled to the parking position and ... crash! Very frustrating.

yesterday I deactivated all third party mods (these were A-4E-C by Heclak, Su-57 by Cubanace and some liveries for different aircraft types), then I flew the syria mission and had no crash. Today I activated the mods again (except Su-57 because I had installed it only for testing), flew the Syria mission and also had no crash. But in both cases the mission duration was a little shorter than one hour. Not sure whether duration time could be a factor.

What I did also yesterday was to increase the DRAM voltage from 1.2V (it was the auto setting in the BIOS) to 1.35V (the max. recommended voltage for my DRAM). I don't know whether to less DRAM voltage can cause such kind of crashes. I will keep it watching and testing. If this has solved my issue I will report to you. Thanks again for your help!

No it wasn't. My DRAM has a factory clock of 3000MHz. Before I upgraded it from 32GB to 64GB it ran with 3200MHz and 1.2V without any issues (all above 2666MHz is overclocking speed for my mainboard). After the upgrade it wasn't stable with this RAM clock and also with lower overclocking speed settings, even with 1.35V (Windows didn't start or crashed with bluescreens). I read that Ryzen processors don't like DRAM overclocking when all RAM banks are full, not sure if it's true. So I set the RAM to non-overclocking speed of 2666MHz with 1.2V. With this it was stable so it seemed. But maybe 1.2V is not enough for four 16GB DIMMs in some cases with high load.

just for your information. The last two weeks I flew several missions in different aircrafts (A-10C-II, AV-8B, F-15C, F-16C, F/A-18C, Su-33) with mission durations between 45 and 90 minutes without any further CTDs. It seems the solution for my issue was a mix of graphic drivers update and DRAM voltage increasing.

Hi Kevstosmart,

sorry for my late answer. I didn't change back to an older driver. I used the 19.12.1 Radeon driver for a long time. After I ran into the described issue I tried the 20.9.1 WHQL driver but with the old Radeon GUI (not these Adrenalin GUI crap) because I need the Frame Rate Target Control setting, which isn't present in the Adrenalin GUI anymore although the function is still existing within the drivers. With the 20.9.1 driver and the increasing of the DRAM voltage the crashes are completely gone. I didn't try the newest WHQL driver (20.11.2) yet, You know, never change a running system.

3a8082e126