Hi Jim,

 

Absolute bummer about getting that STACKHASH when starting FSX. Was that as soon as FSX had placed you at a gate? Where?

 

Sorry but what is DEP? I've looked back in our thread and it's not mentioned.

 

The scenery was spectacular in parts of the flight. But the US is very different to Europe. Lots of vast space with very little variation. Not something you get in Europe except for France perhaps but that's a lot smaller. :wink:

 

Was that STACKHASH with an overclocked system? Might it be worth reverting to normal and trying it - repeatedly if necessary to try and reproduce it? If you still get it that would eliminate overclocking. Clutching at straws here. :unsure:

 

Out of interest was address was shown for the STACKHASH error? I'll list mine tomorrow.

DEP=Data Execution Prevention. I remember now.

And given I have paid a reputable company to overclock it I would trust they know what they're doing. They do bench-test it for 48hrs before despatch so the PC should be stable.

 

Ray

 

Sorry to "gatecrash" but would you be willing to let me know who this reputable company is......even via a 'PM' if you're not willing to state publicly.

 

Its just i have this weekend been given the green light from the better half to pull the trigeer on a new £1600 PC - I have it configured on the companies website, was looking at an ASUS Z87 Sabertooth, and was going to let the company overclock it for me - but having read your thread am a little retiscent re the ASUS board and letting the company OC it for me!!

 

Are they based in West Yorks?!?!

 

Regards

 

Steve

 

 

Was that as soon as FSX had placed you at a gate? Where?

 

Yes, at a gate at FSDT KLAX V2.  Tried it again after reinstalling my sound card drivers and this time I got about 20 minutes out in my flightplan and then it stopped abruptly.  My days of flight simming are nearing an end.  I do know I can fix this by reinstalling Windows/FSX but I'm not going to do that.  I might change the memory settings in the BIOS as ASUS had a problem once of not being able to properly identify the memory and provide the correct settings.  StackHash is memory related.  Memory gets stuck at a certain address (the last four digits of the StackHash error).  Anyone who has two monitors like me will get a StackHash crash 100% of the time if they shutdown FSX in full screen mode and FSX starts up in full screen mode.  You have to Alt-Enter to go to Windowed Mode before you shutdown FSX otherwise you will see a StackHash error.  So, it is something as "simple" as that that causes this error at the gate or 15-30 minutes into the flightplan.

 

I have removed all overclocks and just removed the "Optimized Defaults" to Normal. I mentioned DEP because there are several threads here in the CTD Forum where the individuals have fixed their StackHash errors by disabling DEP.  Just wanted to be sure if anyone is reading this now or in the future, they know it does not work (at least for me).  I did get rid of the ntdll.dll CTD so I did make some progress.  There are many more things I can do to troubleshoot but I'm going to take a short breather.

 

Best regards,

Sorry to "gatecrash" but would you be willing to let me know who this reputable company is......even via a 'PM' if you're not willing to state publicly.

Not a problem Steve. I bought from Scan in Bolton. They came out very well in PC Pro customer satisfaction.

 

 

Its just i have this weekend been given the green light from the better half to pull the trigeer on a new £1600 PC - I have it configured on the companies website, was looking at an ASUS Z87 Sabertooth, and was going to let the company overclock it for me - but having read your thread am a little retiscent re the ASUS board and letting the company OC it for me!!

 

Plenty of people haven't had any problems with the Asus boards but there are quite a few complaints about the frozen bios clock on the Asus (ROG) forums. Impossible to call. You may have no problems. But a friend who ordered at the same time as me switched to a Gigabyte board also after a frozen clock and stutters in FSX and that's been fine. Gigabyte are a very good company too.

 

Whatever you choose I hope you enjoy FSX.

Hi Jim,

 

I does sound as though you're near the end of your tether. I agree it's memory related but the resultant data provided in Event Viewer means nothing to most people.

 

I see you have 16Gb of RAM. Have you tried removing two sticks and seeing if that helps? If it doesn't then swap those two for the other two. It's not inconceivable it might be related to faulty memory.

 

For the record I always start and end FSX in windowed mode even though I fly in full-screen. And try exiting via the menu rather than the red X top right.

 

Clutching at straws I know but it's all I can think of. Please don't lose hope. It's not just FSX that suffers with STACKHASH problems. I googled it last night and other programs also suffer. I even found a site that allegedly found a fix and prompted you to download a file but I was very suspicious and backed out.

Out of interest was address was shown for the STACKHASH error?

 

Forgot to answer this yesterday:  StackHash_0a67 is the current address; early last week I was getting some StackHash_7333 CTD's.  Those appear to be gone.

 

 

 

I see you have 16Gb of RAM. Have you tried removing two sticks and seeing if that helps? If it doesn't then swap those two for the other two. It's not inconceivable it might be related to faulty memory.

 

That's an idea I had not thought of.  I really do not need more than 8 GB's.  I may try this but I have a Noctra D14 cooler sitting on top of my CPU which blocks access to the memory.  So that will be my last resort.

 

I'm knocking on wood again as I did a flight from Los Angeles to Phoenix this morning.  I had the smoothest flight ever and high fps mostly over 70 in the PMDG737NGX.  I was flying over MSE V2 Southern California and Arizona.  I was also running ProATC.  Of course I have had a couple of successful flights in between StackHash's or ntdll.dll CTD's but this flight appeared solid.  I'm really not going to be satisfied until I get several successful flights though.  Last night, I did the same flightplan and crashed at about the same location as had happened all day long.  Before the flight last night I had returned my BIOS to 'normal' instead of Optimized Defaults.  I was looking at the MajorGeeks website and saw a great freeware utility that was just released by a bunch of techie's from http://www.tweaking.com/.  It's called Windows Repair - All in One.  What it does is repair the registry (not a cleaner) back to the norm, repairs the firewall, and repairs your whole Windows installation.  It makes a system restore point in case something goes wrong and also backs up the registry.  It did not mess with any installed programs but it did change the sharing and permissions back to the norm (I had been using the utility "TakeOwnership" as I think a lot of problems with FSX is sharing restrictions).  Did the repair and ran the flight from Los Angeles to Phoenix last night and got a little further than my 'normal' crash site but it did crash again with the same StackHash error.  Frustrated, I went to bed.

 

This morning I decided to try again but wanted to first move my modules folder over to a temp folder so that FSUIPC does not load (I had heard some had issues with the latest version - 4.927a).  I also wanted to check permissions for the FSX folder.  I saw that the folder/sub-folders were being shared.  However, under the Security tab I saw that the Creator Owner had no permissions.  So I gave the Creator Owner of fsx and all fsx addon's full permissions.  I also went into the dll.xml and disabled the following:

 

<Launch.Addon>

    <Name>ObjectFlow_W16.dll</Name>

    <Disabled>True</Disabled>  Changed this line from False to True

    <ManualLoad>False</ManualLoad>

    <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_W16\scenery\ObjectFlow_W16.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>RAASPRO</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>.\RAASPRO\RAASPRO.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>FSUIPC 4</Name>

    <Disabled>True</Disabled>

    <Path>Modules\FSUIPC4_Loader.dll</Path>

  </Launch.Addon>

 

Then I did the flight from Los Angeles to Phoenix as described above which was successful, smooth, and with very high fps (70 or higher in wing view; 40 and over in VC).  LOD_Radius is still at 6.5 and TML is still at 2048.  No tweaks.  So now I just have to figure if any of the actions I did this morning is the fix and which one.  This is a little long and apologize for the lengthy discussion but wanted to make sure I covered everything I had done.  I think I'm closing in on a fix.

 

Hope you have a great weekend!

 

Best regards,

Frustrated, I went to bed.

 

Been there, done that with FSX many of times.   :lol:  I also experienced the Mytraffic 5.4C ntll.dll CTD. It seemed to occur in some areas of the world and not in others. I solved it by uninstalling Mytraffic completely and then reininstalling it and updating to 5.4B only.

 

With all the complex add-ons we have pushing the envelope of the FSX SDK and some going beyond, I'm convinced that these CTDs are from conflicting software, both add-ons and windows update. I have an Asus motherboard and am overclocked to 4.5ghz. I have not had any problems or CTD in months, last being MytrafficX 4.5C. I'm no computer genius by any means but attribute my good luck to the following. When I install any add-on, update, windows update, or any software change for that matter, I log it. I make one change at a time and then for a number of flights to make sure there are no problems. When I do have a problem I start uninstalling in reverse order. This is how I found the MyTrafficX CTD and since I started doing this I have been a lot less frustrated.

 

I hope you guys find the root of your problems soon. We don't have the time to be continuosly troubleshooting computers, its ski season!

 

Ted

 

 

I hope you guys find the root of your problems soon. We don't have the time to be continuosly troubleshooting computers, its ski season man!

 

It's golfing season here on the East Coast starting Monday for me!  Thanks Ted for your suggestions.  Good to hear from you.  Hopefully you are flying the PMDG 777 you won at the AVSIM event in Wichita!  Stay warm in Denver!

 

Best regards,

Actualy it was X-Plane 10 and I haven't had time to install it. What little time I have for Flight Sim is logged on FSX.

 

Ted

Hi Jim,

 

You have been busy making changes. Coincidentally I also flew to Phoenix but from KSFO. Taxied out in the dark and watched a very impressive sunrise.

 

More importantly, no crashes which was nice. But it's only one flight so I'm not holding my breath. As the PC goes back tomorrow I'll hold off running any repair utility but I'll bear that one in mind.

 

I notice you don't limit the fps. Any reason? Once beyond about 35fps I can't detect any difference so limit mine to 30. It just means I'm not thrashing the CPU 100% of the time.

 

I haven't had any FSUIPC crashes but I know Pete is working on a fix so that should be sorted soon. As for my StackHash crashes they've occurred at different memory addresses:-

 

e16f

7333

485c

27eb

0a67

 

Strange how they're not completely random. Does that suggest something?

 

I also notice that after reinstalling Windows and FSX you still had crashes. So it seems there's no guarantee doing that will work. Pity.

 

FSX is not alone in StackHash crashes. Plenty of other programs also crash so it's perhaps a OS problem rather than a program-specific one. Any why would Aces deliberately disable DEP for FSX? Seems a daft decision.

 

I'm about to fly a final flight before the Asus mobo is swapped for a Gigabyte one. I'll catch up with other duties next week. I wish you well with your flights. One day these problems maybe sorted. Perhaps switching to P3D is the answer.

 

 

Hi Ray,

 

None of the "fixes" I had in my post #21 worked.  I did have a successful flight to Phoenix but a subsequent flight from LAX to SFO caused the StackHash to reappear but it happened just as I was coming in for landing so I almost made a complete flight.  Last night I rebuilt my fsx.cfg and had a successful flight from LAX to SFO with no CTD.  Of course I need several before I know the problem is fixed.  Just do not have the time...

 

 

 

I also notice that after reinstalling Windows and FSX you still had crashes. So it seems there's no guarantee doing that will work. Pity.

 

Not sure what you mean by this.  I have not reinstalled Windows/FSX since 27 Nov 2013.  I did say (somewhere) that I fixed a problem a couple of years ago by completely uninstalling/reinstalling Windows and FSX.  That was on my old system.  I just built my current system.  A complete reinstall of Windows/FSX will fix the StackHash crash as you are basically wiping out all former memory addresses and setting up new ones.

 

 

 

Any why would Aces deliberately disable DEP for FSX? Seems a daft decision.

 

DEP is security and Microsoft does not like anyone turning off security for any of their programs.  So it is enabled.  You try to disable it and Windows gets very upset.  It's not a fix for the StackHash crashes anyway.  It's something stuck in memory at a certain memory address.  I think it has something to do with the monitors and the settings you have in your fsx.cfg.  You have a setting for fsx dx9 and one for fsx dx10.  If you have two monitors, then you'll have even more with different resolutions.  We know of a definite fix for multi-monitors and StackHash crashes (starting up in Windowed Mode and shutting down in Windowed Mode).  This is why I think I had success last night with rebuilding my Fsx.cfg.  What happened was that FSX started up in full screen in my smaller, secondary monitor.  I had to alt-enter to go to Windowed Mode and then move fsx over to my 30 inch monitor.  This may account for the reason why we never saw this error back when FSX was first released.  Now many have multi-monitors and many are now using DX10 Preview. 

 

I am now seeing more and more people with the StackHash module crash.  It is almost always accompanied with the type of error as BEX (Buffer_Exception_Overrun).  I suspect one is going to have to run fsx as long as he/she can and, when they come upon a BEX/StackHash CTD, they'll have to reinstall everything and start over.  I'm going to try another flight from LAX to SFO and see if I can get two successful flights in a row under my belt.

 

Best regards,

 

 

None of the "fixes" I had in my post #21 worked. I did have a successful flight to Phoenix but a subsequent flight from LAX to SFO caused the StackHash to reappear but it happened just as I was coming in for landing so I almost made a complete flight. Last night I rebuilt my fsx.cfg and had a successful flight from LAX to SFO with no CTD. Of course I need several before I know the problem is fixed. Just do not have the time...

 

Seems to me Jim that's you're getting these crashes at random places. Have you been able to tie them down to a specific point in a flight plan? A message I posted today in this forum nails one that I can reproduce and it does appear linked to Ai settings.

 

Not sure what you mean by this. I have not reinstalled Windows/FSX since 27 Nov 2013. I did say (somewhere) that I fixed a problem a couple of years ago by completely uninstalling/reinstalling Windows and FSX. That was on my old system. I just built my current system. A complete reinstall of Windows/FSX will fix the StackHash crash as you are basically wiping out all former memory addresses and setting up new ones.

 

Ah right,my misunderstanding. I thought it was something you had done recently rather than installed everything on a new PC.

 

DEP is security and Microsoft does not like anyone turning off security for any of their programs. So it is enabled. You try to disable it and Windows gets very upset. It's not a fix for the StackHash crashes anyway. It's something stuck in memory at a certain memory address. I think it has something to do with the monitors and the settings you have in your fsx.cfg. You have a setting for fsx dx9 and one for fsx dx10. If you have two monitors, then you'll have even more with different resolutions. We know of a definite fix for multi-monitors and StackHash crashes (starting up in Windowed Mode and shutting down in Windowed Mode). This is why I think I had success last night with rebuilding my Fsx.cfg. What happened was that FSX started up in full screen in my smaller, secondary monitor. I had to alt-enter to go to Windowed Mode and then move fsx over to my 30 inch monitor. This may account for the reason why we never saw this error back when FSX was first released. Now many have multi-monitors and many are now using DX10 Preview.

 

Understood. I did add a second monitor recently that is shared by another PC. I'll remove that from the equation and rebuild a fsx.cfg but it will have to wait until my PC is returned. I've now packed it up ready to be collected tomorrow.

 

I am now seeing more and more people with the StackHash module crash. It is almost always accompanied with the type of error as BEX (Buffer_Exception_Overrun). I suspect one is going to have to run fsx as long as he/she can and, when they come upon a BEX/StackHash CTD, they'll have to reinstall everything and start over. I'm going to try another flight from LAX to SFO and see if I can get two successful flights in a row under my belt.

 

Do me a favour if you have the time and fly the route in my other post. You don't need to fly it all. if you get to the DIK VOR then you've passed the point where it crashes on me. I see lots of reports of StackHash errors but few indicate precisely where they were when it happened. I've been able to pinpoint a location where it occurs for me.

 

All we can do is change one thing at a time and see if has a bearing. When I get my machine back I'm going to fly with no Ai for a while and see if that changes things. It might be worth you trying that.

 

 

Do me a favour if you have the time and fly the route in my other post. You don't need to fly it all. if you get to the DIK VOR then you've passed the point where it crashes on me.

 

I will try that.  Is that the plan from Denver to San Fran?  I saw on the Internet that it is located near Dickerson North Dakota http://www.airnav.com/airport/KDIK.  Don't know why your flightplan would be going that way unless you are going around the Rocky Mountains. I agree that the StackHash crashes occur at about the same point.  That's what I've been reporting too. 

 

I just finished another flight from LAX to SFO and no CTD.  Two flights without a StackHash error!  That's from me rebuilding my Fsx.cfg.  I really think it has something to do with the monitor display settings in the Fsx.cfg.  I think they get corrupted after opening in full screen instead of windowed mode or fsx opens in the secondary monitor.  I think our display drivers and fsx are confused and fsx crashes.  This is also why it might be crashing near the same location as we might have changed a view (like from VC to wing or spot view) at that location in the flightplan and fsx/your display driver is expecting this again (they say StackHashes are things stuck in memory). 

 

 

 

When I get my machine back I'm going to fly with no Ai for a while and see if that changes things. It might be worth you trying that.

 

I really don't think it's the AI program; otherwise, everyone who has MyTrafficX would be getting the same error (unless it is corrupted).  When they replace your MB, won't they reinstall Windows and you'll have to reinstall FSX?  I don't think you will see the StackHash error again for some time after you get the new MB.  You might also try rebuilding your Fsx.cfg.  You can rename the fsx.cfg and then, if it doesn't fix the StackHash errors, you can rename it back.

 

Are you still getting any of those ntdll.dll errors?  Or was that fixed with the repair of MyTrafficX?

 

Best regards,

Sorry Jim, you've got to come over the the UK for that. London Gatwick to Venice, Italy. As you have the 777 you'll be able to enter the plan manually as follows:-

 

EGKK DVR UL9 KONAN UL607 KOK UM150 UTABA UL607 ELMEM UN606 GIRIS UZ905 VIC LIPZ

 

Dover SID and then 7DME from DIK is where it crashes for me.

 

I agree that the StackHash crashes occur at about the same point. That's what I've been reporting too.

Good. if you can give me a plan to fly and the point at which it crashes I'll try it.
 

 

I just finished another flight from LAX to SFO and no CTD. Two flights without a StackHash error! That's from me rebuilding my Fsx.cfg. I really think it has something to do with the monitor display settings in the Fsx.cfg. I think they get corrupted after opening in full screen instead of windowed mode or fsx opens in the secondary monitor. I think our display drivers and fsx are confused and fsx crashes. This is also why it might be crashing near the same location as we might have changed a view (like from VC to wing or spot view) at that location in the flightplan and fsx/your display driver is expecting this again (they say StackHashes are things stuck in memory).

I'd love to think it was something like that. But after reloading from a saved flight without changing no views it still failed for me. Only by reducing Ai to zero did it work.
 

 

I really don't think it's the AI program; otherwise, everyone who has MyTrafficX would be getting the same error (unless it is corrupted).

It could be a certain flight at that time of day that causes the problem. If you fly the flight I've given please ensure you take-off at 11:57GMT on a Sunday. That way you'll replicate the Ai flights. I had Ai at 40%.

 

When they replace your MB, won't they reinstall Windows and you'll have to reinstall FSX? I don't think you will see the StackHash error again for some time after you get the new MB. You might also try rebuilding your Fsx.cfg. You can rename the fsx.cfg and then, if it doesn't fix the StackHash errors, you can rename it back.

No reinstall of Windows is required. It will automatically detect the new mobo parameters. I will rebuild the fsx.cfg and add one change at a time. I'm going to use the EGKK-LIPZ flight to test StackHash problem.

 

Are you still getting any of those ntdll.dll errors? Or was that fixed with the repair of MyTrafficX?

I haven't repaired MTX. How do I do that? I have posted about my findings on their forum and am awaiting a reply.

Hi Jim,

I've been eavesdropping on your conversation re CTDs and am wondering how many of the MSEv2 states you load for your flights. I've had a couple OOM CTDs but only when I load in several states and hi res airports like FSDT. Since I backed down textures to 2048 and load only the states I'm flying over I've completely cleared the CTDs. I'm running an i7-2700K on an ASUS z77 platform at 4.6GHz with FSX on a WD Velociraptor and the MSEv2 , ASN and REX Essential + OD on a WD Black. I monitor VAS with Process Explorer and rarely exceed 2.7-8 Gb. I also turn off the software firewall since the router hardware firewall I have provides all the security I need.

 

BTW, I have 16Gb of system ram and ASNext, PFPX and FSCommander in separate windows on a second monitor. I run FSX in windowed mode, no AI, with LOD_Radius at 7.0. As you can see, I push the system pretty hard so FSX can be stable.

 

Rick