no screen with 2 memory sticks

Meindert

Reputable
Sep 30, 2015
2
0
4,510
I think my motherboard (asrock 870 extreme 3 2.0) is broken.
I always used 2 DDR3 Corsair XMS3 of 4gb each, got BSOD's and often the screen stayed black when I started the PC. A couple of resets and it worked. Tested by using only 1 at a time, and 1 of the 2 was dead. the other I tested with memtest, and had 1348 errors. Replaced them with new corsair vengeance LP (2x4gb). PC still only works with 1 stick at the time, otherwise no screen.
I have 4 memory banks, it's the same where ever I put it.
Are there tests I can run to see if something on the Mobo is broken? Can it be the GPU?
Unfortunately I only have money to replace either the GPU or the mobo.. (been saving for a new GPU..)

Thanks!
Specs: mobo: asrock 870 extreme 3 2.0
CPU AMD Phenom II black edition
GPU: Ati radeon 5800
PSU: sharkoon 500w.
 
Solution
Here is the list for all memory sticks ( Ram ) that are compatible with that motherboard http://www.asrock.com/mb/AMD/870%20Extreme3%20R2.0/index.asp?cat=Memory

If one stick works then the memory must be compatible but check that list to make sure.

If the ram isn't on the list get a refund and try to buy a kit that is on the list

If the new kit still doesn't work then the motherboard might be defective so you might want to see if you have a warranty so you can get a new board sent out to you. The Asrock website is http://www.asrock.com

Hopefully this helps
Here is the list for all memory sticks ( Ram ) that are compatible with that motherboard http://www.asrock.com/mb/AMD/870%20Extreme3%20R2.0/index.asp?cat=Memory

If one stick works then the memory must be compatible but check that list to make sure.

If the ram isn't on the list get a refund and try to buy a kit that is on the list

If the new kit still doesn't work then the motherboard might be defective so you might want to see if you have a warranty so you can get a new board sent out to you. The Asrock website is http://www.asrock.com

Hopefully this helps
 
Solution
Thnx for the answer, but I managed to fix it this morning.
I assumed I had the upgraded UEFI, which was not the case. Upgraded UEFI, and now it works.
Solution: always check if everything is up to date.. (also, checking if stuff is compatible, but I always do)
 


Ahh, I forgot about the UEFI! Good that you found that out though! I might just see if mine is up to date when I get home :)