I have been having this issue for a while now. Everytime I descend into the PHNL area with the FSDT scenery, I get a CTD with the following error..

 

 

Problem Event Name: BEX

Application Name: fsx.exe

Application Version: 10.0.61472.0

Application Timestamp: 475e17d3

Fault Module Name: StackHash_ab46

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 74d5c9f1

Exception Code: c0000005

Exception Data: 00000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: ab46

Additional Information 2: ab46b3b696c4386cb918452ef6a6a6e5

Additional Information 3: 3e3d

Additional Information 4: 3e3d69af832149c5f47c99a386ac7394

 

Has anyone else had a similar issue with a possible fix? I tried googling with no luck...

 

Thanks!!!

StackHashes are basically data from programs that are in memory, that is unreserved for that program. You see there is memory reserved for each program when it starts. FSX will fail, or crash when that code is copied into memory and it loses some data. Data loss happens because it simply ran out of room and over wrote the memory that was previously there, stringing the data together confusing the processor. The hexadecimal code, ab46 at the end of your StackHash error is the address in memory of the faulty code. It can also happen if FSX pushes the data into memory blocks and can’t remember it did. This is called buffer overrun. It has too much data to process at the time and it overruns the buffer and is pushed into those reserved blocks of memory I referred to.

 

It has been fixed by many here on AVSIM by changing your virtual memory setting to 'System Managed Size' as FSX, an old program, seems to like that setting better. If this doesn't work for you, I would post your issue over at the FSDT forum as the developer over there is very knowledgeable.

 

 

Best regards,

Jim

Jim, I went ahead and did just as you said. I will report back on my findings. Thanks again for getting back to me, I really appreciate it!!

Hope it works for you too Aaron!

 

Best regards,

Jim

Hey Jim, tried my first flight into PHNL after you suggestion and received the following crash. about 10-15 miles out.

 

 

Problem Event Name: APPCRASH

Application Name: fsx.exe

Application Version: 10.0.61472.0

Application Timestamp: 475e17d3

Fault Module Name: g3d.dll

Fault Module Version: 10.0.61472.0

Fault Module Timestamp: 475e180c

Exception Code: c0000005

Exception Offset: 000583df

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

 

I have the paid version of the most recent FSUIPC installed. Any thoughts on this??

I have the paid version of the most recent FSUIPC installed. Any thoughts on this??

 

At least you got rid of the StackHash error!

 

FSUIPC does not fix every g3d.dll error. It is related to memory. Reducing your sliders and/or display driver settings might fix it. It could be a bad setting in the fsx.cfg that your system doesn't like. You can save your fsx.cfg to fsx.orig, restart fsx and let the config rebuild. Run fsx and see if this fixes the problem. If not, return to the fsx.cfg you saved. It could be bad system memory settings in your bios. Some ASUS boards do not handle memory very well, especially if any setting is set to Auto. Your settings should be set as shown in the CPU-Z SPD Tab (the X.M.P. profile is the best and fastest). The settings are also shown in the Tools tab of your BIOS. It could be a bad overclock too with your CPU voltages set too high or too low. Mine are set to 1.400000 for CPU voltage. Much lower or higher than that will cause problems. Lastly, you did not indicate what kilowatts you have for your PSU but an overclock and a PSU below 700 KW could also cause a crash.

 

Hope this helps.

 

Best regards,

Jim

Hey there Jim,

 

I have an 850W Gold Corsair PSU. My memory settings are in fact set to auto. I remember in the OC process reading the same thing you discussed. I am setting them to 9,9,9,24,2 as showing in my CPU-Z. Hopefully this is the ticket!!

 

Thanks again,

 

Aaron

Jim I adjust the memory as you requested and it seemed to do the trick. I did everything I could to try and bring the error up again...view switching, loading weather, spot plane panning..ect...smooth as butter. Thanks again for the help!

 

Sincerely,

 

Aaron

Hi Aaron,

 

Glad to see you got it fixed (well hopefully it won't come back). I went through this issue myself. With my memory set at auto, I ran Prime95 and other memory system tests and had no problems. My system was stable. I would then run FSX, and bingo, a crash. I then read an article where ASUS has had some problems managing memory for i7 systems so set my own frequency, timings, and voltages. FSX has been running smoothly since then. Thanks for posting the fact this worked for you. It might help others fix their CTD problems too.

 

Best regards,

Jim

Hey Jim, might have spoke too soon. Just did another test flight from PHKO to PHOG and sure enough on approach into PHOG we get a ...

 

 

Problem Event Name: BEX

Application Name: fsx.exe

Application Version: 10.0.61472.0

Application Timestamp: 475e17d3

Fault Module Name: StackHash_5a5f

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 7522c9f1

Exception Code: c0000005

Exception Data: 00000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 5a5f

Additional Information 2: 5a5fff32f14926c7d5dbd240d88f1719

Additional Information 3: 5210

Additional Information 4: 52103f27f9296bfaacfdcd465fabf758

 

 

Hmmmmm....

I am going to turn off DEP in hopes this will solve the stackhash issue. The operation I completed is listed here. http://lkalamaras.blogspot.com/2008/08/was-this-for-our-own-good-part-deux.html

Jim Just tried another flight with a crash and this came up...

 

 

 

Files that help describe the problem:

C:\Users\Aaron\AppData\Local\Temp\WER6345.tmp.WERInternalMetadata.xml

C:\Users\Aaron\AppData\Local\Temp\WER80D4.tmp.appcompat.txt

C:\Users\Aaron\AppData\Local\Temp\WER81AF.tm

 

Any ideas?

Jim Just tried another flight with a crash and this came up...

 

Yes, if you run App Crash View, it will give you the data from these files, much like in post #10. Since you continue to experience crashes, then it has to be a bad overclock or your overclock is causing overheating.

 

Best regards,

Jim

Ok thank you for the input. I have run both prime (4 hrs) and the intel burn test with success to ensure a stable overclock. Under 100% load the hotest my system got was during the end of the intel burn test at 78C, Which I never come close to when running FSX. Any other thoughts on how to ensure my OC is stable?

I don't see how you can turn off DEP because, if you go to the DEP program and select turn on DEP for all programs except the following and you go the fsx.exe folder, it will come back and say you cannot turn DEP off for this program. If it did not fix your problem, I would turn it back on.

 

I would save your current overclock settings in the tools tab of your ASUS bios then return your system to normal 3.4GHz. See if that fixes the problem. If it does, then there is a setting that is wrong in the bios. If the problem still persists, then you can go back and load your overclocked settings again.

 

If that doesn't fix the problem, then look for a possible Malware by running these tools:

 

Malwarebytes Anti-malware : http://www.malwarebytes.org/products/malwarebytes_free

SUPERAntiSpyware : http://www.superantispyware.com/

 

Best regards,

Jim