Sign in with
Sign up | Sign in
Your question
Closed

Far Cry 2, Crashing and Damaging Nvidia drivers

Last response: in Video Games
Share
October 26, 2008 8:08:00 PM

Hi all,
I downloaded and installed far cry 2 on Friday off of Steam. I really was starting to enjoy the game when about 30 minutes into the game it froze then the screen flashed blue then it went back to the frozen game and I couldn't do anything but ctrl-alt-delete and end the process via keyboard control. Windows Vista gave me a "NVLDDMKM" failed and has recovered. If I try to play the game it will immediately give me issues upon loading up the main menu. I then would have to reinstall my nvidia driver to get it to play again for a short period of time. I have tried the new 180.42 and 43 beta drivers as well as the older 178.24. I have tried both Direct X 10 and 9, I have fiddled around with HDR and other video setting to see if it was a specific cause, but to no avail. I have been searching for the solution and tried playing in windowed mode as well as switching from windows aero to windows vista classic desktop mode as suggested by some on other forums. There was a time when Dark messiah of Might and magic came out on steam and I was having the same issues, but then it must have been addressed in a patch because I no longer have the issues with any games I play but this one. I have heard that this was an issue with Nvidia but was hoping someone might be able to help anyway...Thanks


My specs are...

ASUS P5K-E/WIFI-AP LGA 775 Intel P35 ATX Intel Motherboard
Intel Core 2 Duo E8400 Wolfdale 3.0GHz 6MB L2 Cache LGA 775 65W Dual-Core Processor
EVGA 320-P2-N815-AR GeForce 8800GTS 320MB 320-bit GDDR3 PCI Express x16
G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)

Thanks in advance
October 26, 2008 10:15:01 PM

I would keep trying other things, sounds like it's Steam, I was considering getting it on Steam, but decided against it and pre-ordered it from GameStop. Try re-installing the game if possible and check the registry to make sure it's gone. I havn't had any problems like that yet, although I didn't get it on Steam, and don't have Vista.
October 27, 2008 5:30:18 AM

Its not Steam. Do a complete uninstall of your drivers. I mean complete. Uninstall, restart into Safe Mode and run a program called Driver Cleaner to get rid of the extra traces. Restart and install the latest ones. Then try again.
Related resources
October 27, 2008 11:33:10 AM

Use the beta drivers, the latest WHQL have issues with Far Cry 2. Do a driver sweep and re-install the beta's.
October 27, 2008 11:44:38 AM

Thanks guys, I will give this a shot when I get home from work today.
October 27, 2008 3:50:44 PM

I must admit - my PC has been stable for a while now and is a total beast but i too got a BSOD yesterday in Vista 64 Ulti. My first blue screen is ages.

So i was wondering if it was just memory leaks in the first version of FC2 or something similar.
October 27, 2008 11:34:56 PM

Well I tried cleaning out the drivers and installing them fresh and I am still crashing. Hopefully they will patch the game or something unless anyone else has some ideas. Thanks Anyway.
October 28, 2008 12:18:59 PM

I got the latest nvidia beta drivers last night, uninstalled my current nvidia drivers, rebooted into safe mode, used Driver Cleaner on Nvidia, rebooted and installed the new beta drivers. Played for about 5 hours with no lag, bugs, stalls, glitches or BSODs of any kind. The game ran much better than before.

So, i guess they were actually optimised for FC2 :) 

Oh, and by the way - i swapped down to DX9 late last night and apart from the obvious fps improvement, i didnt notice any issues - not to mention the more important fact that i also didnt notice any difference/decrease in graphics quality...

DX10 sucks balls hard. What a load of BS for sure!
October 28, 2008 11:20:08 PM

Yeah, I noticed the graphics thing as well. We must have had different issues though because I was able to play for about an hour then it crashed on me... Dx10 ran like crap when i tried it which is funny because in crysis it runs better than DX9 for me....strange.
October 29, 2008 9:40:25 AM

@ Sarkamen

Ok i played far cry for about 25 mins before it crashed out and after a re-boot my pc giving me an error with my Nvidia Go 7900GS card. The Error was:

nv4_disp (The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop.)


This has now completely fried my VGA card and is not covered under guarantee so ppl beware of this title.
October 29, 2008 11:07:49 AM

Ah, the crashes emerge. I have a 4870 but I get crashing too. In Vista 32 after about 30-45 min of playing the game will stutter for a couple of seconds then close down and I will be at my desktop. No error messages though or Vista crashing. I can start it back up and play for another 40 minutes or so.

It is strange that you NV card holders are getting it worse though. Wonder if this has to do with their pseudo DX10.1 support. I definitely think there is a stability issue with the game though. I will get massive stuttering if I bump up to 4xAA but the FPS come out fine. Sort of odd.

XPS M1710 said:
@ Sarkamen
Ok i played far cry for about 25 mins before it crashed out and after a re-boot my pc giving me an error with my Nvidia Go 7900GS card. The Error was:
nv4_disp (The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop.)


This has now completely fried my VGA card and is not covered under guarantee so ppl beware of this title.


Do you see the BIOS screen when you start up? I have never heard of physical damage from a crash so I am just curious what state your card is in.
October 29, 2008 1:41:27 PM

SpinachEater said:
Ah, the crashes emerge. I have a 4870 but I get crashing too. In Vista 32 after about 30-45 min of playing the game will stutter for a couple of seconds then close down and I will be at my desktop. No error messages though or Vista crashing. I can start it back up and play for another 40 minutes or so.

It is strange that you NV card holders are getting it worse though. Wonder if this has to do with their pseudo DX10.1 support. I definitely think there is a stability issue with the game though. I will get massive stuttering if I bump up to 4xAA but the FPS come out fine. Sort of odd.



Do you see the BIOS screen when you start up? I have never heard of physical damage from a crash so I am just curious what state your card is in.



the bios screen never appeared, i was running the latest MoBo firmware and drivers. the VGA card has gone up the spout, but i have had a new 7950 gtx 512mb ram fitted this morning so i will test again. I can't say whether it's the game or the infamous Nvidia GPU overheating issue. i have done a complete format and reinstalling atm.

read this link: http://direct2dell.com/one2one/archive/2008/08/18/nvidi...

Once i get the game up and running via my bare bone system i will post some results.
October 29, 2008 7:59:46 PM

Ok after loads of updates and my new Nvidia 7950GTX 512mb VGA things are even worse

this is my system specs:

PC, Dell XPS M1710, 2Gig Ram, Nvidia 7950
GTX 512mb VGA. Dual Core Pentium T2600 2.16GHz 994MHz.

After the annoying install and sonys/Ubisofts spyware/malware nonsense, the game fired up. i went into the settings and went about lowering them all to medium and low and reducing the resolution to 1027 by 786, as i was in the settings window before i had chance to change the resolution blue flecks/blocking appeared at the top and bottom of the screen, then my system completely crashed giving me this error:

on a black screen it read:




Your system automatically shut powered off because it became warmer than expected. This may have been caused by:

0) operating or storing the system in an environment where the ambient temperature is too high, or
0) obstructing the air flow from the system fan vents.

If this problem reocurres, please call dell support with error code #M1004
strike F1 to continue, F2 to run setup.






After the error i installed S.T.A.L.K.E.R. Clear Sky and it ran on full, but slow settings for over an hour without any shut down of my system or over heating errors, i believe there is a serious problem with Far Cry 2 and needs to be addressed very soon. If not a complete recall of the title.
October 29, 2008 9:13:07 PM

All i know is I am glad I'm not alone.....
October 30, 2008 10:34:03 AM

Sarkamen said:
All i know is I am glad I'm not alone.....



After i played Far Cry 2 last night with the new card and got the nv4_disp error yet again, i then played crysis and it crashed with the same error, i completely removed the Nvidia drivers (using Drive cleaner Pro) and then reinstalled them, and after a night of playing crysis and stalker without a single crash or my temperature rising (monitoring with SpeedFan 4.35) i'm starting to think that Far Cry 2 is damaging the Nvidia drivers.

i am running the latest drivers for my system:
http://www.nvidia.co.uk/object/winxp_notebook_175.32_wh...

Version: 175.32 WHQL

My System is; Dell PC XPS M1710, 2Gig Ram, Nvidia 7950GTX 512mb VGA. Dual Core Pentium T2600 2.16GHz 994MHz. Win XP Home SP3.
October 30, 2008 11:34:33 AM

The 175 drivers are a bit on the old side...
October 30, 2008 6:10:07 PM

Played last night for 4 hours with nvidia drivers 180.43 with no problem, until I tried DX 10, laggy, no diference in visuals maybe because medium in visual, very high in performance, system specs Core 2 Duo T5570, Nvidia 8600 GT, 1200X800 resolution, on a Dell Inspiron 1520, Ranch Benchmark 26 FPS average, and have the DVD version installed, not the Steam, maybe that is the problem, never downloaded form Steam
October 31, 2008 1:46:53 PM

I've been getting the same crash with non steam Far Cry 2, Vista 64 and 8800 GTS 2x SLI

Few things I've noticed:

Seems like the crash only seems to happen if I push the graphics settings past a certain point. (ie not on 2x anti aliasing but 4x and up)

This game runs the cards hot!!! Interestingly, it seems that the 2nd Sli card is the one it seems to really heat up (verified by reversing cards). Even more interesting is that while monitoring, the temp seemed to shoot up incredibly fast causing an almost instant crash. On 8x antialiasing, the second the fire came into view in the opening jeep ride the machine crashed.

All this coming from a watercooled rig that has never hit over 60 degrees celsius in any other games.

I would say at these temps, your hardware could be at risk. In my opinion without definite answers this game is not worth playing.

rich
October 31, 2008 6:07:49 PM

hmmm, I have dual 8800GTX's running SLI and at native 1920x1080 FSAA2 and everthing else set to max with HDR and Bloom the game runs very well but like you guys after about 20 - 30 minutes the game begins to stutter and than I get a memory dump and the computer restarts.

Also after a restart on one occassion the system did not come back stable but would freeze opening windows and checking on CPU usage and running process showed 99% idle and no processes where locked? I had not launched any games. I had only started Outlook and Agent. I could not close anything and finally had to force shutdown.

Thinking it might have been bug related I ran full scans and my arsenal of utilities but nothing came up. Another restart and it cleared up? I have run the game 3 times and all three times it crashes after about 20 - 30 minutes. Once the audio de synced from the video and than it crashed. Another time after I ran the sleep timer and the shadows began spinning around as the time changed.

November 1, 2008 11:47:40 AM

I played and finished the game on Max settings in DX10, and Have played for hours at a time without so much as a system crash, the game on 1 occasion crashed but after restarting it, ran fine. I am currently playing through a second time(surprisingly the map seems different) using DX9 on max settings w/ 2xAA. (Specs in sig.)

The only driver related problem I had was 180.42's made the Editor inoperable it would crash immediately upon opening, switching back to my old drivers fixed it, I installed the game for my friend after installing his new video card and power supply(He's functionally retarded when it comes to computers, also upgraded for this game and lol Bioshock from a 7800GT) Used the 180.43's and the editor ran fine so i updated mine to them as well and it works on mine as well.

Both copies are Retail, and neither of us has had issues.
His specs are similar, E2160 @ 3ghz/GA-P35-DS3L/4gb DDR2-800/9800GTX/Vista Ultimate 64bit
I have PSU envy though, he (at my recommendation) got a Corsair TX750.

edit:
OH and both cards(8800 and the 9800) are running @ 730/1890/1000 but his memory is 100mhz faster coming out @ 2200 DDR while mine is 2000 DDR and both run very close Temp wise. Mine sees at max 56c in my colder room and his unheated shop room would provide similar since our idle temps were close.
November 1, 2008 1:44:04 PM

I tried some of the suggestion I found on line like, disabling FSAA, forcing sync Off but it is still crashing although not nearly as bad as it only goes to the desktop now as opposed to rebooting the whole system. I also tried the widescreen fix at guru3d.com and it works really well, btw.

It must be game related as Crysis Warhammer and Stalker ClearSky run perfectly.

I game under XP32 with latest 178.24 drivers (don't want to be someone else's beta tester). My temps are not spiking on either card so I don't believe its related to overheating as I have heard others suggest. Its still a mystery but eventually someone will figure it out.
November 6, 2008 7:18:44 AM

i keep getting bsd nv4_dsp error as well... lost planet, civilization4, farcry2...i have repeatedly installed/uninstalled drivers and no luck. its not just farcry2... i think its nvidia... it happened to me in lost planet before i got farcry2 so...
November 6, 2008 10:46:54 AM

Hearing a lot about these issues, did you happen to download the hotfixes and update your drivers (non-beta)?
November 6, 2008 10:50:03 AM

Just thought i would add my 2c, i found something quite interesting.
I own a 8800GTX Extreme OC and generally underclock the card while working to about 50%. I'm running the latest nvidia BETA drivers which i downloaded about 2 days ago.

I had forgot i did this and was playing farcry 2 with mostly very high and some Ultra settings receiving around 40-50fps, not too shabby. No problems, no crashing, the game ran nicely besides the lower fps which i thought was strange (without realising the under clocked card).

I realised my mistake and reset the card to factory defaults, alas 20 minutes in-game with 1680x1050 all settings ultra-high (130fps :D ) the nvidia drivers crash bringing me to the desktop in a horrible loop of driver failures. Forcibly restart the system, start up the game - 20 minutes or so in and again a crash.

I have just underclocked the card to 550Mhz Core and will try this out in the morning to see if the crashes still occur. Funnily enough whenever i select "View System Information" within the nvidia control panel i receive a BSOD.

Hopefully a newer version will be released as i was actually enjoying the game, burning the enemy out of their little huts.
November 10, 2008 11:46:01 PM

My system shows the same issues.

After playing the game for a very short amount of time, it crashes to the desktop with no error code or output.

The only thing I can think is that the game and drivers have a memory leak. There are so many differences in hardware and software and the only constant is the game itself. The problem is most certainly driver:game related.

We have ruled out provider: Steam and Retail DVD have the same issue.
We have ruled out video hardware: Different cards and brands, ATI and NVIDIA all have the issue.
We have ruled out OS: XP and Vista have the issue.
We have ruled out video options: All different settings in and out of game have been tried to no avail.
We have ruled out sound card options and drivers:Same reason as video options, video hardware and drivers; too many variables in brand, versions and settings with no change in results.
Drivers are most likely ruled out due to inconsistency: Beta users and non-beta users alike have the issue as well as older and newer releases of the drivers themselves.

The only known constant is that we all have the game. It is probably some poorly written code within the game engine or something of the like. We must wait for a patch while being as loud as possible the the ear of the developer: Ubisoft. Think of the things you have tried and use elimination with others as well. We are looking for constants to find the cause.

I will be watching this forum to see if anyone has figured it out. Sometimes users release fixes so keep your eyes out and keep everyone posted.

Don't forget to scream at Ubisoft for a fix. You paid for working product. I know I meet the minimum requirements and I know enough to know a faulty piece of software.

Good luck everyone.

By the way, underclocking is just as bad as overclocking; instability can be cause either way.


Games that run fine on my system on high settings include:

Mass Effect
Crysis
Sins of a Solar Empire
Counter-Strike 1.6
Counter-Strike Condition Zero
Counter-Strike: Source
Half-Life
Half-Life 2
Half-Life 2: Episode 1
Half-Life 2: Episode 2
Zombie Panic: Source
Call of Duty 4
Assassins Creed
World of Warcraft
Oblivion
Need for Speed: Most Wanted
Need for Speed: Pro Street
Dead Space
Rainbow Six: Vegas 2
Front Lines: Fuel of War
Hitman: Blood Money
Midieval 2 Total War
The Witcher
Battlefield 2
Battlefield 1942
Titan Quest
Team Fortress 2
Portal
AND MORE

My System is:

Custom Build
Asus Maximus X38 Motherboard
Intel QX6850 Quad-Core Extreme @ 3.5GHz (Water Cooling by Danger Den via 2X 120mm Radiator)
8GB DDR3 RAM
(2X) 750GB Seagate SATA2 3Gb/s
1GB Nvidia GeForce 9800 GX2
Creative SB X-Fi Fatality Platinum
Turbo-Cool 1200W PSU
Windows Vista X64 Ultimate
November 11, 2008 12:53:13 AM

Extreme43 said:
Just thought i would add my 2c, i found something quite interesting.
I own a 8800GTX Extreme OC and generally underclock the card while working to about 50%. I'm running the latest nvidia BETA drivers which i downloaded about 2 days ago.

I had forgot i did this and was playing farcry 2 with mostly very high and some Ultra settings receiving around 40-50fps, not too shabby. No problems, no crashing, the game ran nicely besides the lower fps which i thought was strange (without realising the under clocked card).

I realised my mistake and reset the card to factory defaults, alas 20 minutes in-game with 1680x1050 all settings ultra-high (130fps :D ) the nvidia drivers crash bringing me to the desktop in a horrible loop of driver failures. Forcibly restart the system, start up the game - 20 minutes or so in and again a crash.


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.


November 11, 2008 6:32:39 AM

SpinachEater said:
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.
November 11, 2008 11:22:05 AM

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.
November 12, 2008 11:11:12 PM

Guys same problem here too...

Has anybody started to play around with the Far Cry 2 files???
November 12, 2008 11:33:41 PM

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?
November 13, 2008 2:18:00 AM

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.
November 13, 2008 10:16:15 AM

No, I mean do I need to re-install my Drivers? And should this problem occur with Crysis Warhead as well?
November 13, 2008 9:36:39 PM

Shouldn't be a problem.
November 14, 2008 5:13:18 PM

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
November 14, 2008 5:21:11 PM

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?
November 14, 2008 9:22:16 PM

cliffro said:
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.
November 14, 2008 10:43:16 PM

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?
November 15, 2008 12:09:46 PM

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
November 15, 2008 2:25:45 PM

Well Today I was browsing the FC2 forums over @ ubi and found a thread on SLI and FC2 http://forums.ubi.com/eve/forums/a/tpc/f/1521068375/m/9...

Apparently some of them are able to get it working while others aren't. The game is also very apparently buggy so more than likely its a combination of drivers AND the game.

I'll just chalk my lack of major issues up to being a part of the lucky few.
November 15, 2008 6:11:47 PM

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.
November 17, 2008 3:35:25 AM

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.
May 28, 2009 11:24:52 AM

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
Anonymous
October 8, 2009 11:36:53 PM

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!
October 29, 2009 2:01:12 AM

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



December 7, 2009 2:59:51 AM

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.

January 30, 2012 6:52:20 PM

This topic has been closed by Mousemonkey
!