ttw crashes

[GeneralKevinL]

i don't know what i did but when i started playing the pitt for fallout 3 everything went well but some times memory would run out but once i sided with ashur and had to go back to downtown the game would just freeze or crash or be stuck in loading limbo now when i try to load in

[Mystical Panda]

32bit applications like FalloutNV have available about 3.5gb of virtual memory space (if 4gb patch, or LAA is enabled for a program); though it states about 4gb. Some of that is used by the system to hold linked libraries and other data, some is used by DX to shadow textures (if I understand that part correctly), and the rest is available for your application. If the 4gb patch isn't used, or LAA isn't enabled, the usable space is about 2gb for everything. Gog should provide an LAA enabled executable.

If that's the case, you'll run out of memory when loading up, not just the saved game data, but all the esm records from both games. Extra textures, which are shadowed in the game's virtual space, will start eating that up fast.

NVAC should show a "low_mem" in it's log when memory gets so low the game can't cope- sometimes if there's not enough memory applications just exit, or crash. It's a good indicator if something is awry. Many use it to keep playing an unstable game that'll eventually crash, but I use it as an 'early' detection of potential asset of mod conflict problems. I can really work wonders for that.

The game can 'thrash' if it's trying to 'save itself' when it's virtual memory gets low by freeing up, or swapping out as much as it can. But, if a situation occurs when it's swapping something out it needs, to load something else it needs... it'll slow down, then eventually crash.

I would try troubleshooting those first.

[jlf65]

Systems with AMD video cannot use LAA mode in 32-bit Windows and are restricted to a max of 2GB. I had that problem back before I switched to 64-bit Windows 7.