Nothing that you posted indicates that the Windows 7 memory diagnostics claims that the memory has problems... and there was no need (but no harm) in starting that diag tool from the command prompt.
Please help me out here: Where did you get the impression that Windows thinks that there is a problem with your RAM? As mentioned in post #6: "What do failed updates have to do with memory?"
Doesn`t really matter how you run it.
But what were the results of the test ?
What error is it giving you after windows restarts ?
I thought everything was fine with the Kingston set ?
I`m lost too
I think that the OP interpreted the offer to...
"Check your computer for memory problems"
...as an declaration that problems had already been found.
I do not think that the OP ever ran the test...
...probably just canceled the dialog box and made the post.
:-(
There was no errors in Event viewer MemoryDiagnostics after restart.
What makes me think that there is memory problem is that I did 7-8 clean installs of W7 SP1 OEM with Crucial memory and always Windows upadate failed with error Code 80244019 (Windows could not search for updates. An error occurred while checking for new updates.)
Googled a lot in meantime trying to figure out reason and tried a lot of fixes which didn't work.
So I had a new PC which doesn't run Windows 7 and according to Memetest86+ without memory errors.
Despite of having tested memory several times (more the 8 passes) without any flaws found I finally still decided to obtain Kingston for fun. (because update error Code 80244019 often is hardware failure.)
To my surprise problem vanished with Kingston and to be sure I did 3-4 clean installs to m2s, SSD, HDD SATA - no problem. PC is in best possible condition.
I swapped back Crucial memory and did 3-4 fresh W7 installs for testing and again always there was a problem with updates.
So it's just likelyhood by success failure rates in numbers using different memories.
Crucial always failed and Kingston was fine during updates (and also later for several days until decided to start testing Crucial again for curiosity. Total number of tests 15 perhaps.
Any ideas what is the problem if not memory and how to troubleshoot if Memtest86+ doesn't help?
Last edited by robilong; 27 Jan 2016 at 11:25.
Thanks for taking the time to restate the issue. My apologies for not understanding earlier. All of the info is there in the OP - I just was not understanding it.
I wonder what Crucial would say about your findings. Don't they have a lifetime warranty?
Well I imagine 1. there might be some (few) mem addresses, which are reserved by BIOS and any Memtest can't access these.
2. Something special how Windows handles DDR4 memory reads and writes, which perhaps is not supported by Memtest86+.
There are perhaps also other scenarios which I hope someone with more knowledge can figure out.
But still there remains a unanswered question, how accurate is Memtest86+?
Perhaps DDR4 is out of scope?
Memory is under warranty but if RMA tests memory using Memtest86+ it is not considered faulty
Let us know if you talk to Crucial about this. It would be nice to know what they consider a definitive test.
Quote