I’m really puzzled about what’s going on.
I’m really puzzled about what’s going on.
Hello! Just a quick inquiry – is your motherboard nearing the end of its life? You're currently encountering numerous WHEA-Logger warnings, such as:
- <Event> details provided about the error
- Keywords: 0x8000000000000000
- Time: 2025-08-11T11:21:08.7448118Z
- Computer model: XXX_XXXXXXX
I'm checking if it's just a minor glitch or something more serious. I've replaced my CPU twice in the past year, and those warnings keep coming back. It might be related to thermal issues, but I suspect the mainboard could be the culprit. Additionally, when these errors happen, the screen displays strange blue and white patterns instead of going black. You can view a visual example here (the bezels are relatively small).
I'm not sure if you're experiencing problems with your CPU or if it's the motherboard. The recurring nature of these issues—sometimes appearing and disappearing over time—makes it hard to pinpoint the exact cause. Please let me know what you observe when the errors occur, and I'll help further. Thanks!
Quick question: Why do you have two Wi-Fi adapters and are you using the Wi-Fi 6 one instead of the 6E one? The picture glitching seems more like a RAM or GPU issue than a CPU problem. It could even be related to your SSD or HDD. WHEA errors usually point to hardware issues, so it's likely your software isn't the cause. Good luck!
Are you checking if your motherboard and GPU are using the newest BIOS/drivers? A RAM problem could be resolved by testing one stick at a time or switching to another.
I think the Wi-Fi 6 adapter should come first, as a previous Wi-Fi setup caused this issue. It's important to test it since the adapter is much cheaper than the GPU.
Is the wifi 6E still installed in a PCI-e port? When you mentioned unplugging it, I thought it was a fixed card. Removing both Wi-Fi adapters—USB ones included—what happens? Also, keep in mind that USB adapters might cause hardware issues, though rare. If something unusual occurs, try testing with a different power supply; it could be unrelated but hard to pinpoint the problem otherwise.