The Sims™ 4

The Sims™ 4

Crashes FYI Nvidia fix
I rolled back to 566.36 It has finally solved my problems on crashes for now!
https://www.youtube.com/watch?v=NTXoUsdSAnA
< >
Showing 1-11 of 11 comments
I did clean install and did not install the nvidia app it also updated the nvidia control panel and I did change texture filtering to performance. If you read this please respond to keep it recent for others to see for it might help others.
Last edited by Marks fun; Apr 20 @ 10:04am
Marks fun Apr 20 @ 11:01am 
The crashes I was having said it was the EA app and windows 11 but I now think and hope they were the nvidia driver and so far it seems to be correct.
Jehane Apr 20 @ 1:05pm 
I bet it's Nvidia, I mean, it wouldn't be the first game to crash because one of their drivers isn't working properly. Back when I played Hogwarts Legacy, I had to roll back to an older driver because the game started crashing after an update. Once I did that and tinkered a bit with the graphics options, the gamae worked perfectly fine again.
Thanks very much for this.
Marks fun Apr 22 @ 11:39pm 
I also had problem with gamebar presence writer attempting to run on dcom said something about it did not connect rather I had game bar on or off. I was running okay after installing 566.36 driver but I went ahead and deleted it because I notice sims 4 was crashing that this was one error always there since the crashing started. Anyhow I wanted t o make sure . I did the take ownership option on the video and deleted it. I did not do the registry thing .l used owners as the user name it get to work. I t still produce a error but it could not attempt to connect. I ran the windows cleaner of system files and have seen it yet come back up
https://www.youtube.com/watch?v=tfnNo0KPBeM&t=8s
Last edited by Marks fun; Apr 22 @ 11:44pm
Good to know. I'd fired up TS4 night before last, after an hour of mod updates, and hadn't experienced any crashes. That was testing it on Nvidia's most current driver w/o a roll back.
Game Bar hasn't presented me any issues, but it's best to have a cache of info if ever you need to troubleshoot. I don't blame you on skipping Regedit. It'd unnerve me to ever touch the Registry.

Granted, though, I hadn't played TS4 for very long and still run an RTX 4060, so I don't have the latest and greatest of GPUs. Although, the first vid you'd posted didn't exclude 40 series from Nvidia driver issues. Remains to be seen, I suppose.

Can't pinpoint it yet, but my better concern is just recently, or rather finally caving to Win 11 from 10 (which I immediately detest). I'd surely used Revo U to uninstall a lot of unnecessary sh*tware from 11. Of course, One Drive was easily first to go just as on 10, and just as on 10, more was to go.

Edit: This was just TS4. I'm yet to test it on more graphics intense games.
Last edited by Sovereign Dark; Apr 23 @ 1:45pm
Marks fun Apr 24 @ 12:28am 
I just have a RTX 2060 so the rollback to 566.36 has been outstanding for me . I do not have the app either so no crashes at all so far. The game presence writer would come up dcom error all the time saying it could not connect in time when I have gamebar turn off. I never know whether is was connecting or not but Bitdefender gave it permission never knew if connected or not . Now that I deleted it I get error that it unable to start. I like that better. I will be glad when windows 11 quits adding stuff and work on the stuff they got now.
Originally posted by Marks fun:
I just have a RTX 2060 so the rollback to 566.36 has been outstanding for me . I do not have the app either so no crashes at all so far. The game presence writer would come up dcom error all the time saying it could not connect in time when I have gamebar turn off. I never know whether is was connecting or not but Bitdefender gave it permission never knew if connected or not . Now that I deleted it I get error that it unable to start. I like that better. I will be glad when windows 11 quits adding stuff and work on the stuff they got now.

AVs can be super touchy with permissions. If BitDef's permitted connection, that should be a good sign. With some AVs, all you can do is uninstall the AV itself. Then what's the point?
You could also try sfc and Dism scans in Command Prompt, running as Admin. It could help resolve all sorts of errors including DCOM. You might know how to do that, but if not ...

Type cmd into search and run Command Prompt as Administrator.
(first prompt, type and include space)
sfc /scannow

Let the scan run. Errors will show if found or if clear.

(second prompt, type and include spaces)
Dism /Online /Cleanup-Image /RestoreHealth

Let that scan run.

They both take a few minutes or so. After the scans are completed, restart your PC.
I do not have any issues at present. I have only the error on dcom when I play sims 4 that the presence writer failed well because I deleted which is fine. Sims 4 has never played so well for me since the rollback and gamebar presence writer delete. Thanks for providing the help but I really know most of cmd commands well because I been running windows 11 for about 2 years now. The restorehealth command when you run it you can check the version they are using and new one they use and it be different sometimes being they had some changes in it to repair or configure. Anyhow that what Goggle AI answer was when I ask.
Last edited by Marks fun; Apr 24 @ 3:56pm
Well you know what after you brought it up I ran sfc and well it put the game bar presence writer back so i guess to see if causes Sims 4 crash with it on with 566.36 nvidia driver. If it does I will try to modify ownership and take full control without deleting it. I have not had any crashes without it on nvidia 566.36 so I guess I try with it since it reinstalled the presence writer.
Last edited by Marks fun; Apr 24 @ 4:09pm
Originally posted by Marks fun:
Well you know what after you brought it up I ran sfc and well it put the game bar presence writer back so i guess to see if causes Sims 4 crash with it on with 566.36 nvidia driver. If it does I will try to modify ownership and take full control without deleting it. I have not had any crashes without it on nvidia 566.36 so I guess I try with it since it reinstalled the presence writer.

Might've just been BitDefender fussing about permissions as AVs often do, but that seemed to sort itself out since you're not seeing that same DCOM error with GBPW. I figured you'd know cmd prompts but didn't want to leave them out just in case. Could be of help to others if they're having technical problems, as well.

Hopefully, the Nvidia driver rollback does the trick for you, and no more crashes.

Originally posted by Marks fun:
The restorehealth command when you run it you can check the version they are using and new one they use and it be different sometimes being they had some changes in it to repair or configure.

Actually, I've never paid attention to versions. Thanks for that info. Now, I'll have a look if I need to run cmd. :steamthumbsup:
< >
Showing 1-11 of 11 comments
Per page: 1530 50