Various BSODs ?
Various BSODs ?
When discussing Hardware in General, you're referring to HDDs and their interfaces, SSDs and their read/write speeds, RAM and its interface (read and write speed), as well as the processor, socket, and its frequency. It doesn't need much experience to put these computer parts together. 1) The RAM should be considered when using the Mhz reference in the search engine. 2) The person facing this issue still sticks with the 3200mhz reference, owning a Corsair 3600mhz. 3) Concerning RAM error codes... 1) It could be a sound beep code... 2) Or a system not starting, regardless of screen color. 3) For graphics cards... it's an audio-visual aspect... the chances are: 1) The GPU isn't compatible... 2) Not HDMI compatible... or 3) No support for the SCREEN... I've avoided probabilities 2 and 3 since the owner has been using it for three months without issues.
I share your view on @Colif that the optimal starting point is testing RAM, preferably by removing one stick at a time. Refer to the motherboard manual to confirm that the remaining sticks fit correctly in their slots—three sticks should suffice. You may also test one stick individually, but double-check with the manual to ensure proper placement.
I’m focusing on RAM first since three of your dumps indicate corruption of a LIST entry, likely due to a driver error. This can happen when a driver accidentally overwrites data and only becomes apparent later. Additionally, two dumps show 0xC0000409 exceptions, suggesting a stack buffer overflow possibly from a rogue driver. There are no third-party drivers mentioned before these issues, which points toward a hardware problem and reinforces that RAM is the most probable culprit.
Let us know if removing RAM improves stability or continues to cause BSODs when each stick is present.
After removing the old GPU with artifacts, RAM became my next suspect, but it passed the test and I left it behind. It seems to be the only one that makes sense. The LAN driver has been updated according to the recommendations, and all other drivers/bios are already fixed. Here is the requested SysnativeFile for any further details. We'll start the 3 sticks test soon.
memtest only assesses the health of the drive, it doesn't detect subtle timing issues that might lead to errors. It isn't built to identify them. If you need more than 16GB of RAM, you should have purchased a single unit. Running multiple sticks from different sets increases error risk.
Yeah, that's exactly what I'm thinking. While we wait for @ubuysa to explain more about Sysnative, my brother experienced another BSOD today, this one displaying the failed process: ntoskrnl.exe. Everything points to a driver or RAM issue, but with almost nothing installed since the Windows update, it's clear a faulty RAM module is likely causing the problem after years of the system running smoothly.
I would continue working on the RAM extraction. Was the RAM bought as a set? The part numbers match, which suggests it might have been. The dumps might indicate faulty RAM, but they could also point to a malfunctioning driver. There are several memory-related error codes in your application logs and multiple system restarts in your system logs that aren’t linked to a crash. Both points suggest the RAM may be problematic. You should confirm its condition before proceeding further.
It's two sets, that's what I meant to say.
CMW16GX4M2Z3600C18 = 2x8gb sticks
https://www.corsair.com/ww/en/p/mem...d-...m2z3600c18
I own the RAM myself.
If it were a single 32gb set, it would be CMW32GX4... that's how Corsair RAM is structured.
Consider using two sticks together.
A challenge will be locating two matching sticks since there are four options to choose from. I'm not sure if Corsair labels cases to indicate which set they belong to. You might have to test a few times.
CPU-Z could display it, but I can't confirm because it seems to struggle recognizing my RAM sticks. One tab shows DDR4, another thinks it's DDR2? I'm not sure if I should care.
The dumps encompass nearly all available RAM information (as seen in the Memory Device (Type17) records). Each unit appears uniform, even though I suspect they might represent two separate kits. Notably, they are clocked at 2666MHz, even though their capability is listed as 3600MHz, and I’m aware that AMD CPUs tend to operate faster RAM.
Yeah, the Ryzen 3000 line is known for resetting XMP settings frequently, something I experienced personally. The 5000 series seems to manage it smoothly. After taking out my brothers first and third, there have been no problems so far. Still, occasional crashes can occur, so we keep watching it closely.
My first and third sticks are these links:
https://www.corsair.com/us/en/p/pc-...o-...-cmwlekit2
They reduced the errors and filled all four slots with identical RAM. Windows might think one is 4GB, but it could actually have 4GB RAM for RGB storage.