Faulting application name: FSX.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29cException code: 0xc0000005Fault offset: 0x0002e25bFaulting process id: 0x13bcFaulting application start time: 0x01cb44c60b43da2bFaulting application path: X:\FSX\FSX.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: ae906035-b0be-11df-99c2-6cf049589ee8andFaulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: nvd3dum.dll, version: 8.17.12.5896, time stamp: 0x4c378e88Exception code: 0xc0000005Fault offset: 0x003514c3Faulting process id: 0xd98Faulting application start time: 0x01cb44c4623026caFaulting application path: X:\FSX\fsx.exeFaulting module path: C:\Windows\system32\nvd3dum.dllReport Id: 39afd047-b0b9-11df-99c2-6cf049589ee8Windows7 64-bitThe rest of the info on my system is in my footer.I recently reinstalled FSX on a new SSD. My controller settings never save (so everytime it crashes, I have to go back in and enter them all again.. not fun).If anyone has some clues as to why this is happening, I'm all ears.

FSX running in Admin mode? Security levels set to allow writting to hard drive? Best I can think of......hope it helps.

FSX running in Admin mode? Security levels set to allow writting to hard drive? Best I can think of......hope it helps.

Yes, Yes, Yes. UIAutomationcore placed and all that fun stuff.

Yes, Yes, Yes. UIAutomationcore placed and all that fun stuff.

Somehow this might have all been attributed to REX weather insertion. I replaces it with ASE and it hasn't crashed yet.

Faulting application name: FSX.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29cException code: 0xc0000005Fault offset: 0x0002e25bFaulting process id: 0x13bcFaulting application start time: 0x01cb44c60b43da2bFaulting application path: X:\FSX\FSX.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: ae906035-b0be-11df-99c2-6cf049589ee8andFaulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: nvd3dum.dll, version: 8.17.12.5896, time stamp: 0x4c378e88Exception code: 0xc0000005Fault offset: 0x003514c3Faulting process id: 0xd98Faulting application start time: 0x01cb44c4623026caFaulting application path: X:\FSX\fsx.exeFaulting module path: C:\Windows\system32\nvd3dum.dllReport Id: 39afd047-b0b9-11df-99c2-6cf049589ee8Windows7 64-bitThe rest of the info on my system is in my footer.I recently reinstalled FSX on a new SSD. My controller settings never save (so everytime it crashes, I have to go back in and enter them all again.. not fun).If anyone has some clues as to why this is happening, I'm all ears.

The error 0xC0000005 is generated by an illegal "memory access violation". This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software, or malware. In your case, I think you are placing too many resources on fsx and your way overclocked system is having problems processing all the instructions being placed on it by fsx. Thus, you are getting the illegal memory accesses. Pull back your overclocking gradually until your system becomes more stable when running fsx. Turn down some of your fsx sliders. Best regards,Jim