Windows experiences a crash due to a BSOD during shader cache compilation and gameplay.
Windows experiences a crash due to a BSOD during shader cache compilation and gameplay.
It seems like your device is experiencing some issues. Would you like me to troubleshoot or resolve this?
F4 is a fairly recent BIOS update. Changing it could be useful, though I'm not sure why it matters. The latest version mentions improved memory compatibility, which might be beneficial.
Sure, I understand. Should I upgrade to F6 or F7b? The latest version seems like a beta, and I didn’t like the alpha versions because they were slow. I’ve attached a dump file for you, and I’m planning to test the 7800X3D to check if it improves.
Consider trying F6 or F7b, which are beta BIOS versions. I usually steer clear of them. I'll review them tomorrow—right now it's 2 AM here and I need rest. My brain isn't functioning properly, even more so than usual.
CrystalDiskInfo gathers SMART information from the SSD for self-checking. This feature was significantly reduced with NVMe drives and now offers little value. The percentage reflects wear and isn't linked to the drive's current condition. Among the many faulty NVMe SSDs I've encountered, fewer than five displayed any failure signs in SMART. The overall health rating (Good) is unreliable for SATA drives as well, since status updates depend on the manufacturer, who often act dishonestly. You need to understand the parameters in the lower section of CDI and identify which ones matter most. With NVMe devices, most useful data has been removed. The dump file reveals an Nvidia driver crashing during an ISR (Interrupt Service Routine). This is common with defective Nvidia GPUs. It's normal for ISRs to occur; we don't know why this happens. A Critical_Process_Died indicates a Windows process crash, which isn't inherently alarming as crashes can stem from various causes. If you lack a dump file from the crash (like a DPC_Watchdog_Violation), it raises suspicion about the SSD. Still, Nvidia drivers have had many problems recently, so they could be the culprit. The last stable version predates the 50-series release, meaning 50-series cards can't use it (assuming this is true). I recommend removing the EXPO profile from RAM during troubleshooting. A 6000 boost is a noticeable increase but still counts as an overclock. While adjusting Precision Boost Overdrive (PBO) to Disabled in BIOS helps, keep in mind that multiple factors can trigger random crashes. Using several dump files and crash logs improves the analysis accuracy.
I see. You need more dump files for a better diagnosis, correct? I have more dump files, but they're not recent, and they're probably from the same issue you saw: the ISR. Minidump.rar There's something else that happens on my PC, but I strongly believe it's a driver issue. Sometimes, when I power on my PC, it doesn't send a signal to my monitor after passing the BIOS. Specifically, when entering Windows, it's a black screen, and it loses the signal. So, the dump file might not show the critical process died stop code, as you said. Perhaps it created this dump file because I allowed it to restart automatically instead of turning it off using the button on the case. There are 2 extra dumpfiles that I had a few weeks ago, please check them
I ran memtest86 to check my RAM and got no problems after six runs. I also performed the test without EXPO and PBO, but the issue persisted... an additional stop code appeared before I replaced my PSU—it was memory_management. Should I consider trying another CPU? I might be able to purchase a new one if my current one is faulty.