Wild hearts constantly crashing out
So I got a code for Wild hearts for the EA app from Humble bundle monthly choice a good while back. This game has been on my " want to play list" since it was Announced. My pc more than meets the Rec...
Forum Discussion
EA_Leeuw
Community Manager
Community ManagerHi Karastorm ,
Your system should be capable of running WILD HEARTS, so this does not appear to be a case of simply being below the required specifications.
Since repairing and reinstalling the game has not helped, please try the following:
- Perform a clean installation of the latest NVIDIA Game Ready Driver. Do not rely only on Windows Update or the automatic driver check.
- Disable any overlays and monitoring software, including the EA app overlay, NVIDIA overlay, Discord overlay, MSI Afterburner and RivaTuner.
- Remove any CPU, GPU or RAM overclocking or undervolting temporarily, including XMP/EXPO, and test using default settings.
- Clear the NVIDIA shader cache and the EA app cache, then restart the PC.
- Add WILD HEARTS and the EA app as exceptions in your antivirus or Windows Controlled Folder Access.
- Run Windows Update and install any available AMD chipset drivers for your motherboard.
- Try launching the game after a clean boot to rule out another background application interfering with it.
Please also check Windows Reliability Monitor immediately after the crash. If it lists a faulting application or module, post the name of that module here.
If the game still crashes at the same point, please attach a DxDiag and provide the following:
- Your current NVIDIA driver version
- Whether the game closes without an error or displays a message
- The faulting module shown in Reliability Monitor or Event Viewer
- Whether the crash also occurs with overlays disabled and hardware settings returned to default
Please do not include any personal account information in the files you upload.
Current Nvida driver version 610.74
No error messages when the game crashes
the crash occurs with or without overlays disabled, I'll include the Dxdiag file but there's just no faults on my side or even reasons for the game to be crashing out. This is after fresh installs of everything. I read through the Reliability monitor and it shows no faults either, so I'm yet again at an impass.
- EA_Leeuw
Hi Karastorm ,
Thanks for attaching the DxDiag. I have checked it, and it does contain several recorded WILD HEARTS crashes, even though they are not appearing for you in Reliability Monitor.
The same crash is listed four times:
- WILD HEARTS.exe version 1.0.3.3
- Event: BEX64
- Exception code: 0xc0000409
Your DxDiag also records a separate crash involving the Oculus/Meta software, and shows that the Meta Virtual Monitor driver is active. This does not prove that the Meta software is causing the WILD HEARTS crash, but it is something that needs to be ruled out properly. Disabling an overlay alone would not disable those background services and virtual drivers.Please try the following controlled test:
- Fully close the Meta Quest/Oculus software and stop its background services.
- Disconnect the Quest headset and temporarily disable the Meta Virtual Monitor device through Device Manager.
- Close OBS, Streamlabs, VSeeFace and any other virtual-camera or capture software.
- Disconnect the DualSense controller and test using only a keyboard and mouse.
- Restart the PC and launch WILD HEARTS before opening any other applications.
Your DxDiag also shows some AMD chipset components dated from 2021. Please install the current AMD B450 chipset package directly from AMD, restart the PC and test again.If the crash continues after that, please perform a clean installation of the previous NVIDIA WHQL driver rather than reinstalling version 610.74 again. This will help determine whether the problem is specific to the current driver.
A DxDiag cannot establish that there are “no faults” on either the system or game side, but we now have a consistent crash signature and several background components that can be isolated. Please let us know whether the crash still produces the same 0xc0000409 entry after completing the tests above.
Featured Places
