Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello,

just tried yesterday last version.

Flying with 737NGX on a simple scenery (no addons in that area), repeating an already successful route, I had repeated fsx crashes indicating ntdll.dll as the cause.

the problem arise sistematically every 15-20 min, so in a 90 minutes flight I restarted a lot of times reloading the last autosave flight.

Googling around I found this error can be due to almost anything, expecially bad drivers problems.

But the only change I made in last week was replace fsuipc.dll with the last version.

I kept the previous version I saved on my disk (4747) and restored it, then I was able to complete the last 45 minutes of the flight, and added additional 20-30 min parked at the terminal.

Don't know in which way fsuipc.dll can interact with ntdll.dll but at the moment all seems work fine again.

I'm using autosave feature every 5 minutes, wind smoothing, and a couple of joystick buttons mappings to keyboard (not used yesterday, reverses and push to talk).

If you want, please try investigate about this.

If i can help with some more accurate troubleshooting (take error picture, send configurations files) i'll do pleasantly.

Claudio Colangeli

Italy

Posted

Flying with 737NGX on a simple scenery (no addons in that area), repeating an already successful route, I had repeated fsx crashes indicating ntdll.dll as the cause.

the problem arise sistematically every 15-20 min, so in a 90 minutes flight I restarted a lot of times reloading the last autosave flight.

Googling around I found this error can be due to almost anything, expecially bad drivers problems.

But the only change I made in last week was replace fsuipc.dll with the last version.

I kept the previous version I saved on my disk (4747) and restored it, then I was able to complete the last 45 minutes of the flight, and added additional 20-30 min parked at the terminal.

Don't know in which way fsuipc.dll can interact with ntdll.dll but at the moment all seems work fine again.

There's really nothing in FSUIPC which can cause crashes in NTDLL. Those are almost always video or other driver problems, or even memory problems. And there really have been no serious changes since 4.747 except for the specific G3D crash prevention addition and big improvements in WideServer by the addition of BroadcastMode.

If you want, please try investigate about this.

If i can help with some more accurate troubleshooting (take error picture, send configurations files) i'll do pleasantly.

With NTDLL crashes I don't have a chance in hell of doing anything remotely. Whenever I've had such errors I've eventually sorted them by changing drivers, and once replacing a memory stick. By the time NTDLL crashes it is about 10-20 layers below FS and the stack is usually so corrupted there's no clue whatsoever about where it all started. My most recent occurrence was when I installed UK2000's EGLC extreme scenery. When both that and their EGLL sceneries were both enabled, one or the other would invariably crash in NTDLL. I only overcame that by updating the video driver AND reducing the graphics anti-aliassing settings a notch.

Sorry, I can't help other than by such advice.

Regards

Pete

Posted

Thanks for reply,

I also cannot figure how can ntdll.dll and fsuipc.dll interact.

I'll crosscheck my drivers, but they didn't change in last weeks, and I had several good flights without accidents.

I also will give a try reducing antialias and using again 4749e.

Hope to come back with good news.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.