• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Maybe someone here knows more about this CTD-- HUNGAPPA?

PilatusTurbo

PilatusTurbo

members+, Fighter Fanatic
I've seen this in the little error reports mentioned by Windows. This CTD only happens once in a while, and only on the longer flights. I don't know what that means, this 'hungappa', and it also mentions the FS9.exe. I'm not using any cracked exe, and it is FS9.1 (Disc is always in my bottom CD-Rom).

Anyone know if this is common? I didn't lose much time tonight because of it, but it has ruined 2-3 hour flights in the past, which is remarkably frustrating. :bump:
 
hungappa = hung application a

You might want to check the Microsoft Event Viewer - either the Application Log or the System Log. Check for any Hung App error entries to see if the app that is causing the problem is named. Possibly it's not the fault of Flight Sim itself, but something else running on your system at the same time - even a video controller program such as ATI system panel or nVidia's control program, sound controllers, etc. Even an Anti-virus application running in the background can cause these "hung app" errors, or updater programs for one application or another!
Would need a little more information to ensure a decent explanation of what is happening, but check your Event logs for sure! You can also try "SysInternals" - they have some good program tracking tools for identifying error messages.

Hope this helps a bit!

Mike
 
Well, dang! Thanks Mike! This is why I ask questions here, because I usually learn something new about XP, or the system in general.

However, I don't really know what to do with this, so I'll post it here for others to view. These are the only two that came up, and this is from the crash time last night.

I've attached it for clarity, let me know if you need me to change it to words to help interpret it. I'm clueless on this stuff. :ernae: :bump:
 
Pilatus,
I am not one of the gurus here but maybe your fs9.exe file has a glitch in it. Here is the Properties display for my file (see attached), same version as yours. Any difference in the file size? You might try replacing it with the original fs9.exe file off the CD and see if you continue to get the same error.
 
This is odd, and interesting at the same time. My FS9.exe was created 3 hours before yours! :d However, mine is 1.32 and 1.33 mb in size, which I don't know if that difference is negligible, or important. I'm not a guru, either. :)

I appreciate everyone's help. Maybe, if we put our melons together, we can figure out another CTD culprit. :ernae:
 
Cryptic error displays!

That's the standard Windows cryptic and inocuous error properties page. Sometimes the link you see in the Description window will give some indication if Microsoft has received enough of them to warrant some effort to determine what is causing that particular error. Event ID1002 is associated with many unknown errors, and is usually accompanied by Event ID1001, which may or may not expand on your particular error. One of the causes of these types of errors, especially ones that show memory locations is that two apps may have been trying to access a "memory location" (0x00000000) - hexidecimal for memory address - at the same time - the app that loses is usually in a hung state if it can't be assigned another memory location fast enough. Regardless of how much ram we have on our computers, there is still a limited amount of memory space for actually executing a particular program. So, on long flights, your graphics and processing is using up more and more memory addresses, and sometimes one may not get released back to the OS Kernal in time to be properly addressed again - resulting in a contended location.

OK... enough of that... simple enough to say Windows has hung your computer out to dry! The best solution - try running less programs when on long flights!

Hope this all makes sense!

Mike :isadizzy:
 
Really? I've only got around 26 processes, maybe 28 or 30 at the absolute most.

Should I really try to lean it out even more in MS COnfig? I have a feeling that leaving AVG's multiple processes going doesn't help. However, it did do this in the past, before I ever used AVG. It also did this on a machine with less specs.

Maybe it's an addon? This does always seem to happen in FS Genesis area (Not blaming those great meshes, just not sure if it's important). I don't have a very messy FS install, as I just re-installed everything a month ago (Tried to go Vista, and that just didn't work well.)

I'm not sure. I guess I'll try reducing number of processes before a long duration flight. I have started a new habit of simply checking the GPS here and there, to ballpark my location in case of this. If it crashes, I then simply goto the nearest airport, Ctrl+E, and slew up to whatever cruise altitude I was at. :d :ernae:
 
Is it normal for system idle process to take 99 CPU? I always wondered about that. I've attached a shot of this, too.
 
My System Idle shows 99 for CPU as well, but my CPU usage percentage is between 0 and 2% with XP, Firefox and the rest of my back ground stuff running. I have no idea what the 99 under CPU means...but it does not appear to mean 99%.

OBIO
 
Hi guys,

From what I've seen, most of the time when running "ordinary" programs such as your Office package, web browser etc. your processor will indeed be "idle" for 98-99% of the time, with the odd "spurt" when it has to do something. I run 2 monitors so I can have the Windows Task Manager open on the second monitor and see what's happening in real time.

However if FS2004 is running, when active, your processor usage will probably sit at 100% for most of the time !

Also be aware that the "dynamic memory usage" should remain the same when you open and close applications, but in practice it doesn't (in WinXP anyway.) This means that, for instance, freshly booted, my PC will show around 500-600Mb RAM but after a few days of use this will creep up, heading for 800-900Mb or more, which will obviously impact on the available memory for FS2004. With the likes of UT and real weather (Active Sky) I frequently see well over 1Gb RAM use before I even start flying, and if I load FS2004 with the PC already using nearly 1Gb RAM this can be up to 1.5Gb before flying starts. This leaves only 500Mb "free" memory to be "eaten into" before I hit the ~2Gb maximum Brick Wall and the inevitable "out of memory crash".

So, if you don't already do so, you may find freshly booting your PC before starting an intensive simming session gives you some extra 100s of MB of RAM to play with which may help to prevent this crisis point from being met.

Hope this helps,

Alastair
 
Thanks fellas. :ernae: I have started re-starting the comp before intense flights, as you're suggesting, Alastair. I haven't done it everytime, but I figured, it simply can't hurt my 'crash' chances.

Thanks for all the input and advice. I usually do, and did learn something from our great people here. :ernae:
 
You must log in or register to reply here.
Back
Top