Jump to content

Archived

This topic is now archived and is closed to further replies.

vc10man

Level-D 763

Recommended Posts

Having read a good few posts here about simmers virtually tearing their hair out in exasperation at repeated CTDs, I too am rapidly beginning to join that trend of thinking, asking myself,did MSFS actually beta test this FS extensively or was it like their infamous Me OS,released to make a fast buck without a thorough testing which may explain why Ace Studios disappeared off the face,as has been allegorically remarked in a post herein.Scenario:Perfect T/O from YMML to Park at YPPH with the Level-D 763 using FS2Crew VC.Just before shutdown I tried to use the inherent Ground Call to ask for ground power connection.Result?Instant CTD caused by faulting module StackHash_b87cAnyone ever come across this faulting module or can tell me what is it related to,or what is causing it?

Share this post


Link to post
Share on other sites

Have you posted at the Level D forum? Here is what I found using google:http://www.stackhash...kHash_b87c.aspxA StackHash is literally a hash of the stack at the time a crash occurred in an unidentifiable module. See What is StackHash for an in-depth discussion of StackHash crashes and possible causes.StackHash_b87c is a module used to bucket (correlate) Windows Error Reporting crashes into aWinQual event where the crashes are likely to have the same underlying cause.

Share this post


Link to post
Share on other sites

I had stackhash in other AC too, i doubt its LevelD's fault.THe 767 has actually been one of the most stable AC

Share this post


Link to post
Share on other sites
Have you posted at the Level D forum? Here is what I found using google:http://www.stackhash...kHash_b87c.aspxA StackHash is literally a hash of the stack at the time a crash occurred in an unidentifiable module. See What is StackHash for an in-depth discussion of StackHash crashes and possible causes.StackHash_b87c is a module used to bucket (correlate) Windows Error Reporting crashes into aWinQual event where the crashes are likely to have the same underlying cause.
Thanks for that in-depth reply,Robert.have looked up your links but am no nearer why merely clicking on a button should cause this CTD.

Share this post


Link to post
Share on other sites
I had stackhash in other AC too, i doubt its LevelD's fault.THe 767 has actually been one of the most stable AC
Same here. For me the LDS767 has been a beacon of peace and tranquility amidst a sea of CTD-ing aircraft.

Share this post


Link to post
Share on other sites

UpdateFor starters,let me clarify that I never subscribed this fault to be alluded to Level-D's 767-300ER.That out of the way,I tried another flight,another airport,PHNL.Selected a FS2Crew panel load,then deliberately went to the inherent Ground Crew call button,and selected the options for making Power and Air connections fully expecting a CTD.Astonishimgly,smooth sailing.I'm going to now try and recreate the CTD at the arrival airport,KSFO to eliminate if it is an FS2Crew Voice Commander issue or maybe something else.Will update as and when.Wonder if MS's Windows8 will be any better at eliminating these hard code errors?

Share this post


Link to post
Share on other sites

It's my guess that it'll be worse. Not because of it being a bad operating system, but because we are now a few versions past the operating system FSX was designed for, and with Flight on the way, why should MS do people who want to stick with their old sim any favours? They are in the business of selling new software, not keeping old software alive.Al

Share this post


Link to post
Share on other sites
I'm going to now try and recreate the CTD at the arrival airport,KSFO to eliminate if it is an FS2Crew Voice Commander issue or maybe something else.
I remember this issue from when I first got the Level-D 767. This was before I'd even heard of FS2Crew so I doubt that is the cause of the problem. I learnt to treat that ground call button with some respect :biggrin:It was never something that I could reproduce at will, and it didn't occur that frequently. Just one of those things.

Share this post


Link to post
Share on other sites

Rick, I see now that you are using FS2Crew. The Level D767 will crash if you do not have 2-D instrument panel selected in FSX Settings. Just throwing it out there in case you missed that.

Share this post


Link to post
Share on other sites
Rick, I see now that you are using FS2Crew. The Level D767 will crash if you do not have 2-D instrument panel selected in FSX Settings. Just throwing it out there in case you missed that.
Thanks for that HU,Robert.But as I eschew using VC panels,I always generally use 2D panels,so as de rigueur,also use 2D panels whenever I'm using FS2Crew.Update#2I can now fully sympathise with others who have are thoroughly fed-up with either FSX or a combination of FSX+Win7.(1)Earlier on,at PHNL gate,loaded the FS2Crew panel;went to select Level-D's ground crew call.No problems there.Ground crew connected the power and the air.Took off,en route to KSFO until I inadvertently while trying to close one window too many ended up inadvertently shutting down FSX. Ah,well,you win some you lose some.It's only a sim,no lives lost!(2)So,reloaded FSX once more.Back to same scenario,same airport,same gate.Tried the same Level-D ground crew call.And yes,CTD'd.Checked Event Log expecting to see that StackHash error.Instead,I see terrain.dll,g3d.dll.What the----?So,back to square one.(3)Repeated above scenario.And this time the CTD was caused by an error that has manifested itself here time after time,ntdll.dllWhat on earth gives? Is it an FS2Crew-caused error,or an LDS767-caused error,or an FSX-caused error,or plain old stupid Windows 7 throwing up its usual tantrums? Googled for possible answers but there is such a plethora of outdated answers there that it gets even more confusing than unravelling the Minoan maze.Now,before using Nick's tweaks,I had set my Page File at 2.5x system RAM.Nick advocated 3072Mb on both Mim,and Max.So,I'm throwing this open to the smarter simmers than me.

Share this post


Link to post
Share on other sites

HelloThere is a solution, but I seem to draw a lot of flak whenever I mention it.Chock was getting warm though

Share this post


Link to post
Share on other sites

You don't mean read the small print on the FSX case surely?

Share this post


Link to post
Share on other sites
You don't mean read the small print on the FSX case surely?
HelloGetting warmer :(

Share this post


Link to post
Share on other sites

Update#3Boy,this hobby of ours has an unique way of either proving a pleasure to indulge in at times,or at worst make us want to tear our hair out!(1)Re-booted.Started FSX with usual default Trike,then opted for the Level-D 767.Selected PHNL(FSDT's),heavy gate,night=FSX CTD'd.What's new? Checked Event Log again.Again,terrain.dll,g3d.dll errors.(2)Googled.Saw another poster using Aerosoft scenery having same issues,etc.Then decided to take a wild shot and updated the ATi GPU drivers to latest.Re-booted.(3)Step 1 repeated+FSC9 to give me the map follower,no REX,or anything of that sort.Loaded FS2Crew start-up panel which takes power from the APU.So far so good.Tried the LDS's power+air call-ups again,and amazingly,no CTD.Even managed to switch of the APU.Holy Smoke! Then,close to start-up as per the Voice Commander schedule,was even able to disconnect LDS's power+air at gate after switching to APU,and then disconnect LDS's inter-phone after push-back +good starts.Now safely en route to KSFO. What gives with this crazy,sometimes enjoyable and times downright maddening hobby?

Share this post


Link to post
Share on other sites
....Use Windows XP 64bit....?
HelloWe have a winnerIf you would like to run FSX with all of the compatability & stability it had under XP but would prefer to miss out on the OOM issues of 32bit then XP64 is the logical choice.I only mention this as I have Zero issues with either Sim with loads of addons and hardware connected.I will now put my tin hat on and duck for cover :(

Share this post


Link to post
Share on other sites

There is a rather long sicky thread on this very issue in the Level D FSX forum. It would be worth trying the things mentioned in there if you haven't already.I also agree with above poster. XP64 is the better platform for FSX.

Share this post


Link to post
Share on other sites
HelloWe have a winnerIf you would like to run FSX with all of the compatability & stability it had under XP but would prefer to miss out on the OOM issues of 32bit then XP64 is the logical choice.I only mention this as I have Zero issues with either Sim with loads of addons and hardware connected.I will now put my tin hat on and duck for cover :(
Thanks for that very helpful suggestion.Trying to get a WinXP 64-bit is even much more difficult than the trials and tribulations I had nailing this down.No need for your tin hat though!

Share this post


Link to post
Share on other sites
Thanks for that very helpful suggestion.Trying to get a WinXP 64-bit is even much more difficult than the trials and tribulations I had nailing this down.No need for your tin hat though!
HelloEbay seems to be the best place now.But for some reason it seems to attract a lot of bids and consequently can get expensive

Share this post


Link to post
Share on other sites
HelloEbay seems to be the best place now.But for some reason it seems to attract a lot of bids and consequently can get expensive
Silly me! Now why did I not think of that? Yes,a 64-bit XP would also address my 16Gb RAM,or I hope it'd do.But I'm a bit aware of Alan's comment of the sim going backwards with an old OS.Thanks for the tip all the same.

Share this post


Link to post
Share on other sites
Silly me! Now why did I not think of that? Yes,a 64-bit XP would also address my 16Gb RAM,or I hope it'd do.But I'm a bit aware of Alan's comment of the sim going backwards with an old OS.Thanks for the tip all the same.
HelloIt is an old Sim that benefits from being run on the platform that was around at the time it was developed.Starting its Development under XP and DX9, in the beginning MS had hoped that FSX would be a marquee release to herald the arrival of Vista.Unfortunately Vista bombed, 5ghz single core cpu's never happened and Aces never got round to completing DX10 support -- then got fired..There is nothing in W7 that FSX absolutely needs, added to that W7 is still a moving target with constant updates that risk destabilising the house of cards that is FSX + addons.My system here runs without issue using XP64 Dx9c and Nvidia driver 182.50, TrackIr driver is one revision back on purpose.Recently I have updated to the new Goflight Drivers which have included i-fly support but will view this set with suspicion until proved stable on my Sim rig, if something does go screwy I know what to blame.I may at some future date have to move OS's if new hardware dictates, but for now it all works fine.Luddite?, this hobby makes you that way in the end :(

Share this post


Link to post
Share on other sites

Final UpdateTime to file the latest,and fingers crossed,Last Update.Just landed at KSFO(Flightbeam's),night.At heavy gate,went through the Shutdown Checklist with my 'grumpy FS2Crew FO.Saved the flight,then went to the LDS's ground crew call to connect power and air fully anticipating that CTD.Voila! Power+Air connected! Time to disconnect the APU and get the hell out of here,FO.What's ya name,BTW?All works now.Phew! What I do not know for sure is,did increasing the Page File from Nick's 3720Mb or the latest ATi drivers make that significant swing? Thanks for the various inputs.

Share this post


Link to post
Share on other sites

Just when I thought I had overcome the g3d.dll error bringing down FSX,as per previous post,lo and behold the gremlin strikes again.And caused by? After a long FS2Crew Voice created KSFO-PHNL flight,just about to commence descent into PHNL,FA's button in the middle driving me bananas with its constant bing-bong,went to switch it off,and down comes FSX.Event Log reports faulting module as g3d.dll. As per MS ran dxdiag,passed all tests,so what exactly triggers this g3d.dll to crash FSX? I have searched high and low for an answer.Nobody seems to have found a solution that I have been able to source.Maybe somebody has an answer? How can merely pressing a button bring down FSX?

Share this post


Link to post
Share on other sites

Rick, have you thought of posting over at the FS2Crew forum by any chance? I am sure you are becoming extremely frustrated, you might as well give it a try.

Share this post


Link to post
Share on other sites

×
×
  • Create New...