[SOLVED] Faulty RAM?

[Lukyen]

I recently got 2 blue screens, one which was memory related but I cannot remember the error code for sure and one that was related to corruption. I ran a drive health test and both my drives are ok. Then I ran Memory Diagnostic Tool and it said that it detected a hardware problem. Does that mean I have to change my RAM? Also, I would like to mention that this was my first pc I ever built and the ram was ordered 2 days ago. (this is a repost since I still need help)


Update: I ran MemTest86 too, got a lot of errors.

 

[egda23]

I recently got 2 blue screens, one which was memory related but I cannot remember the error code for sure and one that was related to corruption. I ran a drive health test and both my drives are ok. Then I ran Memory Diagnostic Tool and it said that it detected a hardware problem. Does that mean I have to change my RAM? Also, I would like to mention that this was my first pc I ever built and the ram was ordered 2 days ago. (this is a repost since I still need help)


Update: I ran MemTest86 too, got a lot of errors.

Hardware reference ? RAM, CPU, Motherboard ?
Did you enable XMP ?
If yes, try a MemTest at stock speed.
Anyway, with good sticks, there should be zero errors with MemeTest

 

[Lukyen]

Hardware reference ? RAM, CPU, Motherboard ?
Did you enable XMP ?
If yes, try a MemTest at stock speed.
Anyway, with good sticks, there should be zero errors with MemeTest

Cpu: Ryzen 5 2600
Mobo: Gigabyte B450 Gaming X
Ram: LPX Black Corsair 8gbx2 sticks, 3200Mhz CL16

Yes, I enabled XMP because it was running at a much lower frequency.

 

[dorsai]

I recently got 2 blue screens, one which was memory related but I cannot remember the error code for sure and one that was related to corruption. I ran a drive health test and both my drives are ok. Then I ran Memory Diagnostic Tool and it said that it detected a hardware problem. Does that mean I have to change my RAM? Also, I would like to mention that this was my first pc I ever built and the ram was ordered 2 days ago. (this is a repost since I still need help)


Update: I ran MemTest86 too, got a lot of errors.

Try unplugging and reseating the memory on the motherboard...make sure the lock tabs snap into the locked position when inserting the memory.

You may also have to set the memory voltage manually in the motherboard BIOS.

 

[Lukyen]

Try unplugging and reseating the memory on the motherboard...make sure the lock tabs snap into the locked position when inserting the memory.

You may also have to set the memory voltage manually in the motherboard BIOS.

I have to go somewhere and when I come back I will try to take the ram out and place it back. Also when I installed it im sure it snapped into place. A friend is coming later with 2 working sticks of ram so that will be useful for troubleshooting too.

 

[DeanTH23]

A lot of Gigabyte motherboards have XMP issues...I had a similar issue myself with a B450 Aorus Pro.
It could be a faulty stick or sticks, but the motherboard is the number one suspect.

Run the sticks at 2.133MHz (disable XMP).Check if they're stable there.
Even if they are stable, i recommend a BIOS Update.

 

[Lukyen]

A lot of Gigabyte motherboards have XMP issues...I had a similar issue myself with a B450 Aorus Pro.
It could be a faulty stick or sticks, but the motherboard is the number one suspect.

Run the sticks at 2.133MHz (disable XMP).Check if they're stable there.
Even if they are stable, i recommend a BIOS Update.

Ok, will try that

 

[Lukyen]

A lot of Gigabyte motherboards have XMP issues...I had a similar issue myself with a B450 Aorus Pro.
It could be a faulty stick or sticks, but the motherboard is the number one suspect.

Run the sticks at 2.133MHz (disable XMP).Check if they're stable there.
Even if they are stable, i recommend a BIOS Update.

Wait, if I cant run my XMP profile does that mean I have to run my ram at 2133Mhz?... Thats a really big downside

 

[DeanTH23]

You can try for 3000,2933,2800,2666 etc. but all the issues with Gigabyte motherboards showed me that the stock speed is the only possible solution.

I hope that it's different with your motherboard.

First of all, make sure it's stable at 2.133 and then you can try for higher speeds.

 

[Lukyen]

You can try for 3000,2933,2800,2666 etc. but all the issues with Gigabyte motherboards showed me that the stock speed is the only possible solution.

I hope that it's different with your motherboard.

First of all, make sure it's stable at 2.133 and then you can try for higher speeds.

Okay...

 

[Lukyen]

You can try for 3000,2933,2800,2666 etc. but all the issues with Gigabyte motherboards showed me that the stock speed is the only possible solution.

I hope that it's different with your motherboard.

First of all, make sure it's stable at 2.133 and then you can try for higher speeds.

Okay so I set XMP to disabled. Im running Memtest 86 rn and I get no errors where I should've gotten 1000 errors. Should I try to make the frequency higher? How much of an impact will this decrease in frequency have?

 

[DeanTH23]

A proper test should last at least 1-2 hours...I know it's super boring but this is only way to be 100% sure that it's stable.

After that try for 2.666...If it's stable move to 3.000 etc.
If it's unstable, update the BIOS...Then re-do the same for 2133,2666,3000 and 3200.

If you find that you are stable at 2.133MHz and unstable at anything else, use other sticks to eliminate the possibility of bad module/modules but since you get 0 errors at 2133MHz i think the modules are fine.

 

[Lukyen]

A proper test should last at least 1-2 hours...I know it's super boring but this is only way to be 100% sure that it's stable.

After that try for 2.666...If it's stable move to 3.000 etc.
If it's unstable, update the BIOS...Then re-do the same...

If you find that you are stable at 2.133MHz and unstable at anything else, use other sticks to eliminate the possibility of bad module/modules.

Okay, thanks a lot for the help. Ill update you tomorrow and tell you whats the situation.

 

[EthanThePCNerd2005]

You may also want to consider clearing the CMOS battery and moving the jumpers on the board to reset the hardware configurations if your hardware problem persists. This response is a bit different than the others, but I suggest creating a Linux Live DVD or USB, then booting from there. Run it for a little while, and then see if there is any change in errors. If it works fine in Linux, but not in Windows, you know you have an issue with your Windows configurations. Note: You do not want to add too many variables to the equation. Keep the independent variable equal to no greater than 1. I hope this helps, please let me know what your results are.