RAM serial number
Should you be able to read the serial number of the RAM in your BIOS if the manufacturer has included a section for it? I have an ASUS Prime Z270-K mother board and have nothing but zeros listed under the serial number for my RAM. Wondering if this is normal.
memory bios
add a comment |
Should you be able to read the serial number of the RAM in your BIOS if the manufacturer has included a section for it? I have an ASUS Prime Z270-K mother board and have nothing but zeros listed under the serial number for my RAM. Wondering if this is normal.
memory bios
add a comment |
Should you be able to read the serial number of the RAM in your BIOS if the manufacturer has included a section for it? I have an ASUS Prime Z270-K mother board and have nothing but zeros listed under the serial number for my RAM. Wondering if this is normal.
memory bios
Should you be able to read the serial number of the RAM in your BIOS if the manufacturer has included a section for it? I have an ASUS Prime Z270-K mother board and have nothing but zeros listed under the serial number for my RAM. Wondering if this is normal.
memory bios
memory bios
asked Feb 2 at 11:04
blackpineblackpine
125
125
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
For this feature to work, all three of the below prerequisites are needed:
- The mainboard (all the way from the DIMM sockets to the software) must support it
- The DIMMs themselves must support it
- The implementation in the DIMMs must be compatible with the implementation in the mainboard
In your case, it seems like the first point is to be answered with yes, but we do not know about the latter two. You could try to find out whether other DIMMs show a serial number.
This is in any case just an inconvenience, not a problem: if your RAM works fine (e.g. according to memtest86 or Windows RAM diagnosis) you have no reliability problem.
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
1
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
add a comment |
As addition to the first answer:
You could try to get the RAM info from within the OS.
If you're on Windows try wmic and memorychip through the Commandline.
Or use a Live Boot System like SystemRescueCd or other variation of Linux, and boot into it.
Use a GUI Tool like lshwgtk or bash commands to get the informations e.g.
cat /proc/meminfo
or
sudo dmidecode --type 17 | more
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401291%2fram-serial-number%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
For this feature to work, all three of the below prerequisites are needed:
- The mainboard (all the way from the DIMM sockets to the software) must support it
- The DIMMs themselves must support it
- The implementation in the DIMMs must be compatible with the implementation in the mainboard
In your case, it seems like the first point is to be answered with yes, but we do not know about the latter two. You could try to find out whether other DIMMs show a serial number.
This is in any case just an inconvenience, not a problem: if your RAM works fine (e.g. according to memtest86 or Windows RAM diagnosis) you have no reliability problem.
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
1
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
add a comment |
For this feature to work, all three of the below prerequisites are needed:
- The mainboard (all the way from the DIMM sockets to the software) must support it
- The DIMMs themselves must support it
- The implementation in the DIMMs must be compatible with the implementation in the mainboard
In your case, it seems like the first point is to be answered with yes, but we do not know about the latter two. You could try to find out whether other DIMMs show a serial number.
This is in any case just an inconvenience, not a problem: if your RAM works fine (e.g. according to memtest86 or Windows RAM diagnosis) you have no reliability problem.
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
1
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
add a comment |
For this feature to work, all three of the below prerequisites are needed:
- The mainboard (all the way from the DIMM sockets to the software) must support it
- The DIMMs themselves must support it
- The implementation in the DIMMs must be compatible with the implementation in the mainboard
In your case, it seems like the first point is to be answered with yes, but we do not know about the latter two. You could try to find out whether other DIMMs show a serial number.
This is in any case just an inconvenience, not a problem: if your RAM works fine (e.g. according to memtest86 or Windows RAM diagnosis) you have no reliability problem.
For this feature to work, all three of the below prerequisites are needed:
- The mainboard (all the way from the DIMM sockets to the software) must support it
- The DIMMs themselves must support it
- The implementation in the DIMMs must be compatible with the implementation in the mainboard
In your case, it seems like the first point is to be answered with yes, but we do not know about the latter two. You could try to find out whether other DIMMs show a serial number.
This is in any case just an inconvenience, not a problem: if your RAM works fine (e.g. according to memtest86 or Windows RAM diagnosis) you have no reliability problem.
edited Feb 2 at 17:43
Lightness Races in Orbit
2,81411527
2,81411527
answered Feb 2 at 11:12
Eugen RieckEugen Rieck
11.2k22429
11.2k22429
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
1
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
add a comment |
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
1
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
Yes, this is just for my understanding. The RAM works fine. All DIMMs show a string of 0's for the S/N, so maybe the RAM is the incompatible link.
– blackpine
Feb 2 at 11:15
1
1
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
There's another possibility you've overlooked: the serial number in the SPD chip on the DIMM really is all zeroes, and the computer is reporting that correctly.
– duskwuff
Feb 2 at 20:52
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
@duskwuff Which would IMHO be Nr.2 - the DIMMs not supporting it
– Eugen Rieck
Feb 2 at 21:02
add a comment |
As addition to the first answer:
You could try to get the RAM info from within the OS.
If you're on Windows try wmic and memorychip through the Commandline.
Or use a Live Boot System like SystemRescueCd or other variation of Linux, and boot into it.
Use a GUI Tool like lshwgtk or bash commands to get the informations e.g.
cat /proc/meminfo
or
sudo dmidecode --type 17 | more
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
add a comment |
As addition to the first answer:
You could try to get the RAM info from within the OS.
If you're on Windows try wmic and memorychip through the Commandline.
Or use a Live Boot System like SystemRescueCd or other variation of Linux, and boot into it.
Use a GUI Tool like lshwgtk or bash commands to get the informations e.g.
cat /proc/meminfo
or
sudo dmidecode --type 17 | more
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
add a comment |
As addition to the first answer:
You could try to get the RAM info from within the OS.
If you're on Windows try wmic and memorychip through the Commandline.
Or use a Live Boot System like SystemRescueCd or other variation of Linux, and boot into it.
Use a GUI Tool like lshwgtk or bash commands to get the informations e.g.
cat /proc/meminfo
or
sudo dmidecode --type 17 | more
As addition to the first answer:
You could try to get the RAM info from within the OS.
If you're on Windows try wmic and memorychip through the Commandline.
Or use a Live Boot System like SystemRescueCd or other variation of Linux, and boot into it.
Use a GUI Tool like lshwgtk or bash commands to get the informations e.g.
cat /proc/meminfo
or
sudo dmidecode --type 17 | more
answered Feb 2 at 14:15
Tech-IOTech-IO
3661414
3661414
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
add a comment |
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
wmic etc only reads information it is given though. If bios doesn't present information to the OS then the OS can't read it no matter what OS or command you use.
– lx07
Feb 2 at 17:59
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
Thank you. I don't know exactly how and from where the OS or BIOS read the Ram-Specs. But it might not be a problem with the bios-ram compatibility, perhaps checking for the right Ram version to install or a BIOS Update ?
– Tech-IO
Feb 2 at 21:56
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
The driving force of this question is due to a malware infection that I have. I am trying to narrow down any and all possibilities of where the malware is hiding, which is why I've posted another question in regards to the SPD data. My honest belief is that the serial number should be present and there may be something going on that I don't fully understand at this point, with respect to the RAM or firmware but that is only a theory.
– blackpine
Feb 3 at 7:31
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401291%2fram-serial-number%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown