Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
11 years ago

Re: Recent crashes due to atidxx64.dll

after 8 months it is still "recent".

and it is not only x64 - I have the same problem with x86 /atidxx32.dll

I tried to attach Microsoft Visual Studio debugger

it detects "Unhandled exception at 0x64CCD659 (atidxx32.dll) in bf4_x86.exe: 0xC0000005: Access violation reading location 0x00000010." for x86

and " Unhandled exception at 0x000007FEF41FAE4D (atidxx64.dll) in bf4.exe: 0xC0000005: Access violation reading location 0x0000000000000018" for x64

I tried to reinstall catalyst drivers with no result. And delete PROFSAVE files - as soon as I restore MSAA the game crashes.

Are DICE and AMD going to do something asbout it??

specs:

Intel i7-4770k

ASRock z87 Extreme4

2x4 GB DDR3-2133

2x HD6950 CF

Win 7 Ultimate

And i suggets to remove the solved status from this thread. Disabling antialiasing is a workaround but not a proper solution.

4 Replies

  • puma29x's avatar
    puma29x
    Not applicable
    11 years ago

    i delete "PROFSAVE_profile" and run the game as Administrator:
    Go to the Origin games folder (C:\Program Files (x64)\Origin Games\Battlefield 4) and find Bf4.exe. Right click it and go to PROPERTIES, then COMPATIBILITY and check the box next to RUN THIS PROGRAM AS ADMINISTRATOR.

    i played 30min with no problem therefore it seems that the problem is AAA 

    tnx for help !

  • Anonymous's avatar
    Anonymous
    Not applicable
    11 years ago

    I found a solution for my AA crash. I have a HD 6000 card like the most of the people with this problem. Only driver 13.2 worked for me (for almost 1 year!!),
    but now i can use the new 15.3beta with the better perfomance and antialiasing on!!

    Solution:

    - First, you need to have installed driver 13.2
    -search for atidxx64.dll on your computer (windows folder)
    -copy the atidxx64.dll file from the System32 folder (9.30MB)
    -install the 15.3beta driver (haven´t tested others)
    -search again for the atidxx64.dll in the System32 folder
    -replace the new atidxx64.dd with the old one you´ve copied first
    -if you can´t replace it, cause it´s used by windows, then shut down dwm.exe in the taskmanager
    or use "unlocker" tool to dele it.

  • AstrixAU's avatar
    AstrixAU
    Rising Scout
    11 years ago

    I started betting this crash after quitting BF4, I'm lucky there.

    It only happens when I quit the game and the window is about to close so the last fraction of a second it crashes.

    Only started happening recently and I haven't updated the driver since Omega months ago.

    I have recently switched from Mantle to DX11 to record gameplay maybe that's why I've only the last week or so noticed it.

    Fault bucket 81816450020, type 5
    Event Name: BEX64
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: bf4.exe
    P2: 1.4.2.25648
    P3: 54e3fd7a
    P4: atidxx64.dll_unloaded
    P5: 8.17.10.581
    P6: 546e9ecc
    P7: 00000000005ed7ec
    P8: c0000005
    P9: 0000000000000008
    P10:

    Faulting application name: bf4.exe, version: 1.4.2.25648, time stamp: 0x54e3fd7a
    Faulting module name: atidxx64.dll_unloaded, version: 8.17.10.581, time stamp: 0x546e9ecc
    Exception code: 0xc0000005
    Fault offset: 0x00000000005ed7ec
    Faulting process ID: 0x1104
    Faulting application start time: 0x01d06f7d5badf6a2
    Faulting application path: C:\Program Files (x86)\Origin Games\Battlefield 4\bf4.exe
    Faulting module path: atidxx64.dll
    Report ID: c4f852c8-db70-11e4-83e5-ac220b2c993f
    Faulting package full name:
    Faulting package-relative application ID:

  • Abishai619's avatar
    Abishai619
    Not applicable
    11 years ago

    Same issue exactly as the above. Anyone fix this?

    Faulting application name: bf4.exe,

    version: 1.4.2.25648,

    time stamp: 0x54e3fd7a
    Faulting module name: atidxx64.dll_unloaded, version: 8.17.10.581, time stamp: 0x546e9ecc
    Exception code: 0xc0000005

    Could it be the Omega driver?
    First saw the error on 03/22/15 been dealing with it since waiting for a fix.
     
    Also happened with 14.9 as well as Omega which is why I switched both clean installs