Strange display issue with new RAM?

[adammonty]

Hi,

I have the MSI H110M PRO-VD PLUS motherboard,

I have just upgraded the RAM to 2x Corsair Vengeance LPX DDR4 XMP 2.0 RAM 2400 MHz. 2 x 16GB

According to the motherboard specs this should be viable (right?)

When I boot with 1x 16gb it boots fine, but when I try with 2x16g the pc powers on but I cannot get any display.

I have checked both sticks in both slots individually, I also tried going back to the original 2x4gb sticks and this boots fine. Based on that it cannot be a faulty stick or faulty slot (right?)

I have tried changing my BIOS to the relevant voltage and MHz and then back to auto which it was originally on, but for some reason it just won’t boot with both sticks of the new RAM in.

Am I missing something?

Thank you in advance

[veeg]

Hello

I am assuming you had no issue’s prior to this?

@Bruce

[Bruce]

what is the speed of the original memory?
the new ones are 2400Mhz.
motherboard specs says it only supports 2133Mhz.
is there a BIOS update available?

[ATTACH type=“full”]7033[/ATTACH]

[adammonty]

Hello

I am assuming you had no issue’s prior to this?

@Bruce

Correct, everything was fine prior to this

[adammonty]

what is the speed of the original memory?
the new ones are 2400Mhz.
motherboard specs says it only supports 2133Mhz.
is there a BIOS update available?

[ATTACH type=“full” alt=“1603160522406.png”]7033[/ATTACH]

That is correct but I thought that in that case the ram would just run at a lower clock speed?

I have just updated to the newest version of BIOS with M-flash as per the MSI instructions and now I can’t even boot.

I have a blue screen “choose an option; continue, use a device, troubleshoot, turn off” Continuing to windows doesn’t do anything.

Any ideas?

[adammonty]

That is correct but I thought that in that case the ram would just run at a lower clock speed?

I have just updated to the newest version of BIOS with M-flash as per the MSI instructions and now I can’t even boot.

I have a blue screen “choose an option; continue, use a device, troubleshoot, turn off” Continuing to windows doesn’t do anything.

Any ideas?

also the speed of the original memory was also 2400mhz

[adammonty]

also the speed of the original memory was also 2400mhz

sorry for the rambling but update:

Ok so it seems with the BIOS update it restored my boot priorities. I changed it to what it should be and it now boots fine, with the newest version of BIOS.

I tried going back to step 1 and checking both sticks of RAM separately. It now boots fine with one stick, but not the other.

I guess this means I must have a faulty stick?

[veeg]

Yes that would indicate the ram or maybe a faulty slot.

[Bruce]

if one stick of RAM boots with it in one slot and the other stick doesn’t boot in the same slot, then it’s the stick.

if the stick that boots in one slot, then doesn’t boot when put in the other slot, then it’s the motherboard.

[freestyler24]

Hi,

I have the MSI H110M PRO-VD PLUS motherboard,

I have just upgraded the RAM to 2x Corsair Vengeance LPX DDR4 XMP 2.0 RAM 2400 MHz. 2 x 16GB

According to the motherboard specs this should be viable (right?)

When I boot with 1x 16gb it boots fine, but when I try with 2x16g the pc powers on but I cannot get any display.

I have checked both sticks in both slots individually, I also tried going back to the original 2x4gb sticks and this boots fine. Based on that it cannot be a faulty stick or faulty slot (right?)

I have tried changing my BIOS to the relevant voltage and MHz and then back to auto which it was originally on, but for some reason it just won’t boot with both sticks of the new RAM in.

Am I missing something?

Thank you in advance

Check the compatibility of the memory stick on the motherboard QVL page with exact model: https://www.msi.com/Motherboard/supp...#support-mem-4 . You will get to know if it is supported and if it does then you need to check if it supports dual channel or single channel on the mobo. If the stick is not found in the QVL the probable it would be the compatibility issues.

[phillpower2]

Redundant thread closed.