Page 1 of 1

BSOD help

PostPosted: Fri Sep 02, 2011 3:54 pm
by Groovin_DC-10
Hello flight simmers,
I'm having some problems with the blue screen crash on my rig.  I've googled it but can't seem to find a solution. 

What happens is that once in a while my FSX would get the blue screen crash with the message "Memory Management".

Anybody know what's causing this?  I heard it has to do with the RAM settings but I'm not sure.  My PC is a dedicated FSX machine with no other games on it and I'm not very technical when it comes to PC's.

Here's what I'm currently running....

Win7 Ultimate 64bit
FSX Gold
AMD Phenom IIx4 OC'd to 4ghz
8g RAM
ATI 4670 512mb
UTX Canada, US, Europe
GEX North America, Europe
FEX
UT2
Audio Environment X
and a handful of CLS aircraft add ons.

Any help greatly appreciated.

Thanks

Re: BSOD help

PostPosted: Fri Sep 02, 2011 4:50 pm
by Capt.Propwash
What aircraft are you flying when you get the "Blue Screen of Death"? Also, are you flying over any addon scenery when this happens?

Re: BSOD help

PostPosted: Sat Sep 03, 2011 12:29 pm
by Groovin_DC-10
Most of the time I'm flying my CLS planes when it happens.  Also it has happened on the default aircrafts too.  Scenery didn't seem to matter.  It sometimes BSOD'd on default terrain and sometimes on the add on terrain I listed on my first post.

But I may be on to something.  Last night, I was looking for tweaks to add in my fsx.cfg file and decided to try HIGHMEMFIX=1.  Usually I only use WideViewAspect=1 and ForceFullScreenVSync=1 (will probably disable it because even though it stops "image tearing", I get more stutters with it enabled.
With the HIGHMEMFIX added in, I tried switching aircrafts and location every few minutes in free flight.  This usually makes my FSX angry which eventually leads to a BSOD or CTD.  But so far it's ok.  I will keep trying because the BSOD doesn't happen often.

Let's see how this goes.

Re: BSOD help

PostPosted: Thu Sep 08, 2011 8:06 am
by Jared
have you tried making a backup copy of the FSX.cfg file and deleting the one from the folder thus allowing fsx to recreate a generic one?

If you do that and it still has issues there's something seriously wrong, if not then it's just tweaking the fsx.cfg back to where you want it and where it's the most stabilized.