June 26, 201411 yr Starting to get a few CTD lately. Any ideas on this one? Log Name: Application Source: Application Error Date: 26/06/14 8:37:38 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: bb-PC Description: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3 Exception code: 0xc000000d Fault offset: 0x00008aa0 Faulting process id: 0x1398 Faulting application start time: 0x01cf9133715cc7cf Faulting application path: E:\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll Report Id: 094f96ed-fd37-11e3-8ce7-c8600024690b Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-06-26T13:37:38.000000000Z" /> <EventRecordID>641463</EventRecordID> <Channel>Application</Channel> <Computer>bb-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>MSVCR80.dll</Data> <Data>8.0.50727.6195</Data> <Data>4dcddbf3</Data> <Data>c000000d</Data> <Data>00008aa0</Data> <Data>1398</Data> <Data>01cf9133715cc7cf</Data> <Data>E:\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll</Data> <Data>094f96ed-fd37-11e3-8ce7-c8600024690b</Data> </EventData> </Event> ZORAN
June 26, 201411 yr What this error is telling you is that a program using Microsoft Visual C++ 2005 w/SP1 is not installed properly or as intended by the developer of the product and threw a STATUS_INVALID_PARAMETER exception code. Maybe something as simple as moving your FSX.cfg to a temporary directory or renaming it to Fsx.orig and then restarting FSX and letting it rebuild will fix the problem. If it happens constantly, then I suggest you uninstall/reinstall or repair FSX. If this is the first time you have seen this or it does not happen often, I would not worry about it. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
June 26, 201411 yr Author Thanks Jim, I will see if the error repeats and then follow your instructions Cheers ZORAN
June 29, 201411 yr Author Hi again Jim, I just got another one. Would you say they are related? Log Name: Application Source: Application Error Date: 30/06/14 5:09:04 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: bb-PC Description: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x753bcb49 Faulting process id: 0xb2c Faulting application start time: 0x01cf93dc8f63a201 Faulting application path: E:\Microsoft Flight Simulator X\fsx.exe Faulting module path: unknown Report Id: faaf9443-ffd9-11e3-9116-c8600024690b Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-06-29T22:09:04.000000000Z" /> <EventRecordID>5724579</EventRecordID> <Channel>Application</Channel> <Computer>bb-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>753bcb49</Data> <Data>b2c</Data> <Data>01cf93dc8f63a201</Data> <Data>E:\Microsoft Flight Simulator X\fsx.exe</Data> <Data>unknown</Data> <Data>faaf9443-ffd9-11e3-9116-c8600024690b</Data> </EventData> </Event> ZORAN
June 29, 201411 yr It's hard to tell whether they are related. The faulting module here is unknown but that usually indicates you will get a StackHash or NTDLL.dll error soon. In any case it is impossible to diagnose an "unknown module". Did you do anything prior to this message as I suggested above like rebuilding your FSX.cfg? At least it got rid of the Microsoft Visual error. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
June 30, 201411 yr Author Yes sorry forget to mention I rebuilt fsx,cfg, so thats a good result there. Okay thanks I will keep an eye on things but the sudden regular CTD;s have pretty much ceased ZORAN
July 1, 201411 yr Hi i had alot of crashes too but all seemed to go with jims help some returned but got fixed i recently re-installed fsx NOT in the default folder and my addons too. Seemed to do the trick buddy :) Also i had alot of MSVCR80.dll CTD now there gone by like i said above not installing fsx in the DEFAULT folder worked for me! Try this link to re-install fsx properly, http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx Vernon Howells
Create an account or sign in to comment