Hi all

 

So FSX stops. Sound carries on, but all else is locked. I go to the task manager and click the Performance tab. One the eight cores is showing 100% usage and the rest essentially none. Physical memory usage is 4.24GB. The hard drive light is chugging away. On my previous fs PC, after a while (maybe two minutes, might be 10) the clogged core would drop back normal and I could carry on my merry way. With the current set up that doesn't happen.

 

I'm flying over FTXG in a Carendo Bonanza, so not exactly pushing the limits. I'm not getting an OOM message, which I have had when getting a bit carried away. But the physical memory thing might suggest it's that.

 

I've got hyper threading on and no affinity mask in the cfg.

 

Any ideas?

 

Cheers

 

Mike

This is an automatic message.

 

This topic has been moved from "MOBO, RAM, CPU's & Other Hardware" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Check out the AVSIM CTD Guide regarding OOM's (see pinned topic in CTD Forum).  You are running out of VAS.

 

Best regards,

Thanks Jim. I was afraid you were going to suggest it's OOM. I'll have to investigate some more. LOD is not high. Have flown the MD11 from KPHX to KSEA without issues, although the NGX was too much for it... And have done 10hr flights in the MD as well. So a bit surprised. But not really. Anyway, you've given me somewhere to start. Thanks again.

 

Mike

Sounds like you also need an 84 as affinity mask. First 2 cores (1 real 1 hyperthreaded should be reserved for the OS) then utilize only the real CPU cores and leave the hyperthreaded ones unused.

You have to use the AffinityMask tweak to get more than one core to work.  This is one of the better explanations on how to use this tweak - http://fsxtimes.wordpress.com/2010/08/18/affinitymask/.  I personally would not recommend it (as well as some other experts like NickN -http://www.simforums.com/forums/the-fsx-computer-system-bible-in-pdf-format_topic46757.html starting around the 4th post).  With your system you should be able to run FSX w/o any tweaks except maybe increase your LOD from the max of 4.5 to 6.5 and your Texture_Max_Load to no higher than 2048.  I understand that FSX does not use all cores.  It was not programmed to use all cores but the Job Scheduler can somehow make it happen. 

 

I would like to know if you are getting any type of crash reports because you can with the screen freezing and sound running in the background.  You should see an error message after you go to the task manager (something like fsx has to close and restart then a details icon to click on in the lower left corner).  I would also take a look at my BEX/StackHash/NTDLL.dll topic in the CTD Forum and try using the TakeOwnership program.  If you have an access violation (that can also be caused by a program not sharing with you), then fsx will freeze up or crash.  Simple as that.

 

Of course, lack of VAS as I indicated above is also a great possibility.

 

Hope this helps.

 

Best regards,

Thanks all. I'm away from my PC at the moment. Once I get back I'll try the same flight and get as many details at the point of failure as possible.

 

Mike

OK, so I've set up FSUIPC with the logging of 024C (S32), which I understand is to monitor the remaining VAS. My last freeze shows 1633020. So whether it's used or remaining, I would expect to have headroom. I also understand from recent reading that the VAS must be contiguous. Not sure if the FSUIPC reading is that or total.

 

The problem event name is AppHangB1, hang type 2304. I'll go do some research on that when it's not 1am...

 

Mike

Event 2304 - Looks like you have a sharing/permissions problem - http://technet.microsoft.com/en-us/library/dd638608(v=ws.10).aspx.

 

I'm not sure why you are watching the VAS remaining counter.  FSUIPC will start chiming when you are getting low on VAS (then you can go into the Task Manager and check what's taking up so much VAS and maybe shutdown some programs).  The most common thing that will take up VAS is any photoscenery as all photoscenery you have enabled will load no matter whether you are flying there or not.  Look in the AVSIM CTD Guide for the utility SceneryConfigEditor.  Disable any scenery you will not be using during a projected flight.  Of course, a bad tweak or high FSX settings (LOD_Radius above 6.5) will cause this crash too if you don't have photoscenery.

 

Best regards,