Latest Windows 10 release triggering BSoD error
Latest Windows 10 release triggering BSoD error
I received the newest Windows 10 update without any issues on my end. However, if your RAM caused BSODs when using XMP... The probable cause is the RAM itself. Manufacturers specify these speeds, and if it doesn’t meet them, it’s defective. Alternatively, the motherboard might be involved—especially since this issue occurred with your 2600x. Likely the CPU memory controller is at fault, given that a newer BIOS (B450) was released to support the 5600x.
Could this be linked to the GPU using too much VRAM? I noticed that when it occurred, I was closing Siege, which without my notice altered all the settings to maximum. It required around 400MB over the 4GB the card needs to function with. I haven’t experienced this issue before. It seems unlikely the motherboard is the problem since the 2600x model doesn’t support 3200MHz RAM speeds, but the 5600x does. According to Gigabyte, the board can handle up to 3600MHz and isn’t the cause. I understood the 2600x wouldn’t handle that speed, yet I tried it anyway expecting the outcome. This situation is unusual because I’ve been using the system for just over an hour and a half without any obvious problems since the BSoD appeared. That’s strange because if the issue were RAM or defective, it would have shown up sooner. In reality, the system wouldn’t likely crash if this were the case.
RAM problems can really throw a wrench into things. They don’t always fail right away. Sometimes you’re using it for days or weeks without any issues, then suddenly it crashes. That’s why many people ask why their system feels unstable after overclocking, even when it worked perfectly before. If it only happens once, maybe it was just a minor glitch caused by Windows being unstable. But if it keeps happening, share the minidumps so we can check what went wrong. If the analysis doesn’t point to one cause, you’ll need to follow standard troubleshooting—something that takes time and requires the PC to be off during testing.