June 13, 20232 yr Hi, Lately I've been getting CTDs with API.dll as the faulting module. I've read that the main cause is an issue or error related to memory. I tried monitoring my VAS remaining using FSUIPC and I never ran out of VAS. So in my attempt to find the possible cause I loaded up a flight like I normally do, with Process Monitor running in the background. Applications that run during my flights are: -Active Sky 2016 -REX Sky Force 3D -vPilot -littlenavmap -vroute I even got the CTD without ANY programs running in the background, on various aircraft. According to Process Monitor my FSX crashed when it was trying to read the "kernel32.dll" file under C:\Windows\SYSWOW64. I have never had this issue before, and I'm thinking that it could be related to a windows update, but I want to rule that one out :'). Following the CTD guide I installed Take Ownership using registery editor and took ownership of the FSX folder. Furthermore other things I've tried: -disabling DEP (data execution prevention) -disabling UAC -disabling antivirus & firewall -trying a different VATSIM pilot client (vPilot > swift). Did not work. -disabling any other application that could prevent data from being written or read. Note: I do not have Addon Scenery installed, just updated AFCAD files that I make myself. I have no shaders and no ENB series installed. Important to note is that sometimes it does successfully read the kernel32.dll. The sim then does not crash. Last saturday I did a 9 hour flight from EHAM to CYYC and I had no CTD. I do not recall the kernel32.dll being read at all during that flight. I'm looking forward to suggestions :) -jessy
Archived
This topic is now archived and is closed to further replies.