OK what on earth did I do here?

 

On Saturday I was flying around just as happy as could be. Installed a couple sceneries. Then installed KTVL. And at some point in the process I updated my video drivers. Now this.

 

 

Been searching internet threads looking for solutions.

 

1. Rolled back the NVIDIA drivers -- no change.

2. Logbook.bin was not the culprit.

3. Used old scenery config files -- didn't fix it.

4. Installed SceneryConfigEditor v1.12 and it found no errors. Renumbered all the layers and entries, still no change.

5. I even found one guy whom I know from these forums who had a similar issue which was resolved by reinstalling ORBX libraries. So I even tried that, to no avail.

 

Of course I removed the scenery additions from yesterday (the one exception being KTVL, I left that one alone). Still no luck.

 

Anything else that I might be overlooking?

Why not KTVL?

 

Rolled back the NVIDIA drivers .... to what?

 

Rolled the NVIDIA driver back to --

 

Driver version 9.18.13.3788

Driver Date 5/19/2014

 

The newest one I had was 7/2/2014.

 

Removed KTVL from my scenery config list and testing that now.

 

 

I also failed to mention in my OP that I ran a registry cleaner tool and I had hundreds of bad registry entries -- probably this was a result of changing around/upgrading SSD drives, where FSX resides.

"probably this was a result of changing around/upgrading SSD drives,"

 

Sounds like a PC hardware problem .. not FSX.

Well, it might sound like that, but until yesterday it was working fine. Made these changes quite some time ago, and had no issues.

"Made these changes quite some time ago, and had no issues."

 

It would have been helpful if mentioned in previous post(s).

 

The more background information the better for others to help.

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Rip,

 

How long are you waiting at that screen?

 

Install ProcessMonitor, filter out all non-FSX stuff and see if files are loading in the background.

If you have FSDT scenery installed, then download and run the latest Addon Manager on their website. The key to your problem is that it is not loading terrain data. You do not have to remove your installed scenery but you do want to disable all of your addon scenery via the Scenery Library or the Scenery Config Editor. It's possible that the texture files are not compatible with FSX for recent addons.

 

If you are getting a crash or freeze, you can download and run AppCrashView and/or look in your Event Viewer to see if it is showing a problem with an fsx module. Information on how to do his is on the 1st and 2nd pages of the AVSIM CTD Guide located to the right of this forum under Hot Spots. It has more troubleshooting tips too.

 

Best regards,