Only one channel of ram is working

[quanash]

If BIOS sees the memory as 16GB, but OS sees as 8GB, the problem might be OS related. From screen shots, I see that your OS is in Turkish. I'll explain it in both English and Turkish for easy navigation, so you won't miss it.

*click to the search ( arama sekmesi ) and type "msconfig" without ""
msconfig (sistem yapılandırması) option will appear, click to it.

*an small window will appear on desktop
select boot ( ön yükleme ) sub category from the left.

*select the advanced options ( gelişmiş seçenekler )
there is a category named maximum memory ( bellek üst sınırı ), just click to the box next to it and type 16384 ( 16 GB in MB : 16*1028MB ) than click ok and exit from all the pages clicking ok. System restart request will appear, just click ok and let the system to restart. Probably the issue will be solved when system restarts.

 

[eidairaman1]

If BIOS sees the memory as 16GB, but OS sees as 8GB, the problem might be OS related. From screen shots, I see that your OS is in Turkish. I'll explain it in both English and Turkish for easy navigation, so you won't miss it.

*click to the search ( arama sekmesi ) and type "msconfig" without ""
msconfig (sistem yapılandırması) option will appear, click to it.

*an small window will appear on desktop
select boot ( ön yükleme ) sub category from the left.

*select the advanced options ( gelişmiş seçenekler )
there is a category named maximum memory ( bellek üst sınırı ), just click to the box next to it and type 16384 ( 16 GB in MB : 16*1028MB ) than click ok and exit from all the pages clicking ok. System restart request will appear, just click ok and let the system to restart. Probably the issue will be solved when system restarts.

This is a apples oranges comparison but I would only see this on my sig rig if I was trying to run 2400 with a cas of 9 or less.

 

[Valantar]

If BIOS sees the memory as 16GB, but OS sees as 8GB, the problem might be OS related. From screen shots, I see that your OS is in Turkish. I'll explain it in both English and Turkish for easy navigation, so you won't miss it.

*click to the search ( arama sekmesi ) and type "msconfig" without ""
msconfig (sistem yapılandırması) option will appear, click to it.

*an small window will appear on desktop
select boot ( ön yükleme ) sub category from the left.

*select the advanced options ( gelişmiş seçenekler )
there is a category named maximum memory ( bellek üst sınırı ), just click to the box next to it and type 16384 ( 16 GB in MB : 16*1028MB ) than click ok and exit from all the pages clicking ok. System restart request will appear, just click ok and let the system to restart. Probably the issue will be solved when system restarts.

It does not necessarily mean there's an OS issue. I had the same thing happen with several systems with faulty RAM (confirmed, refusing to boot with only one stick inserted, tested in other systems, etc.). This is normal windows behaviour when it sees RAM but isn't able to communicate with it properly from what I've been able to tell.

 

[basco]

i am with quanash here:
in the tsakmanager on the right side there under DIMM should not be: Hardware reserved 8gb !
on my system its 90mb.

 

[Lbrthelbr]

If BIOS sees the memory as 16GB, but OS sees as 8GB, the problem might be OS related. From screen shots, I see that your OS is in Turkish. I'll explain it in both English and Turkish for easy navigation, so you won't miss it.

*click to the search ( arama sekmesi ) and type "msconfig" without ""
msconfig (sistem yapılandırması) option will appear, click to it.

*an small window will appear on desktop
select boot ( ön yükleme ) sub category from the left.

*select the advanced options ( gelişmiş seçenekler )
there is a category named maximum memory ( bellek üst sınırı ), just click to the box next to it and type 16384 ( 16 GB in MB : 16*1028MB ) than click ok and exit from all the pages clicking ok. System restart request will appear, just click ok and let the system to restart. Probably the issue will be solved when system restarts.

I did this before and still the same. I tried with memtest86 which is a standalone bootable and it also says 8gb usable when 16gb installed. Linux mint is the same too.
I'm guessing it's hardware related.

 

[bug]

At the moment I'm more concerned with video output failure than a stick of memory.

If the system is using the IGP, it wouldn't have the VRAM to display anything if it can't use the RAM stick.

 

[Valantar]

At the moment I'm more concerned with video output failure than a stick of memory.

It's not a video output failure, it's a POST failure.

If the system is using the IGP, it wouldn't have the VRAM to display anything if it can't use the RAM stick.

There is no iGPU in a Ryzen 2600.

i am with quanash here:
in the tsakmanager on the right side there under DIMM should not be: Hardware reserved 8gb !
on my system its 90mb.

That is exactly what Windows showed me in two separate cases, both of which were faulty RAM. Windows and the BIOS both detected both/all four sticks in those systems, but Windows also detected that one stick was faulty and thus "reserved" it to avoid BSODing when using it. It is expected behaviour and a way to avoid crashes in the case of RAM hardware faults. However, unlike in both of my cases, this system boots and works fine with either stick installed in slot 0, but not in slot 1. That means neither stick can really be faulty - though just to be sure, I'd run a bootable memtest instance on each of them separately. But with the DIMM itself being ruled out, the other possible sources for a RAM hardware error causing Windows to refuse to use that RAM are: slot, motherboard traces, solder joints, CPU pins, IMC. The OP has checked the pins and slot, which leaves traces and solder joints as by far the most likely causes. Which of the two this is? Unless you have a microscope or want to strip the soldermask off each RAM trace and check for continuity on ~500 traces, it's more or less moot. The error is >95% likely with the motherboard.

 

[Chomiq]

Just so I know I have this information right....

You say in what I quoted that "Both sticks installed xmp disabled thaiphoon burner:" which makes me think it is possibly not enough SOC voltage, assuming that 1.35VDIMM set with DOCP is actually delivering that. From old school use of gigabyte, they tended to undervolt a bit, but no idea if that is still a thing.

Also my intention was to get a screen shot with DOCP enabled, but I did not say that much, sorry.

I would look into borrowing another set of RAM, or whatever you need to do to troubleshoot this. I see you are on the latest BIOS, so that would fix many of the issues. the only other thing I could suggest is opening a support ticket with Gigabyte and see what they may say.

They overvolt now. Input 1.4V in UEFI, actual voltage will be 1.41-1.42V.

 

[bug]

It's not a video output failure, it's a POST failure.

There is no iGPU in a Ryzen 2600.

Oops, I missed that.

 

[Mekki]

OP, did you find the solution or where the issue was?

I am having the exact same problem as you in a Gigabyte B450 Aorus M, Ryzen 5 2600.

 

[Adlanedjeki]

OP, did you find the solution or where the issue was?

I am having the exact same problem as you in a Gigabyte B450 Aorus M, Ryzen 5 2600.

Hello, im having the same thing, and I’ve got the same cpu, did u manage to fix it?

 

[Mekki]

Hello, im having the same thing, and I’ve got the same cpu, did u manage to fix it?

Yes, I fixed it. The issue was a short with the case screws and the motherboard. I saw the motherboard was working outside the case, but not in the case.

Then I loosened the screws a bit from the motherboard and it resolved for me.

Hope you can fix your issue too!

Cheers.

 

[Adlanedjeki]

Yes, I fixed it. The issue was a short with the case screws and the motherboard. I saw the motherboard was working outside the case, but not in the case.

Then I loosened the screws a bit from the motherboard and it resolved for me.

Hope you can fix your issue too!

Cheers.

much appreciated, will do so, thank you for answering

 

[eidairaman1]

Yes, I fixed it. The issue was a short with the case screws and the motherboard. I saw the motherboard was working outside the case, but not in the case.

Then I loosened the screws a bit from the motherboard and it resolved for me.

Hope you can fix your issue too!

Cheers.

Check for Stray stand offs in case that don't match up to any motherboard screw holes