Forum Discussion
Hey there,
Firstly- thanks again for your help!
I followed Crinrict's guide to the letter and did a clean reinstall of the graphics driver, another sfc /scannow for good measure (nothing), and started playing. Unfortunately the freezing came back and now it is in both modes, live and build/buy. I can only assume that the issue is with the latest update of TS4, given the freezing started then and continues on every household and lot, the GPU's stress test came back normal, the clean reinstallation of the graphics driver hasn't fixed it, and the PC is running every other game and piece of software normally on ultra-high graphics.
A quick theory: the driver reset issue shown in the DxDiag is what was causing Baldur's Gate 3 to crash after its first hotfix. To work around having to edit the registry and potentially make the system unstable, I turned anti-aliasing off and NVidia DLSS on in BG3 and this fixed the problem. I'll explore in TS4's settings as well, but I suspect this problem comes from EA.
Thanks enormously again for your help! Regardless of the TS4 issue, you've given me tons of useful PC knowledge.
@ThisMicrophone It's certainly worth reseting the Nvidia Control Panel's options, either globally for for Sims 4, if you've changed anything there. And if you've overclocked any component of your computer, please rest that to default as well, at least for now. Other than that, Sims 4 really shouldn't be freezing, and it doesn't on most systems.
Are you getting new errors related to the freezes? You can check in the Reliability Monitor. Hit 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 any errors that happened at exactly the time of a freeze, specifically after you reinstalled the graphics driver. 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. And if you don't see any errors with the correct timestamp, please check the technical details of the ones you do find. I've noticed that some errors show the wrong time in the overview but the correct one in their details.