(PC) Wild Hearts Crash after first cut-scene
I started the game Wild Hearts. At first the menu was choppy and attempting to even watch the initial cut-scene was impossible. doing some research I found that you need to set the audio to 5.1 surround sound. After I did that the menu and cut-scene play just fine no matter what other settings I change. Looking around online I'm not the only one with the crash issue after the first cut-scene most people in other forums seem to be people that played the game when it first came out and went to try to do a second play-through and pretty much just gave up on the idea after it crashed. They seem to pretty consistently say this wasn't an issue for them the first time around. To be clear from a hardware perspective I have an AMD Ryzen 7 9800X3D an NVIDIA 5090 and 96GB of RAM so there really shouldn't be a hardware issue here. I have standard Win 11 pro without any OS mods. I have run through all the standard attempts at fixing this. I have reinstalled the game from scratch. Attempted to validate the the game files through steam. Attempted to clear multiple areas of caches. Made sure I was up to the latest on Windows updates / driver updates. reinstalled graphics card drivers. made sure to validate windows updates. made sure to validate the VC++ libraries are installed properly. Made sure to run everything as Admin. I have even spent quite a few hours updating various settings to see if this changes anything. I tried lowering the graphics settings down to nothing to see if that would help. There are some rabbit holes out there around NVIDIA settings to try and I have attempted to flip those on and off in various combinations. There are some posts that talk about disabling your services for audio and that doesn't seem to matter. I know I had some issues with various games with the old Nahimic service where disabling that magically fixed the game. Though my new computer doesn't seem to use that. To be clear so far I have played Forspoken, banishers ghosts of new eden, Frostpunk 2 and Roblox all without any problems and all with the settings cranked to max. I'm fairly certain that banishers is a more intense game on the system. When Wild Hearts crashes it simply closes the game and doesn't display any kind of error looking in event viewer I find: Faulting application name: WILD HEARTS.exe, version: 1.0.3.3, time stamp: 0x64fabc74 Faulting module name: WILD HEARTS.exe, version: 1.0.3.3, time stamp: 0x64fabc74 Exception code: 0xc0000409 Fault offset: 0x0000000002d2a750 Faulting process id: 0x5D68 Faulting application start time: 0x1DBA183478E6EFD Faulting application path: D:\Programs\Steam\steamapps\common\WILD HEARTS\00_game\target_origin\ex\WILD HEARTS.exe Faulting module path: D:\Programs\Steam\steamapps\common\WILD HEARTS\00_game\target_origin\ex\WILD HEARTS.exe Report Id: 641c36b3-eae1-4cbc-af16-46d214783f4b Faulting package full name: Faulting package-relative application ID: Which when you look up this error it is apparently a super generic error message. Though maybe someone more familiar with Wild Hearts code would know why this happens. I attached a dxdiag of my computer for reference since looking at the other EA forum where another person has this same issue that seems to be what support wants to see.
Entire PC crashes playing Wild Hearts
I bought Wild Hearts 2 weeks ago, and I haven't had the chance to really play it because it crashes my entire PC after only a few minutes of play. When it doesn't crash, it'll freeze for multiple seconds every few seconds. my specs are as follows: Processor: AMD Ryzen 7 5700X 8-Core Processor 3.40 GHz Installed RAM: 32.0 GB Graphics Card: RTX 2080
Wild Hearts crash
I recently purchased Wild Hearts on Steam, but I'm having trouble because the game keeps crashing. After watching the character creation movie, the game crashes, and when I try to start a new game, it crashes again after the opening movie. I've tried verifying the integrity of the game files, reinstalling the game, lowering the graphics settings, and checking the Dxdiag, but nothing has resolved the issue. What should I do to fix this?
