March 29, 201214 yr Commercial Member Hi guys,I have been super unlucky recently, only completing 1/10 flights, it has been super frustrating.At the moment, I just saved my flight before another crash, loaded in again.By clicking "Clr" on my FMC, caused the Flight simulator to freeze immediately/ completely, twice at the same point.AlexP.sMaybe some help or none at all, the faulting module path is "unknown" Alex Ridge Join Fswakevortex here! YOUTUBE and FACEBOOK
March 29, 201214 yr Alex,I think your best bet at getting help with CTDs is to include the application event log showing the crash. If you're running Win7, type "Event Viewer" in the Start menu lookup. In the Event Viewer, go to "Windows Logs-->Application" and find the FSX entries. There should be a Red icon next to the log entry showing that there was an Error. Often times there will be more than one, so find the one that contains Faulting module (e.g., ATC.dll) and copy the contents in your post. If it's always the same module causing your crash, it's easier to narrow down the problem. if you're seeing a variety of modules causing the CTD, then it's probably unstable hardware (e.g., bad RAM or unstable Overclock). There are other common causes of CTDs that can be addressed if you provide the faulting module. Stacey Weaver Windows 7 Home Premium, 64-bit Intel Core i7 875K, 2.93GHz (OC 3.6GHz) 8GB DDR3 1600 30GB 2.5" SATA MLC-SSD (Main Boot Up Drive), 1TB (1 x 1TB) SATA-II 3.0Gb/s 7200RPM HDD, 128GB SSD dedicated for FSX NVIDIA GeForce GTX 465 1GB PCI-Express Asetek 120mm Liquid Cooling System 2 x ASUS 24" Widescreen HD LCD Monitor DVI CH Yoke, Pedals, Throttle Quadrant
March 29, 201214 yr Author Commercial Member Alex,I think your best bet at getting help with CTDs is to include the application event log showing the crash. If you're running Win7, type "Event Viewer" in the Start menu lookup. In the Event Viewer, go to "Windows Logs-->Application" and find the FSX entries. There should be a Red icon next to the log entry showing that there was an Error. Often times there will be more than one, so find the one that contains Faulting module (e.g., ATC.dll) and copy the contents in your post. If it's always the same module causing your crash, it's easier to narrow down the problem. if you're seeing a variety of modules causing the CTD, then it's probably unstable hardware (e.g., bad RAM or unstable Overclock). There are other common causes of CTDs that can be addressed if you provide the faulting module.Thanks for the reply,"""Maybe some help or none at all, the faulting module path is "unknown""" Next time I experience this I will upload itAlex Alex Ridge Join Fswakevortex here! YOUTUBE and FACEBOOK
March 29, 201214 yr FYI, there usually is 2 or 3 error logs created when FSX crashes and often only one of them will identify the faulting module. Stacey Weaver Windows 7 Home Premium, 64-bit Intel Core i7 875K, 2.93GHz (OC 3.6GHz) 8GB DDR3 1600 30GB 2.5" SATA MLC-SSD (Main Boot Up Drive), 1TB (1 x 1TB) SATA-II 3.0Gb/s 7200RPM HDD, 128GB SSD dedicated for FSX NVIDIA GeForce GTX 465 1GB PCI-Express Asetek 120mm Liquid Cooling System 2 x ASUS 24" Widescreen HD LCD Monitor DVI CH Yoke, Pedals, Throttle Quadrant
Create an account or sign in to comment