TS4 APPCRASH

@TheSuperWolf100  That's an access violation.  It can caused by anything from bad mods or custom content to an in-game bug to another program on your computer interfering with the game.  I'd start with removing mods and cc and go from there.

How can you tell its an access violation

@TheSuperWolf100 The simple answer is your computer is trying to access a memory location it doesn't have rights to. The long answer is you have to know how the the cpu works. This usually happens when a stack is manipulated wrong or an array is corrupted or incorrect cpu instructions. Usually caused by bad coding. You would first need to understand what you want the cpu to do at a machine level then work backwards to find out why the cpu is not doing what you want it to do. A computer will only do what you program it to do - right or wrong.

If you saw JurassicPark Nedry: "You know anybody who can network 8 connection machines and debug 2-million lines of code for what I bid for this job?"

@TheSuperWolf100  This exception code:

Exception Code: c0000005

is an access violation.  Windows uses eight-digit codes like this to indicate a variety of issues, for example 80000003 is a breakpoint error.

still getting access violations in sims and others Games I ran memetest 86 no error found what could it Be

@TheSuperWolf100  It's unlikely to be an issue with your computer's RAM, so I'm not surprised MemTest came up clean.  Did you test without mods and custom content yet?  Have you tried a new save, or are you only testing in your current one?

Like I said before, there are a lot of causes of access violations.

Ya I found the problem to the game still kept crashing on a clean version with no mods so I ran diagnostics on the memory controller on the motherboard and that returned a fault look like I need to do an RMA because one time it says my ram has faults and the other time it reports it clean due to a faulty memory controller 

@TheSuperWolf100 Traditionally the memory controller is inside the northbridge chip of the motherboard chipset, With modern CPUs the memory controller is built directly into the CPU itself, While not impossible a bad memory controller is rare. Bad memory modules are rare but can be found in the wild. I once built a computer that would blue screen once a day/ The problem was a bad memory module. As the module was new I exchanged the memory and the computer lived happily ever after. First thing I would try is to reseat (take out and reinsert) the memory modules. If you still have the problem exchange the memory modules (take one out and put the other module where the first one was and then put the other in the socket you took the other out of. If you still have an issue then take one of the modules out  and and boot the computer on one module. If you still have an issue exchange the modules and boot on one module. Doing this should tell you which module might be bad.  hth

okay im starting to think its the memory controller inside the CPU because i ran a memeory diagnostic test and it passed it all but when i run a CPU test i get a lot of errors for the vitual cores so it seems like the CPU is defective gotta call intel for an RMA for the cpu since i ran tests on the whole system and onlt the CPU is returning errors