Buy Parenthood And Now Getting Issues

@Nakatomi_Uk  Start by clearing Origin's cache and restaring your computer.

https://help.ea.com/en-us/help/faq/clear-cache-to-fix-problems-with-your-games/

Is your base game currently installed?  If so, please try repairing it: open your game library, right-click on the Sims 4 icon, and select Repair.  Then try to download just one pack.  If it works, download one more, and then one more.  It's tedious but sometimes helps.  Any time you get an error, clear Origin's cache, restart your computer, and try again.

If this doesn't help, try disabling your antivirus while downloading.  As long as you don't do anything on the internet other than downloading the game, you should be fine.

I tried the repair option after clearing the cache didn't work, I even went to the extreme of removing sims 4 and origin and downloading them all again but under the sims 4 content section there was The Sims 4 Legacy Edition and it was free, I added that and it downloaded and then I shut down Origin. I then restarted Origin and then all my add ons downloaded and installed I got S4 running then after 20 mins it just crashed without warning again.

I assume the crashing is the issue with a sound bug and they are patching or fixing the issue for next week yes??

@Nakatomi_Uk  The crashing due to sound issues will hopefully be fixed soon, but that's not the only reason the game can crash.  More immediately though, running the Sims 4 Legacy Edition means you won't be able to use any content released in the last year, whether packs or free updates.  You also won't have the benefits of patch fixes, although I'm not sure whether the sound issue counts.

Are you currently running the LE?  You should be able to switch back and forth in Origin: open your game library, right-click on the Sims 4 icon, select Game Properties > Advanced Launch Options, and select the version you want from the dropdown menu.  If you don't see the option to switch to 64-bit, repair the game and look again.

As for the crashing itself, I can take a look at a dxdiag if you want and let you know whether there are any other obvious issues that might account for the issue.  Since the game was running badly before, there might be something you can address.  Hit Windows key-R, enter "dxdiag" without quotes, let the scan finish, click "Save all information," and save the file to your desktop.  From there, upload it to a third-party filehosting site and link it here.  This site's virus scanner is currently blocking all attachments.

No I have my Sim 4 Limited Edition installed and the add ons I own only, As I said before this is now a fresh install and it didn't download any patch so I assume the current patch is already intregrated into the current sims 4 release, I have uploaded my dxdiag text file for you and here's the link to see it

https://drive.google.com/drive/folders/1lzGP6TXBNWAFVSHt67bxAjkio2yfz-bJ?usp=sharing

@Nakatomi_Uk  Just to clarify, if you added the Legacy Edition to your game library, it could download the same way other packs do.  The important thing in general is to make sure you're launching the 64-bit version, which you can check within Origin, as described.  And yes, if you reinstall after a patch, you get the fully updated version of the game.  But if the LE also downloads, you may be running that by default and effectively be playing the version of Sims 4 that was current a year ago.  Having said that, the errors in your dxdiag show you're running the 64-bit version.

The most recent Sims 4 crashes in your dxdiag look like everyone else's Sims 4 crashes, at least among those posting in the mega crashing thread.  That's not definitive proof that you're experiencing the same issue, but given the timing, it's reasonably likely.  I don't see anything else in your dxdiag that clearly indicates another issue either.  And of course your hardware is more than sufficient for whatever you're trying to do in-game.

I'm sorry I can't give a better answer other than either try playing with the -nosound command line argument (as mentioned in the crashing thread) or wait for a fix from EA.  But I don't know of any other fix or workaround at this point.