There are blue screens everywhere! You need assistance.
There are blue screens everywhere! You need assistance.
we began experiencing frequent blue screen issues, but I don’t have any spare components to test. i attempted to remove two RAM sticks, yet nothing changed. i’m still hoping it will function properly because i have other uses for the device and i want this to work.
Do you have the Asus Armoury crate set up and active in BIOS? If yes, turn it off in BIOS and use the Armoury Crate Uninstall Tool at the provided link. You experienced the same BSOD once with a 9700K on a Z390 Hero XI. Reinstalling Windows resolved the problem. Later, the same error appeared again but more often. After some testing, it turned out to be a faulty RAM stick. Consider reinstalling or replacing the RAM. A 2x16GB kit is now available at a reasonable price.
Check the driver if it points to a specific file. Otherwise, random kernel crashes suggest hardware issues like RAM or CPU problems. You can verify RAM health by running memtest.
You can verify your RAM using memtest and inspect SSDs with tools that display their health status or obtain from the maker. If you recently installed a driver, consider reverting to an older version. Are the blue screens frequent or limited to gaming sessions? If you think about the power supply unit or graphics card, you might try booting without them.
I would dismiss this unless all other factors are verified because CPUs don't simply fail unexpectedly. If they did, you'd be very unlucky since such incidents are rare. Also, try adjusting frequencies and voltages manually in the BIOS to eliminate CPU/RAM issues. Go through AI Tweaker to balance core ratios, set core ratio to 40, and adjust core voltage to manual mode at 1.2V. This conservative setup ensures stability across all CPUs. Make sure XMP is turned off to prevent RAM interference. Share screenshots of all four RAMs for comparison to confirm compatibility. Test one RAM at a time to spot defects, but only if crashes persist after manual tuning.
CPUs only malfunction due to voltage spikes from events like lightning or faulty setup, or incorrect BIOS configurations. Normal wear and tear in transistors is almost impossible, though when it occurs it usually affects the cache. AMD lacks such a diagnostic feature, but Intel provides a tool (PDT) that tests all CPU functions to confirm chip health.
I'm curious about the outcome if I tested it on any of my CPUs. You mentioned you've pushed your I7 930 to 2V VTT, but haven't really ventured into the 1.9V VCore range. I've never actually used a CPU in the 2V VTT range, though I managed to get it stable at around 3200 on two sticks. Now it's scaling down to about 1.87V, but it seems to get worse above 1.8V. It looks like it's not working well for a DDR3 3300 screen. There might be some damage from improper installation, possibly due to drops. Even with pad scratches, it's not always a guarantee of revival. Your BIOS settings seem to reflect the abuse you're doing, but old hardware can still handle it—except for the 1156 model where an I3 540 died at 1.85V instead of the usual 2.1V+. It was running at around 70°C in BIOS with a 5.2GHz processor, which is pretty extreme.
I've reviewed your crash logs and it seems most dumps are being saved as kernel dumps, which limits the number of files you can share. This also complicates debugging since patterns aren't visible in a single dump. However, you're encountering a specific crash that provides more detailed diagnostics. Generally, you're seeing a combination of crash messages, often indicating memory issues. Since most crashes since December have been WHEA_Uncorrectable_Error, suggesting hardware problems with the CPU or PCIe devices, this is helpful for troubleshooting. The crashes are primarily memory-related, but about half of them since December have been CPU or PCIe errors. The most frequent causes are Internal Parity Error and Internal Timer Error, with TLB errors being less common. The TLB manages virtual to physical memory mapping; if it's overclocked, consider removing it. Monitor CPU temperatures and ensure your BIOS is up to date—updates can sometimes cause crashes, though they risk corrupting the BIOS. If you experience a crash during an update, it might damage your BIOS. ASUS' CrashFree feature may differ from Flashback in how it handles crashes during BIOS updates; you might want to verify its behavior or ask others if it can recover from a corrupted BIOS. A faulty BIOS could brick the motherboard if recovery options are missing, and power issues can also play a role. My main concern is the CPU itself.
If you're curious, examine the lower MCI values of WHEA crashes to identify CPU issues. Transform the last four hex digits of the lower MCI into binary and apply the programming guide (it's regularly refreshed, so page numbers shift, but you mainly need the "Simple Error Codes" and "Compound Error Codes" sections). AMD and Intel error lists are largely identical, though Intel includes more details for 13th and 14th generation chips. An AMD fault will likely appear in the Intel manual (though this could change), whereas an Intel fault might not match AMD entries. Locating AMD documentation can be challenging. I’ve already reviewed several crashes for you. My debugging happens on another forum, so my perspective might be limited. I typically analyze 10–15 cases daily. A faulty CPU appears 2–5 times each week. Usually, it’s a newer CPU that slipped past quality checks, making it less common on older models. Alternatively, users with older CPUs may upgrade sooner when problems arise. I’ve encountered many defective 4000 series laptop CPUs—Lenovo being the most frequent—but also a significant number of Ryzen 5 3600 units, which sold quickly enough that a typical failure rate would naturally be higher.