• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

nv4_disp CTD in campaign

D

Dirk98

Guest
Guys, I get repetitive CTD in campaign when about crossing the no man land. I get black screen and 'nv4 display' error (FPS are stable all the way to CTD). It never happens in quick combat. My video card is 8800GT, driver 169.21. I never saw this error before. Most of the game settings are @4, clouds @3.

Btw, I never installed CFS3, just used the CD when it was requested. I'm not sure now if the version of the exe I have on my CFS3 CD is correct, in the properties it says: version 3.1.0.30203.

I'm on WinXP SP2, game patch 1.25 applied, OS language tweaks applied. Any ideas?

Thanks,
Dirk.
 
Dirk I had exactly that in my CTDs with OFF on my new PC that has just now been set up - also other random memory corruptions - trees etc.

It turned out to be a Faulty Dimm....

HTH

WM
 
I played with 4:3 aspect in campaign, since changing it back to 16:10 the game is ok so far. Flying campaign.

Dirk.
 
The 'aspect' reference in my post above was misleading. Winder was right pointing at RAM as a possible culprit. Finally I had to notch down from 4.4Ghz ovc to 4.3Ghz and that fully cured the problem. I was confused by nv4 display error. But it was all RAM problem. Indeed, in my specific configuration in highly overclocked condition RAM is prone to errors under stress which OFF3 offers a lot (turns out more than FSX @ high).

For those who are serious about overclocking your systems pls note the following:

just a reminder: neither Prime nor Orthos have the capability of fully testing the stability of an overclocked Intel system anymore. The only tool that can really fully load a (modern, Core based) Intel system is the "IntelBurnTest", which essentially is a wrapper around Intels internal "Linpack" processor test.
Give it a try here:
http://downloads.guru3d.com/IntelBurnTest-v1.6-download-2047.html
But be prepared for higher temperatures than you have seen with Prime/Orthos! +5 or +10 degrees celisius is not uncommon.
Click to expand...
 
You must log in or register to reply here.
Back
Top