Quick Reply
Search this Thread
Test Subject
Original Poster
#1 Old 11th Nov 2009 at 10:48 PM

This user has the following games installed:

Sims 2, University, Nightlife, Open for Business, Pets, Seasons, Bon Voyage
Default Again, more EXC_BAD_ACCESS errors.
Hey! I was hoping that maybe someone would be able to help me with this whole EXC_BAD_ACCESS error problem. It's been talked about before, and it was supposedly answered, but the answer that was given isn't working for me. I'm guessing there won't be much help for me here, since everyone is switching to the sims 3 and nobody is coming here anymore, but it is worth a shot.

My game is crashing when I try to load a previously made family that I had moved into a maxis-made lot before closing the game. When it's loading, and I see the family portrait, the game stops loading around about the fourth line of icons in the background and crashes.

This is the (scaled down) error that I'm receiving:

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

While this error is talked about in this archived thread, the answer that was proclaimed a fix there is not working for me.

Quote:
That's a memory error- either the Sims 2 is trying to do something illegal with your memory (it's been known before) or else you have faulty RAM. Rule out the latter by running the hardware check that is on the OSX install disc. For the former- run through the usual tests as outlined in this article, as this will determine for sure whether the game is at fault. Do each step, don't just read it!


That was the moderator's fix for this problem. I've done this, and it (unfortunately) did not work. The other suggestion was to delete some of the other files from the sims 2 folder.

Quote:
Just after I posted the message above, I decided to try something else before trying to figure out if a downloaded item was the problem. So I deleted the Accessory.cache, ContentRegistry, and Cigen.package files. That didn't work. So, then I deleted the Groups.cache file, and YES!!! It worked!! The game launched fine after that, and wasn't very slow despite my 3,000+ downloads.


Again, while this seemed to work for the people who posted in the archive thread, I've tried this route and it hasn't worked for me. Does anyone have any other suggestions?
Attached files:
File Type: zip  Full-Crash-Report.zip (6.8 KB, 5 downloads) - View custom content
Description: This is a copy-paste account of my crash report, with all the gory details.
Forum Resident
#2 Old 12th Nov 2009 at 12:13 AM
Previously made family - is this a family from a different neighborhood? Those are known to hose your game.

Have you ruled out bad custom content by attempting to enter the lot with your downloads folder moved to another location, like the desktop, so the game can't access it? If it works, do not save but exit the lot and quit the game.

If it's not CC your final resort is to back up anything you want to keep and try reinstalling the game - do it right, deleting the plist files and saving any hoods, cc, and sims you want to keep elsewhere.
Test Subject
Original Poster
#3 Old 12th Nov 2009 at 5:43 AM
This is a family that I created in the neighboorhood, using CAS. When I meant a previously created family, I meant that I had made them, exited the game, and then came back to play them the next day. When I tried to load them again, the game crashed.

I am absolutely certain that this isn't custom content related. I don't play with any other CC except for minor hacks and skin/hair/eyes (general bodyshop). I've done all I can trying to weed out any bad custom content, and at this point I believe that I may have run out of memory, or something equally costly.

:sigh:

I will post back here when I figure out if it's a memory problem. All I know is that games by Aspyr are known to create these kinds of errors. Frankly, it pisses me off that this game is so hard to keep running for any permanent length of time.
Forum Resident
#4 Old 12th Nov 2009 at 5:28 PM
Interestingly, my game has always run just fine. Any problems have always been caused by bad CC or a power outage causing the game to quit improperly.
Back to top