Forum Discussion
14 Replies
- Carbonic11 years agoHero+
My guess is that your registry is somehow been corrupted in a way that is very hard to fix. Using several softwares and uninstallers has probably just made it worse.
You might want to try http://treexy.com/products/driver-fusion several times to remove the drivers after you have used the official AMD uninstaller (always reboot after running each uninstall/program).
If that doesn't work I would probably just do a format of your operating system, starting over from scatch.
- Anonymous11 years ago
Ok but the first times -monts ago- when the 14.1beta was out (the first driver version after 13.12) i was not using 3rd party uninstallers and i was still cleaning my registry so i can't really find the solution.I mean after i tried the 14.1beta and the next stable one (i can not remember the version) i searched for these uninstallers and more people had this problem and used the 13.12 version.
Format is getting closer and closer...:mansad:
Edit
I am not sure but i think i formated my pc once the last months so...
Either way i am going to keep you updated.
For me it is "Mantle refunction error"
- Anonymous11 years ago
I formatted my Windows but nothing changed.The problem remains the same as i thougt.:mansad:
Hey man, Can you say what version of drivers do you have and I will try to search some information. Peace!
- Anonymous11 years ago
I have the 13.12 version.Every version after 13.12 crashes my Battlefield 4 just after the loading screen.
Hi man, try do this and it shuold fix :
1. Delete AMD Catlyst install mananger useing control panel
2. Find and delete this in your PC : C:/AMD/support/14-4-win7-win8-win8.1-64-dd-ccc-whql
3. Re-download and install newest drivers useing custom and just install display and hdmi drivers and Catlyst : http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64#amd-catalyst-packages
4. Disable Vsync in game
5. Or if it not works if you useing mantle change it to DirectX
Sorry for not right language.If I help you revard me with xp and if I solved it press Accept as a solution
Peace , Noah!
- Anonymous11 years ago
Look i appreciate that you want to help but i already said this is not a solution.Please read my first post and the title of the thread then the other posts.
I got this problem too long time ago but then I installed my new dirvers it fixed cuz Mantle now is compatible with 14.2 or newest drivers so you can give a try for this solution. If it don't help you I try to search for more information.
Peace, Noah!
- Anonymous11 years ago
As i said you should read all the posts...
- Anonymous11 years ago
@Goldust34 wrote:I got this problem too long time ago but then I installed my new dirvers it fixed cuz Mantle now is compatible with 14.2 or newest drivers so you can give a try for this solution. If it don't help you I try to search for more information.
Peace, Noah!
The GPU he uses does not support Mantle. He can only use DirectX.
Ok ,14.7 drivers is coming soon and AMD said that it should fix all bugs ,crashes etc. Just wait for it and with that drivers all should be okay. By the way check page 3 of this case. I think I find solution. If not you should wait or go to help.ea
Peace, Noah.
I think I found solve for this issue : Go to My computer>Advanced system settings>Advanced>Performance>Settings>Data Execution Prevention> Mark this : Turn on DEP for all programs and services except those I select. > Press add> Find BF 4.exe > press apply and OK
Then you did it let us know if it help
Peace, Noah.
- Anonymous11 years ago
About the 14.7 version:
In the changelog of the 14.7Beta they say nothing about my problem so i guess that when the stable 14.7 releases nothing will change like all the previous releases...
About your solution:
When i try to add the bf4.exe it says "You can not set DEP attributes on 64-bit executables"
and when i try to add the bf4_x86.exe says " This program must run with data execution protection (DEP) enabled.You can not turn off DEP for this program."
About Battlefield Franchise Discussion
Recent Discussions
- 30 minutes ago
- 13 hours ago