So, I'll be brief and go by points.
1. I have read the sticky for the possible fixes.
2. Far Cry 3 crashes during loading screens when I fast travel or enter/exit missions. happens around every 20-40 minutes.
3. crash log is in russian, so I've just used google translate since it's just formal english and such:
Faulting application name: farcry3_d3d11.exe, version: 0.1.0.1, time stamp: 0x50d1e5f6
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, timestamp 0x4df2be1e
Exception code: 0xc0000005
Fault offset: 0x00001ed7
Faulting process id: 0x13b0
Faulting application start time: 0x01ce096eb810e846
Faulting application path: E: \ Games 2 \ FarCry 3 Game \ bin \ farcry3_d3d11.exe
Faulting module path: C: \ Windows \ system32 \ MSVCR100.dll
Report code: 6f8a8d3a-7565-11e2-9ec9-d43d7e1870a4
4. MSVCR100.dll - indicates I might have issues with Microsoft Visual C++ redist. I have all of them installed from 2005 to 2010. I've checked the integrity via cmd sfn/scannow and found no issues there. I've reinstalled the latest ones just in-case, and rescanned - no issues found. I've also reinstalled net.framework 4.0 and 4.5
5. 0xc0000005 - that indicates potential RAM issues. I've tested my ram previous with memtest. And did this again overnight run - no issues. I've took down it from 1866 to 1600 - didn't help. I took down the speeds to 1333 and put relaxed 11-11-11-30-2T timings - didn't help
6. I've tried various drivers ( 12.11, 13.1, 13.2 betas)
7. I've tried to set my OC back to stock
8. I've tried to add voltage to CPU
9. I've tried to add voltage to GPU core and GPU mem. ( I would assume 1.2v for reference 925/1375 clocks is an overkill for stability)
10. I've tried to reinstall FC3 on a different hard drive
11. I've tried to reinstall FC3 from Uplay as opposed to distributive that ubisoft provided the first time I purchased the game
12. I've closed all other programs ( kaspersky, steam, origin, afterburner etc) to make sure FC3 is not conflicting with them
13. I've tried to add admin rights to FC3 dx11 exe.
14. I've tried to run the game without eyefinity.
15. GPUs and CPU are watercooled in a custom loop. Temps on GPUs under load don't exceed 45c. So it's not an overheating issue
16. GPUs are recently "checked" by running 3dmark 11 maxed out settings , 3dmark 13 trial vers., Unigine 3.0 maxed out + maxed out tessellation ( ran that for 5h straight) + Unigine 4.0 today
17. CPU is checked via Prime95 and OCCT multiple runs for 12h each
18. This is the only game that behaves so.
System specs:
i7 3930k @ 4.5 ghz / stock ( tried both as mentioned above). Prime95 and OCCT stable.
32gb ddr3 1866 11-11-11-30-2T memtest and Prime95 stable
3x7970 @ 1185/1525 @ 1.23v / stock ( tried both, as well as stock speeds + 1.2v)
Win 7 Ultim 64bit
13.1 WHQL drivers
Any advice ? any help ? been having this issue since release date
Sounds like its not a hardware problem given all the (un)tweeking you did and its still reproducible. Which is good in some ways but bad in others... because it's probably some software interoperability/compatibility issue. If you haven't opened a ticket with Ubisoft support you probably should and provide more info about software drivers and services on your system. Maybe they can spot some incompatible thing in there.
The cruntime is crashing trying to access memory at an invalid address, the instruction that generates the bad mem access is at this location in the .dll, 0x00001ed7. A search of that offset shows that a good number of programs end up crashing here. Probably bad inputs to some std c library function that expects a pointer to valid data of some kind but is given a non-sense pointer by the calling application code. Hopefully they have some kind of crash reporting system and can get a call stack given the report ID, I'd definitely pass that number along to the support guys too.
Good luck in finding a resolution.