F5F Stay Refreshed Hardware Desktop Part of memory not avaiable

Part of memory not avaiable

Part of memory not avaiable

Y
yNetFlix
Member
187
06-03-2018, 02:35 PM
#1
I'm experiencing issues with my PC after purchase. Despite having two 16GB RAM sticks, the operating system reports only 15.9GB used, while OS shows 32GB available. RAM-Z lists 32GB but OS claims 15.9GB. Could this be a compatibility problem? My system includes an AMD Ryzen 7 1700 processor, MSI X470 motherboard, NVIDIA GeForce GTX 1060 GPU, and other components like SSDs, case cooler, and display.
Y
yNetFlix
06-03-2018, 02:35 PM #1

I'm experiencing issues with my PC after purchase. Despite having two 16GB RAM sticks, the operating system reports only 15.9GB used, while OS shows 32GB available. RAM-Z lists 32GB but OS claims 15.9GB. Could this be a compatibility problem? My system includes an AMD Ryzen 7 1700 processor, MSI X470 motherboard, NVIDIA GeForce GTX 1060 GPU, and other components like SSDs, case cooler, and display.

X
xxXJolanXxx
Member
221
06-11-2018, 04:22 AM
#2
These issues typically involve four steps: 1. BIOS update if possible. 2. Remove CPU and reinsert properly. Memory relies on CPU pins, so a single pin not connecting can affect performance. 3. Check RAM modules one by one—if 16GB works correctly and slots match (channel 1 for 1-3, channel 2 for 2-4), proceed. 4. If all else checks out, you’ll need to return it for replacement.
X
xxXJolanXxx
06-11-2018, 04:22 AM #2

These issues typically involve four steps: 1. BIOS update if possible. 2. Remove CPU and reinsert properly. Memory relies on CPU pins, so a single pin not connecting can affect performance. 3. Check RAM modules one by one—if 16GB works correctly and slots match (channel 1 for 1-3, channel 2 for 2-4), proceed. 4. If all else checks out, you’ll need to return it for replacement.

I
ItsYuno
Junior Member
21
06-11-2018, 11:00 PM
#3
The defective motherboard caused an issue. I managed to secure a replacement at the last moment.
I
ItsYuno
06-11-2018, 11:00 PM #3

The defective motherboard caused an issue. I managed to secure a replacement at the last moment.