Could the memory be damaged?
Could the memory be damaged?
I purchased some laptop RAM from GSKill and encountered blue screen errors related to paging and memory problems. This issue started less than two months ago. I've tried almost everything except using them on another machine, as it's an OEM system. I recently updated the BIOS via a Windows update, which seems to have helped reduce the problems. Blue screens still occur during boot-up and occasionally while gaming. I haven't discarded the idea that it might be related to the GPU RAM. I reinstalled drivers, games, and apps, but haven't attempted a fresh Windows install. My SSD appears to be failing, having been used nearly full capacity for two years straight. I ran WMD, which indicated there was faulty hardware. Don’t throw away the $150 just yet—come see if I can offer any suggestions.
Have you installed the new RAM and tested it with just the original setup? This could clarify if the problem stems from the new RAM. Also, try running memtest using a USB drive and booting from it to check for RAM issues.
Can't transmit the memory since I'm not in the states. Will try again.
I purchased a specific type of RAM and my laptop came equipped with it.
I own an HP 15 gaming notebook, an Intel i5 9300H, 1GHz, and 1x8GB DDR4 2666 RAM. I upgraded with two 2x8GB DDR4 2666 CL19 RAM sticks from Kingston. It functions properly initially. The serial numbers on their site are valid. After reinstalling drivers, the problem improves temporarily; clearing CMOS helps for a short time, and running DISM in command line resolves it briefly. However, when I run memory-heavy applications—whether games or Chrome—it eventually crashes again. Even after playing WMD, they mention a hard wear issue. It seems the situation is likely resolved here.
You might test Kingston and GSKILL RAM together. It could be one of the GSKILL units is faulty. I’d consider using just one stick at a time to isolate the problem. Also, check if any DIMM slots on the motherboard are damaged—use only the slot that matches the original RAM type before trying another. This will help pinpoint the exact issue.