Issues with PC crashes frequently occur across most games.
Issues with PC crashes frequently occur across most games.
As discussed, the problem stems from a CPU issue affecting 14th Gen Intel processors with DX12/UE5 titles. I outlined steps to resolve it. Changing games to DX11 also helped, though some titles are exclusive to DX12. Focus is mainly on DX12/UE5 games like Fortnite and Alan Wake 2, where you encounter GPU errors and crashes to desktop. Using a 14900k processor works, but the XTU fix should resolve everything without needing a DX11 switch. GTA 4 crashes likely relate to Windows version or RAM problems—possibly due to Windows updates or memory shortages, which also trigger crashes in other programs. Memory issues can lead to game failures, so both CPU and RAM concerns need investigation.
If you continue experiencing issues: Navigate to C:\Windows\Minidump and verify the presence of any minidump files. Should be present, return to the Windows directory and transfer the entire Minidump folder to the Downloads folder (desktop works if OneDrive isn't syncing). Compress the copied folder and include it in a post. Please adhere strictly to the provided steps as Windows does not permit modifications in this area.
Sure, I've completed everything. I'll check for crashes now. If I don't, I'll mark this as solved. Appreciate all the support you've provided.
Well, I can ease your worries about RAM and CPU when it comes to BSODs. These issues usually stem from BattlEye. If you spend a lot of time debugging, you'll often see BattlEye, EAC, and Vanguard anticheats appearing. Restart BattlEye; if it still fails, provide fresh dump files to verify it's still the original game. You may need to reach out to the developers for updates if it remains BattlEye. What’s happening? BattlEye interferes with memory → Windows detects errors → BSOD appears. You might think it could be a memory controller (CPU) or RAM problem, but the chances are very low. If RAM is faulty or the controller is, the corruption could randomly affect multiple processes, making it seem like a random crash. BattlEye would have to randomly use those faulty bits several times in a row without any other program using them beforehand.
I haven't encountered any issues since I completed everything. I'll remember this if I face problems with BattlEye. Thanks a lot to everyone for the updates!
You're experiencing the same issue despite adjusting the p-core rate and enabling XMP1. Some users believe it stems from a CPU or motherboard defect that resolves after replacement. It seems to recur over time, suggesting possible hardware wear. Changing the core rate through XTU might affect your warranty. Interestingly, Control runs smoothly in DX12 mode without problems. Also, Cinerbench24 only starts tests when you adjust the p-core ratio—though it's not a UE5 game.
I've disabled XMP and set the p-core speed to 55, and everything is working smoothly in games and software. I'm still puzzled about what's happening.
Hmm? This situation is being examined by game developers as well as Intel, and no one is claiming it's a hardware malfunction. Was that just one comment? The linked post also covers problems with the 13900KS, including other concerns beyond just DX12 games or CPU-heavy apps crashing or failing to start. As I mentioned, I own the 14900K, while others have the 14900K; so far most issues are with that model (though both 13900K and KS have seen similar problems). Once you set up XTU and it launches at startup, you shouldn't run into trouble, and the issue doesn’t return. I’ve noticed it reappearing only when XTU fails to launch initially. I’ve spoken to an Intel representative and a few developers investigating these matters. Both confirmed it isn’t hardware failure, pointing to potential issues with Windows or application handling of higher clocked P-Cores. If this were a hardware problem—especially CPU wear—it wouldn’t be so silent, and we’d likely see more users encountering the XTU fix again.