@MollyMoon216 Your dxdiag lists a number of Sims 3 crashes due to access violations, which unfortunately could be caused by any number of issues. Your 28 GB of custom content is certainly a prime suspect, but it's not the only one.
A couple of the errors also mention the VC++ runtime that Sims 3 uses, so it's worth reinstalling it, even if the problem is likely elsewhere. Click Windows key-i, select Apps, scroll down to the Microsoft Visual C++ 2005 x86 Redistributable, click on it, and uninstall. (Don't touch the versions from any other year.) You can download a new copy directly from Microsoft:
https://www.microsoft.com/en-us/download/details.aspx?id=26347
You can skip the x64 and _IA64 versions.
I don't think this is the underlying issue though. It's worth testing with no custom content at all. You can use "save as" to rename one of your existing saves, then quit, remove your cc, and experiment on the new copy of the save you've made. The original will reman intact under its current name, and once your put your cc back (or most of it, if some turns out to be broken), your sims will still be wearing it in that save.
Point is, please run the game with no cc at all, at least for one play session, just to see what happens. Please test in one of the two custom worlds, not in Isla Paradiso, which has its own issues independent of any mods or cc. As for the mods, it would help to know which ones you're using. You can list them or take a screenshot of the folder they're in.
