timmmay:
Did you mean to say it's a driver issue or a RAM issue?
I did test this when I built the machine a few years ago, and recently. Apparently memtest x86 sucks and can't detect memory errors even when run for 24 hours +.
I will likely build a new machine either in the next couple of weeks if it can't be sorted, or later this year if it works ok on 8GB for now.
What I found weird was that with other operating systems, it worked fine. Which suggests a driver compatibility issue with Windows 7/10, and perhaps also suggests that HCI is telling you porkies. Something I otherwise can't account for as I've never heard of Memtest 86 (there is a newer Memtest 86+ you might want to try if not already using it) not picking up serious errors that would cause interruption of day to day use in such a dramatic manner. I'm not sure of the reputation of the diagnostic tool you used, but I've certainly never heard of it. Could it be possible that it was just a false report or similar?
If I was testing the memory, I'd be doing it one unit at a time in each channel to make sure. It's the only way to reliably test memory if an error is found across a whole bank. It takes days though.
I recently suffered from a power event, which destroyed my ethernet port, PCI-E expansion slots except the 16X and channel two on my motherboard, which meant I was forced to drop down to 8GB of RAM, the other 8 going in to a new machine which is now my partners. I tested all the memory in one slot and when no errors occurred, I tested them all in the next slot and continued until I heard the dreaded beep code.
Not saying you have to do that in this case, but it could still be a driver/RAM/board issue at this stage if the memory has only been tested together in or separately in a singular slot on the same channel.



