I have assembled a new computer with these components:
Motherboard: GA-890GPA-UD3H Rev. 2.1
Memory: Corsair Vengeance CMZ8GX3M2A1600C9
CPU: AMD 1090T
Graphics controller: motherboard's internal only
BIOS version: FF
I did not try to overclock, and the memory has alway been set at 1333 MHz.
The problem is that sometimes it stops recognizing one of the memory modules. This has happened both in Linux and Windows. I Don't know how to reproduce the problem using these operating systems; it *seems* to be random (but I suspect it isn't). The only way I believe it can be reproduced is with Memtest86+; as soon as it starts, it recognizes only one module, and from then on, both with Linux and Windows I have only half the installed memory. I did not try enough times to be sure that Memtest86+ is a way to reproduce the problem.
The way I have found to get both modules working again is:
Swithch off the computer.
Take away one module.
Start the computer with the remaining module: It does nothing but long beeps.
Switch off the computer.
Move the module to another slot.
Start the computer: if it doesn't start and beeps, move it again to another slot till the computer works.
Once the computer works with one module, switch off the computer and add the second memory module.
If the computer works with both modules, switch it off an put both modules in the right way to get double channel.
Once, only once, the problem solved doing nothing but leaving the computer switched off overnight.
Well, where do you think it is the problem? it sounds like a fault in the mother board; do you agree? or maybe the RAM? maybe the CPU? Have you ever heard about this?
Just in case it were relevant, I was never able to see the AMD 1090T turbocore feature working, although it is enabled in the BIOS. I was about to start a new thread with this topic, but I mention it here just in case it were a clue for something.
