Actually I've changed the UIAutomationCore.dll, went back to Nvidia driver 304.48 and did a rebuild of my fsx.cfg. With all that I did a flight from KSEA to KSFO with Carenados B200, REX-highres textures, ActiveSky weather engine and Plan-G on a second monitor. After 3 hrs. I've had a good landing in frisco.

 

So this was my first try, I'm going on testing. But the results seem to be very good - thanks for the help!! The next question are optimal settings in Nvidia-inspector. I thought there was an instruction anywhere, but cannot find it anymore?!

This is the link to the complete DX10 dosier, Markus: there's a folder called "Inspector" where there are four screenshots of three recommended starter settings - Low (4xSGSS), Med (4xSGSS+4xS) and High (8xSGSS), plus one which came from Bumpy (8xSGSS + 8xQ + Bioshock AA Compatibility). I am using this last one, but don't see much, if any, difference between it and the straight 8xSGSS.

Thank you very much, Paul! :good:

After some flights unfortunatly I've got my problem back. A short flight in Skagit Regl., for about 20 min all is working fine. But in the moment of touch down the screen freezes and the PC could only be "reanimated" by pressing reset. I took a picture with my camera from the screen:

OK.. fsx.cfg, please Markus! This is a gpu issue - either being force-fed, and not able to keep up - or overheating.... let's see what that cfg says, then we will have a clue, perhaps. :good:

Thanks, Paul. I've attached my DX10-fsx.cfg. The only thing I can exclude is overheating ^_^.

Looks like its raining dollar signs. Yeah that screen looks more like a hardware issue to me. Edit: Could be driver related too, TOTAL removal then fresh driver install wouldn't hurt to try.

Here she is, Markus: I've made some changes, but nothing jumps out as "wrong", spelled wrong, or in the wrong section. There are some entries that I've pulled back, a couple "rem'd" out, and some reduced while you're playing with it, that you might ease back in later.. You might look back in the How-To doc again, as I''ve included Carl's (ctiger) CCC settings now, and will add others as they come up.

 

If these steps don't get rid of the issue - then wind back the overclock to 4.4 or something that is more "friendly" to the hardware and then run the unit for a week or so. If you still get the hangs and the green blobs while it's downclocked then - I suggest you download the purchased version of Memtest64, install it to a bootable CD, DVD or on a USBkey, and, after rebooting the machine, and before the OS itself boots - run Memetest on your physical memory, and see what pops up. It might well be that you have a chunk of bad memory. -

 

Actually, Markus, with 16GB - why not just pull 8 of them and switch the others remaining around, taking great care to push the dimms home very completely, and test it with the reduced memory. I would do this after testing the changed config, but before reducing the clock speed and mem tests. OK? Good Luck..

 

 

I have had this same kind of screen blackout and hang, followed by that window about the graphics has recovered from an error. This is most likely caused by instability within your GPU, which is hopefully induced by too high of a GPU overclock (which may also be voltage starved), even if it is a "factory" OC. Otherwise, if not overclocked, your GPU may be on the brink of failure. That screen shot of yours suggests this may be the case.

 

When fiddling around with GPU overclocks, I have had benchs and stress tests run perfectly only to later have a game lock up in this manner within a few minutes.

I suspect you are dead right, Rod..

Yes, when trying to overclock my GPU, I can replicate this display driver is not working error 100% of the time. (Just had to throw my two cents in here!)

 

Best regards,

Jim

Thank you very much, friends, very good support and help! I will test your new fsx.cfg, Paul. Thanks for having a look on mine. And I will reduce the frequency of my GTX 570 from 786 MHz down to 732 MHz. Hope it will help...

 

I already used Memtest and even tried FSX with only 8 GB, changing the modules one by the other - RAM is okay. I'm wondering why DX9 works without any problem but DX10 makes this confusion on my PC :wacko:.

..because DX10 makes the gpu work harder, and also gives back a slew of system memory which DX9 doesn't allow, so there's more pressure on the gpu to perform.

Well Paul and all others, I've tried a lot, but something is going wrong on my PC with FSX and DX10. Maybee its my grafic card, maybee ORBX sceneries, I realy don't know it. Even with the new fsx.cfg AND droping the GTX 570 down to default: after a while the screens freezes and I get my green points. Thank you a lot for your help, but this seems to be a special problem with my FSX installation. I am waitung fpr P3D 2.0 coming out this winter. Until that I will fly my FSX in DX9 mode with no problems. The last weeks I spent more time in trobbleshooting than in flying, and that's not good.

 

Anyway: I've learned a lot and for a small screenshot the DX10-patch even works for me, too!

 

Again, thanks a lot for your help!! :p0503:

I am waitung fpr P3D 2.0 coming out this winter

 

Wow. Please share that insider information you have.