Bringing this back from the dead, mainly because the new update is out and felt I should give it another go. Like before, nothing happened, and I even attempted another clean boot to make sure nothing is interfering. If anybody wants to know the exact process that happens every time, I'll transcribe it.
- I click "play" on Sims 4.
- In Windows Task Manager, Activation UI and TS4 open up, Activation UI closes shortly after (I'm assuming because it's verified the game)
- TS4 begins to start using CPU, ranging between 4-8 percent
- TS4 after remaining at 8 percent for about 3 seconds, drops down to gradually to 0 and then closes.
There's no error in performance manager's reliability tab whenever this occurs, so I can't even trace an error to it.
I have no idea what's going on, all of my hardware is up to date, sans my GPU driver (which has been up to date every other time, Nvidia is just pushing a CoD driver right now). All of my games do run on a separate disk drive to my OS, but I don't see how that would factor, because every other Origin game follows the same rules and loads up perfectly fine.
EDIT: I have installed Process Explorer just to get a more detailed look at how the process itself is loading, this is what the process looks like in Process Manager right before it closes.
Thanks for the extra info.
I assume you also tried without Steam running (should not run in clean boot so I think it's an obsolete question but just wanted to make sure)
Yes, I tried it without steam running. Outside of the clean boots I did, I disabled my antivirus, closed down anything that would effect the game potentially like Steam or Razer Synapse. I feel like it's trying to access something, and when it can't, it just quits, but nothing I have could show me what it's looking for specifically before the app closes. It's really puzzling me.
Which processes are present if you do a clean boot ? In Process Monitor I mean ?
I should actually give that a look when I have a chance, today my troubleshooting has mostly revolved around me sending files to EA support for them to figure out what might be causing the issue. I've also contacted my manufacturer to see if they'll look at it when they have a chance. I'm sure it's a very small percentage that have the issue this badly, but at this point if people are still seeing this issue like I am, then I'll do all I can as far as data collection goes to help solve it.
Community Manager
