Sign in to follow this  
Jeeeno

Issue when closing FSX using the B777

Recommended Posts

Hello,

 

I have an issue when using the B777 on FSX SP2: every time I close FSX it crashes. The faulting module is always kernel32.dll. I searched through the forum and I found many topics about this subject but they never offered a solution. I have FSUIPC free edition fully updated, W7 64 bit fully updated. I don't have VAS issues when ending a flight as I have as low as 3GB of Virtual memory.

I also tried PMDG support ticket but they didn't answer. 

 

Any solutions?

 

Giorgio

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Any solutions?

No solutions. I can't remember exactly what support wrote me when I submitted a ticket 3 years ago but the basics of it was there is no solution.

 

This was the final reply from support. "The problem cannot be fixed in FSX DVD version unfortunately since Microsoft dropped support for the product. FSX SE is the only version of FSX actively in development if you don't count Prepar3D."

Share this post


Link to post
Share on other sites

 

 


kernel32.dll

 

This is a Windows module - not a PMDG module.

 

 

 


I also tried PMDG support ticket but they didn't answer. 

 

Highly unlikely. I just cleared the queue.

 

When did you submit, and how?

Share this post


Link to post
Share on other sites

A suggestion if you are not always doing this. Are you ending the flight first via the FSX menus?  I do this to insure that the flight is written to the flight log, but it provides a different sequence to shutting down FSX (two steps) compared to just exiting without ending the flight!

Share this post


Link to post
Share on other sites

Ok Kyle, but Giorgio says it only happens with the 777 and Michael acknowledged the problem so it definitely has something to do with PMDG.

Share this post


Link to post
Share on other sites

This is a Windows module - not a PMDG module.

 

 

 

Highly unlikely. I just cleared the queue.

 

When did you submit, and how?

So, I'm using FSX with dozen of other aircraft with no issues at all and the problem is Windows. Seems legit.

I submitted the ticket on the 7th or 8th of December. Cannot check in this moment

 

  

No solutions. I can't remember exactly what support wrote me when I submitted a ticket 3 years ago but the basics of it was there is no solution.This was the final reply from support. "The problem cannot be fixed in FSX DVD version unfortunately since Microsoft dropped support for the product. FSX SE is the only version of FSX actively in development if you don't count Prepar3D."

 

 

I cannot understand this: FSX boxed and FSX-SE are basically the same simulator.

 

 

 

A suggestion if you are not always doing this. Are you ending the flight first via the FSX menus?  I do this to insure that the flight is written to the flight log, but it provides a different sequence to shutting down FSX (two steps) compared to just exiting without ending the flight!

In general when I end a flight I always use this procedure: press ESC, checking flight analysis, then click on end flight. After clicking on "end flight" I have the crash when using the 777.

Share this post


Link to post
Share on other sites

I checked now. My ticket was sent on the 7th of December and is still saying "waiting for agent"

Share this post


Link to post
Share on other sites

 

 


So, I'm using FSX with dozen of other aircraft with no issues at all and the problem is Windows. Seems legit.

 

If you're going to be smarmy, be smarmy with:

  1. someone who isn't trying to help you
  2. someone who doesn't know more than you about who code and other functions work - being smarmy and wrong gets a little embarrassing

So I'm building a table in my living room that calls for a bunch of hand tools: a hammer, a screwdriver, and a socket wrench. I then go to IKEA to get an end table and notice that it requires a metric socket that the socket set that I bought from Home Depot no longer contains because I snapped it a while ago.

 

Is this an IKEA problem or a Home Depot problem? It's a Home Depot problem. The IKEA furniture may have called for the use of a tool, but it isn't the fault of IKEA if you don't have it, or it's broken. Similarly, if the faulting module isn't one we've written, but your install of Windows contains a corrupted dll, or is otherwise in a state where our code is not able to work, then...well...it isn't going to work.

 

 

 

So...after that little reset, let's start over and I'll forget the earlier smarmy remark...

 

What operating system are you using? If it's Win7, have you done the uiautomationcore.dll fix?

 

 

 


I cannot understand this: FSX boxed and FSX-SE are basically the same simulator.

 

Basically the same, yes. Exactly the same? No.

 

 

I checked now. My ticket was sent on the 7th of December and is still saying "waiting for agent"

 

It was forwarded directly to one of our other agents. I'll hit him up to see if he says anything different.

Share this post


Link to post
Share on other sites

cannot understand this: FSX boxed and FSX-SE are basically the same simulator.

At the time PMDG Support answered my ticket, I belive there was some development going on with FSX-SE by Dovetail. PMDG was hoping the code might be changed so that a proper exit could be made by the few FSX-SE users that reported this issue. As for FSX it not changed in the past ten years and will never change.

Share this post


Link to post
Share on other sites

Briefly: is FSX SP2 supported by PMDG? 

 

FSX SP2 and FSX Acceleration are both supported.

Share this post


Link to post
Share on other sites

FYI

I have no problems at all with 777 and 737ngx. I just exit FSX, not End Flight first. Doing that it just exits without any msg.

 

Win7 64 bit professional and FSX:SE. Exit that way also worked OK in box FSX

Share this post


Link to post
Share on other sites

FYI

I have no problems at all with 777 and 737ngx. I just exit FSX, not End Flight first. Doing that it just exits without any msg.

 

Win7 64 bit professional and FSX:SE. Exit that way also worked OK in box FSX

 

Didn't have time to test yet. Will have a try, thanks.

Share this post


Link to post
Share on other sites

Tried to close FSX by pressing X on the right upper corner: didn't work. Still kernel32.dll error.

 

I ran out of options.

Share this post


Link to post
Share on other sites

PMDG,

 

does this also happen on FSX-SE or is this one really supported?

It looks like this type of crash on exit on FSX is resetting the airframe hours, which I'd call a game-breaking bug!

Share this post


Link to post
Share on other sites

So? Are we just gonna leave Jeeno with a bugged triple seven? That's something I'd expect from mindstar, not from PMDG. Can at least someone confirm that the kernel32 crash on exit bug is not present on FSX Steam Edition?

 

Buying FSX SE and going through the process of reinstalling every addon, only to find out that the kernel32 is still messing up the 777... Giorgio would be pretty bewildered and worked-up I think.

 

I don't have the 777 but never had any issues with the 737, neither in FSX boxed, nor in P3D.

 

Regards,

Fabrizio

Share this post


Link to post
Share on other sites

 

 


So? Are we just gonna leave Jeeno with a bugged triple seven?

 

I'm assuming you missed my earlier comment that the Kernel32.dll is not a PMDG module, it's a Windows module. As such, it isn't a bug in the 777, and it's not something we can fix.

Share this post


Link to post
Share on other sites

So what? Are you telling me that it's time for a C: format? :)

 

Reformats should always be the last step, because most of the time, reformats don't solve anything (and end up erasing all of the information that could lead you to a solution).

 

Also: your earlier post indicated that you'd simply elected yourself as a representative of Jeeno, and not that you're having the issue yourself. Best to avoid speaking for others in general, particularly if you also need help, otherwise you may not get the help you need for your own individual problem. Because I'd assumed you were just opening a thread back up to be critical, I'd addressed you at that level instead of the level necessary to provide support.

 

So, are you seeing the issue as well? If so, what add-ons do you have that you use together with the 777?

Share this post


Link to post
Share on other sites

I have no issue at all, because I don't have the 777  :P It doesn't suit my style, too much automation. The only long range bird I'm interested in is the 747, and I'll get the 747 V3 for P3D as soon as it's out.

 

I only have the FSX version of the 737 Base Package and the P3D version of the 737 Base package and the 600/700 expansion. Never had any problems with them. That is why I recommended PMDG to my long-time friend Giorgio (Jeeno). His favourite plane is the Triple Seven and PMDG is the way to go for that, isn't it?

 

Now, I am sort of speaking on his behalf... because he's almost given up! I expected the 777 to work flawlessly on his system as the 737 works on mine, but something's up. 

 

Some are saying that the kernel32 has nothing to do with the PMDG 777, whereas some others say it's a known and irresolvable issue of the 777 in FSX Boxed. 

So how should he proceed? Will FSX:SE fix that, or is a format really required? Both option are quite time consuming, so choosing the right one is important I'd say.

 

I'd say Giorgio's experience with PMDG has been less-than-stellar for now, and I kinda regret recommending him the 777. I hope you can help him, Kyle!

 

Regards,

Fabrizio

Share this post


Link to post
Share on other sites

 

 


Now, I am sort of speaking on his behalf... because he's almost given up! I expected the 777 to work flawlessly on his system as the 737 works on mine, but something's up. 

 

Has he? I feel like you're making an assumption here, which is not yours to make. I can say that we responded to him both here and in the support system and have yet to hear back.

 

Again, you're also assigning blame to us for a kernel error. These kinds of things are fundamental to the OS. It isn't something we can fix, and I cannot say for sure that a reformat will fix it. It isn't our code, a reformat is really drastic, and takes a long time to get everything reinstalled, all for something that's essentially a crash on exit, which is similar to getting a little particular about a house being demolished piece by piece or going up in flame.

 

Yes, ideally, it would be nice if the program exited gracefully, but the code that is causing the less-than-graceful exit isn't in our control. A quick glance around the internet referencing the kernel32.dll and FSX returns a number of hits, generic in nature, and not specifically related to any of our products.

Share this post


Link to post
Share on other sites

 

 


Has he?

Yes, he has. He uninstalled it and decided to stick to GA planes for some time. No assumptions were made here.

 

 

 


Again, you're also assigning blame to us for a kernel error.

Not exaclty blaming, but wondering why it happens only with the 777. I was just asking what would you recommend, as it is clear that you've heard about this kernel32 before, irrespectively of it being tied to the 777 or anything else.

 

 

 


all for something that's essentially a crash on exit, which is similar to getting a little particular about a house being demolished piece by piece or going up in flame.

 

Something that's causing the 777 not to save the hours flown, making the Service Based Failures unusable. That may not be a burning house, but it sure is something.

 

I'll get Giorgio to report back.

Share this post


Link to post
Share on other sites

Some people will never understand, that complex add-on does rely on many other pieces of code/software/mood/weather. SimConnect being just one of them. I never saw any answer about other add-ons used by OP. Many problems with closing FSX:SE are because of outside software still running. VFX, ASN, vPilot, VAinterface etc etc. Try closing these, wait for few seconds and then close FSX.   

Share this post


Link to post
Share on other sites

I've never closed FSX before having closed any sort of Acars or other programmes. The last thing I'll try is to close ASN before FSX, but I'm far from confident.

 

If format couldn't solve the issue, do I have hammer my computer to see if it may work?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this