April 29, 201412 yr Hi guys - advice/suggestions invited ! My SP2 system has recently started to crash on ending a flight or when exiting FSX (and only at these points - the rest of the time it runs fine). The module most commonly flagged in the Event Log is nvwgf2um.dll, which is puzzling, since (I think) that is a DX10/11 module and I am running DX9. I'm running a GTX580 and driver 306.97, which was installed over a year ago, and has been running fine until this point. The rest of my specs are in my profile. I take regular system images, so I can roll the system back to a point before the crashes started, but I'd rather not do that unless really necessary as there are quite a few changes to be re-installed. And of course if the cause is hardware, then that won't help. Prior to that I will probably try re-building the FSX and re-installing the driver, but all other suggestions gratefully received !
April 29, 201412 yr In Internet Options>Advanced>Accelerated Graphics, make sure the box is unchecked. If this is okay, then you will need to reinstall your graphic drivers. I would do the clean install option provided when the Nvidia installation screen opens and you select Advanced Options. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
April 29, 201412 yr Author Assuming you mean IE Internet Options, then that's certainly something I wouldn't have thought to look at ! But in any event, it is unchecked. Thanks
May 9, 201412 yr Author Well, it took a while, but I found the cause of the problem. And not where I expected. Turns out there was a bug in the aircraft.cfg file for one of my AI aircraft. The line that should have read: atc_parking_types = was mistyped as atc_parking_codes = so in fact the file had two atc_parking_codes lines and no atc_parking_types line. No idea why this should have cause the type of CTD that I was seeing, but it did. What made finding the problem really difficult was that it only occurred when a AI flight plan using this particular a/c was active when I ended the flight I was on. Which meant that it only happened at certain times of the day ! And I doubt I would ever have found it had I not kept a detailed record of all the changes I made since he last backup and when the error first occurred. In the course of tracking the bug I backed off to a previous level and back again several times. Rebuilding now . . .
May 9, 201412 yr Jeez, not sure how you found that, but bravo to you sir. Intel i7 10700K | Asus Maximus XII Hero | Asus TUF RTX 3090 | 32GB HyperX Fury 3200 DDR4 | 1TB Samsung M.2 (W11) | 2TB Samsung M.2 (MSFS2020) | Arctic Liquid Freezer II 280mm AIO | 43" Samsung Q90B | 27" Asus Monitor
Create an account or sign in to comment