I was tuning via Nick's tuning thread for FSX and not paying attention.I have Windows 7 64 bitIn the section for Out Of Memory Errors, I picked up where it applied to Vista, not realizing I was still in the Out Of Memory section. I carried out the command of bcdedit /set IncreaseUserVA 2560 How do I set it back to default for my system ? He gives a command for taking it back to default (bcdedit /set IncreaseUserVA 2048), but I don't know if that would apply to Windows 7-64 bit. Any help?

I was tuning via Nick's tuning thread for FSX and not paying attention.I have Windows 7 64 bitIn the section for Out Of Memory Errors, I picked up where it applied to Vista, not realizing I was still in the Out Of Memory section. I carried out the command of bcdedit /set IncreaseUserVA 2560 How do I set it back to default for my system ? He gives a command for taking it back to default (bcdedit /set IncreaseUserVA 2048), but I don't know if that would apply to Windows 7-64 bit. Any help?

I believe this was for 32 bit users, XP I believe. Win 7 will not be subject to those memory constraints.Bob

I was tuning via Nick's tuning thread for FSX and not paying attention.I have Windows 7 64 bitIn the section for Out Of Memory Errors, I picked up where it applied to Vista, not realizing I was still in the Out Of Memory section. I carried out the command of bcdedit /set IncreaseUserVA 2560 How do I set it back to default for my system ? He gives a command for taking it back to default (bcdedit /set IncreaseUserVA 2048), but I don't know if that would apply to Windows 7-64 bit. Any help?

The default is 2048 so that would be the figure to set it at if you changed it to something else. The bcdedit does not apply to 64 bit systems.Best regards,Jim

Thanks for the info.

I believe this was for 32 bit users, XP I believe. Win 7 will not be subject to those memory constraints.Bob

That command is for the Vista/Win 7 users, XP uses a different command (and edits the boot.ini).I found this thead because I was trying to find out what this command did. I was having OOM issues (usually proceeded by spiking) and it got really bad after I started to use the Orbx NA Blue scenery. Anytime I got near a large city like Portland or Seattle, FSX would crash with a OOM message. It was even happening near San Francisco where this wasn't a problem before. Yesterday I used the bcdedit/set IncreaseUserVA 2560 command and I haven't had an OOM error yet, but I still need to do more testing.John K