This may be a coincidence, but I have been plagued with BSOD's since I built my new rig in September.
I have swapped motherboards.
Swapped RAM.
Swapped PSU.
Swapped cables.
I was ready to pin the blame on the CPU at one point.
I have the WD 850x.
I swapped it out with a Samsung PRO, really old NVME drive.
And the past three days I have not suffered the BSOD that I usually had when rebooting or shutting down.
The strange thing is, I built the same rig for my Son. Same motherboard, Same PSU, same SSD. He has had zero problems.
But he doesn't update his system if he can help it.
I'm thinking that it's one of the KB that improves shecudling for AMD CPU's. Not just a 24h2. I was running 242. Reverted back to a clean install of 23h2, and did an update (but not to 24h2), and still had problems.
All of which, went away when I swapped my SSD.
Incidentally, I have another 4tb WD ssd (same model). But it's only when I put the 2tb drive in, do I have issues.
I really wish I had known about this issue a few months ago now. It would have been the first thing I tried. And would have resolved my issue.
I'm thinking there might be just a bad batch of certain WD drives, that are causing havoc. And certain Windows updates are turning borderline drives, into ones that cause this issue.
I've been analysing the minidumps, but they have been utterly random. As has the reason for my BSOD's. It's made diagnosing the problem ten times harder.
One common theme was memory corruption of some kind. Hence why I thought it was the ram, the motherboard, or the CPU.
Whilst another poster has commented the 850x has it's own RAM. That does not mean it's immune from this issue. It could still be misconfigured and is corrupting the Main RAM as is the case with other WD drives.
I've been sat around with baited breath waiting for my machine to BSOD. So I did a search to see what kind of issuse NVME drives can have, and I found this article. Which explains everything!
Personally, I think the issue is shared between WD and Microsoft. In all my years of building rigs, this has been the worst nightmare of them all.
I think I'm going to start taking my sons advice. Make of that what you will. I know I will be at risk, but when that risk is lesser than updating. I'll take it.
I have zero intentions of 'tweaking' my registry. Currently I'm stable, and I'm sending back the WD drive for a refund.
I'm not going to faff around and run back into that instability issue I've been having. I've had two months of it. I've had enough of it.
There will be some who will disagree in the comments. To them, pfft, I'd like to see how smug you would be after two months of random BSOD's, swapping parts in and out to isolate it, only to find out it was your SSD and Microsoft the whole time!!
You'd feel exactly the same, don't even attempt to claim otherwise.
Facebook
Twitter
Instagram