I've had freezes before but not for a long time, and now they're gone long ago. I didn't change my card, I'm using an nVidia N9600GT (MSI), and the newest drivers. (196.21)
The "Freeze" problem (
with or without graphical corruption, with or without total driver failure), from my experience, is not related with lack of resources from the graphic card... As more FPS are pulled, more likely the freeze becomes. At least that has been my experience so far...
For instances, my card-OS-system combo runs Race ON with max detail (including draw distance) at an FPS well above my TFT-LCD capacity... If I lower the graphics demand, theoretical FPS goes well above 100 fps and the "freezes" become more common.
A 9600GT card is (
was) a low end games card (
yours with an always nice passive cooler) from the previews NVIDIA card range (
9600 to 9800), so maybe your FPS are already low in first place, and in accordance to my experience that would lower the likelihood of a "freeze".
Notice that you type that in the past you had "freezes", but you also type next that you don't have one for some time. I don't remember very well now when exactly, but
SimBin increased the scenery draw distance in the Evolution pre-Race On preparation patch (
consequently lowering fps to anyone that didn't notice the change and didn't went back to change it to the old settings).
My game seems to stutter now (GTX260) since i have updated my drivers to the latest version. Will post a thread in the hardware section later to ask how to revert to the previous set as i have no clue how to do that.
The GTX 260 card
Bram types about in the next post is the low end version of the following NVIDIA game card range (
I would call it the newest card range, but as always there is already a new card range in the pipes). The "stutter" problem he types about,
is not the "freeze" problem; in fact "stutter" could theoretically be solved by finding out what graphic effect/setting is causing it and lowering it (
one way). The "stutter" is "only" the card going to the "limit"... now why it goes?!... excess load,
incompetent drivers-OS mix?, hardware handling of the CPU-GPU necessities (
Motherboard)... who knows...
As always with these things, "one's" solution many times isn't the "other's" solution... good luck mixing and than
isolating those variables :wink: