Faulting application name: FarCry4.exe, version: 0.1.0.1, time stamp: 0x54c981af
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff8442200c3
Faulting process id: 0x1024
Faulting application start time: 0x01d047a295982d91
Faulting application path: E:\Programs\Ubisoft Game Launcher\games\Far Cry 4\bin\FarCry4.exe
Faulting module path: unknown
Report Id: d4682ade-b395-11e4-82cc-10c37b6af77a
Faulting package full name:
Faulting package-relative application ID:
from debug.log
[0213/101940:ERROR:backend_impl.cc(2157)] Corrupt Index file
[0213/101940:ERROR:cache_util_win.cc(43)] Unable to move the cache: 5
[0213/101940:ERROR:backend_impl.cc(137)] Unable to move cache folder E:/Programs/Ubisoft Game Launcher/cache/http2/ to E:/Programs/Ubisoft Game Launcher/cache\old_http2_000
[0213/101940:ERROR:backend_impl.cc(224)] Unable to create cache
have you tried to verify your game files? ..it may help
info on how to do so can be found here
http://forums.ubi.com/showthread.php...ake-it-sticky)
I am running afterburner and rivatuner.Originally Posted by WID992007 Go to original post
Please note, I have been for over 40 hours of game time.
try the game without those processes running ..you may need to reconfigure them with the latest patch as they have been known in the past to cause issues with this title
as its been documented many times on both these forums as well as the steam forums that exiting out of those will make the game run perfect ..and in some cases people only had to reconfigure afterburner to set FC4 up some how as a low priority or some thing .. dunno as i don't use em
well, that worked. thanks and have a good weekend!Originally Posted by WID992007 Go to original post
You don't have to turn MSI AB off entirely - just turn off the on-screen display via RTSS settings -
You will have to turn it off anyway to be able to run Uplay overlay.
I found out that MSI AB version 4.1.0 is incompatible with FC4 when you turn RTSS OSD on. I rolled back to 4.0.0 and it's working again.
You can also try to set application detection level to "Low" - it worked for some people to enable OSD with version 4.1.0.
Originally Posted by akunamatataa Go to original post
see i thought knew some one i knew posted about that
hmmm you should add that to your guides Sir .. i wish Ubi would sticky your thread already about the file verify