F5F Stay Refreshed Hardware Desktop Unusual memory problem Random data loss observed System behavior inconsistent

Unusual memory problem Random data loss observed System behavior inconsistent

Unusual memory problem Random data loss observed System behavior inconsistent

Pages (2): 1 2 Next
C
csige791
Posting Freak
818
10-30-2024, 09:21 AM
#1
I have an old MSI Z270 Tomahawk board on a machine (the specs are all worn out) that I'm running as a server. Today I decided to replace the RAM and ran into this strange problem. The board has four DIMM slots; the previous memory was two 8GB G.SKILL Ripjaws V 3200MHz units, and the new upgrade is four 16GB Crucial Pro 3200MHz sticks. The issue I'm encountering is that the PC won't power on (the EZ Debug light keeps toggling between CPU and RAM states, I've tried clearing CMOS but can't even reach BIOS). It only works in certain odd configurations. I thought the new sticks were faulty until the weird part happened when I tried: X X G C – Boot and RAM appear in BIOS X C G C – No boot C X C X – No boot C C C C – No boot C X X X – No boot X C X X – No boot X X X C – No boot. So I assumed the Crucial sticks were bad, but then the odd sequence occurred. Any advice would be greatly appreciated.
C
csige791
10-30-2024, 09:21 AM #1

I have an old MSI Z270 Tomahawk board on a machine (the specs are all worn out) that I'm running as a server. Today I decided to replace the RAM and ran into this strange problem. The board has four DIMM slots; the previous memory was two 8GB G.SKILL Ripjaws V 3200MHz units, and the new upgrade is four 16GB Crucial Pro 3200MHz sticks. The issue I'm encountering is that the PC won't power on (the EZ Debug light keeps toggling between CPU and RAM states, I've tried clearing CMOS but can't even reach BIOS). It only works in certain odd configurations. I thought the new sticks were faulty until the weird part happened when I tried: X X G C – Boot and RAM appear in BIOS X C G C – No boot C X C X – No boot C C C C – No boot C X X X – No boot X C X X – No boot X X X C – No boot. So I assumed the Crucial sticks were bad, but then the odd sequence occurred. Any advice would be greatly appreciated.

K
kotomchi
Member
61
10-30-2024, 09:21 AM
#2
The new sticks are x8 or x16. Your BIOS is how many years old?
K
kotomchi
10-30-2024, 09:21 AM #2

The new sticks are x8 or x16. Your BIOS is how many years old?

L
lhs2924
Junior Member
15
10-30-2024, 09:21 AM
#3
I don't have access to specific RAM specifications. Could you provide the model details or confirm the device you're referring to?
L
lhs2924
10-30-2024, 09:21 AM #3

I don't have access to specific RAM specifications. Could you provide the model details or confirm the device you're referring to?

I
IamHenrik
Junior Member
31
10-30-2024, 09:21 AM
#4
Are you familiar with checking your BIOS updates?
I
IamHenrik
10-30-2024, 09:21 AM #4

Are you familiar with checking your BIOS updates?

E
ExoSpade
Junior Member
32
10-30-2024, 09:21 AM
#5
Uncertain about it, but the model matches: 16GB DDR4-3200 UDIMM 1.2V CL22 CP16G4DFRA32A.M8FF with four sticks supporting 64GB. Latest BIOS is available on the MSI site for this board. Confirmed!
E
ExoSpade
10-30-2024, 09:21 AM #5

Uncertain about it, but the model matches: 16GB DDR4-3200 UDIMM 1.2V CL22 CP16G4DFRA32A.M8FF with four sticks supporting 64GB. Latest BIOS is available on the MSI site for this board. Confirmed!

A
AcidixBlitzHD
Member
200
10-30-2024, 09:21 AM
#6
If your system fails to start with essential RAM, it suggests the RAM might be faulty. Attempt using Crucial RAM and G.Skill, then perform a memory test.
A
AcidixBlitzHD
10-30-2024, 09:21 AM #6

If your system fails to start with essential RAM, it suggests the RAM might be faulty. Attempt using Crucial RAM and G.Skill, then perform a memory test.

4
4rw3D
Junior Member
24
10-30-2024, 09:21 AM
#7
I searched online but didn’t find any confirmation. Corsair mentions possible density options like x8 or x16. Another idea is that the 3200 JEDEC modules might not have been available when your motherboard was released, which could cause it to misinterpret the SPD data and fail. This explanation fits because you’d need a G.Skill module in certain slots for the board to recognize the information and boot. You’re likely right that those modules can have multiple profiles in their SPD table—probably including 2400 as well.
4
4rw3D
10-30-2024, 09:21 AM #7

I searched online but didn’t find any confirmation. Corsair mentions possible density options like x8 or x16. Another idea is that the 3200 JEDEC modules might not have been available when your motherboard was released, which could cause it to misinterpret the SPD data and fail. This explanation fits because you’d need a G.Skill module in certain slots for the board to recognize the information and boot. You’re likely right that those modules can have multiple profiles in their SPD table—probably including 2400 as well.

J
janrooijen
Member
205
10-30-2024, 09:21 AM
#8
You should run three passes. The initial mention of G.SKILL likely refers to a specific setup or version, and there’s no workaround mentioned. To verify, check the current configuration settings.
J
janrooijen
10-30-2024, 09:21 AM #8

You should run three passes. The initial mention of G.SKILL likely refers to a specific setup or version, and there’s no workaround mentioned. To verify, check the current configuration settings.

T
TOMASpires
Member
65
10-30-2024, 09:21 AM
#9
Execute the test repeatedly to verify every RAM component. I also checked and found that disabling XMP can be helpful. Some users report success with a 3200MHz configuration.
T
TOMASpires
10-30-2024, 09:21 AM #9

Execute the test repeatedly to verify every RAM component. I also checked and found that disabling XMP can be helpful. Some users report success with a 3200MHz configuration.

C
CobraGamingYT
Junior Member
2
10-30-2024, 09:21 AM
#10
A slightly different motherboard might still be useful
C
CobraGamingYT
10-30-2024, 09:21 AM #10

A slightly different motherboard might still be useful

Pages (2): 1 2 Next