Oh! That's really interesting. But as I can see in that article, this solution is not working in modern Windows releases. Or it does? Author mentions only versions 2004 and 20H2 as problematic, but doesn't says anything about 21H1, 21H2, 22H1...
There's a big warning:Article updated 5/21. That's around an update, but version shouldn't make a difference.
So... should I downgrade my system version first?
This article doesn't say anything about adding info (it's just about viewing and deleting), however I found this one BCDEdit /set - Windows drivers, but it doesn't say anything about badmemoryaccess or badmemorylist from the first article you gave.
Oh, well I had a guess that BSoDs may be happened because of bugs in the Windows code. I had various devices on Win10 and Win7, and on Win10 I saw BSoDs really more often. And also I'm sad that due to a bug I can't use RAM blacklisting in my Win10 2004.I've had an HP Windows Vista machine since late 2007, still running it, and it has never had a BSOD. Windows 10 is a vastly inferior operating system.
Yes unfortunately, I'm glad that I've solved this issue on 90%, but what if it's the start of an adventure? I mean, what if I'll replace RAM sticks and this will not help? I heard that this issue may be related to the motherboard or even CPU, do you have any prediction (according to your experience of building PCs) which PC component could be most likely the culprit? I don't have any additional motherboards and CPUs to troubleshoot it deep enough, I guess I have only 2 solutions:As yiou have found out, software cannot run perfectly on hardware that isn't.
Putting your system to sleep all the time should not be an issue. I've been doing that for almost 10 years now (occasional restart based on updates or program install) and I've never had an issue with BSODS. I did have a recent issue with random BSODS like mentioned in this thread, and I thought it could have been because I was using sleep mode as some mentioned. But, I started testing everything and discovered I had two bad sticks of RAM, I RMA'd them and the system is back to working flawlessly again.I wouldn't be concerned about one or two BSODs a month. Your computer likes to be restarted from time to time.
Hi, this thread is several months old. Well yes, the culprit was a faulty RAM stick, I unplugged it and have no BSoDs since then. Memtest86 helped me a lot, albeit the built-in Windows memory scanner said my RAM has no problems at all. I contacted the manufacturer and they agreed to send another stick as soon as they'll be able to. 👍🏻I'd also Run Mem test on each stick of ram separately as 32 Gb could take a very long time (several Hrs) to to cycle through more than once. It's possible that you have some bad blocks and with 32 Gb it may be hitting those sectors only at certain times. If one of ;your sticks are bad then this method should help isolate which stick (or both) may be having issues.