• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Far Cry 3 crashes.

A

Akriant

n00b
Joined
Jul 7, 2012
Messages
33
Hello everyone, maybe someone had a similar problem and found some magic solution.
Problem: Far Cry 3 CTD's with "stopped working" error. When I look at the log I see either a farcry 3 dx11 engine.exe error or atixxx32.dll being faulty ( after looking up the log)

System:
i7 3930k @ 4.5ghz
MSI Big Bang Xpower II
4x8gb ddr3 1866
3x7970 @ 1170/1600
1x40gb ssd boot
2x1tb hdds for storage
Win 7 Ultimate
CPU + GPUs are water-cooled. ( 1 loop, 2 mcp 655, 2x360 rad + 1x140 rad)
AX1200W corsair PSU

What I've tried:
1. Reinstall the game on each of the HDDs
2. Tried 12.11, 13.1, 13.3 beta3, 13.4, 13.5 beta2 drivers
3. Run dx9 ( will crash, but takes more time, around 30-40 minutes, and during loading screens only, dx11 crashes within 10 minutes)
4. Run stock CPU + stock GPU speeds
5. Run all stock + ram downed down to 1333 and 11-11-11-30-2T super relaxed timings
6. Run all stock + add xtra voltage on CPUs and GPUs just in case
7. Run at single monitor and in eyefinity setup
8. Contact Ubisoft support, but they said "amd at fault" bascially

System runs prime 95 just fine, system runs 3dmark 11 on extreme, 3dmark 13 on extreme, Metro 2033 maxed out at 5670x1080 res, same res for Crysis 3, same for Heaven benchmark and Valley benchmark, same with Serious Sam 3, same with BF3.

Soooo before I go and format the ssd to get a new copy of the Windows up, any other idea why this game behaves so ?
 
Have you tried just 1x 7970?

Try underclocking.
Try swapping RAM out/around


Looked at your thread for idea's on my system lol. Got a AMD PHII x4 @3.9GHz and Nvida 570GTX and blood dragon locks up (the game not the system) after 20~40mins. Really hate the no save in mission crude. I'll be looking at the GPU overclock here in a few.
 
Sorry if it was mentioned, but have you tried running one card?
And is it installed via Uplay or Steam? If its installed via uplay try disabling the uplay overlay.

Its not AMD fault imo, as I get a lot of crashes in Blood Dragon on an 680 sli setup.
 
Are you running something like MSI Afterburner or RadeonPro?

Disable the Uplay overlay if so. They conflict and cause the game to crash at launch.
 
TheGamerZ said:
Are you running something like MSI Afterburner or RadeonPro?

Disable the Uplay overlay if so. They conflict and cause the game to crash at launch.
Click to expand...

I've disabled Uplay overlay and even disabled MSI Afterburner at startup and get a crash. Can't even get passed the first mission in time.

Here are the crash logs in EV for me:

Event ID 1000
Code: 
 Faulting application name: fc3_blooddragon_d3d11.exe, version: 0.1.0.1, time stamp: 0x516c08f3
Faulting module name: FC3_d3d11.dll, version: 0.1.0.1, time stamp: 0x516c08b6
Exception code: 0xc0000005
Fault offset: 0x00607e20
Faulting process id: 0x109c
Faulting application start time: 0x01ce47a13d65633b
Faulting application path: D:\GAMES\Steam\steamapps\common\Far Cry 3 Blood Dragon\bin\fc3_blooddragon_d3d11.exe
Faulting module path: D:\GAMES\Steam\steamapps\common\Far Cry 3 Blood Dragon\bin\FC3_d3d11.dll
Report Id: f0373815-b398-11e2-be9e-001b2143721b
Faulting package full name: 
Faulting package-relative application ID:

And Event 14:
Code: 
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\Video1
CMDre 00000001 000000c0 ff1fe204 00000004 00000084
 
Another update. Got to the first autosave finally without a crash!!

I did a clean install of 314.22... Created a profile for FC3:BD. under profile I enabled the power savings to maximum performance and also for v-sync to adaptive.

In MSI Afterburner I took GPU voltage up to 1050mv vs. 1038.

Now the weird part. The game around to 30-minute mark did go blank for a second but kicked back in with windowed mode instead of fullscreen. After that it worked fine for another 20mins or so before I had to leave.

So I'm thinking of bringing everything back up in clocks and just try to run the game in Windowed mode instead of fullscreen.



Of course it is always a good idea to have power management in "High Performance" so the cpu/gpu isn't messing with you. I've had mine set like that for awhile even with crashes.
 
Last edited:
Yeah, tried with one card, a looong time ago, and it worked, but the fps was poor-ish, as I play at 3x1080p displays.


Installed via Uplay. Yes I do have afterburner installed and running, but trying without it too - no dice. uplay in offline mode gave me xtra 15m of gameplay before crash in dx11, and up to 1h 45m in dx9 without crash strange.

Oh well, anyway, just finished the game, now I can uninstall it and forget about it.
 
If you have factory OCed cards, get still them down to the stock cards clocks. I had to under clock my PE 670, as FC3 really pushes the GPU to the limit, and it can easily overheat the card.
 
You must log in or register to reply here.
Back
Top