coestar15 The first error is extremely generic: Sims 4 (TS4_x64) crashed because it crashed, because of an access violation, which simply means that the game tried to access memory in a way that isn't permitted. That alone is never useful. The second crash, however, is a buffer overflow exception (BEX), and it looks like the kind of crash we see with conflicting software.
Before going down that route, please move or rename the Sims 4 folder in Documents > Electronic Arts, in case you have any files inside that are causing problems. For example, a stale file in ConfigOverride can cause this type of crashing. It's faster to simply rename the folder though. This will prevent your saves and other user data from loading, but it'll all still be intact and can be restored later.
If that doesn't help, please try playing in a clean boot:
https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
The one service to leave enabled is the EABackgroundService, which the EA App needs in order to run. Disable the rest as described.
When you reboot your computer, go through the Task Manager's background processes list shutting down any service that doesn't absolutely need to be running, for example anything from MSI Afterburner to RGB software might still be enabled. If you accidentally kill a critical process and it doesn't restart on its own, just reboot your computer again.
Don't open anything other than Sims 4 and the EA App while testing, not even a browser window.
If this helps, you can selectively reenable services until you find the culprit, then either leave that disabled or (if it belongs to an app you want to keep using) let me know what it is so we can try to fix the underlying issue.
If the game freezes or crashes in a clean boot, please try again, except with your computer offline. You can sign into the EA App and put it in offline mode, then disable wifi and/or disconnect the ethernet cable before pressing Play.
I would like the same Reliability Monitor info from any other crashes going forward, although you don't need to post exact duplicates; just say you saw however many of one particular error.
