marks217

Well, it just crashed again at 14,000 feet on descent, so I guess that added flag didn't help. I'm happy to post any reports or logs, but I guess it's time to start narrowing things down. SLC is the newest addition to my previously stable setup, so I'm guessing that everything running is just using too much memory.

Oh, I already know that. I've used it many times before. My apologies for the misunderstanding. I meant what it might have been doing at that specific time that may have caused a crash. To my understanding, it gets loaded with all of the other DLLs in the dll.xml upon starting FSX, but I hadn't used it at any point at all during the flight. Hopefully this is just a corrupt weather file somewhere as Pete suggested. As soon as I get some free time to test that fix, I will let you know what happens.

Thanks for your response, Pete. I will definitely try that weather parameter next time and I'll report back. Just to better my own understanding, do you have any idea what that RecorderFSX.DLL could have been doing? My only guess is that it gets loaded when FSX starts up, but without actually using it, I'm not sure what could have forced it to go wrong. If not, no worries.

Hello, I unfortunately suffered an FSX CTD at 1,500 feet on my approach and I'd like to figure out what the issue was and if it was related to FSUIPC at all. Everything was going normally until the simulator locked up around 1,500 feet, froze for a minute or two, and then closed. This was on VATSIM in a busy airspace, though my sim will usually just stutter in such instances without crashing. The Windows crash details indicate FSRecorder as the faulting module, though it seems to always throw up the same .dll as the faulting module after a CTD. I was not using FSRecorder at the time, nor had I used it at all during this particular flight. Here's the report anyway: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d Exception code: 0xc0000005 Fault offset: 0x0000cf30 Faulting process id: 0x4b0 Faulting application start time: 0x01d6e2202b6bcb94 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: RecorderFSX.dll Report Id: 50e32fd4-f1f9-45a1-9845-d7b065db7543 Faulting package full name: Faulting package-relative application ID: Here's another one from less than a minute later. Looks almost identical. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d Exception code: 0xc000041d Fault offset: 0x0000cf30 Faulting process id: 0x4b0 Faulting application start time: 0x01d6e2202b6bcb94 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: RecorderFSX.dll Report Id: a2d2cafe-1c8a-4005-93b0-43fc01b60d80 Faulting package full name: Faulting package-relative application ID: Here's a final one from 13 minutes later, perhaps when I tried to relaunch FSX. This one lists ai_player.dll as the faulting module. Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57 Exception code: 0xc0000005 Fault offset: 0x00037399 Faulting process id: 0xfe4 Faulting application start time: 0x01d6e23a68099c7d Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll Report Id: 810a2d1a-9dbc-4473-b32d-9b30b28fc566 Faulting package full name: Faulting package-relative application ID: I've attached the FSUIPC4.log file to the post. This is an unregistered copy of FSUIPC and I just updated it the other day through DVA ACARS. I was flying an addon 717 (can look up developer later if needed). Addons I was using were ASN, DVA ACARS, projectFly, vPilot, and Self Loading Cargo. I had also used FS Real Time early in the flight but was not at the time. I know it doesn't look like FSUIPC was at fault, so I'm just trying to get to the bottom of what happened. Self Loading Cargo users have been reporting issues with a recent version of FSUIPC, but it may be for MSFS, I'm not sure, or if that's related to my issue. Any help would be appreciated. Thanks in advance. FSUIPC4.log