🛈 Announcement
Greetings! Far Cry forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game.
  1. #141
    Originally Posted by EternalCore Go to original post
    When was the last time you did a fresh install of windows?
    Quite a while... but somewhat irrelevant since quite a few new and old games install and work fine.

    Farcry2 did the same thing across multiple reinstalls of windows xp (32 bit), vista (32 bit), windows 7 (64 bit) and god knows how many driver versions, bios updates and so forth.
    Share this post

  2. #142
    Originally Posted by EternalCore Go to original post

    You might aswell try dual booting to w7 as Lots of people are having major issues with the newly released games and win8.
    i just created a dual boot with a W7 64bit version. Fresh formatted Hard drive (normal one iso SSD) with a fresh W7 installation and a fresh far Cry 3 Game installation. NO strange background processes and ... yes still crashing on the same point, with the same error code.

    Windows 7 is completely updated. Using 310.70 WHQL.

    Probleemhandtekening:
    Gebeurtenisnaam van probleem: APPCRASH
    Naam van de toepassing: farcry3_d3d11.exe
    Versie van toepassing: 0.1.0.1
    Tijdstempel van toepassing: 50d1e5f6
    Naam van foutmodule: FC3_d3d11.dll
    Versie van foutmodule: 0.1.0.1
    Tijdstempel van foutmodule: 50d1e5b3
    Uitzonderingscode: c0000005
    Uitzonderingsmarge: 005ebca1
    Versie van besturingssysteem: 6.1.7601.2.1.0.768.3
    Landinstelling-id: 1043
    Aanvullende informatie 1: 0a9e
    Aanvullende informatie 2: 0a9e372d3b4ad19135b953a78882e789
    Aanvullende informatie 3: 0a9e
    Aanvullende informatie 4: 0a9e372d3b4ad19135b953a78882e789

    I can still try the things in the start topic on the W7 installation.

    But it's quite clear though that it's a problem of Far Cry.
    It's no hardware / no software / No Windows 8 and no driver problem...
    Share this post

  3. #143
    So I get the error on both sticks of ram (took one out, left one in, and switched), the game wouldn't launch with either stick --> Uplay doesn't launch from Steam.

    When I get back from Holiday break I'll try re-installing windows. I'll also buy 2 more sticks of ram and test em.
    Share this post

  4. #144
    Originally Posted by Mukkel_NL Go to original post
    i just created a dual boot with a W7 64bit version. Fresh formatted Hard drive (normal one iso SSD) with a fresh W7 installation and a fresh far Cry 3 Game installation. NO strange background processes and ... yes still crashing on the same point, with the same error code.

    Windows 7 is completely updated. Using 310.70 WHQL.

    Probleemhandtekening:
    Gebeurtenisnaam van probleem: APPCRASH
    Naam van de toepassing: farcry3_d3d11.exe
    Versie van toepassing: 0.1.0.1
    Tijdstempel van toepassing: 50d1e5f6
    Naam van foutmodule: FC3_d3d11.dll
    Versie van foutmodule: 0.1.0.1
    Tijdstempel van foutmodule: 50d1e5b3
    Uitzonderingscode: c0000005
    Uitzonderingsmarge: 005ebca1
    Versie van besturingssysteem: 6.1.7601.2.1.0.768.3
    Landinstelling-id: 1043
    Aanvullende informatie 1: 0a9e
    Aanvullende informatie 2: 0a9e372d3b4ad19135b953a78882e789
    Aanvullende informatie 3: 0a9e
    Aanvullende informatie 4: 0a9e372d3b4ad19135b953a78882e789

    I can still try the things in the start topic on the W7 installation.

    But it's quite clear though that it's a problem of Far Cry.
    It's no hardware / no software / No Windows 8 and no driver problem...
    That error "Uitzonderingscode: c0000005 -> Exception Code: c0000005" is due to a memory issue; So Restore your Overclocked settings to default then Run this to test your ram: http://www.memtest.org/#downiso
    Also this game has memory Fault checks implemented and because Ram is tricky it can fail at random times, so if that test shows nothing then you can try and remove one stick at a time to attempt to see if one of your sticks is bad; Or you can buy New higher quality ram to get rid of the issue completely.
    Originally Posted by newfrank Go to original post
    So I get the error on both sticks of ram (took one out, left one in, and switched), the game wouldn't launch with either stick --> Uplay doesn't launch from Steam.

    When I get back from Holiday break I'll try re-installing windows. I'll also buy 2 more sticks of ram and test em.
    Roger I suggest you get higher quality ram, like from corsair: http://www.corsair.com/us/memory/int...-upgrades.html
    Share this post

  5. #145
    Memory isn't overclocked and running the game on stock didn't help.
    I got some corssair sticks its a good brand.

    Last week I tested them with mem86 and ran oke for four passes, then I stopped it.
    But
    if it was memory I should have problems with all applications and games.
    Not only with fc3.
    Share this post

  6. #146
    Originally Posted by Mukkel_NL Go to original post
    Memory isn't overclocked and running the game on stock didn't help.
    I got some corssair sticks its a good brand.

    Last week I tested them with mem86 and ran oke for four passes, then I stopped it.
    But
    if it was memory I should have problems with all applications and games.
    Not only with fc3.
    Not Necessarily because FC3 is most likely allocating memory that is normally unused because it requires more and bigger chunks to operate, thus if it hits a spot where the ram is faulty the game will Throw an exception error and crash because it couldn't read or write to the block or chunk it required to.

    So if a Stick is bad, errors such as these don't always show up until you use a heavy load on the memory. Ram is layered, like a cake for example; and a Game that requires big chunks can, and will, allocate the layers as whole layers which can fail due to faulty ram.

    I hope this helps you understand it more.
    Share this post

  7. #147
    Originally Posted by EternalCore Go to original post
    Not Necessarily because FC3 is most likely allocating memory that is normally unused because it requires more and bigger chunks to operate, thus if it hits a spot where the ram is faulty the game will Throw an exception error and crash because it couldn't read or write to the block or chunk it required to.

    So if a Stick is bad, errors such as these don't always show up until you use a heavy load on the memory. Ram is layered, like a cake for example; and a Game that requires big chunks can, and will, allocate the layers as whole layers which can fail due to faulty ram.

    I hope this helps you understand it more.
    While that is correct I've never had my farcry3 use more than 6-900 mb of memory. X3:AP on the other hand I've seen use 2.8 gb If ... my memory serves me correct.
    Share this post

  8. #148
    Originally Posted by NT78stone Go to original post
    While that is correct I've never had my farcry3 use more than 6-900 mb of memory. X3:AP on the other hand I've seen use 2.8 gb If ... my memory serves me correct.
    The longer you play it the more ram it will use and I believe it has a 3GB cap. When It gets close to 3GB it starts over-writing in areas that are no longer near where it's being accessed. But if you use fast-travel then it will clear the ram faster and load in the new data of where you are; Which is why it has a loading screen.
    Share this post

  9. #149
    Originally Posted by EternalCore Go to original post
    The longer you play it the more ram it will use and I believe it has a 3GB cap. When It gets close to 3GB it starts over-writing in areas that are no longer near where it's being accessed. But if you use fast-travel then it will clear the ram faster and load in the new data of where you are; Which is why it has a loading screen.
    The point being that other games certainly could "reach" memory errors just as easily as farcry3.

    So some people should be getting errors in more than farcry3 if it was memory problems.

    I tend to believe it's just shoddy programming.
    Share this post

  10. #150
    Originally Posted by NT78stone Go to original post
    The point being that other games certainly could "reach" memory errors just as easily as farcry3.

    So some people should be getting errors in more than farcry3 if it was memory problems.

    I tend to believe it's just shoddy programming.
    Most programs don't allocate the ram layers like FC3 is doing because they don't require big chunks of memory to operate.

    If you want another game to test out then Try GTAIV as it uses the Ram in a slimier way.
    Share this post