thefrocker Thanks for the dxdiag. The Sims 4 errors it lists reference one of the VC++ runtimes, but often the problem isn't the runtime itself, rather something using it incorrectly. When you started with a clean folder, did you add anything back before testing? If so, please try another clean folder with absolutely no added content, AND make sure that nothing (like OneDrive) is redownloading your previous content. I've seen that happen—mods reappear after being removed and before the player is able to test without them present.
Additionally, do you use ReShade/GShade or any other utilities that would go into the game's program files? Uninstalling would have removed them, but I want to make sure you didn't add anything back.
If none of this is relevant, try reinstalling the newest VC++ runtimes. Open Windows Settings > Apps, scroll down to the Microsoft Visual C++ Redistributables, and uninstall any version from 2015 or newer. (Don't touch the older ones, which are standalone.) You can get fresh copies here, under "latest supported redistributable version":
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
You need both the x86 and x64 versions, but not the ARM version, which is for a different class of device. Restart your computer after installing these and before trying to play, of course still with no mods or other extra content.
If this doesn't help either, please look for new errors in the Reliability Monitor. Click Windows key-R and enter "perfmon /rel" without quotes, and you'll see a chart of errors and updates with a column for each day. Today is on the right.
Look for an error that happened at exactly the time of your most recent Sims 4 crash, specifically after reinstalling the runtimes. If you find one, double-click it to see more details, then copy that info and paste it into a reply here. If you don't see a new error, check back in an hour or so—the Reliability Monitor doesn't always update right away.