I played around on Nraas story progression on a new neighborhood and it seemed to be stable after playing for an extended period of time. I checked back on one of the saves that crashed with AM SP and it seemed to be fine, but at that point I didn't have time to play it longer to see if crashes are actually gone for good. Still, I'm fairly sure the problem wasn't corruption, but rather a performance issue.

I guess Awesomemod's SP is working as intended, and I'll just have to get used to using Nraas SP. I'm just glad the bug fixes and features in AM aren't the cause of the crashes.

The save crashes are actually very uncommon and might not be related.
After some more playing, it seems like the game gets more and more unstable after only about four weeks in game time. I thought it would only crash after a couple hours playing, but it seems to be a combination of the two and after a certain point it just crashes too much to even bother trying to continue playing the save.

I recently checked that my computer's processor just meets the minimum requirement (2.4 GHz on Vista), and I guess the problem may be that Awesomemod's story progression could be pushing it over the edge? I don't really know, it's just about the only thing I can come up with to explain the constant crashing even when I reinstall with a cleaned out registry and whatnot. But would that really produce corrupt saves? I'd understand if CLA is just misunderstanding the crash log, but it seems that the saves get more and more unstable, suggesting actual corruption.

Maybe I'll have to try out Twallan's SP just to see if there are continued crashes.

I'm getting random crashes as well. I've played with Awesomemod back before Generations came out with no issues, but I've come back to the Sims during the 1.34 patch and with Awesomemod, it's been randomly crashing after about 1-2 hours of play. The crash log analyzer typically says the issue is a corrupt save. I've tried deleting the entire Sims 3 folder under My Documents, and done reinstalls, but a fresh Sunset Valley save with Awesomemod always eventually gets random corrupted save crashes even when I had nothing else but Awesomemod installed. I can't pinpoint the crashes as they tend to disappear if I fuck off and play the Sims 3 later and which point it runs for another 1-2 hours before the crashes come back. I've got it up to date, and I've made sure the base game is patched as well as all the expansion packs I have (WA, Ambitions, LN), but it keeps happening. I've got Awesomemod installed via Documents framework.

The crash log produced by the game itself usually says its an access violation at reading address 0x00000030, and the address under it is usually always the same depending on the patch (for 1.34 it was always 0x00d5d48f and another address for 1.36). Sometimes when it crashes during saving, CLA just says it's an unknown issue.

My system shouldn't be an issue, as the game runs fine graphically without Awesomemod and I've got 8 gigs of RAM. At this point, I honestly don't know what to do next to try and fix whatever issue I'm having.