What could be causing these random BSODs with different error codes?
Asked by
MellowPine47
For the past three or four months, my Windows 11 PC has been crashing with seemingly random BSODs anywhere from once a week to once a day. It can happen while working in Premiere, opening a webpage or Windows window, switching browser tabs, or occasionally while gaming. The crashes don't seem tied to any particular workload, and the stop codes vary. So far I've seen 0xA (IRQL_NOT_LESS_OR_EQUAL), 0x1E, 0x133, 0xF7, 0x20001, and 0x3B, with 0xA and 0x133 appearing more than once.
The system has a Ryzen 7 3700X, MSI B450 Gaming Plus Max motherboard, 64 GB of Corsair Vengeance LPX DDR4-3200 memory, a Sapphire RX 7800 XT, a Seasonic Focus GX 750W PSU, a 1 TB Patriot Viper VPN100 NVMe SSD, two SATA hard drives, and a 2 TB SATA SSD. Most of the platform dates from around 2019–2020, while the GPU, PSU, and second 32 GB memory kit were purchased last year.
The two memory kits will not run reliably at their advertised 3200 MHz speed, so I reduced the RAM to 2133 MHz. The second kit was installed about a year before the crashes began. I also occasionally experience GPU driver crashes in some games, especially Alan Wake 2 with ray tracing enabled, although driver updates have not resolved that issue.
CrystalDiskInfo reports no obvious storage problems, and Windows Memory Diagnostic found no errors. I have collected several minidump files. What should I test first, and does this pattern point more toward faulty RAM, the CPU's memory controller, a motherboard issue, or a driver?
Answers
I had random BSODs stop after changing the RAM arrangement. Try reseating the modules and testing them individually, then test the other DIMM slot if necessary. Also, mixing two separate dual-channel kits can be less reliable than using one matched 64 GB kit, even when the specifications appear identical. Running four modules or mixed kits may require lower speeds and looser timings.
Reply to this answer
The varying stop codes and the dump analysis pointing toward memory make system memory the first thing I’d investigate. “Memory” does not automatically mean a bad RAM module—it can also involve the CPU’s integrated memory controller, motherboard settings, or data being paged through storage—but the RAM configuration is suspicious here.
Disable any overclocking, undervolting, EXPO/XMP-style profile, or other tuning and run the system at conservative defaults. Then test each DIMM by itself, using the motherboard’s recommended slot. Use the PC normally with one stick installed at a time. If one module consistently causes crashes and the other does not, that identifies a likely bad stick. If both behave similarly, the CPU memory controller, motherboard, or memory compatibility becomes more likely. A basic Windows memory test can miss intermittent DDR4 faults, so passing it does not completely clear the RAM.
Reply to this answer
The minidumps are useful here, and the pattern does not strongly suggest a failing drive. With storage-related crashes, at least some dumps often identify a storage controller or storage driver, whereas these appear more consistent with memory corruption. I would still check SSD firmware and run normal drive health checks, but RAM and memory stability should come first.
If the crashes continue with each DIMM tested separately at default settings, the next suspects would be the CPU’s memory controller or the motherboard. Keep a record of which module, slot, and BIOS settings are in use for each crash so the results are easier to compare.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions