FSX Lockup

[dvpro]

So I got that new 285 installed and the computer is working as expected for all my normal uses. When FSX runs...I'm locking up more and more. OC'd to 4.04 @ 22X182. Idle at 37ish and occt maxes out at maybe 70 with never once an issue of instability or temp issues.
Lock up happends in clouds and on clear skys with default planes or payware. Sometimes it locks up than will free itself, but I know in a few minutes it will do it again eventually never recovering. A few times it has caused the system to totally reboot on its own.

When I installed the new 285 from a 260 I never uninstalled the drivers (current one for Vista 64) I just swapped the cards and everything looks good (visually). I do get some artifacts in fsx when panning. Shimmer is next to none. Nhancer was checked and maybe one or 2 adjustments were made to follow Nicks guide. Nhancer is exactly as directed to be. Vista is too, except for the fsx.cfg file was never ammended. Otherwise all settings are as directed to by Nicks guides. I highly doubt that is the issue because things were working fine b4 the card change. I'm wondering if the drivers are causing this and why? How do I fix it?
Thanks

[vgbaron]

DVPro - I just went through this with my system. At 4GHZ system passed OCCT, Prime95 and Memtest for hours BUT FSX would randomly lockup. After a lot of testing, finally dropped down to 3.88 and haven't had a problem since. System is smooth, fast and sharp.

Just because your clock is bench stable doesn't mean that it is FSX stable.

Try reducing the clock a tad and fly that way for a few days and see what happens. If it locks again, drop down some more until you find the sweet spot.

JIC you get back to normal and the lockups STILL happen, you know that it's something else.

As Nick is always saying, the system has to be in balance for the best results. For me with a Q9650/XP64/4G ram - 3.88 seems to be it.

Ifyou change a card, you change the system and you start over.

I run 30fps locked at 30 even in heavy clouds and mainly around the LAX area which is pretty demanding on the system.

Good luck

Vic

[dvpro]

Thanks,

I simply uninstalled the driver and reinstalled it. I set the fsx.cfg to a few of the settings Nick says...some of those are not mission critical, I did not mess with the ......i forget the name of it, I didn't change anything major.....OH, wait, I remember one thing about that...the display was still set to the gtx 260 and the gtx 160.1
I changed that to the 285 and 285.1

Loaded up fsx and went with the 172 from KCMA to KMRY than to KRNO. I was basically flying the shoreline looking for the WX. Sim ran very smooth. Loaded up the 763 and went from KPHX to KSFO, but I missed the WX in SF. Locked in at 32 fps and had a pretty smooth flight. I need to spend some more time on it.

As for this proc, I know I could take it to maybe 4.2 while the WX is cool, but I don't want to rail this thing. I just want it simple and clean. I'll do more testings soon.