Again, no major hardware change, just change in bios setting. I knew about updating Bios see post last year below, and I noted this, Should this occur? What if I find the bios back to performance if I find the change did not remedy the out of memory error in windows...Having to de activate and then re activate every time I need to change a bios setting seems extreme.
The problem is caused by your BIOS that, for some reason, is behaving as if it was a different machine when changing that setting. As explained already on the forum, we don't do ANY hardware detection, at all. We don't set policies about what hardware can be changed. We don't even KNOW what those policies are, it's a black box for us.
Note that, if enabled AHCI, Windows usually switches to a whole new set of drivers (disk, cpu, etc.), so that might look as a new hardware. Again, I'm only guessing, because no software we wrote ever tries to do hardware detection directly, it's done by the Esellerate library.
There's nothing we can do about it, other than (since your mainboard seems to have this problem) always Deactivating before changing a setting in the BIOS, and there's no limit of the number of Deactivations.
But the main issue is: it was wrong trying to fix "out of memory" error when using a memory-hungry airplane that leaves no room for the scenery. No BIOS setting will overcome the hard limit of addressable space for a 32 bit app. The only things that will save you some memory are:
- Using a less memory-hungry airplane
- Lower your settings, especially the ones related to terrain range
- Don't use HD textures
- Use DX10
Or, a combination of all the above. It's not as if you don't have choices.
