Hi AMH,
You are looking for the possibility of bad RAM and/or bad slots.
If a RAM stick fails to boot or fails the memtest86, run it in another slot. If it passes this will indicate a possible bad slot.
Next, put another RAM stick that you know has passed in one of the other slots, into slot 1, run memtest86. If it fails this will confirm the bad slot.
If you want to be sure, since the issue with 2 sticks running at 666 Mhz and the other two possibly running at 200 Mhz, try all four one at a time in slot one.
just now I tried firing the PC up with the third stick of ram in the first slot, the pc powered on but my screen remained blank. I reset it twice and it still remained blank.
I swapped to slot 2 and hooked everything back up and this time it booted just fine. Running memtest86 though showed no errors with the ram, although it is listed as 200MHz (DDR400) just like the other stick.
I did a quick, 5 minute, search on your MOBO and found a reference to an issue with this board running more than two RAM sticks, actually not being able to run more than two sticks of RAM.
Someone mentioned that they had read this on a couple different forums, so not 100% fact.
They also mentioned that some brands of RAM and certain timings gave this board problems.
Running at 1600 caused it not to boot.
You may need to set everything back to 1333 and see if it will run.
Did you buy all four RAM sticks at the same time and place?
Are they exactly the same timings and voltages?
Your board recommends 1.5v for RAM, running above this can cause an issue. This was also mentioned in my search.
Is it AMD tested memory?
If it's the Intel RAM there are lots of issues mentioned, You need to make sure it's the AMD spec RAM.
Tell us the exact settings you put the RAM at in BIOS.
Can you give us a
CPU-Z snip of the Memory and SPD tabs?
In your previous post,
Just finished drive check, downloading seatools now to run that. Here's a screenshot of what the drive check said.
At the bottom of the snip it says:
View attachment 82268
Did you run CHKDSK with the /F option to fix the Bitmap error?
Then run Check Disk again to ensure it has been fixed?