Facing issues? Reboots are unpredictable and occasional BSODs occur during gameplay.
Facing issues? Reboots are unpredictable and occasional BSODs occur during gameplay.
All WHEA logs gathered here should clarify things. Appreciate the explanation. Event logs.zip
Just to verify, there are no dump files available. The WHEA events seem quite challenging to interpret completely and prone to mistakes, so having dump files would be helpful as a backup. If you don’t have them, these appear to resemble the CPU specifications I see. Eliminate any overclocking settings—especially memory speeds above 3200 and turning off Precision Boost Overdrive in the BIOS. Ensure the system isn’t overheating. We’ve also noticed some stability problems with 5000 series CPUs requiring a slight overvoltage. Since I don’t overclock, I’m unfamiliar with most BIOS voltage adjustments, but you could try setting an SoC Voltage Offset to +0.050v (please read this precisely: 0.05v, not 0.5v).
This situation raises concerns since WHEA without a dump file signals a potential problem with the NVMe SSD (if applicable). Various configurations and conditions can stop the creation of a dump file, and the occurrences seem unrelated to storage issues overall. Factors that might block dump generation include insufficient space on the drive for the page file. During a BSOD, it may release substantial RAM data into the page file, sometimes everything, meaning you require at least your RAM plus 2-3GB of free space. If manually adjusting the page file size, the same principle applies—ensure adequate capacity. Encrypted drives also prevent dump creation because the process runs outside Windows; encrypting storage with tools like BitLocker blocks access. You might also look for a kernel dump if the system fails to produce a minidump. A file named Memory.dmp should be located at right C:\Windows, but avoid uploading it due to possible sensitive data. Instead, use free WinDbg from the Windows Store. After installation, double-click the debugger, select "!Analyze -v", and capture the top section. Adjust a registry entry under `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl` by adding a DWORD value named "DisplayParameters" with a value of 1 (hex or decimal). Save changes and reboot. If unsure about registry edits, skip this step. To ensure the BSOD displays extra details, modify the registry to include a field in `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl`. The next crash should show the crash arguments in the top-left corner.
I just completed reinstalling my R7 3700x. I’ll give it a shot; if it doesn’t crash within an hour, I’ll think it’s a success. If it does, I’ll stick to the steps you provided. I’ll update you in a few hours since I need to test it first. Thanks!
Alright so little update for you, it seems that changing the CPU resolved the issue, since I've not had a crash for a good 40 minutes session. I'll continue a bit more but I'm clearly noticing a lot of CPU bottleneck. I'll have to check if the 5900x has any real issue or if it's the motherboard that cannot correctly support the 5900x even with the BIOS update. If the CPU is all good, I'll definitely change the motherboard for a newer B550 that supports directly the 5000 Ryzen processors. As for the bottleneck, in Vermintide 2, the R9 3090 combo was working as following : 30-40% usage for the CPU, 85-95% GPU averaging around 185 fps in extreme settings on a UQHD 1440p monitor. As for the R7 3090 combo, it goes like this : 60-70% CPU usage, 45-60% GPU usage average around 100 fps in extreme as well. So I clearly need a better CPU, but I need to figure out if it doesn't crash at the moment because my GPU is not working enough or simply that the CPU / Motherboard combo was at fault. I'm left with a few questions, but I'll definitely have to check the CPU at a local shop to see if it works fine on another board. I'll update if any crash/bsod occurs in the next hours.