Turns out the textures arent the problem. I just flew for 4 hours from Nellis AFB, to Macdill AFB only to have my game crash on me during final. I noticed my throttles were stuck at idle, even though they were around 50 percent on my saitek throttles. I moved them forward to see if it would change, and the power went back down to idle. I threw on the auto throttles to land, and my #4 engine went to full power, while the others were at 30%. Right after that I was looking at the "flight simulator has stopped running" error. I went into the event viewer to see if there was an error report, and sure enough there was.
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: MSVCR80.dll, version: 8.0.50727.4927, time stamp: 0x4a2752ff
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x12ac
Faulting application start time: 0x01ca97a0a9ae2906
Faulting application path: F:\Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVCR80.dll
Report Id: 4ee54528-03b8-11df-ad24-001e4cccf639
The faulting module is MSVCR80.dll. I looked for that on my computer, and found it under an ati folder in my documents. My display drivers are about 4 months old now, and I am having other issues so I need to upgrade. Dont see that the issue is a driver fault. Even if it is should that really effect my throttles like that?
This has worked fine for me for a while, but I have my saitek throttles set up for the individual engines, and then my X-52 throttle is still linked to engine 1. I can easily switch from my C-17 to an F-16 and not have any throttle issues, so long as the un used throttle is at idle. I havent noticed any throttle failure with my previous crashes in the F-16 though.