@ImIncrediblyOlD Please repair the game, again, to revert the program files, and don't make any changes afterwards. Remove the Mods folder as well. Try playing a new save in Sunset Valley. If the game freezes, try playing in a clean boot:
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 3 and the EA App while testing, not even a browser window.
If you get another freeze, please post a new dxdiag.
Going forward, please don't add or change any files unless I specifically ask you to, or unless the game is stable again and we're at the point where it's time to add back some content for testing. It makes troubleshooting harder when the player is adding other factors in while an existing problem is unresolved. (I'm not annoyed or anything, just saying please don't do this in the future.)
Additionally, do not use any Steam guide for performance or anything else. Most of these guides make suggestions that are actively harmful, and all of them list "critial" steps that are completely unnecessary and make other misleading claims. Leave Simler90's mod out as well: it's incompatible with NRaas mods, and any guides that say they can be made compatible are inaccurate and should not be trusted. This is according to the current NRaas developer, among others, and he would know.
so it still froze, even after doing a clean boot also when i removed the bin folder it just reinstalled it again when i tried to play was that your intended instructions? or should i try to remove the bin folder again.
also can i keep the computer in a clean boot or do i have to reverty back to normal changes?
@ImIncrediblyOlD The clean boot is only for testing Sims 3, so you can revert it for regular use. However, I'd suggest not reverting just yet; there are a couple more tests I'd like you to run while in the clean boot.
First, I don't think we covered it, but are you playing in fullscreen or windowed mode, and does it make a difference to switch? Please do so at the Main Menu and quit to desktop before loading a save just to make sure you're getting the full effect.
Your dxdiag shows a few more generic Windows errors, and since DISM and sfc apparently didn't clear these up, I'd suggest running a repair install:
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
This shouldn't delete any of your data, but if you get to step 13 and are NOT asked to keep personal files and apps, back out and start over.
If this doesn't help either, I'd like to see the results of some hardware monitoring, still in a clean boot, to see whether any of your computer's components are behaving in an odd way. Please download hwinfo (it's free) from here:
https://www.hwinfo.com/download/
You don't need to install anything; just choose the Portable version, unzip it, and launch it from Downloads or wherever you like. If you do want the full installer, be sure to click the button for hwinfo itself, not for lansweeper.
Restart your computer, open hwinfo, choose Sensors Only, and click the button that's a sheet of paper with a + to start logging. Save the log file to your desktop for easy access. Wait five minutes, then open Sims 3 and play for at least 20 minutes. Don't alt-tab out of the game or run any other programs, aside from the EA App of course, while you're testing. When you're done, click the same button to stop the logging.
Please upload the log to the third-party filesharing site of your choice (Google Drive, Dropbox, etc.) and link it for me. Either leave it in .csv format or, if you're going to use OneDrive, create a .zip file, and don't open the log before uploading it, or else my log reader might not be able to interpret it.
