I just reproduced an error I got last night, flying into FSDreamTeam's ORD from MKE.You the point when their scenery loads - normally I get a slight pause then the scenery pops up. When I just tested it I got the pause alright, then a G3D.dll CTD!Any of you guys have their FSDreamTeam stuff? If so, trying starting far away from the scenery, maybe 40 miles at least, then fly towards it - see if you get a CTD when it loads.Maybe this is all Windows SP1 related? Who knows..edit: naw it can't be SP1 specific because people were posting in 2009 in the FSDT forums about G3D.dll ctd

I have none of their scenery installed again yet. It must be nvidia driver related

I have none of their scenery installed again yet. It must be nvidia driver related

Ok, so you're just having the problems in PNW? I have that scenery as well.Brand new drivers released today WHQL 270.61 - I'm going to try those... FWIW... :(

Was having problems in PNW but disabled it and flew around Europe in UTX Europe, same dll errors.I'll check out those drivers

<br />Try this, just make a shortcut of the fsx.exe file, don't check run as administrator.<br /><br />Remove the fsx sdk lines in the dll.xml file<br /><br />rebuild fsx.cfg file and see if you get any errors<br />

<br /><br /><br />So far I don't want to jinx it, but I'm flying for over an hour now without a dll crash! In the middle of a flight CYLW-PAKT2 more hours to go

It will probably take more testing than that... I went for about a week without any errors.And that error I said I reproduced... can't do it anymore.. though I did just install the new drivers.Somehow I doubt that will fix it :(

I wasn't able to complete a flight over an hour before, now I just landed at PAKT and the sim was running great.Now for the big test, KJFK-ELLX as Cargolux 659

Yeah I too admit I've been trying all the usual problem areas and no CTD's yet - with this new driver.The only other thing I've done is increase my GPU can speed so it's a little louder (not too bad though), and the GPU core temp is lower.

I have nothing to support my theory, but it just very well could be a memory management issues and tied deeply in the fsx code.Resource management and the allocation and deallocation of memory is incredibly important and the result is what many areseeing. One time one module is the problem and the next time maybe it's another.Bob

Yeah I too admit I've been trying all the usual problem areas and no CTD's yet - with this new driver.The only other thing I've done is increase my GPU can speed so it's a little louder (not too bad though), and the GPU core temp is lower.

As in physical modules of RAM?

This comes under the heading of 'Clutching at straws'. Like most of you, I too was/am having the odd g3d.dll crashes, this time with the new X4 Katana. I discovered a ROOT_g3d.dll in FSX\Setup\XPackCache. as well as the g3d.dll in the root folder. Question: Is it significant that the one in the root folder is sized 882KB and the one in the XPackCache is 741KB? If it IS significant I'm applying to the Nobel commitee. :(

This comes under the heading of 'Clutching at straws'. Like most of you, I too was/am having the odd g3d.dll crashes, this time with the new X4 Katana. I discovered a ROOT_g3d.dll in FSX\Setup\XPackCache. as well as the g3d.dll in the root folder. Question: Is it significant that the one in the root folder is sized 882KB and the one in the XPackCache is 741KB? If it IS significant I'm applying to the Nobel commitee. :(

I just wanted to send you to this post now you come with a bloody curve ball again..I dont know. I will check and see mine quickly.EDITFSX Root Folder: right click properties. select details tabFile version: 10.0.61637.0size 882 KBthis is right one for you.The setup is root_g3d.dll is old files from first setup before updates to SP's adn acceleration.That one is 742 and you will see its date is way before the one you find in FSX root itself.Not to worry about this. Sorry that is not your problem