I had this problem with the JS4100 voice commander aswell, I keep getting an ntdll.dll error when flying in orbx regions.Faulting module path: C:Windows\Sys WOW64\ntdll.dllThis only happens when doing a flight with fs2crew, maby its just pushing my system over the edge, anyone else? Or does anyone have advice.

I've use Orbx scenery a lot as do a very large chunk of FS2Crew users routinely use Orbx scenery with no problems.So it's something else.See this thread:http://forum.avsim.n...nt-to-orbx-pnw/Cheers,

bryan ever since i installed the fscrew2 i get the above ctds as well and i never had them before. will try another aircraft the ifly using the same route to see if i get it will let you know if i get the ctd with the ifly 737. Also got orbox as well i get it all the time if i fly cyvr to cycg 9 out of ten times

Try moving your sliders to the left a touch and try appling *******' FSX.CFG update to optimize your FSX.As mentioned, though, Orbx works fine for me. I love their scenery.Cheers,

ok had the same ctd at the same spot all the time just past the weigh point cilli with the ifly737 so looks like its orbox related since havnt flown this route at all before

No worries,I'd send a support ticket to Orbx and let them know of the location so they can fix it.Cheers,

 

No worries,I'd send a support ticket to Orbx and let them know of the location so they can fix it.Cheers,

thx ryan but i wouldnt be holding my breath on a fix for this seems a hard one to track down i just give this route a misss lol

No worries,I'd send a support ticket to Orbx and let them know of the location so they can fix it.Cheers,

Hi bryan just to let you know that i selected another route using the same departure and destination and i didnt get the ctd that i always got. so now going to put my sliders back where they were and use fscrew2 to see if i dont get a ctd. If i dont, than its most likely a navigraph error some where in the fmc. will try tomorrowThis is the route that i always had ctds cyvr fsr2 yvr v342 cilli j514 emeto j500 locan cg cycg and this is the new route that i didnt get a ctd cyvr yvr4 V342 antlr ydc V300 locan Cg cycg the trip is about 200 nm so a short trip if some one else would like to try this route. I let you know cycg is a most challenging airport to land at most difficult alot harder than lowi

Try moving your sliders to the left a touch and try appling *******' FSX.CFG update to optimize your FSX.As mentioned, though, Orbx works fine for me. I love their scenery.Cheers,

Hey Bryan still getting the ntdll error, I don't think its your product causing it, but I do believe its just this one extra thing running that is pushing my system over the edge :) Do you increase your LOD Radius at all? I had mine set to 7.5 when I got the crash, I then reduced it to 6.5 and got the crash aswell, maby I will have to go back to the original 4.5 when flying in orbx and using fs2crew or maby its something entirely different. Just trying to pin point the problem, and just so everyone knows this is not the famous g3d.dll errors fsuipc fixed that for me.

Try changing your LOD setting. You never know.Are you flying around Seattle?For some reason, Seattle seems to be the "Bermuda Triangle" of FSX... lots of weird stuff goes down when flying over Seattle scenery....

Try changing your LOD setting. You never know.Are you flying around Seattle?For some reason, Seattle seems be the "Bermuda Triangle" of FSX... lots of weird stuff goes down when flying over Seattle scenery....

No CYVR, Vancouver, what LOD are you using? I know increasing it above 4.5 can be very taxing on your system especial in a detailed orbx area.

Right now I'm testing SP1 so my sliders are full left so FSX will load as fast as possible so I can quickly test code changes.But generally I'd keep my settings around those recommend by Orbx, and my system is about 3 years old.I'll let others chime in.

Right now I'm testing SP1 so my sliders are full left so FSX will load as fast as possible so I can quickly test code changes.But generally I'd keep my settings around those recommend by Orbx, and my system is about 3 years old.I'll let others chime in.

Man I can't figure this one out, got rid of my overclock, got rid of my tweaked out fsx cfg file, reduced all my sliders to the left and still get the ntdll.dll error, if I disable fs2crew and do the same flight its fine, but then when I enable it again I get the crash, I also re installed the ngx and fs2crew several times, Im out of idea's.

Try it on a different route away from that specific scenery area. Try a flight in Europe.Cheers,

Try it on a different route away from that specific scenery area. Try a flight in Europe.Cheers,

It works everywhere Bryan, it just seems to be this one specific area, in and around Vancouver, I tested it in other orbx area's and it worked fine, if I disable fs2crew and fly the same route it works fine, so it must be some sort of weird orbx error, combined with fs2crew combined with my system in this one little area that is causing the problem, Im going to snoop around trying to find some duplicate afcad files or missing scenery objects, this must be the problem.