I had JUST finished everything, from all the puzzles to technology when my game constantly crashes. My roomate also has a game and hers isnt' affected. Here's the error:

error accessing 0x004057d7 (tried to access 0x03A8A08C)

That's not verbatim, but it's something really close to that.

I've tried the repair option which has fixed these types of errors in the past, but that will not work. I've completely uninstalled the game and reinstalled with no help.

I was really looking forward to letting my villagers do as they pleased, and now the game is toast. Help please!

Can you tell us more about the computer you run it on? Memory, video memory, directx version?

Running Win XP
my ram is 256
video memory is also 256
directx is 9.0c

Thanks for your reply!

oops....my regular ram is 512

posting a message to keep this on the front page so I might get a reply. thanx

Put the game on pause and quit it. Download the game again from where you bought it and reinstall to the same directory.
If that doesn't stop the error, you may have to run a ram test to see if your ram has a bad spot

alright...i'll give that a shot. Thanx

Okay, that didn't do anything for me either, and i don't think it can be a system issue b/c my wife's game works just fine, and mine always has up until this point. And the error is the same exact one each time. I've put up a search on the search engines and it comes up with nothing.
Any other ideas?

Is your wife's game on the same computer? If so, and she is not having the problem, I suspect that something happened to corrupt your savegame file at some point. A corrupted savegame file essentially loads bad data into the game, causing the crashes.

Ahh.. didn't realise you were playing two different games on the same machine - in that case, shouldn't be a bad ram problem. This might be a long shot, but you could try copying the *.ldw files from the game directory to a temp directory, then deleting them from the game directory and copying them back from the temp directory to the game directory (thinking of a possible bad cluster on the drive in this case). Otherwise, check the ldwlog.txt file in the game directory and see if there's any indication there of what might be happening