The only time that Windows should crash due to high memory usage is if it runs out of virtual and physical memory. So Gebe's suggestion of upping the virtual memory page size may alleviate a lot of the high polygon problems some are experiencing, and I have done that in mine. The slow response after a bit of time if you are constantly adding things to the scene could also come from this as well. After all, the more swap space it uses, the slower it's gonna be, because the hard drive is nowhere near as fast as RAM. If it crashes because of high polygons, then that is a completely different error that may be fixed by more physical RAM, but also should be looked at at e-on as well.

I think there is some confusion when I and other say Resources. Resources are not where windows stores the code, 3d model and texture data, etc. Resources are things like requesters, menus, static items that the program uses upon request. For instance, when you call up a menu, that menu is allocated in the resource table. When it is done, it's yanked from the table. The resource table is a locked size area within the windows protected zone. It has protocols as to how to allocate, write and delete resources from that table. No matter how much physical or virtual RAM you have, it still only has a fixed length. This table is used by all the programs in the system that uses interfaces. The reason this table doesn't fill up on it's own generally is that you are only using one application's interface at any given moment. Now, if a program is not deleting and thus freeing memory in that table when it does one of the interface functions, than it is leaking resource memory. When that memory fills up, it leaves no other room for any other program or itself to be able to send menu, requester information to windows. Therefore, you get all that craziness. Now if the table gets overflowed, than it can and will crash Windows. Normally programs protect against that by putting in checks for whether a certain resource can be allocated or not. If it cannot, then it usually throws a message that says, "Out of Memory" error. This does not always mean out of physical/virtual memory (though it can), but it can also mean out of Resource Memory that again is finite and not part of the main memory stack. Therefore, no amount of memory is going to fix the problem if this is indeed the error, as it seems to be based on what has been said.

I have not had a chance to play with Vue Pro since the update, so I don't know if this has been fixed or not, although I am losing hope after Gill's post, but I will let you know what I discover. And I will be the first to applaud E-on for a job well done if they fix this.

ShadowWind