Can’t upgrade RAM HP Victus 15L

[Danbo22]

 

Can’t get my computer to upgrade ram it just beeps when I put these in, they work individually just fine. Original is on top, newly bought is on bottom

 

[NonSequitur777]

@Danbo22,

Welcome to our HP User Forum!

Your HP Victus 15L should have no problem whatsoever accepting both Samsung M378A1K43EB2-CWE 8GB RAM sticks as per: UserBenchmark: HP Victus by HP 15L Gaming Desktop TG02-0xxx Compatible Components, where your RAM is listed as the most used:

You are using a matching (same brand/model) RAM set.

I'm sure you already did, but it doesn't hurt to ask, did you:

1.) Check running  HP Support Assistant | HP® Support and see if it discovers a BIOS update (making sure you have the latest BIOS version available),
2.) Check that the RAM are seated properly and did you clean the RAM slots with compressed aka "canned" air,
3.) Check the RAM & RAM slots are not faulty by trying each individually RAM stick in either RAM slot.

One other thing that came to mind that helped me once in a similar situation: shut down desktop, disconnect power, install both RAM sticks, disconnect any externally plugged-in device(s) such as a printer, USB hub, backup drive, etc. except your monitor, mouse and keyboard. Reconnect power. Push your desktop's power button in until it beeps and turns off.  Repeat.  Then start up again.

Hope this was helpful.

Kind Regards,

NonSequitur777

[NonSequitur777]

@Danbo22,

Also, if the above doesn't help, install each RAM stick one by one and perform the memory test:

1.) Shutdown your desktop,

2.) Turn the computer back on again and repeatedly tap on the ESC until a Startup menu appears,

3.) Press F2 once,  

4.) Go to the Component test,

5.) From the list, run the Memory (extensive) test,

6.) Obviously, all should pass.

This is what I would do in your situation.

In my admittedly limited anecdotal experiences, I have yet to experience an actual faulty RAM stick.  [I'm sure I have just jinxed myself -0h, well.] In my uncooperative RAM scenarios it turned out to be a motherboard issue and I had to replace it.

Kind Regards,

NonSequitur777