I've also a lot of crashes/freezes in this game with a similar hardware (gtx980 GPU and 4770k CPU).
I've encountered a similar bug, causing the crash of all games I wanted to launch in full screen after but resolved after a reboot of the pc.
Hope ubi will resolve this soon, because it's a really good game, when it runs...![]()
Same - I've got a 980 too and mine has just started (2h into the game) crashing when loading the campaign save game - at about 80% of the progress bar the process will die.
Faulting application name: FarCry4.exe, version: 0.1.0.1, time stamp: 0x547c8f31
Faulting module name: nvwgf2umx.dll, version: 9.18.13.4411, time stamp: 0x5414a27b
Exception code: 0xc0000005
Fault offset: 0x00000000008d63e7
Faulting process id: 0x18bc
Faulting application start time: 0x01d0259140a42ad5
Faulting application path: D:\Games\Uplay\Games\Far Cry 4\bin\FarCry4.exe
Faulting module path: C:\Windows\system32\nvwgf2umx.dll
Report Id: 0289ba5a-9186-11e4-8f55-50e549e1705a
This is with apparently the 1.6.0 patch.
after debugging(breakpoint), GTX980 video driver crashes here:
Name der fehlerhaften Anwendung: FarCry4.exe, Version: 0.1.0.1, Zeitstempel: 0x547c8f31
Name des fehlerhaften Moduls: FC64.dll, Version: 0.1.0.1, Zeitstempel: 0x549b10dc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001a7113e
ID des fehlerhaften Prozesses: 0xd3c
Startzeit der fehlerhaften Anwendung: 0x01d024761be156c5
and
Name der fehlerhaften Anwendung: FarCry4.exe, Version: 0.1.0.1, Zeitstempel: 0x547c8f31
Name des fehlerhaften Moduls: FC64.dll, Version: 0.1.0.1, Zeitstempel: 0x549b10dc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000009402f
ID des fehlerhaften Prozesses: 0x5f4
Startzeit der fehlerhaften Anwendung: 0x01d02469fe77741b
nice good job.
Ubisoft why you don't give your game developers more time for coding?
There were some reports from people that had similar issues after updating to the newest driver 347.09...
So it could be a coincidence and the cause for the problem is not the patch, but the driver.
Try to roll back to the previous driver 344.75, it works pretty well:
http://www.guru3d.com/files-details/...-download.html
I see that you're using older driver (344.11). According to a faulting module It seems to be a driver issue. Try to update your driver to 344.75 from the link above.Originally Posted by mabnz Go to original post
I wouldn't recommend updating to the latest 347.09 for the reasons I mentioned before...
You have a different issue, known as FC64.dll error. You can possibly find a solution in this thread:Originally Posted by OasterHasenWurm Go to original post
http://forums.ubi.com/showthread.php...-dll-Corrupted