Far Cry 2, Crashing and Damaging Nvidia drivers

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.


I heard a few times that the game doesn't like overclocked hardware. Seeing your problem, it definitely seems like GPU overclocks are bad news for FC2. I was just playing and it took ~35 minutes and then I crashed. It is like clockwork. I am going to downclock my 4870s and see what happens. I am currently running them at 790MHz. After the 1st crash it is usually like every 20minutes for the next crashes so we will see what happens.


 



well here is the weirdest thing, my system plays fallout 3 at a high level without any tof the crashes, bsod's or nv_disp errors causing my drivers to be damaged.
 
Yeah same here. I am overclocked everywhere but no other game crashes even after hours of running. Temps never spike up....

Dannyboy and awop are probably right about the memory leak.
 
Ok People, I had a similar problem with Crysis Warhead now, has this thing with Far Cry 2 completely fried my drivers or card? or is it a completely different problem?
 
Don't worry. The game could not possibly fry your card unless there was already something physically wrong with it. As for the drivers; all of us are having issues.
 
I went and did a analysis of the game as I played. Although I have no clue what to do with the information. So I am posting it here... and just maybe someone can make sence of it and it might help to identify with the problem. Here is my log.

Loading control script C:\Program Files (x86)\DebugDiag\scripts\CrashRule_Process_FarCry2.exe.vbs
DumpPath set to C:\Program Files (x86)\DebugDiag\Logs\Crash rule for all instances of FarCry2.exe
[11/14/2008 10:26:41 AM] Process created. BaseModule - C:\Program Files (x86)\Ubisoft\Far Cry 2\bin\FarCry2.exeBaseThread System ID - 3648
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3652
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 1036
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3000
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2984
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2968
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2996
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3168
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3172
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3528
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3520
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3524
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3560
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2372
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 348
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2488
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3228
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2768
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3224
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 744
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2668
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 560
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 736
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3312
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 3040
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 2040
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\ntdll.dll loaded at 0x7d600000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\kernel32.dll loaded at 0x7d4c0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\USER32.dll loaded at 0x7d930000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\GDI32.dll loaded at 0x7d800000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\ADVAPI32.dll loaded at 0x00300000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\RPCRT4.dll loaded at 0x7da20000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\Secur32.dll loaded at 0x7d8d0000
[11/14/2008 10:26:41 AM] C:\Program Files (x86)\Ubisoft\Far Cry 2\bin\Dunia.dll loaded at 0x10000000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\WS2_32.dll loaded at 0x71c00000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\msvcrt.dll loaded at 0x77ba0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\WS2HELP.dll loaded at 0x71bf0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\ole32.dll loaded at 0x77670000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\OLEAUT32.dll loaded at 0x00910000
[11/14/2008 10:26:41 AM] C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6B128700\MSVCP80.dll loaded at 0x7c420000
[11/14/2008 10:26:41 AM] C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6B128700\MSVCR80.dll loaded at 0x78130000
[11/14/2008 10:26:41 AM] C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.3790.4278_x-ww_AD682293\gdiplus.dll loaded at 0x4dd60000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\dbghelp.dll loaded at 0x6d580000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\VERSION.dll loaded at 0x77b90000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\DINPUT8.dll loaded at 0x6cef0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\d3d9.dll loaded at 0x4e010000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\d3d8thk.dll loaded at 0x6da60000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\WINMM.dll loaded at 0x76aa0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\d3dx9_38.dll loaded at 0x009a0000
[11/14/2008 10:26:41 AM] C:\Program Files (x86)\Ubisoft\Far Cry 2\bin\EAX.DLL loaded at 0x003b0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\XINPUT1_3.dll loaded at 0x003d0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\SETUPAPI.dll loaded at 0x770e0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\IPHLPAPI.DLL loaded at 0x76cf0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\PSAPI.DLL loaded at 0x76b70000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\WININET.dll loaded at 0x46a70000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\SHLWAPI.dll loaded at 0x00d70000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\Normaliz.dll loaded at 0x003f0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\iertutil.dll loaded at 0x46300000
[11/14/2008 10:26:41 AM] C:\Program Files (x86)\Ubisoft\Far Cry 2\bin\binkw32.dll loaded at 0x18000000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\CRYPT32.dll loaded at 0x761b0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\MSASN1.dll loaded at 0x76190000
[11/14/2008 10:26:41 AM] C:\WINDOWS\WinSxS\x86_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.3959_x-ww_D1A2C081\WINHTTP.dll loaded at 0x4e7c0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\SHELL32.dll loaded at 0x7c8d0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\DSOUND.dll loaded at 0x73e50000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\IMM32.DLL loaded at 0x7dee0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\WinSxS\WOW64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_5FA17F4E\comctl32.dll loaded at 0x7dbd0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\rsaenh.dll loaded at 0x68000000
[11/14/2008 10:26:41 AM] C:\WINDOWS\SysWOW64\MSCTF.dll loaded at 0x4b3c0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\apphelp.dll loaded at 0x75e60000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\msctfime.ime loaded at 0x4dc30000
[11/14/2008 10:26:41 AM] C:\WINDOWS\System32\mswsock.dll loaded at 0x7db30000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\DNSAPI.dll loaded at 0x76ed0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\System32\winrnr.dll loaded at 0x76f70000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\WLDAP32.dll loaded at 0x76f10000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\rasadhlp.dll loaded at 0x76f80000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\DDRAW.dll loaded at 0x73860000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\DCIMAN32.dll loaded at 0x73b30000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\HID.DLL loaded at 0x684b0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\WINTRUST.dll loaded at 0x76bb0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\imagehlp.dll loaded at 0x76c10000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\CLBCatQ.DLL loaded at 0x777b0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\COMRes.dll loaded at 0x77010000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\xpsp2res.dll loaded at 0x050d0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\D3DIM.DLL loaded at 0x6d9e0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\nvogl32.dll loaded at 0x69500000
[11/14/2008 10:26:41 AM] C:\Program Files (x86)\DebugDiag\LeakTrack.dll loaded at 0x071c0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\nvapi.dll loaded at 0x037a0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\wdmaud.drv loaded at 0x72d70000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\msacm32.drv loaded at 0x72d60000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\MSACM32.dll loaded at 0x77b70000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\midimap.dll loaded at 0x77b60000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\KsUser.dll loaded at 0x73e20000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\nvLsp.dll loaded at 0x0abb0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\msapsspc.dll loaded at 0x71e00000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\MSVCRT40.dll loaded at 0x78080000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\hnetcfg.dll loaded at 0x5f270000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\msnsspc.dll loaded at 0x71e20000
[11/14/2008 10:26:41 AM] C:\WINDOWS\SysWOW64\schannel.dll loaded at 0x76750000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\USERENV.dll loaded at 0x76920000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\NETAPI32.dll loaded at 0x71c40000
[11/14/2008 10:26:41 AM] C:\WINDOWS\System32\wshqos.dll loaded at 0x57b60000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\wshtcpip.dll loaded at 0x71ae0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\dssenh.dll loaded at 0x68100000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\cryptnet.dll loaded at 0x73ca0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\system32\SensApi.dll loaded at 0x722f0000
[11/14/2008 10:26:41 AM] C:\WINDOWS\syswow64\urlmon.dll loaded at 0x44130000
[11/14/2008 10:26:41 AM] C:\Program Files (x86)\Yahoo!\Messenger\idle.dll loaded at 0x60300000
[11/14/2008 10:26:41 AM] C:\Program Files (x86)\Yahoo!\Messenger\MSVCR71.dll loaded at 0x7c340000
[11/14/2008 10:26:41 AM] Thread created. New thread system id - 844
[11/14/2008 10:26:41 AM] Initializing control script
[11/14/2008 10:26:41 AM] Clearing any existing breakpoints
[11/14/2008 10:26:41 AM]
[11/14/2008 10:26:41 AM] Current Breakpoint List(BL)
[11/14/2008 10:26:41 AM] Thread exited. Exiting thread system id - 844. Exit code - 0x00000000
[11/14/2008 10:27:07 AM] Thread exited. Exiting thread system id - 2040. Exit code - 0x00000000
[11/14/2008 10:27:09 AM] First chance exception - 0x406d1388 caused by thread with system id 3648
[11/14/2008 10:27:09 AM] Thread created. New thread system id - 3808
[11/14/2008 10:27:09 AM] First chance exception - 0x406d1388 caused by thread with system id 3808
[11/14/2008 10:27:09 AM] First chance exception - 0x406d1388 caused by thread with system id 3648
[11/14/2008 10:27:09 AM] Thread created. New thread system id - 3824
[11/14/2008 10:27:09 AM] First chance exception - 0x406d1388 caused by thread with system id 3824
[11/14/2008 10:27:09 AM] Thread exited. Exiting thread system id - 3824. Exit code - 0x00000000
[11/14/2008 10:27:11 AM] Thread exited. Exiting thread system id - 3808. Exit code - 0x00000000
[11/14/2008 10:27:11 AM] First chance exception - 0x406d1388 caused by thread with system id 3648
[11/14/2008 10:27:11 AM] Thread created. New thread system id - 3748
[11/14/2008 10:27:11 AM] First chance exception - 0x406d1388 caused by thread with system id 3748
[11/14/2008 10:27:12 AM] Thread exited. Exiting thread system id - 736. Exit code - 0x00000000
[11/14/2008 10:27:12 AM] First chance exception - 0x000006c5 caused by thread with system id 3648
[11/14/2008 10:27:12 AM] First chance exception - 0x000006c5 caused by thread with system id 3648
[11/14/2008 10:27:12 AM] First chance exception - 0x406d1388 caused by thread with system id 3648
[11/14/2008 10:27:12 AM] Thread created. New thread system id - 3840
[11/14/2008 10:27:12 AM] First chance exception - 0x406d1388 caused by thread with system id 3840
[11/14/2008 10:27:12 AM] First chance exception - 0x000006c5 caused by thread with system id 3648
[11/14/2008 10:27:12 AM] Thread created. New thread system id - 3856
[11/14/2008 10:27:12 AM] First chance exception - 0x000006c5 caused by thread with system id 3856
[11/14/2008 10:27:12 AM] Thread exited. Exiting thread system id - 3856. Exit code - 0x00000000
[11/14/2008 10:27:34 AM] Thread exited. Exiting thread system id - 3748. Exit code - 0x00000000
[11/14/2008 10:30:17 AM] Thread exited. Exiting thread system id - 3652. Exit code - 0x00000000
[11/14/2008 10:31:47 AM] Thread exited. Exiting thread system id - 2968. Exit code - 0x00000000
[11/14/2008 10:32:12 AM] Thread exited. Exiting thread system id - 560. Exit code - 0x00000000
 
I'm noticing a trend sort of anyways, A lot of you that are experiencing crashes have Muli-GPU setups.

For those of you that do have more than 1 Video Card, have you tried running the game(s) with just 1?
 



I have a single BFG 8800 GT and I still freeze in safe mode. Generally I can CTRL+ALT+DEL outta the game then click on it to find it unfrozen. but it still freezes later, and eventually ACTL+ALT+DEL does nothing.
 
I am also running it on a single 8800 GTX. I have reintalled the new beta 180.43 driver after a driver sweeper run, Crysis Warhead is running like clock work, I have n't tried Far Cry 2 yet for the fear of reinstalling the driver once again...
Has anybody tried contacting Ubisoft?
 
There is a v1.01 patch out. I hope it helps... can anybody install and tell us what happens? I have currently uninstalled far cry 2, so I can't
 
Well, I am running on a single "EVGA 320-P2-N815-AR GeForce 8800GTS 320MB 320-bit GDDR3"

I am going to see about that patch, problem is I am using the steam version so I dunno if they have it or not... I will be sure to respond if I get it working.
 
Anyone brought this up on the official FC2 forums? There doesn't seem to be any mention of this in the list of issues being addressed in the upcoming patch.
 
Hey i have a pentium 4 HT and geforce 8500 gt.
The game runs well at 1024X768 resolution(My monitor can only support upto that resolution only).........All other settings are high
 
Hey guys, not sure if you have managed to resolve your problems yet but I stumbled upon this thread and thought I'd give a bit of input. I had been experiencing very similar issues with Far Cry 2 for ages (we're talking several months) and I simply couldn't figure out what the problem was, although I was convinced it had something to do with SLI as it only seemed to concistently crash when it was enabled. But lets cut to the chase, I decided I'd experiment by putting a fan (just a typical office-type fan) next to the computer (side panel's off) and give the game a whirl and now the problem seems to be solved. It's important to remember that sandbox games (i.e. FC2, GTA4) are extremely cpu intensive. I downloaded speedfan to get an idea of system temperatures and, after only around 10 minutes of playing FC2, my cpu (core 2 duo E6850) temp had jumped from 50 to 65...with TWO external fans aswell!! If you do decide to test this it would be worth your while to give the inside of your pc a clean out as nothing builds heat more than layers of dust. Please remember, this has worked for me but is absolutely NOT guaranteed to work for anyone else (unfortunately nothing in life is that simple apparently), I just thought I'd share as it was an issue that had been bugging me for months on end!! Hope it helps a few of you!
 
Dell XPS M1710 NVIDIA 7950GTX SOLUTION!!!!(it really works)

I have a crazy fix for your problem. The chip on the NVIDIA 7950gtx on your dell is bad. I have the same computer and video card. Do the research and you will find that this fix works. The fix was found on a French website. Since the card cannot be replaced with anything else but a 7950gtx I figured what could I lose. My screen would display green dots then go blank at boot up.

It's crazy but here is what I just finished doing 30 minutes ago.

-take your card out and remove all the black metal guard on the bottom and the heat sink on the top
-clean the thermal compound off of the GPU
-preheat your oven to 300 degrees for 10 min
-place the video card on a sheet with wax paper(don't allow it to touch metal)
-place it in the oven for three minutes, flip the card over and put it back in for three more minutes
-allow it to completely cool
-install it into your computer and use silver thermal compound( found at staples..the company that makes it is called antec) follow the antec's instructions
-turn on your computer and it should be fixed(for how long? I have found a post that someone is going on 6 months and counting....for me it has been an hour and counting)


I guess the theory is the heat cycles tend to get the NVIDIA chip out line and cooking it in the oven exactly by the instructions seems to line things back up....in layman's terminology...I would like to find the exact reason for the way the fix works but trust me it does. if you have questions feel free to email me at my yahoo mail.... vincent996rs



 
Far Cry 2 Concerning the PC version:

Many people, including myself, had terminal crashes when playing Far Cry 2. My game crashed at 21% of completion. In that game I accumulated a very large number saved games. I think this makes the game crash and glitch.

When I restarted the game I was able to complete it without crashes or terminal glitchs. The only thing I did different was to limited myself to only a few saves. When ever I wanted to save after the first 5 saves I overwrote previous saves instead of creating a long list of new saves. This means I never used the quick save function (F6) nor the "Save and exit" choice when exiting at bus stations.

 
Status
Not open for further replies.