[FIXED] [PC/MAC] Error code 134:b378c837

Clean install with Eco Lifestyle expansion, no CC or MODS, started a new save after the expansion got released and after a few days the household stopped loading, just crashing the game. Tried various workarounds, repair the sims 4, load into another household and then into my main, nothing worked the game kept crashing. After the 6/10/2020 update I cannot load any household new or old anymore and I am getting the error code 134:b378c8374240d837.

Could you send me your save ? Instructions in my signature

• This is a known error code that is being looked into by Maxis. There is no ETA on when it will be fixed.
• No amount of troubleshooting your general game will get the save to work
• It might be possible to get the save to work by deleting certain families that cause the issues in the first place but it's often tedious work. I tested several saves trying that and had no luck even deleting all Sims and all lots.
• Best to wait until it gets fixed. Maybe play another game meanwhile.
• Don't delete your save, it's not lost. Also always make backups of your saves before patching.
• Start a new save to play until this error gets fixed although that seems that it can occur again any time. It might have to do with a certain playstyle or the reusage of certain families that are causing the error in the first place even if you place them in a fresh save. As I don't know what the actual cause is (it does seem to have to do with rabbitholes according to the LastException the game throws), I have no tips on how to prevent it.

Hi Everyone,

I have recently re-installed The Sims 4, I had a different error that was repaired with the re-install!! However, I have now been hit with game failed and a loading error. I don't have any mods, but i am losing the battle with the error code. I have tried repairing which was a waste of time and didn't help at all. 

Any advice would be much appreciated, this past week I have encountered endless issues since downloading the Eco package.

Thanks in advance

@K282828 

Please update with yesterdays patch.

For me the error code appeared after most recent update (June 10, 2020). I’m not able to load any households. 

tried it, doesn't fix it.

@crinrict Hello, I have the same problem since yesterdey but on PC (after 1.63.136.1010 patch). The patch created the problem.

Error code: 134:b378c837:4240d837

Have no idea what to do with it. All I did was to install the latest hotfix. Everything worked before this update.

Have no mods, never used mods.

@peter88s. Yes, the code has appeared after the update. The game is now unplayable, finding it really frustrating!! Since downloading Eco I have had nothing but problems.

Product: The Sims 4
Platform: PC
Which language are you playing the game in? Polish
How often does the bug occur? Every time
What is your current game version number? 1.63.136.1010
What expansions, game packs, and stuff packs do you have installed? Outdoor Retreat, Get to Work, Perfect Patio, Spa Day, Cool Kitchen, Get Together, Movie Hangout, City Living, Vintage Glamour, Vampires, Bowling Night, Parenthood, Jungle Adventure, Seasons, Get Famous, Strangerville, Island Living, Realm of Magic, Discover University, Tiny Living Stuff, Eco Lifestyle
Steps: How can we find the bug ourselves? It occurred after I installed the latest patch yesterday
What happens when the bug occurs? I'm not able to enter the household with my family in. I'm basically not able to play any family on this save. Game opens but I can't play with any family because the error occurs. I also checked my other saves and I have the same problem with them. What is also interesting - when I start a new game with new save, everything works fine.
What do you expect to see? I want my old save to be fine
Have you installed any customization with the game, e.g. Custom Content or Mods? Never used
Did this issue appear after a specific patch or change you made to your system? Yes, the latest hotfix (yesterday)

I'm sending to @crinrict my save as I was asked to. 

I also attached here a screenshot of the error.

Have no idea what to do with it. Everything worked fine since yesterday and the hotfix.