I usually don't have issues with resolving anything PC related but this one has me completely stumped.
In 2011 I built my first PC and have upgraded it over the years. As far as memory goes, I installed another 16GB and for quite a while had 24GB of memory with no issues on Windows 7 Ultimate 64 bit.
However, somewhere in the last few months I've had something happen where BIOS is only recognizing half of my memory, although it does recognize all 4 slots. The upgrades I've done recently is upgrade to Win10 Pro 64 bit, install a new 8GB GPU, and install a new wireless card.
Specs:
Windows 10 Pro 64 bit
MB: H67MA-USB3-B3
CPU: Intel Core i5 2500
I realize the memory is different but I've tried extensive troubleshooting with just 1 type in every arrangement possible and still always get only half the memory recognized, although again all of the used slots register memory.
Additionally I have:
In 2011 I built my first PC and have upgraded it over the years. As far as memory goes, I installed another 16GB and for quite a while had 24GB of memory with no issues on Windows 7 Ultimate 64 bit.
However, somewhere in the last few months I've had something happen where BIOS is only recognizing half of my memory, although it does recognize all 4 slots. The upgrades I've done recently is upgrade to Win10 Pro 64 bit, install a new 8GB GPU, and install a new wireless card.
Specs:
Windows 10 Pro 64 bit
MB: H67MA-USB3-B3
CPU: Intel Core i5 2500
I realize the memory is different but I've tried extensive troubleshooting with just 1 type in every arrangement possible and still always get only half the memory recognized, although again all of the used slots register memory.
Additionally I have:
- Updated BIOS as well as install older versions, even back to my original version
- Made sure the memory limit box in Win10 was unchecked
- Reset CMOS both in BIOS and pulling/replacing the battery
- Reseated the CPU and checked for bent pins
- Removed the GPU
- Removed the new wireless card
- Run memtest86. I did get 1 error with memtest86 (test 9) but in the course of figuring out which stick caused the error I could not replicate it, even when using the same setup I used when first encountering the error.
Last edited: