Moved FSUIPC to top of dll.xml (after addon manager). Still get error.

 

Then Im afraid you must follow the long way, been there, done that (many times in our software company)

 

Remove all entries, and start adding one by one until you nail the culprit. (If dll.xml is where the problem is.)

Are you running AddonConverter, Jim?

Are you running AddonConverter, Jim?

 

No. I have nothing to convert (except I had some stuff at Victoria but I renamed those bgl's and no longer have that problem). Ramon (above) sent me a nice PM asking if I needed the orig General10 shader folder and I told him you had provided it in the DX10 Forum. I also provided him some of the other findings which I will add here so that all can see what I have done:

 

"In addition to some of the other 'fixes' I had (like renaming the dll.xml or turning off DX10), I started up FSX and let FSX run on my secondary monitor. I have two monitors, one the Dell 30" and one the Alienware 22". FSX always starts up on the smaller monitor where I normally go to windowed mode and move FSX over to the primary monitor. I then go to full screen and let FSX run for a few seconds, then close it and the StackHash error pops up. If I leave it on the secondary monitor (the smaller one) and close FSX, the error does not appear. So it could be video card drivers. I also disabled the secondary monitor and ran fsx on the primary monitor, closed FSX and the error did not appear. So think now it's something to do with the monitors (drivers are up-to-date) or the video card drivers. I suspect there could be a setting in Nvidia Inspector that DX10 doesn't like but then others would be having that issue too. I will disable items in the dll.xml two at a time and see if there's an issue with one of the modules. I think the fact that the renamed dll.xml freed up memory is why the error did not occur or a fluck. Thanks again for your help!"

 

Best regards,

Jim

Hmmm .. sounds like something's happening when switching between the two ports.. still a single 580, right? Do you configure FSX for both ports separately in Inspector?

Do you configure FSX for both ports separately in Inspector?

 

Sorry for the delay in responding Paul. Busy. Had to golf. :lol:

 

No. I do not configure ports separately in Inspector. In Nvidia Control it shows two monitors... and 1 and a 2. My primary is the 30 inch. The secondary is the 22 inch. What is strange is that I have been using two monitors for over a year now and have had no problems. The secondary goes dark when I switch to full screen in FSX. Thanks again for your help.

 

Best regards,

Jim

Okay, after days and hours of Googling and reading the suggestions from my fellow flight simmers, I found the solution (at least in my case). In my case I had DX10 Preview turned on. If I went to DX9, the problem went away. If I had DX10 Preview turned on and opened FSX, FSX would open on the main FSX screen (I have two monitors). When I clicked Go Fly, FSX would open up on my secondary monitor in full screen view and my main monitor went black. I had to alt-enter to go to Windowed Mode then move the screen over to the main monitor and alt-enter and go to full screen. No problems. FSX ran great until I shut FSX down. The StackHash error appeared. The StackHash error will always appear in DX10 mode if you close FSX on the main monitor in Full Screen. If you go to Windowed Mode then close FSX on the main monitor, there was no error. If you are in full screen or windowed mode on the secondary monitor and close FSX, no StackHash error. It only occurs if exiting from the main monitor. So make sure you go to Windowed Mode before exiting FSX. That way, when you reload FSX, it will start up in Windowed Mode and you simply need to hit alt-enter to go to full screen. Hope this helps someone.

 

Best regards,

Jim

Glad you got it figured out Jim. Just read this thread as it came up in a search I did after my first stackhash crash. I've never used the dx10 preview and only have 1 screen. I guess I'll need to look elsewhere for a solution.

 

-Kevin

I guess I'll need to look elsewhere for a solution.

 

If you look a couple of posts down in this forum, you'll see others had StackHash crashes. As you can see in one, the SuperSpyWare program and cleaning of the registry fixed a problem for one. The StackHash crash is complicated and hard to fix but we have a few here in this forum who have been successful. If you want any help, please post your crash report in a new post. And, if you do find a fix and didn't post a crash report, it would be helpful if you posted what happened and how you fixed your crash (even if it's the same as using the SuperSpyWare program). Good luck!

 

Best regards,

Jim

Hey Jim: FWIW...I NEVER had this issue for years until now. I just upgraded to Win8Pro(64) but I don't think that has anything to do with it (although I've run into a lot of issues with the install). In the upgrade process, I spent days updating all my drivers, and used two driver update program to confirm all are up to date. I've always run DX9 mode. Running my 737NGX with FS2Crew and GSX, I always save my flight in Full Screen, but in the 2D cockpit. I have found that if I don't make any changes to anything, I might get it to stay stable. But if I as much as change the date and/or time, within a minute or two I get the StackHash CTD afterwards. I was amazed to find your post here (in fact, as you helped another gentleman out with a AppCrash problem, I was about to post my issue!), because the only Google search I ever found with "StackHash_????" were about 10 Russian sites, one of which suggested a virus. I have run two scans: one with Defender, and another with Malwarebytes- no issues. Fsx.cfg is *******' tweaks only. I am about to pull what hair I have left all the way out. I hope you find us all a solution...good luck to US!!! :-) And thanks for all your work here!

I am about to pull what hair I have left all the way out. I hope you find us all a solution...good luck to US!!! :-) And thanks for all your work here!

 

Hi Sean,

 

Sorry to hear you are have this issue too. If you are searching for StackHash errors, just search for StackHash. Don't be concerned with the hexadecimal code at the end such as _ab58 as that is only the address in memory of the faulty code. A BEX StackHash CTD is the same for everyone but with different solutions. 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. Adjusting memory settings in the BIOS has helped others as maybe the memory frequency, timings, or DRAM voltages are wrong.

 

In my case above, it was not DX10 that caused the crash but my two monitors (and it really wasn't a crash but the error message popped up everytime I closed FSX). I think FSX stores info into memory that says FSX was last closed in full screen mode but somewhere along the line I opened up fsx on my secondary monitor and closed it on my primary monitor thus confusing FSX and it then initiated a StackHash error with the hexadecimal code at the end showing the address in memory of the faulty code. I can replicate it right now by closing FSX in full screen in DX10 mode but I know now I only have to go to Windowed Mode before closing FSX and I'll have no error.

 

One of the things you can try is to periodically clear your memory cache. Here's how:

 

Right click your desktop and select New Shortcut.

Once it opens, type the location of the item you want to run: %windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks (copy and paste this into the box)

Give it a name such as Clearing Unused Ram

 

You are all set. Just double-click this and you should see a little more performance on your system (until the cache gets full again).

 

It might not fix your StackHash crash but it's an easy way to find out if it does. You can also copy and paste the command into your Run command box and it will do the same. Nothing will open up. It will only clean the memory cache.

 

In addition to the above, make sure you have checked 'Empty scenery cache on exit' in the Scenery Library.

 

Wish there was a magic bullet for this crash but evidently not as some 'fixes' work for some and not for everyone (like the uiautomationcore.dll fix. I have never employed it or have had the problems some members have had with this CTD but the uiautomationcore.dll fix works for those who do get some crashes, like a menu crash).

 

Hope this helps!

 

Best regards,

Jim

Jim:

 

Thanks for all the suggestions- especially the Shortcut one- that's pretty nifty. Short of fiddling with my BIOS settings (all I've got is Asus' auto-oc feature on for a mild OC and have had it since I put this computer together in May and haven't had any problem, I tried all the other suggestions, but to no avail. I'm starting to wonder if "something" corrupted my files, so I'm going to do a reinstall of FSX and all my add-ons.

 

A couple of days ago, all the way back to finding out Full Screen mode years ago, I've always saved in Full Screen. Even after getting the 737NGX and FS2Crew, I always did with nar a problem. And I never had the uiautomationcore.dll problem either (and don't now).

 

Sure do appreciate your help here....one of these days hopefully the definitive answer will pop out!

 

Sean

Asus' auto-oc feature on for a mild OC

 

I have an ASUS board too and tried the auto oc feature and it never worked for me. Constantly got crashes (but can't recall what kind). It would work for a few hours or a few days but then a crash. Ran Prime 95 and the Intel Burn Test and the Windows Memory Diagnostic test and everything passed. I then ran the CPU-Z utility and decided to reset the memory settings in the BIOS based on the settings shown in the SPD tab of the CPU-Z. I had read somewhere on the Internet where that ASUS has a hard time setting memory automatically for their boards. As I recall the memory frequency was set to Auto and so were the timings but the voltage was set okay. So I changed the frequency to 1600 and went to the timing page and set the timings in accordance with those shown and then made sure the voltage was set to 1.50. It worked! No more crashes. Since then I have set my memory settings at the highest frequency possible and that's the settings shown under the X.M.P. profile. First off you have to change your profile to X.M.P. (the first setting in the BIOS, then your freq to 800 (800 x2 = 1600MHz), then the timings. The DRAM voltage was 1.65 for my memory (it's shown in the CPU-Z or in the last TAB in the ASUS bios under Tools). It worked! So first off I would go back to the original 1.34 GHz setting for your board then maybe manually overclock as I have suggested.

 

Best regards,

Jim

Jim:

 

I decided to uninstall ALL of my FSX and it's related programs, ran CCleaner, and checked all the folders. I also found that when you think you are turning off UAC in the normal interface, that's it off- it isn't. You have to go into the Reg to completely turn it off. So I did. I then set my BIOS back to normal, and started reinstalling FSX. But in between each part of the install, I ran the 747 up and made changes...then started to get the uiautomationcore.dll errors! Never had those! I then got a DPC_WATCHDOG_VIOLATION, followed by a couple of other BSOD (although Win8 doesn't really "blue screen" on you these days) issues.I ran memtest86-4.0a last night, no errors, so I don't know where to go now. The common denominator to all these problems is Windows 8 and a new Samsung 840 Pro SSD I bought to load it onto. I am now in a quandary to either reload Win8 without my system overclocked, or go back to Win 7 (I loaded Win7 back in May with an OC'd system). When I can get a stable system running, I will then fool with the BIOS OC. I will also probably bug you for some more info as you've stated above, as I'm not an overclocker and never really intended to be one, but it sure is nice with FSX when you've a few more gHz going!!! Thanks again!

Jim:

 

UPDATE: I decided to take the plunge and delve into the BIOS (What the heck...I was contemplating suicide anyway, ey?!). I set XMP in BIOS, while also letting it auto OC the CPU, and have registered on the Gskills forum and posted for settings information (nice value they add!). I did take the default 747 for a spin (about 10 minutes worth) and no problems so far! CPUID is confusing, but things seem to be running OK for now. Will report back on any developments. Thanks for your efforts here! System is lighning fast right now....I was getting 50-70 fps with the default 747! Next task is to load all the other stuff (especially my beloved 737NGX!)

Hi Sean,

 

DPC_WATCHDOG_VIOLATION indicates you most likely had a hardware failure or a driver to one of your pieces of hardware is corrupt and not installed properly - http://msdn.microsoft.com/en-us/library/windows/hardware/jj154556(v=vs.85).aspx. Here is a possible solution - http://www.sysnative.com/forums/showthread.php/2090-BSOD-DPC_WATCHDOG_VIOLATION-in-Windows-8. You need to look at your Device Manager (click on your Start button and in the menu search bar type Device Manager then look up in the menu and click on Device Manager). Once open look for a yellow or red X and that should tell you what is the bad device or it did not install properly. Once there you can double-click and select the driver tab and then request an update to the driver. In your BIOS, make sure that it shows your SATA SSD Mode is set to AHCI and not IDE. Here's a complete guide on installing SSD's - http://lifehacker.com/5932009/the-complete-guide-to-solid+state-drives. You also have to make sure the TRIM command is on but I think that happens automatically when Windows identifies your SSD.

 

Best regards,

 

Jim

 

I set XMP in BIOS, while also letting it auto OC the CPU,

 

Great! XMP profile is the fastest for your system and installed memory.

 

Best regards,

Jim