I build my new rig a few days ago (Specs in sig) and ran Memtest86 on it before I installed my OS. I have 32GB of ram total, and Windows 8.1 Pro 64bit. I've noticed that sometimes when I start my PC up from a cold boot Windows only sees 24 of my 32GB of RAM. I noticed this the other day when I opened up the task manager to check a few things. A simple reboot will fix the issue and Windows will see all 32GB again. Right now I am using XMP profile 1 on my MB. Any ideas? I shouldn't have to reboot my machine here and there just to get all of my RAM to show up.
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Problem with Corsair RAM being reported in Windows
- Thread starter Proxy
- Start date
drescherjm
[H]F Junkie
- Joined
- Nov 19, 2008
- Messages
- 14,941
and ran Memtest86 on it before I installed my OS
How many passes? Remember 1 pass will likely not find marginal ram at all. You need to run memtest86+ 5.XX in multithreaded mode for at least 12 hours. I have had systems fail memtest86+ after 72 hours.
How many passes? Remember 1 pass will likely not find marginal ram at all. You need to run memtest86+ 5.XX in multithreaded mode for at least 12 hours. I have had systems fail memtest86+ after 72 hours.
Okay I will do that tonight. I let it run for a single pass.
This sounds like a slam dunk reason to save time and RMA the ram set. Especially with it being Corsair - they have great customer service.
Well it definitely seems to be the XMP profile. I set it to the second one, and there has not been any odd behavior. All the tests I ran such as memtest didn't report any errors so I don't know about the RMA thing. I know that XMP profiles can be funny so I'm fairly satisfied with the answer.
Last update:
So as it turns out I was only half correct. The main source of my odd system behavior was the stupid Sleep State, or hybrid sleep in W8 which is enabled by default. For some reason the system played nicer when I enable the lower XMP profile with these settings. What gave it all away was I looked down this morning after a cold boot (or what I thought was a cold boot) and notice the code on my MB was reading "40" - Then after logging into Windows my PC hard locked for about two minutes while the code was still 40.
Needless to say I looked it up in my MB manual, and was able to find out what that meant. Well hopefully it's all fixed now. I edited my power settings, and I'm gonna change my XMP profile back and see what happens. Thanks for all the input!
So as it turns out I was only half correct. The main source of my odd system behavior was the stupid Sleep State, or hybrid sleep in W8 which is enabled by default. For some reason the system played nicer when I enable the lower XMP profile with these settings. What gave it all away was I looked down this morning after a cold boot (or what I thought was a cold boot) and notice the code on my MB was reading "40" - Then after logging into Windows my PC hard locked for about two minutes while the code was still 40.
Needless to say I looked it up in my MB manual, and was able to find out what that meant. Well hopefully it's all fixed now. I edited my power settings, and I'm gonna change my XMP profile back and see what happens. Thanks for all the input!