I am experiencing the following problem, which occurs occasionally but not always. Perhaps you can point me in the right direction.I will have FS9, and my entire system lock up. The sound goes into a "loop", I lose the keyboard and mouse and there is nothing I can do but a hard reboot. There is nothing listed in Event Viewer. I have backed off slightly on my GPU overclock, for lack of any idea what else is causing this. Note that my GPU temps are fine when this happens so I'm not sure I should blame the GPU OC?Any ideas as to what may be causing this? Vic

Can you provide any hard numbers for your GPU and CPU temps, while running intensive programs (fs9, etc)? It's a bit hard to check them as your system locks up. Does your system always lock up when running fs9?If so, how long after?Does it lock up running any other game?It could also be a corrupt memory card.

My GPU runs 43-47* C while FS9'ing (which seems very cool?). I will have to figure out how to get CPU numbers but I have huge air cooling installed.The lock ups do not occur all the time...only occasionally (say 20% of the time on long flights?)It never locks up running any other game.These are my system specs:Windows XP Pro (SP2, 32 bit)ASUS Rampage Extreme x48Intel C2Q 9650 3.0ghz4gb OCZ RAMBFG GTX260, 896mb(C:720, S:1480, M:1220, mhz) NOTE these have been downgraded to:C:700, S:1430, M:1190, mhz in an attempt to solve problem...not tried yet.SoundMAX X-fiASUS VW266H lcd flat panelNO FSB, CPU or RAM OC'ing is being used, other than setting the XMP setting.I need a proggy to record CPU temps to give you that info...any suggestions?

Well since almost every other modern game creates more heat from the GPU, you can pretty much rule that out, since it doesn't hang in other games. You didn't mention if you use add-ons or not, and if the lock ups correlate to the amount of add-ons you're using/are visible. What fs9 does have over many other games is memory use...if I had to guess at this point, I'd say something wrong with memory. But just incase, get a CPU temp program like RealTemp and record your temps while flying. GPU temperatures are very cool indeed.

OK, ran a long flight overnight in the PMDG 747-400F. RealTemp CPU temps average was 47*C with a highest of 51*C. GPU averaged 46*C. Had no lock ups and this was an exact refly of the last flight which did cause trouble...so it doesn't seem to be scenery related as it didn't re-occur? I only use my VA's ACARS program and occasionally, on long flights, FSPause. Both of these were also running last night.

And BTW...the flight that worked was done with the GPU OC dropped as mentioned above. From what I've read GPU temperature is not the only factor to consider when OC'ing? Stability and artifacts may also come into play. My original OC (not given above) would do the same thing but show lots of patterned artifacts on the locked up screen. Maybe I was still unstable...but not enough to show noticeable artifacts when it locked up last time? Anyway, still open to suggestions and will have to fly many flights to see if the new GPU OC numbers have helped or if there is some other issue.

Yea, sure sounds like an unstable OC on the GPU. You're right in saying that temp isn't the only indicator. I would say get a good Stress test program for the GPU and test it there, with your original clocks, and incremental overclocks. That will give you a good stable OC. If it doesn't fail a stress test, you can be sure it'll be fine in fs9.

Yea, sure sounds like an unstable OC on the GPU. You're right in saying that temp isn't the only indicator. I would say get a good Stress test program for the GPU and test it there, with your original clocks, and incremental overclocks. That will give you a good stable OC. If it doesn't fail a stress test, you can be sure it'll be fine in fs9.

I would suspect the GPU overclock, too. I'd start by backing off the GPU to stock settings and see if the problem goes away...I can't imagine that the GPU overclock is making a tremendous difference in FS9 with the CPU only running @ 3 GHz.Another thing to look at is to make sure that the most recent sound drivers are installed, as well as recent DirectX/video driver/nHancer versions.A good GPU stress test is the GPU test in OCCT (it's freeware).RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I am experiencing the following problem, which occurs occasionally but not always. Perhaps you can point me in the right direction.I will have FS9, and my entire system lock up. The sound goes into a "loop", I lose the keyboard and mouse and there is nothing I can do but a hard reboot. There is nothing listed in Event Viewer. I have backed off slightly on my GPU overclock, for lack of any idea what else is causing this. Note that my GPU temps are fine when this happens so I'm not sure I should blame the GPU OC?Any ideas as to what may be causing this? Vic

I too experienced the same problem. It's related to your Nvidia card. FS9 doesn't like the newer drivers on some systems. I use the 8800GTX card. The driver I use to eliminate the random freezes is the 182.50. Give it a try but remember to use driver cleaner pro to remove old reminates of drivers.Bill M

Thanks for the help, guys! AFAIK sound drivers/DirectX/video driver/nHancer versions are all up to date...but will verify that. That being said my nVidia GPU drivers are 178.xx...these are the only one's that will allow me to set a 3 X 4 resolution in the NCP without "garbling" (for lack of a better term). See this thread:http://forums.guru3d.com/showthread.php?t=292724 I'm really hoping it's too much OC on the GPU. Once this issue is resolved I'm planning on some CPU/FSB/RAM OC'ing as that would certainly help FS9's propensity for CPU/RAM usage.

Nope...just crashed again on a NZAA to NFNA flight...same old same old... lighted keyboard goes black, mouse goes dead and sound loops. Nothing but a hard reboot will get the system back up and running. What does the loss of USB inputs indicate? And why does it only occur in FS9? If it was a system problem, I would think it would show up at other times?Y'know...I never had these problems with my old CRT? Seriously, it's all seemed to have started after getting the ASUS 26" LCD...does that ring any bells?Pardon me while I pull the icepick out of my eye...and then stuff it in my left ear. :(

Hmm..Well regarding the new LCD...is it a higher resolution then your old CRT? If so, that puts a greater strain on your system in general, so that can always contribute...but I doubt it considering your specs. I'd go back to my first idea of having bad memory. Those things fail more frequently then you'd think. Get yourself the program 'memtest' and test each memory card individually. That'll tell you for sure if you have one bad one.If that doesn't work, we'll keep thinking.

I think Red is probably right about the memory here. Try pulling the memory sticks out and then replacing. Sometimes its just a poor connection. Be sure to earth yourself first!Dave

Thanks for the help, guys! AFAIK sound drivers/DirectX/video driver/nHancer versions are all up to date...but will verify that. That being said my nVidia GPU drivers are 178.xx...these are the only one's that will allow me to set a 3 X 4 resolution in the NCP without "garbling" (for lack of a better term). See this thread:http://forums.guru3d.com/showthread.php?t=292724 I'm really hoping it's too much OC on the GPU. Once this issue is resolved I'm planning on some CPU/FSB/RAM OC'ing as that would certainly help FS9's propensity for CPU/RAM usage.

Try totally removing the video card driver and reinstalling it.Bill M

Before trying that, go to your FS9 cfg file and check this line:TEXTURE_BANDWIDTH_MULT=80 (whatever your figure is)I experienced the same problem with my 9800GT until I reduced TBM from 200 to 80 with frame rate locked at 25 fps. Now it is smooth without stutters. If your frame rate is locked at about 25 or 30, then this figure should not really be higher than 100. If it is, your card probably can't cope with the texture loading .Gary