Hi All

 

I recently purchased a new system for FSX (upgrading from FS9) and CTDs are ruining my fun!

 

I get CTDs with "a fatal error has occurred" message all the time, so much so that I can barely complete a flight as it's almost guaranteed that during the preflight, climb out or cruise phase I will get a CTD either while panning around in spot view or even sometimes just when in the VC.

 

At first I thought SweetFX might be the cause, so I recently started up the sim, disabled this, but still getting CTDs.

 

I tried putting the file that solves some peoples crashes (I forget the name) into my FSX directory but still no joy.

 

I'm running FSX, have installed SP1 and SP2, Win7 64 bit, PMDG NGX, ORBX England, and a few other addons.

 

I also thought it might be to do with overclocking my computer, but it handles 8 hours of Prime95 blend testing with no worries, so guess it's not that.

 

Would appreciate any help as this is sucking all the fun out of my FSX.

 

Cheers

Martin

Can't help without a crash report, either from your Event Viewer or AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html. Copy and paste the crash report here.

 

Best regards,

Jim

Hi Jim

 

I've just gone into Event Viewer (never used this before so not really sure what I'm looking for!) and here are the details from the "Errors" listed from today's crashes:

 

1)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: panels.dll, version: 10.0.61472.0, time stamp: 0x475e180d

Exception code: 0xc0000005

Fault offset: 0x0000e0c6

Faulting process id: 0xf7c

Faulting application start time: 0x01cdc745981a6c70

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\panels.dll

Report Id: 46cf892c-333a-11e2-9736-902b345949d4

 

2)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000096

Fault offset: 0x0364ff4c

Faulting process id: 0xf28

Faulting application start time: 0x01cdc7470fd9c77f

Faulting application path: C:\FSX\fsx.exe

Faulting module path: unknown

Report Id: cd7f55b9-333a-11e2-9736-902b345949d4

 

3)

 

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Flight Simulator® because of this error.

 

Program: Microsoft Flight Simulator®

File:

 

The error value is listed in the Additional Data section.

User Action

1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.

2. If the file still cannot be accessed and

- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.

- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.

3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.

4. If the problem persists, restore the file from a backup copy.

5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

 

Additional Data

Error value: 00000000

Disk type: 0

 

4)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: panels.dll, version: 10.0.61472.0, time stamp: 0x475e180d

Exception code: 0xc0000005

Fault offset: 0x0000e0c6

Faulting process id: 0xd58

Faulting application start time: 0x01cdc747a73c876f

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\panels.dll

Report Id: e45323f0-333b-11e2-9736-902b345949d4

 

5)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: panels.dll, version: 10.0.61472.0, time stamp: 0x475e180d

Exception code: 0xc0000005

Fault offset: 0x0000e0c6

Faulting process id: 0xc10

Faulting application start time: 0x01cdc748ab8dce77

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\panels.dll

Report Id: c6d700f4-333e-11e2-9736-902b345949d4

 

Whatever it is, it seems my "panels.dll" is at the heart of it...

 

Many thanks

Martin

And a couple more from recent days

 

1)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: g2d.dll, version: 10.0.61472.0, time stamp: 0x475e180c

Exception code: 0xc0000005

Fault offset: 0x00043762

Faulting process id: 0xd70

Faulting application start time: 0x01cdc768845ad091

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\g2d.dll

Report Id: e7503484-335c-11e2-9736-902b345949d4

 

2)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3

Exception code: 0xc0000005

Fault offset: 0x0001537a

Faulting process id: 0x13b8

Faulting application start time: 0x01cdc769ae6a877b

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

Report Id: 8fa8fab6-335d-11e2-9736-902b345949d4

 

3)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: PMDG_737NGX_2.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c1b5e4f

Exception code: 0xc0000005

Fault offset: 0x6df5ea9d

Faulting process id: 0x104c

Faulting application start time: 0x01cdc431cd47b7d7

Faulting application path: C:\FSX\fsx.exe

Faulting module path: PMDG_737NGX_2.dll

Report Id: 6d8bdeff-3025-11e2-9cc0-902b345949d4

 

4)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3

Exception code: 0xc0000005

Fault offset: 0x0001537a

Faulting process id: 0x9d8

Faulting application start time: 0x01cdbf2a70f24ef4

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

Report Id: b3b91b94-2b1f-11e2-862a-902b345949d4

 

5)

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: ai_player.dll, version: 10.0.61472.0, time stamp: 0x475e180c

Exception code: 0xc0000005

Fault offset: 0x000364f9

Faulting process id: 0xa58

Faulting application start time: 0x01cdbeb24eaad1e1

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\ai_player.dll

Report Id: 8775fb6a-2ab8-11e2-ac0c-902b345949d4

 

Seems like it's not just the panels.dll module...

Recently had a similar problem, but have not read report errors and were not as many mistakes.

What had my attention the fact that a new system was renovated.

My problem occurred when replacing HD by SSD, also memories, Kingston1333 for AMD (Patriot) 1600.

I did everything from ground zero.

I would need an exorcist, so I thought I'd test memories, testing Windows 7 all ok, but when using Memtest, modules AMD had problems, but only on my computer, I went back old memories and everything resolved.

Memories AMD are new, recently purchased, a friend installed on your computer everything ok, I sold him.

 

My computer:

Phenom II X6 2.8 ghz, Mobo Asus M4A79XTD-EVO, 8 GB Kingston 1333, SSD Intel 180GB (Windows, FSX and P3D only) + HD WD 500GB SATA, ATI 6950 2GB, PS XFX 750W(80Plus Silver).

 

 

João Alfredo

Thanks for your input João.

 

I have checked my RAM modules with Memtest and apparently no errors, so I don't think faulty RAM is the issue. Plus no issues with any other applications other than FSX...

What aircraft were you flying? There's a problem with a gauge or module in one of the panels, most likely the one you were trying to load. Reinstall the aircraft.

 

Faulting module name: MSVCR80.dll, version: 8.0.50727.6195. Indicates an installed program in FSX is looking for this Microsoft Visual 2005 module and cannot find it or it is not installed properly - http://www.microsoft.com/en-us/download/details.aspx?id=3387. You will need to make sure the 2005 SP1 is also installed. A link to that MSV is at the bottom of the link I just provided.

 

Faulting Module: PMDG_737NGX_2.dll. This module is part of the PMDG activation process. According to the error report in post #4, it was unloaded. Evidently the product did not activate properly or there is a problem. I would recommend completely uninstalling the PMDG 737 and reinstalling it. I think the is the crux of all of your errors including the panels.dll faulting.

 

You have the right version of g2d.dll installed (comes with SP2). A lot of problems have been fixed by uninstalling SP2, running FSX, then reinstalling it.

 

Faulting module name: ai_player.dll - This module is caused by a problem with a scenery file in a FTX/Orbx program. You need to go to their forum and do a search for ai_player.dll. This module will not cause a crash but will show up in the logs when you exit FSX.

 

Each one of the crashes or error reports showed a Memory_Access_Violation (0xc0000005). Those are hard to diagnose but it's a very common error and would not worry about it. For instance, if there's a fault in the g2d.dll module calling a file or texture, your system will freeze and the error will be created. Sometimes though it is caused by sliders in the fsx settings set too high.

 

Exception code: 0xc0000096 means STATUS_PRIVILEGED_INSTRUCTION. It is mostly related to video card drivers. You might try reinstalling your video card drivers.

 

Hope this helps!

 

Best regards,

Jim

Hi Jim

 

Thanks for your very detailed reply, I appreciate your help.

 

I was flying the PMDG NGX at the time (it's pretty much all I fly). This morning I uninstalled it completely as well as installing the Microsoft Visual 2005 module and SP that you linked to. I booted up FSX and selected the QW Bae146 to see if I could crash that! I had a little taxi around EGLL, turned on to the runway, applied full throttle, switched to spot view...and....FREEZE! This time, no error message and the application didn't shut down. But it froze and eventually I had to CTRL + ALT + DEL out of FSX.

 

I haven't yet tried uninstalling SP2 and reinstalling. In add/remove programs, I only have an entry for SP2, no entry for FSX itself. If I hit uninstall on this is it going to uninstall the whole program?!

 

One other thing, I mentioned before about the overclocking, well I have a LOT of these warning messages in Event Viewer (not errors, just warnings)

 

A corrected hardware error has occurred.

 

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Internal parity error

Processor ID: 2

 

The details view of this entry contains further information.

 

I'm guessing this means that my overclock isn't 100% stable? But presumably as they're warnings and not errors this isn't what's bringing FSX to a grinding halt?

 

Cheers

Martin

And another one

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: FSRecorder_FSX.dll_unloaded, version: 0.0.0.0, time stamp: 0x4fb8ab92

Exception code: 0xc0000005

Fault offset: 0x0dd7c880

Faulting process id: 0xf7c

Faulting application start time: 0x01cdc7e292464c0c

Faulting application path: C:\FSX\fsx.exe

Faulting module path: FSRecorder_FSX.dll

Report Id: c5e953f5-33d6-11e2-a13c-902b345949d4

 

Again a memory access violation error. This is so frustrating it's unreal!

 

I did several passes of Memtest a few weeks ago and no errors found. I am going to try updating all of my MOBO and GFX drivers and seeing if that helps. I've even turned XMP off in my BIOS and still the same.

I've even turned XMP off in my BIOS and still the same.

 

X.M.P needs to be turned on! It's the best profile for your memory and it's the only setting where you can have the highest timings, frequency, and Dram voltages for your installed memory. If you removed XMP profile, you also need to make sure your frequency, timings, and voltages are appropriate by looking at the CPU-Z utility and then under the SPD tab look at all the various timings and voltages available. XMP is all the way to the right and the best setting for any i7 SB system.

 

Best regards,

Jim

Jim

 

I just do not know what to do anymore, I'm so frustrated with this. Have tried numerous things over the last 8 hours and all to no avail. (By the way I have reenabled XMP now).

 

What I have tried:

 

- Alternate set of memory modules to rule out bad sticks of RAM

- Uninstalled video card drivers and reinstalled a previous version

- Tried running FSX in compatibility (XP SP3) mode

 

None of this seems to make any difference.

 

Every time it's the 0xc0000005 memory violation thing.. I just don't know what else to try. I only have a problem with FSX, no other programs.

 

Also, it seems to now be more often than not that the faulting module is g2d.dll

 

I'm at the point now where I want to throw my PC from a tall building.

 

I have saved a test flight (sat on active runway at EGLL in thunderstorm) which I use as my test as this should be as stressful a situation as should come up in the sim. More often than not I don't even get to the end of the runway before I have a problem and a CTD.

 

Anything else you could suggest? Could it simply be that my sliders are too high and placing too much demand on the resources? Problems with the overclock (although stable in Prime95 and temps ok)? Driver issues? If so what else should I uninstall/reinstall? Motherboard drivers? I don't really have a lot of hardware connected, just joystick and printer.

 

In terms of FSX itself I have QW BAE146, some payware airports and GTX/UTX and ORBX England (this was happening before installing ORBX though).

 

Also using SweetFX and EZDok but have tried disabling these and problem still persists

 

Appreciate any help you can offer.

 

Martin

According to my research on your memory - Corsair XMS3 2000Mhz - timings should be 9-9-9-24 and voltage should be 1.65. You have 9-10-9-27. This appears to be wrong (you may not have changed your My PC profile so maybe you do have the right settings). This is important. You memory will run on goofy screwed up memory settings for some time and even pass stress tests but not for long.

 

FSPassengers has caused several g2d.dll crashes. Fixed by deleting missionpanel.cfg. The g2d.dll is one of the two main FSX renderer libraries. I would look very closely at video drivers and system overheat as a potential source of crashes.

 

The latest version of g2d.dll came with SP2. As I recommended above, did you uninstall SP2, run fsx, then reinstall SP2?

 

The 00000005 exception (memory_access_violation) happens 99% of the time and is not the cause of any of your problems. It's telling you that FSX tried to call a texture, a gauge, a file, whatever and it could not find it so the memory lost it and crashed your system.

 

I thought I might have recommended it but you should be able to save your current overclocked settings in your BIOS (usually in the Tools section). Make sure you save the current overclock, then go to your main BIOS page and reset your settings to the default. See if that fixes the problem. If not, you can always go back in and return to your previous overclock settings. This can be done on an ASUS board, just not sure with Gigabyte BIOS.

 

Did you ever download and install a Driver Updater? I use Driver Scanner - http://www.uniblue.com/. It looks for updates and will charge you if you select to have the program download and install the updates. But you'll see right away what drivers are out-of-date and you can then take that info and go to the sites that have those drivers, download them yourself, and install them. It's much, much easier though to pay for it. It updates your CPU, your USB ports, networking ports, printers, well.... everything.

 

It's looking more and more like you are going to have to completely uninstall FSX and remove any leftover files, run a registry cleaner, then reinstall everything. If you decide to do that then I recommend the procedure at the following link - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx. It is most important that everything about FSX is removed. If you accidently leave the scenery.cfg or the fsx.cfg, or the dll.xml, these files could corrupt your new installation. Before you go through this awful procedure, make sure you try the suggestions above first.

 

Best regards,

Jim

 

According to my research on your memory - Corsair XMS3 2000Mhz - timings should be 9-9-9-24 and voltage should be 1.65. You have 9-10-9-27. This appears to be wrong (you may not have changed your My PC profile so maybe you do have the right settings). This is important. You memory will run on goofy screwed up memory settings for some time and even pass stress tests but not for long.

 

FSPassengers has caused several g2d.dll crashes. Fixed by deleting missionpanel.cfg. The g2d.dll is one of the two main FSX renderer libraries. I would look very closely at video drivers and system overheat as a potential source of crashes.

 

The latest version of g2d.dll came with SP2. As I recommended above, did you uninstall SP2, run fsx, then reinstall SP2?

 

The 00000005 exception (memory_access_violation) happens 99% of the time and is not the cause of any of your problems. It's telling you that FSX tried to call a texture, a gauge, a file, whatever and it could not find it so the memory lost it and crashed your system.

 

I thought I might have recommended it but you should be able to save your current overclocked settings in your BIOS (usually in the Tools section). Make sure you save the current overclock, then go to your main BIOS page and reset your settings to the default. See if that fixes the problem. If not, you can always go back in and return to your previous overclock settings. This can be done on an ASUS board, just not sure with Gigabyte BIOS.

 

Did you ever download and install a Driver Updater? I use Driver Scanner - http://www.uniblue.com/. It looks for updates and will charge you if you select to have the program download and install the updates. But you'll see right away what drivers are out-of-date and you can then take that info and go to the sites that have those drivers, download them yourself, and install them. It's much, much easier though to pay for it. It updates your CPU, your USB ports, networking ports, printers, well.... everything.

 

It's looking more and more like you are going to have to completely uninstall FSX and remove any leftover files, run a registry cleaner, then reinstall everything. If you decide to do that then I recommend the procedure at the following link - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx. It is most important that everything about FSX is removed. If you accidently leave the scenery.cfg or the fsx.cfg, or the dll.xml, these files could corrupt your new installation. Before you go through this awful procedure, make sure you try the suggestions above first.

 

Best regards,

Jim

• 
   
  

 

Hi Jim

 

Thanks for your continued efforts to try and help me.

 

The memory timings I posted in my profile I took directly from the retailer that I purchased the memory from here:

 

http://www.scan.co.uk/products/8gb-(2x4gb)-corsair-ddr3-xms3-pc3-16000-(2000)-non-ecc-unbuffered-cas-9-10-9-27-165v

 

I haven't amended any settings for the memory in the bios other than enabling xmp.

 

I am going to try first of all doing a driver update as you suggest. If this doesn't solve the issue I will try uninstalling and reinstalling SP2. I do not own FSPassengers so we can rule that one out.

 

If none of the above works I am going to revert to default bios settings

 

Will keep you updated on progress.

 

Thanks again

Martin

 

The memory timings I posted in my profile I took directly from the retailer that I purchased the memory from here

 

Okay. Thanks for that. Only the the X.M.P profile can you have a memory voltage of 1.65. Any other profile and the DRAM Voltage should be 1.50v. (Again, this comes from the CPU-Z utility under the SPD tab).

 

A corrected hardware error has occurred.

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Internal parity error

Processor ID: 2

 

Intel's documentation states that you can see this event when a processor wakes up from a low power state. Intense searching on the Internet indicates this is most likely an overclocking or heat issue. Some individuals corrected this by updating their BIOS but I would check your voltages. According to the Gigabyte website for your MB - http://www.gigabyte.com/products/product-page.aspx?pid=4144#ov - there are many updates for this board. Have you installed them? I would do this instead of using the Driver Scan program I recommended above. Look under the Downloads tab and select your appropriate OS to see the list. You can also make sure you have the latest BIOS. I see the F16 bios was just released last month. It has updates for utilities too. I saw that Easy Tune 6 is not compatible with some games and should be uninstalled.

 

Hope this helps.

 

Best regards,

Jim

Jim

 

I don't want to speak to soon but I think I've (you've!) solved my problem...

 

Tried loads of things and no good, then, did what I should have done from the start and restored from my overclock to default settings. Now I can't crash it no matter how hard I try.

 

I loaded up the QW BAE146 at EGLL with Major Thunderstorm theme, and held my finger on "S", cycling through the views at huge speed, zooming in and out at the same time as well as going to town on the hat switch, all these things before were making it crash faster than I could say "V1"!

 

Now doing the same thing at default BIOS settings I can't get it to crash no matter how hard I try!

 

Default BIOS means XMP is OFF and the ram is running at (i think 1066Mhz)

 

Should I turn it ON and see if that works? Also when I turn it on, the RAM frequency goes to Auto (20.00) but before when I set it at 20 Windows wouldn't boot, so had to set it to 18.66.

 

Also the question is now, am I ok to try overclocking again?

 

Thanks so much for your help so far!

 

Martin