|
|
Post by aspen31 on Dec 9, 2008 17:46:41 GMT -5
Hi all
Anyone have any experience with an FS message "Runtime Error r6025, pure virtual memory call" followed by the dreaded black screen and an FS restart. I have looked at other forums but really have not found an answer. I do have quite a few add ons but check each one after installation -- normally by operating the sim for a reasonable length of time. Problem is that everything appears to function properly -- right until it doesn't sometimes for quite a while. I flew today for at least 1 hour 10 minutes until -- ZAP!!!
Help or suggestions aqppreciated.
Thanks
Warren
|
|
|
|
Post by Tom/CalClassic on Dec 9, 2008 20:17:58 GMT -5
|
|
|
|
Post by aspen31 on Dec 10, 2008 6:27:46 GMT -5
Hi Tom
Thanks for a very thorough response. In this case it sounds like the fix is nearly as complicated as the problem. I think I can elliminate a few of the possibilities and the rest I'll poke away at. This FS stuff is great but I'm looking across the room at my old American Flyer thinking how much simpler it was to get it around the track -- no CTDs and black screens there.
Thanks
Warren
|
|
|
|
Post by pung on Dec 10, 2008 18:31:57 GMT -5
The few times I have a blackout of my sim-- is always where as opposed to how long (usually happens just as you reach approach of an airport). Which is either scenery (AFCAD) or occasionally an AI aircraft problem. Try the same airport during another time or season, if the problem does not reoccur, it is an AI issue, if the problem remains it is probably a scenery issue.
|
|
|
|
Post by sunny9850 on Dec 11, 2008 2:02:58 GMT -5
Life is truly full of coincidences....I was having this error the first time yesterday and put it off to running too many things for my old machine.
Then it happened again today with only FS9 running.
Both times at Bermuda Intl with FreeFlow Bermuda activated in the scenery lib. Turned that scenery off and the sim is happy.
So before going through too many other hoops I would agree with Pung and try a different flight location and see if the problem still happens.
Stefan
|
|
|
|
Post by johnhinson on Dec 11, 2008 2:41:44 GMT -5
If the problems approaching destinations with add-on scenery relate to a "Windows has run out of available memory" message this is a completely different issue to the one raised here and there are solutions to make more of your memory available to the simulator. I feel sure that has been discussed on here before, try searching here or on the web for "4GB Patch".
John
|
|
|
|
Post by aspen31 on Dec 11, 2008 6:46:47 GMT -5
Hi all
Thanks for the useful information. In my case the failure has occurred at various time and locations from a few hundred miles off the east coast to a few miles west of Memphis. Some reading suggests that the problem may be related to a part of Free Flow scenery involving specific AI -- namely the ferry or / and the garbage barge add on. So far I changed the aircraft.cfg to .bak (for these 2) and have flown for about 1+30 without a crash -- at least not one involving the runtime error. Airmanship is of course another issue. I also use Free Flow Bermuda so will keep that one on the back burner to look at. I use a combination of early classic and later AI including some GA provided by a program called GA-Traffic. I have read that it can cause the described failure so that may be the next step if required.
Still staring at my American Flyer
Thanks
Warren
|
|
|
|
Post by johnhinson on Dec 11, 2008 11:26:26 GMT -5
Yes, AI can cause FS crashes - I have come across two common reasons.
Textures that are reflective, when you haven't got Render to Texture or Aircraft Reflections turned on. This usually gives a ntdll.dll failure.
Duplicate AFCAD files given different co-ordinates. This makes FS think there are two airports close to each other and probably can't figure out how to place the traffic. This usually gives a ai_playr.dll failure and usually crashes some miles away from the offending airport when the scenery/AI loads.
I think this is the issue that has caused it to be suggested that you should never have duplicate AFCADs. There is no problem with that, in principle, as long as the co-ordinates are the same. FS will use the last to load in the scenery library order.
If you do get a message when FS crashes, it really is worth noting what has offended Flight Simulator as it can point you to the problem.
But the "Runtime Error" is not something I have experienced - a search on the Net suggests it is something external to Flight Simulator.
John
|
|
|
|
Post by aspen31 on Dec 11, 2008 15:38:24 GMT -5
Hi again all
In my case I have experienced this error for a couple of years -- very intermittently. It occurred at some point not long after I added the GA-Traffic program and many of the Free Flow packages. Subsequent to the most recent occurrence and after reading as much as I could I decided to disable the Free Flow AI garbage barge and the ferry. So far I have flown about 4 hours with no problem so just maybe I got it. In response to info from COL77 (thanks) I also ran a registry scanning program and this corrected (apparently) quite a few problems. Bottom line -- for now everything is fine. Time for another download perhaps.
The electric train is back on the mantle for a while.
Warren
|
|
|
|
Post by Tom/CalClassic on Dec 11, 2008 15:54:07 GMT -5
Welcome back!  |
|
|
|
Post by sunny9850 on Dec 11, 2008 23:34:38 GMT -5
It sure looks like it is one of the FF Bermuda traffic files in my case. I just took all of them out and so far no issues at Bermuda.
I am going to add them back in one by one and see which bgl does cause the hangup.
As usual with anything PC or Sim related there is always a combination of things at work. The same scenery with a different user airplane may run fine.
I have been using GA traffic for quite some time and never had an issue...until I flew the Starliner to Bermuda. So it may be that combination for my box. But the runtime error came back with a default C-172 in my case so I am positive it is not the Lockheed.
|
|
|
|
Post by Col7777 on Dec 12, 2008 5:11:01 GMT -5
After the episode of the black screen and CDT I had and doing a bit of searching, I didn't realise just how common this is.
Some it is the owner of the sim that has caused it but a high percentage is from add-on stuff mainly graphics, I must have been lucky so far as I cured my problem but for some it is drastic.
After this it has me a little frightened to load any scenery up now unless I think I really need it, like having a nice airport in Russia is no point if I don't fly there.
|
|
|
|
Post by pung on Dec 12, 2008 7:54:35 GMT -5
Thanks for the tips--I had a problem with Wright-Patterson in Ohio, seems the new AFCAD had slightly different coordinates than my AI traffic. Changed my traffic coordinates-no more problem.
|
|
