this post was submitted on 15 Jul 2023
41 points (100.0% liked)
Technology
37717 readers
479 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Since what everyone else has suggested hasn't worked, there's 3 more things to test:
Update your BIOS. Depending on the age difference between your CPU and your MOBO, the BIOS might not be configured correctly for your CPU and thus half your RAM is unable to be addressed.
Test your RAM sticks and memory slots individually. Put your sticks in the primary channel (per your MOBO specs) one at a time and reboot to see if they're actually working. Then try moving them around to see if the issue is a bad slot, rather than a bad stick.
Are you sure you're not running a 32-bit OS? You'd be capped at 4GB system memory on 32-bit Windows, for example, no matter how much physical RAM you have.
Tried updating my bios but when attempting to through the bios itself it states "not a valid bios" even though it's through the updater built in??
Do you mean you're getting an error message saying the "selected file is not a proper BIOS file"?
Or are you getting a different error? If it's the above, you'll need to remove and redownload the updated BIOS, as it was corrupted during download, and you'll need to make sure you have a stable connection while downloading to avoid it happening again.
If you're getting a different error I'd need to know the exact wording to help any further.