Bowen

I'm not sure if this will help you, but that memory.dll sanity check usually occurs with 32-bit games running under 64-bit OS's like Vista x64. This fix might very well work for your problem too.

MS has just released a hotfix that addresses problems with games which CTD because of the incompatibility. It's especially bad with certain games, such as BF2 and BF2142, which I had a problem with. There's a few more, but I only had this problem with those two games. It's completely fixed now, thanks to MS! Here's the hotfix and apparently it's not just limited to Vista x64, but Vista x32 as well. Both hotfixes are here: Virtual address space usage in Windows game development

As I said earlier, I personally tested it and I actually first found out about this at the forums at nvnews.net and I recently saw it at fudzilla.com here: Fudzilla - Microsoft release Vista game hotfix
Nvidia.com Hotfixes apparently has this fix posted too, or maybe it's a link to MS. In any case, it's a welcome fix because the previous fix that I posted does work for BF2142, but not for BF2. It actually works for BF2, but the wonderful PunkBuster thinks you're cheating and so you get kicked after a map change or shortly after you first enter a game. This fix allows you to play the game without having to modify anything, as it should be!

So, with this new fix, you should no longer have to implement any sort of fixes in order to get games to work if you have high memory and/or if you're running Vista x64.

*EDIT*
Sorry, I see now that DizConnected posted the same link earlier....sorry. Anyway, he's right.....hopefully that should help you too and should definitely help everyone with a CTD during games that give this type of error or no error report at all. If you look in Event Viewer you'll see something but many times Windows won't tell you what's wrong when this error occurs.