When did computers stop checking memory on boot?Memory-limited workloadsHow did the IBM PC handle multiple physical devices serving memory at the same physical address?Why did expert systems fall?A different way to share the memory bus between the CPU and the VideoTMS9918 with shared memoryDid the PC/AT-bus use its expanded address space?IBM PC memory map - why RAM at the bottom?Protected/virtual memory support in classic AmigaOSLargest memory peripheral for Sinclair ZX81?
How to delete a game file?
Running code in a different tmux pane
Does "solicit" mean the solicitor must receive what is being solicited in context of 52 U.S. Code Section 30121?
Which of these will work? HDMI to VGA or HDMI to USB?
What was the motive for inventing Gröbner bases?
Why oil is used as lubricant in hydro, wind power generators, while water is the most available, cheapest and accessible lubricant?
What other tricks were there to get more data onto floppy disks?
Stack data structure in python 3
A new type of builder pattern
Generalize superdense encoding
Were there ever 12-, 24-, 48-, etc bit processors?
What are the minimum element requirements for a star?
Reproduce diagram relating different continuity properties
Is it possible to animate 2 folds on the same sheet?
Can a UK passport valid for two months travel to Germany post-brexit?
What does this docker log entry mean?
What is the correct way for pilots to say times?
Deny access to all PHP files using FilesMatch, but make an exception for one file
Engine sync for jet engines; vs prop sync to eliminate beats
If a photon truly goes through both slits (at the same time), then why can't we detect it at both slits (at the same time)?
Beautiful planar geometry theorems not encountered in high school
Plot Dini's surface
Leaf nodes in tikz-qtree are not aligned with parents when using grow=left
data.table linearly interpolating NA values without groups
When did computers stop checking memory on boot?
Memory-limited workloadsHow did the IBM PC handle multiple physical devices serving memory at the same physical address?Why did expert systems fall?A different way to share the memory bus between the CPU and the VideoTMS9918 with shared memoryDid the PC/AT-bus use its expanded address space?IBM PC memory map - why RAM at the bottom?Protected/virtual memory support in classic AmigaOSLargest memory peripheral for Sinclair ZX81?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible? If not, when did it stop, and why? (Imagining it might take too long with today's memory and/or not be necessary?)
history hardware memory
add a comment
|
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible? If not, when did it stop, and why? (Imagining it might take too long with today's memory and/or not be necessary?)
history hardware memory
17
POST (Power On Self Test) is still very much a thing. You may not be seeing memory checks because it's hidden on a lot of consumer PC's (...and likely set to an abbreviated/quick mode). I can assure you that memory is checked as a part of most boot operations. On modern servers it can take a fair amount of time to run through a check of hundreds of gigabytes (...or even several terabytes) of memory.
– rnxrx
Sep 7 at 3:21
I think I've already seen this question a while ago O_o
– motoDrizzt
Sep 7 at 7:46
2
@motoDrizzt POST often only checks a small bit of memory nowadays, although an option to check all the memory is usually available in BIOS settings (i.e. "fast boot").
– forest
Sep 8 at 1:00
add a comment
|
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible? If not, when did it stop, and why? (Imagining it might take too long with today's memory and/or not be necessary?)
history hardware memory
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible? If not, when did it stop, and why? (Imagining it might take too long with today's memory and/or not be necessary?)
history hardware memory
history hardware memory
asked Sep 7 at 2:33
dashnickdashnick
9006 silver badges15 bronze badges
9006 silver badges15 bronze badges
17
POST (Power On Self Test) is still very much a thing. You may not be seeing memory checks because it's hidden on a lot of consumer PC's (...and likely set to an abbreviated/quick mode). I can assure you that memory is checked as a part of most boot operations. On modern servers it can take a fair amount of time to run through a check of hundreds of gigabytes (...or even several terabytes) of memory.
– rnxrx
Sep 7 at 3:21
I think I've already seen this question a while ago O_o
– motoDrizzt
Sep 7 at 7:46
2
@motoDrizzt POST often only checks a small bit of memory nowadays, although an option to check all the memory is usually available in BIOS settings (i.e. "fast boot").
– forest
Sep 8 at 1:00
add a comment
|
17
POST (Power On Self Test) is still very much a thing. You may not be seeing memory checks because it's hidden on a lot of consumer PC's (...and likely set to an abbreviated/quick mode). I can assure you that memory is checked as a part of most boot operations. On modern servers it can take a fair amount of time to run through a check of hundreds of gigabytes (...or even several terabytes) of memory.
– rnxrx
Sep 7 at 3:21
I think I've already seen this question a while ago O_o
– motoDrizzt
Sep 7 at 7:46
2
@motoDrizzt POST often only checks a small bit of memory nowadays, although an option to check all the memory is usually available in BIOS settings (i.e. "fast boot").
– forest
Sep 8 at 1:00
17
17
POST (Power On Self Test) is still very much a thing. You may not be seeing memory checks because it's hidden on a lot of consumer PC's (...and likely set to an abbreviated/quick mode). I can assure you that memory is checked as a part of most boot operations. On modern servers it can take a fair amount of time to run through a check of hundreds of gigabytes (...or even several terabytes) of memory.
– rnxrx
Sep 7 at 3:21
POST (Power On Self Test) is still very much a thing. You may not be seeing memory checks because it's hidden on a lot of consumer PC's (...and likely set to an abbreviated/quick mode). I can assure you that memory is checked as a part of most boot operations. On modern servers it can take a fair amount of time to run through a check of hundreds of gigabytes (...or even several terabytes) of memory.
– rnxrx
Sep 7 at 3:21
I think I've already seen this question a while ago O_o
– motoDrizzt
Sep 7 at 7:46
I think I've already seen this question a while ago O_o
– motoDrizzt
Sep 7 at 7:46
2
2
@motoDrizzt POST often only checks a small bit of memory nowadays, although an option to check all the memory is usually available in BIOS settings (i.e. "fast boot").
– forest
Sep 8 at 1:00
@motoDrizzt POST often only checks a small bit of memory nowadays, although an option to check all the memory is usually available in BIOS settings (i.e. "fast boot").
– forest
Sep 8 at 1:00
add a comment
|
4 Answers
4
active
oldest
votes
When did computers stop checking memory on boot?
Never.
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible?
Exactly. And it has been simplified and speed up as well. But more important, it's usually hidden under some manufacturer boot logo or whatsoever funny pic one installs. Check your BIOS and you should find an option to make it visible.
Imagining it might take too long with today's memory
It was already way too long back then. The original PC and its direct clones did a thruout check, way more detailed than most other contemporary (desktop) computers. A habit IBM took from their professional systems to increase reliability.
and/or not be necessary?
It still is, but nowadays, at least on consumer machines, it's reduced to a general initialization. Convenience trumps reliability. For serious usage (Servers) memory test is still a thing that will take up quite some time. After all, one wants to be sure that there is no hidden memory error crashing the machine during productive work.
Today BIOSes often offer a setup option to select no test, fast test, or full test. Or it's hidden under an subsumizing 'quick boot' option.
(Followup question as recomended by Kaz)
[W]hen did computers stop doing this comprehensive memory check on boot?
I can't tell an exact date or BIOS Version, but it has been in the end of the 1980s when RAM sizes of more than 1 MiB became standard for consumer machines. So about the time of fast 286, NEAT boards, upcomming 386 and Windows. The focus is here really the consumer segment, as boot times don't really matter on office machines (*1). About that time people became conscious about startup time and companies using it as sales argument.
*1 - Every employee likes a reason to fetch a fresh brew :))
1
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
4
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
1
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
2
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
5
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
|
show 23 more comments
The DDR4 spec actually includes a RAM tuning test, to be performed at boot time, as part of supporting today's multi-gigahertz signalling speeds on a consumer-priced motherboard.
This accounts for the several seconds that often elapses between the machine powering up and the graphics output coming alive; the GPU is only initialised after this initial RAM check is complete.
2
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
2
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
3
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
2
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
1
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
|
show 1 more comment
...It just seemed to disappear! Certainly my old 486-100 had it. I think it's no longer done, as a result of reliable RAM, and the vast amounts of RAM now fitted. This machine has 8GB, a little tight by modern standards. My 486 started off with 4MB, and finally ended up with I think 24MB.
Of course, RAM and CPUs have got faster since then, partly making up the difference. But that 486's RAM ran at 33MHz. For my modern machine with 2048x as much, it would need to run at 66GHz, all things being equal. This next part I was going to guess at, but let's ask Sandra... 1.6GHz RAM speed. Actually 800MHz double-data-rate. So to check the RAM now would take 40x longer than my 486 did. Not acceptable! It started to get annoying when I'd upgraded it to 8MB!
And usually, back in the day, you'd press Esc to skip the test anyway. That's why BIOSes started to add the skip option.
RAM tests don't really need doing at bootup. If it worked when it was installed, it'll almost certainly be fine now. Any RAM problems that do occur will show up soon enough one way or another. And they're so rare, it's just not worth checking.
I can't say for certain it doesn't check, say, every millionth byte just to be sure. But the old tests are no longer needed. They probably weren't even in the 486 days. The early PCs with low-density single-chip RAM, where you'd have a few dozen individual RAM chips installed on the motherboard, sometimes pressed into sockets, not soldered, were a reliability liability! But no longer. So because it's impractical and barely necessary, they dropped it at some point down the line. I haven't seen a BIOS in a long time that even mentions RAM test, and I tinker with a lot of PCs.
There you go! I even mentioned the old dozens of RAM chips, often with only 8K
(64k x 1-bit) per chip. The 4164 DRAMs. And they were the modern ones! Before about 1982, companies used the 4116's instead. You can guess the capacity!
http://www.old-computers.com/history/detail.asp?n=43&t=3
Tells me the 4164 is from October 1978. But they were very expensive for the first few years. Too expensive for the fun home computers we all love!
Early PCs really did have lots of RAM chips, when I say dozens... using the relatively large 4164s, you'd need 80 of them for the full 640K! Often you'd install a card into one of the ISA slots with 256K on it. Or two of these for 512K, plus the 64K on the motherboard (if you went for that option, not the 16K base option), would be 576K. So RAM expansion cards were a sea of little chips, and early RAM ran hot. Not enough to use heatsinks like the fusion furnaces of modern CPUs, but still hot.
Later PCs could use the 61256 chips, 256kx1, which is 32K altogether, so more RAM was less error-prone, and indeed possible to fit on a motherboard. Then eventually to SIMMs but we all know that.
[If you want a bonus factoid... Sometimes the RAM chips could climb out of the sockets by themselves! The RAM chip's pins were bent slightly outward. The connectors in the socket were springy to push themselves onto the pins.
It's thought the cause was thermal cycling, ie hot and cold through working in the day and cooling off at night. This would cause minute expansion and contraction of the metal in the chip's pins, causing them to gradually push themselves up and out of their socket. One day, something would go weird (on early IBM PC's with 9-bit parity-checking RAM, you'd get a "PARITY CHECK 2" error, the mainboard raising an interrupt to tell the processor something was wrong). You might open the case, eventually notice one of the dozens of RAM chips was gone, and perhaps find it rattling around somewhere.
Modern consumer PCs don't bother with parity. It added 1/8th to the RAM cost, and all it got you was an immediate crash to an error message you had to turn off the machine for. ECC RAM for servers is it's grandchild. It costs more, mostly because of the lower demand for it, but also because people who want reliability like that are willing to PAY for it!
Some early computers, though not IBM PCs I think, a maintenance option was to drop it onto a concrete floor from 1 metre up! Re-seated the RAM chips nicely! Wish I could remember which computer that was. Anything with a floppy drive or other mechanics would be right out. ]
Enjoy your free RAM related fact-let!
2
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
add a comment
|
Certainly not before standards for RAM enumeration (SPD serial presence detect) were introduced (with the SDRAM 168pin form factor). Earlier systems needed the memory check to established what memory was actually installed, and at which addresses (especially since there could even be discontigous configurations with some even earlier, expansion board based schemes...).
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "648"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: 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%2fretrocomputing.stackexchange.com%2fquestions%2f12258%2fwhen-did-computers-stop-checking-memory-on-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
When did computers stop checking memory on boot?
Never.
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible?
Exactly. And it has been simplified and speed up as well. But more important, it's usually hidden under some manufacturer boot logo or whatsoever funny pic one installs. Check your BIOS and you should find an option to make it visible.
Imagining it might take too long with today's memory
It was already way too long back then. The original PC and its direct clones did a thruout check, way more detailed than most other contemporary (desktop) computers. A habit IBM took from their professional systems to increase reliability.
and/or not be necessary?
It still is, but nowadays, at least on consumer machines, it's reduced to a general initialization. Convenience trumps reliability. For serious usage (Servers) memory test is still a thing that will take up quite some time. After all, one wants to be sure that there is no hidden memory error crashing the machine during productive work.
Today BIOSes often offer a setup option to select no test, fast test, or full test. Or it's hidden under an subsumizing 'quick boot' option.
(Followup question as recomended by Kaz)
[W]hen did computers stop doing this comprehensive memory check on boot?
I can't tell an exact date or BIOS Version, but it has been in the end of the 1980s when RAM sizes of more than 1 MiB became standard for consumer machines. So about the time of fast 286, NEAT boards, upcomming 386 and Windows. The focus is here really the consumer segment, as boot times don't really matter on office machines (*1). About that time people became conscious about startup time and companies using it as sales argument.
*1 - Every employee likes a reason to fetch a fresh brew :))
1
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
4
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
1
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
2
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
5
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
|
show 23 more comments
When did computers stop checking memory on boot?
Never.
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible?
Exactly. And it has been simplified and speed up as well. But more important, it's usually hidden under some manufacturer boot logo or whatsoever funny pic one installs. Check your BIOS and you should find an option to make it visible.
Imagining it might take too long with today's memory
It was already way too long back then. The original PC and its direct clones did a thruout check, way more detailed than most other contemporary (desktop) computers. A habit IBM took from their professional systems to increase reliability.
and/or not be necessary?
It still is, but nowadays, at least on consumer machines, it's reduced to a general initialization. Convenience trumps reliability. For serious usage (Servers) memory test is still a thing that will take up quite some time. After all, one wants to be sure that there is no hidden memory error crashing the machine during productive work.
Today BIOSes often offer a setup option to select no test, fast test, or full test. Or it's hidden under an subsumizing 'quick boot' option.
(Followup question as recomended by Kaz)
[W]hen did computers stop doing this comprehensive memory check on boot?
I can't tell an exact date or BIOS Version, but it has been in the end of the 1980s when RAM sizes of more than 1 MiB became standard for consumer machines. So about the time of fast 286, NEAT boards, upcomming 386 and Windows. The focus is here really the consumer segment, as boot times don't really matter on office machines (*1). About that time people became conscious about startup time and companies using it as sales argument.
*1 - Every employee likes a reason to fetch a fresh brew :))
1
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
4
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
1
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
2
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
5
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
|
show 23 more comments
When did computers stop checking memory on boot?
Never.
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible?
Exactly. And it has been simplified and speed up as well. But more important, it's usually hidden under some manufacturer boot logo or whatsoever funny pic one installs. Check your BIOS and you should find an option to make it visible.
Imagining it might take too long with today's memory
It was already way too long back then. The original PC and its direct clones did a thruout check, way more detailed than most other contemporary (desktop) computers. A habit IBM took from their professional systems to increase reliability.
and/or not be necessary?
It still is, but nowadays, at least on consumer machines, it's reduced to a general initialization. Convenience trumps reliability. For serious usage (Servers) memory test is still a thing that will take up quite some time. After all, one wants to be sure that there is no hidden memory error crashing the machine during productive work.
Today BIOSes often offer a setup option to select no test, fast test, or full test. Or it's hidden under an subsumizing 'quick boot' option.
(Followup question as recomended by Kaz)
[W]hen did computers stop doing this comprehensive memory check on boot?
I can't tell an exact date or BIOS Version, but it has been in the end of the 1980s when RAM sizes of more than 1 MiB became standard for consumer machines. So about the time of fast 286, NEAT boards, upcomming 386 and Windows. The focus is here really the consumer segment, as boot times don't really matter on office machines (*1). About that time people became conscious about startup time and companies using it as sales argument.
*1 - Every employee likes a reason to fetch a fresh brew :))
When did computers stop checking memory on boot?
Never.
I remember my old 8088 used to do this (640K OK) but can't remember seeing anything like this since. Does this still happen and it's just not visible?
Exactly. And it has been simplified and speed up as well. But more important, it's usually hidden under some manufacturer boot logo or whatsoever funny pic one installs. Check your BIOS and you should find an option to make it visible.
Imagining it might take too long with today's memory
It was already way too long back then. The original PC and its direct clones did a thruout check, way more detailed than most other contemporary (desktop) computers. A habit IBM took from their professional systems to increase reliability.
and/or not be necessary?
It still is, but nowadays, at least on consumer machines, it's reduced to a general initialization. Convenience trumps reliability. For serious usage (Servers) memory test is still a thing that will take up quite some time. After all, one wants to be sure that there is no hidden memory error crashing the machine during productive work.
Today BIOSes often offer a setup option to select no test, fast test, or full test. Or it's hidden under an subsumizing 'quick boot' option.
(Followup question as recomended by Kaz)
[W]hen did computers stop doing this comprehensive memory check on boot?
I can't tell an exact date or BIOS Version, but it has been in the end of the 1980s when RAM sizes of more than 1 MiB became standard for consumer machines. So about the time of fast 286, NEAT boards, upcomming 386 and Windows. The focus is here really the consumer segment, as boot times don't really matter on office machines (*1). About that time people became conscious about startup time and companies using it as sales argument.
*1 - Every employee likes a reason to fetch a fresh brew :))
edited Sep 9 at 19:37
answered Sep 7 at 3:52
RaffzahnRaffzahn
75.5k9 gold badges189 silver badges315 bronze badges
75.5k9 gold badges189 silver badges315 bronze badges
1
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
4
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
1
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
2
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
5
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
|
show 23 more comments
1
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
4
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
1
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
2
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
5
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
1
1
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
It may be worth considering the implied follow-up question, which would be "when did computers stop doing this comprehensive memory check on boot?"
– Kaz
Sep 7 at 7:18
4
4
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
Many modern BIOSes have an option to select how thorough a memory check to perform. The ones I typically see offer three options, with names along the lines of "none", "quick" (usually the default), and "thorough".
– John Bollinger
Sep 7 at 12:29
1
1
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
If memory serves, the Mac Plus does a full memory test from a cold boot even if upgraded to a full 4mb. Which is indeed a very tedious thing to sit through.
– Tommy
Sep 7 at 15:20
2
2
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
It is worth noting that machines with ECC almost always do a full memory test at boot. As the memory devices power up with unknown data, the ECC syndrome bits will not be valid (well, perhaps in a few locations they might be) so a full write and readback of every memory location sets the syndrome bits correctly. There are other methods but they can be complex compared to just doing a full memory write / read at startup. ECC checking is turned on after the test so it won't throw errors during the test.
– Peter Smith
Sep 8 at 10:36
5
5
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
@RonJohn Nop, it has been mostly removed. Just think, memory hasn't gotten much faster since the 1990s. Access time for DDR4-4000+ is still about 8ns. That's barley double the speed of 2000s SDRAM - but RAM size for average PC has more than 20 fold over the last 20 years. Still boot times have decreased a lot. The only way to reach this is by no longer testing, but barely initializing RAM As with only serial writing all modern performance miracles do kick in.
– Raffzahn
Sep 8 at 13:07
|
show 23 more comments
The DDR4 spec actually includes a RAM tuning test, to be performed at boot time, as part of supporting today's multi-gigahertz signalling speeds on a consumer-priced motherboard.
This accounts for the several seconds that often elapses between the machine powering up and the graphics output coming alive; the GPU is only initialised after this initial RAM check is complete.
2
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
2
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
3
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
2
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
1
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
|
show 1 more comment
The DDR4 spec actually includes a RAM tuning test, to be performed at boot time, as part of supporting today's multi-gigahertz signalling speeds on a consumer-priced motherboard.
This accounts for the several seconds that often elapses between the machine powering up and the graphics output coming alive; the GPU is only initialised after this initial RAM check is complete.
2
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
2
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
3
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
2
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
1
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
|
show 1 more comment
The DDR4 spec actually includes a RAM tuning test, to be performed at boot time, as part of supporting today's multi-gigahertz signalling speeds on a consumer-priced motherboard.
This accounts for the several seconds that often elapses between the machine powering up and the graphics output coming alive; the GPU is only initialised after this initial RAM check is complete.
The DDR4 spec actually includes a RAM tuning test, to be performed at boot time, as part of supporting today's multi-gigahertz signalling speeds on a consumer-priced motherboard.
This accounts for the several seconds that often elapses between the machine powering up and the graphics output coming alive; the GPU is only initialised after this initial RAM check is complete.
answered Sep 7 at 18:21
ChromatixChromatix
2,38811 silver badges14 bronze badges
2,38811 silver badges14 bronze badges
2
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
2
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
3
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
2
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
1
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
|
show 1 more comment
2
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
2
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
3
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
2
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
1
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
2
2
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
Given that many graphics cards use rather complicated FPGA or similar devices which generally have some on-chip RAM, I wonder if there would be any difficulty having a display card power on in a diagnostic mode which could use a small amount of internal RAM to show a text screen showing the status of those initial tests?
– supercat
Sep 7 at 19:00
2
2
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
AFAIK, most modern GPUs have at least one built-in microcontroller (often an ARM Cortex-M0 which is truly minuscule) which is effectively in charge of the GPU's boot process, as well as subsequently interpreting legacy VGA register settings and raw framebuffer writes into a form suitable for the modern hardware. But this is not even triggered by the PC BIOS until the RAM test is complete.
– Chromatix
Sep 7 at 21:24
3
3
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
Unless things have changed a lot since I last looked at PC architectures, graphics cards receive power as soon as the motherboard is powered up, before the CPU has had a chance to do anything. I don't know at what point a graphics card would see anything meaningful on the bus (e.g. I have no idea if a BIOS would still output POST codes) but I wouldn't think anything would prevent a card from generating a basic screen on its own initiative. Even if the card couldn't receive any info about what to display, having a screen which shows the card is connected and has power would be helpful.
– supercat
Sep 7 at 21:31
2
2
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
I think that @supercat 's idea is great; even if the PCI bus never comes alive beyond power and there's no communication from the rest of the computer, having your graphics card able to tell you that already usefully narrows the area to be debugged.
– Curt J. Sampson
Sep 8 at 2:28
1
1
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
@CurtJ.Sampson: Among other things, if one doesn't have a physical hard drive to make noise, the symptoms of a dead motherboard might be indistinguishable from those of a disconnected display cable. But if the graphics hardware shows an image, that could be ruled out.
– supercat
Sep 8 at 18:13
|
show 1 more comment
...It just seemed to disappear! Certainly my old 486-100 had it. I think it's no longer done, as a result of reliable RAM, and the vast amounts of RAM now fitted. This machine has 8GB, a little tight by modern standards. My 486 started off with 4MB, and finally ended up with I think 24MB.
Of course, RAM and CPUs have got faster since then, partly making up the difference. But that 486's RAM ran at 33MHz. For my modern machine with 2048x as much, it would need to run at 66GHz, all things being equal. This next part I was going to guess at, but let's ask Sandra... 1.6GHz RAM speed. Actually 800MHz double-data-rate. So to check the RAM now would take 40x longer than my 486 did. Not acceptable! It started to get annoying when I'd upgraded it to 8MB!
And usually, back in the day, you'd press Esc to skip the test anyway. That's why BIOSes started to add the skip option.
RAM tests don't really need doing at bootup. If it worked when it was installed, it'll almost certainly be fine now. Any RAM problems that do occur will show up soon enough one way or another. And they're so rare, it's just not worth checking.
I can't say for certain it doesn't check, say, every millionth byte just to be sure. But the old tests are no longer needed. They probably weren't even in the 486 days. The early PCs with low-density single-chip RAM, where you'd have a few dozen individual RAM chips installed on the motherboard, sometimes pressed into sockets, not soldered, were a reliability liability! But no longer. So because it's impractical and barely necessary, they dropped it at some point down the line. I haven't seen a BIOS in a long time that even mentions RAM test, and I tinker with a lot of PCs.
There you go! I even mentioned the old dozens of RAM chips, often with only 8K
(64k x 1-bit) per chip. The 4164 DRAMs. And they were the modern ones! Before about 1982, companies used the 4116's instead. You can guess the capacity!
http://www.old-computers.com/history/detail.asp?n=43&t=3
Tells me the 4164 is from October 1978. But they were very expensive for the first few years. Too expensive for the fun home computers we all love!
Early PCs really did have lots of RAM chips, when I say dozens... using the relatively large 4164s, you'd need 80 of them for the full 640K! Often you'd install a card into one of the ISA slots with 256K on it. Or two of these for 512K, plus the 64K on the motherboard (if you went for that option, not the 16K base option), would be 576K. So RAM expansion cards were a sea of little chips, and early RAM ran hot. Not enough to use heatsinks like the fusion furnaces of modern CPUs, but still hot.
Later PCs could use the 61256 chips, 256kx1, which is 32K altogether, so more RAM was less error-prone, and indeed possible to fit on a motherboard. Then eventually to SIMMs but we all know that.
[If you want a bonus factoid... Sometimes the RAM chips could climb out of the sockets by themselves! The RAM chip's pins were bent slightly outward. The connectors in the socket were springy to push themselves onto the pins.
It's thought the cause was thermal cycling, ie hot and cold through working in the day and cooling off at night. This would cause minute expansion and contraction of the metal in the chip's pins, causing them to gradually push themselves up and out of their socket. One day, something would go weird (on early IBM PC's with 9-bit parity-checking RAM, you'd get a "PARITY CHECK 2" error, the mainboard raising an interrupt to tell the processor something was wrong). You might open the case, eventually notice one of the dozens of RAM chips was gone, and perhaps find it rattling around somewhere.
Modern consumer PCs don't bother with parity. It added 1/8th to the RAM cost, and all it got you was an immediate crash to an error message you had to turn off the machine for. ECC RAM for servers is it's grandchild. It costs more, mostly because of the lower demand for it, but also because people who want reliability like that are willing to PAY for it!
Some early computers, though not IBM PCs I think, a maintenance option was to drop it onto a concrete floor from 1 metre up! Re-seated the RAM chips nicely! Wish I could remember which computer that was. Anything with a floppy drive or other mechanics would be right out. ]
Enjoy your free RAM related fact-let!
2
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
add a comment
|
...It just seemed to disappear! Certainly my old 486-100 had it. I think it's no longer done, as a result of reliable RAM, and the vast amounts of RAM now fitted. This machine has 8GB, a little tight by modern standards. My 486 started off with 4MB, and finally ended up with I think 24MB.
Of course, RAM and CPUs have got faster since then, partly making up the difference. But that 486's RAM ran at 33MHz. For my modern machine with 2048x as much, it would need to run at 66GHz, all things being equal. This next part I was going to guess at, but let's ask Sandra... 1.6GHz RAM speed. Actually 800MHz double-data-rate. So to check the RAM now would take 40x longer than my 486 did. Not acceptable! It started to get annoying when I'd upgraded it to 8MB!
And usually, back in the day, you'd press Esc to skip the test anyway. That's why BIOSes started to add the skip option.
RAM tests don't really need doing at bootup. If it worked when it was installed, it'll almost certainly be fine now. Any RAM problems that do occur will show up soon enough one way or another. And they're so rare, it's just not worth checking.
I can't say for certain it doesn't check, say, every millionth byte just to be sure. But the old tests are no longer needed. They probably weren't even in the 486 days. The early PCs with low-density single-chip RAM, where you'd have a few dozen individual RAM chips installed on the motherboard, sometimes pressed into sockets, not soldered, were a reliability liability! But no longer. So because it's impractical and barely necessary, they dropped it at some point down the line. I haven't seen a BIOS in a long time that even mentions RAM test, and I tinker with a lot of PCs.
There you go! I even mentioned the old dozens of RAM chips, often with only 8K
(64k x 1-bit) per chip. The 4164 DRAMs. And they were the modern ones! Before about 1982, companies used the 4116's instead. You can guess the capacity!
http://www.old-computers.com/history/detail.asp?n=43&t=3
Tells me the 4164 is from October 1978. But they were very expensive for the first few years. Too expensive for the fun home computers we all love!
Early PCs really did have lots of RAM chips, when I say dozens... using the relatively large 4164s, you'd need 80 of them for the full 640K! Often you'd install a card into one of the ISA slots with 256K on it. Or two of these for 512K, plus the 64K on the motherboard (if you went for that option, not the 16K base option), would be 576K. So RAM expansion cards were a sea of little chips, and early RAM ran hot. Not enough to use heatsinks like the fusion furnaces of modern CPUs, but still hot.
Later PCs could use the 61256 chips, 256kx1, which is 32K altogether, so more RAM was less error-prone, and indeed possible to fit on a motherboard. Then eventually to SIMMs but we all know that.
[If you want a bonus factoid... Sometimes the RAM chips could climb out of the sockets by themselves! The RAM chip's pins were bent slightly outward. The connectors in the socket were springy to push themselves onto the pins.
It's thought the cause was thermal cycling, ie hot and cold through working in the day and cooling off at night. This would cause minute expansion and contraction of the metal in the chip's pins, causing them to gradually push themselves up and out of their socket. One day, something would go weird (on early IBM PC's with 9-bit parity-checking RAM, you'd get a "PARITY CHECK 2" error, the mainboard raising an interrupt to tell the processor something was wrong). You might open the case, eventually notice one of the dozens of RAM chips was gone, and perhaps find it rattling around somewhere.
Modern consumer PCs don't bother with parity. It added 1/8th to the RAM cost, and all it got you was an immediate crash to an error message you had to turn off the machine for. ECC RAM for servers is it's grandchild. It costs more, mostly because of the lower demand for it, but also because people who want reliability like that are willing to PAY for it!
Some early computers, though not IBM PCs I think, a maintenance option was to drop it onto a concrete floor from 1 metre up! Re-seated the RAM chips nicely! Wish I could remember which computer that was. Anything with a floppy drive or other mechanics would be right out. ]
Enjoy your free RAM related fact-let!
2
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
add a comment
|
...It just seemed to disappear! Certainly my old 486-100 had it. I think it's no longer done, as a result of reliable RAM, and the vast amounts of RAM now fitted. This machine has 8GB, a little tight by modern standards. My 486 started off with 4MB, and finally ended up with I think 24MB.
Of course, RAM and CPUs have got faster since then, partly making up the difference. But that 486's RAM ran at 33MHz. For my modern machine with 2048x as much, it would need to run at 66GHz, all things being equal. This next part I was going to guess at, but let's ask Sandra... 1.6GHz RAM speed. Actually 800MHz double-data-rate. So to check the RAM now would take 40x longer than my 486 did. Not acceptable! It started to get annoying when I'd upgraded it to 8MB!
And usually, back in the day, you'd press Esc to skip the test anyway. That's why BIOSes started to add the skip option.
RAM tests don't really need doing at bootup. If it worked when it was installed, it'll almost certainly be fine now. Any RAM problems that do occur will show up soon enough one way or another. And they're so rare, it's just not worth checking.
I can't say for certain it doesn't check, say, every millionth byte just to be sure. But the old tests are no longer needed. They probably weren't even in the 486 days. The early PCs with low-density single-chip RAM, where you'd have a few dozen individual RAM chips installed on the motherboard, sometimes pressed into sockets, not soldered, were a reliability liability! But no longer. So because it's impractical and barely necessary, they dropped it at some point down the line. I haven't seen a BIOS in a long time that even mentions RAM test, and I tinker with a lot of PCs.
There you go! I even mentioned the old dozens of RAM chips, often with only 8K
(64k x 1-bit) per chip. The 4164 DRAMs. And they were the modern ones! Before about 1982, companies used the 4116's instead. You can guess the capacity!
http://www.old-computers.com/history/detail.asp?n=43&t=3
Tells me the 4164 is from October 1978. But they were very expensive for the first few years. Too expensive for the fun home computers we all love!
Early PCs really did have lots of RAM chips, when I say dozens... using the relatively large 4164s, you'd need 80 of them for the full 640K! Often you'd install a card into one of the ISA slots with 256K on it. Or two of these for 512K, plus the 64K on the motherboard (if you went for that option, not the 16K base option), would be 576K. So RAM expansion cards were a sea of little chips, and early RAM ran hot. Not enough to use heatsinks like the fusion furnaces of modern CPUs, but still hot.
Later PCs could use the 61256 chips, 256kx1, which is 32K altogether, so more RAM was less error-prone, and indeed possible to fit on a motherboard. Then eventually to SIMMs but we all know that.
[If you want a bonus factoid... Sometimes the RAM chips could climb out of the sockets by themselves! The RAM chip's pins were bent slightly outward. The connectors in the socket were springy to push themselves onto the pins.
It's thought the cause was thermal cycling, ie hot and cold through working in the day and cooling off at night. This would cause minute expansion and contraction of the metal in the chip's pins, causing them to gradually push themselves up and out of their socket. One day, something would go weird (on early IBM PC's with 9-bit parity-checking RAM, you'd get a "PARITY CHECK 2" error, the mainboard raising an interrupt to tell the processor something was wrong). You might open the case, eventually notice one of the dozens of RAM chips was gone, and perhaps find it rattling around somewhere.
Modern consumer PCs don't bother with parity. It added 1/8th to the RAM cost, and all it got you was an immediate crash to an error message you had to turn off the machine for. ECC RAM for servers is it's grandchild. It costs more, mostly because of the lower demand for it, but also because people who want reliability like that are willing to PAY for it!
Some early computers, though not IBM PCs I think, a maintenance option was to drop it onto a concrete floor from 1 metre up! Re-seated the RAM chips nicely! Wish I could remember which computer that was. Anything with a floppy drive or other mechanics would be right out. ]
Enjoy your free RAM related fact-let!
...It just seemed to disappear! Certainly my old 486-100 had it. I think it's no longer done, as a result of reliable RAM, and the vast amounts of RAM now fitted. This machine has 8GB, a little tight by modern standards. My 486 started off with 4MB, and finally ended up with I think 24MB.
Of course, RAM and CPUs have got faster since then, partly making up the difference. But that 486's RAM ran at 33MHz. For my modern machine with 2048x as much, it would need to run at 66GHz, all things being equal. This next part I was going to guess at, but let's ask Sandra... 1.6GHz RAM speed. Actually 800MHz double-data-rate. So to check the RAM now would take 40x longer than my 486 did. Not acceptable! It started to get annoying when I'd upgraded it to 8MB!
And usually, back in the day, you'd press Esc to skip the test anyway. That's why BIOSes started to add the skip option.
RAM tests don't really need doing at bootup. If it worked when it was installed, it'll almost certainly be fine now. Any RAM problems that do occur will show up soon enough one way or another. And they're so rare, it's just not worth checking.
I can't say for certain it doesn't check, say, every millionth byte just to be sure. But the old tests are no longer needed. They probably weren't even in the 486 days. The early PCs with low-density single-chip RAM, where you'd have a few dozen individual RAM chips installed on the motherboard, sometimes pressed into sockets, not soldered, were a reliability liability! But no longer. So because it's impractical and barely necessary, they dropped it at some point down the line. I haven't seen a BIOS in a long time that even mentions RAM test, and I tinker with a lot of PCs.
There you go! I even mentioned the old dozens of RAM chips, often with only 8K
(64k x 1-bit) per chip. The 4164 DRAMs. And they were the modern ones! Before about 1982, companies used the 4116's instead. You can guess the capacity!
http://www.old-computers.com/history/detail.asp?n=43&t=3
Tells me the 4164 is from October 1978. But they were very expensive for the first few years. Too expensive for the fun home computers we all love!
Early PCs really did have lots of RAM chips, when I say dozens... using the relatively large 4164s, you'd need 80 of them for the full 640K! Often you'd install a card into one of the ISA slots with 256K on it. Or two of these for 512K, plus the 64K on the motherboard (if you went for that option, not the 16K base option), would be 576K. So RAM expansion cards were a sea of little chips, and early RAM ran hot. Not enough to use heatsinks like the fusion furnaces of modern CPUs, but still hot.
Later PCs could use the 61256 chips, 256kx1, which is 32K altogether, so more RAM was less error-prone, and indeed possible to fit on a motherboard. Then eventually to SIMMs but we all know that.
[If you want a bonus factoid... Sometimes the RAM chips could climb out of the sockets by themselves! The RAM chip's pins were bent slightly outward. The connectors in the socket were springy to push themselves onto the pins.
It's thought the cause was thermal cycling, ie hot and cold through working in the day and cooling off at night. This would cause minute expansion and contraction of the metal in the chip's pins, causing them to gradually push themselves up and out of their socket. One day, something would go weird (on early IBM PC's with 9-bit parity-checking RAM, you'd get a "PARITY CHECK 2" error, the mainboard raising an interrupt to tell the processor something was wrong). You might open the case, eventually notice one of the dozens of RAM chips was gone, and perhaps find it rattling around somewhere.
Modern consumer PCs don't bother with parity. It added 1/8th to the RAM cost, and all it got you was an immediate crash to an error message you had to turn off the machine for. ECC RAM for servers is it's grandchild. It costs more, mostly because of the lower demand for it, but also because people who want reliability like that are willing to PAY for it!
Some early computers, though not IBM PCs I think, a maintenance option was to drop it onto a concrete floor from 1 metre up! Re-seated the RAM chips nicely! Wish I could remember which computer that was. Anything with a floppy drive or other mechanics would be right out. ]
Enjoy your free RAM related fact-let!
edited Sep 8 at 20:03
answered Sep 8 at 19:32
GreenaumGreenaum
2705 bronze badges
2705 bronze badges
2
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
add a comment
|
2
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
2
2
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
I believe you are trying to think of the Apple III techjunkie.com/apple-iii-drop
– stephan.com
Sep 9 at 16:11
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
4116 do not have a reputation of being all too bulletproof on their own...
– rackandboneman
Sep 11 at 9:58
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
Oh sure! The implication I was going for was that having 4x as many chips just in itself is going to increase problems. Probably by more than 4x, some sort of complexity theory. That's besides the shitty 4116s needing +5V, +12V, and -5V. The reason why, I imagine being to do with the easiest way to do things on early NMOS etc processes, using multiple voltages so stuff could be biased relative to other stuff. 4164s only need 5V, so run a lot cooler too. Overheating was another common 4116 catastrophe!
– Greenaum
Sep 15 at 0:09
add a comment
|
Certainly not before standards for RAM enumeration (SPD serial presence detect) were introduced (with the SDRAM 168pin form factor). Earlier systems needed the memory check to established what memory was actually installed, and at which addresses (especially since there could even be discontigous configurations with some even earlier, expansion board based schemes...).
add a comment
|
Certainly not before standards for RAM enumeration (SPD serial presence detect) were introduced (with the SDRAM 168pin form factor). Earlier systems needed the memory check to established what memory was actually installed, and at which addresses (especially since there could even be discontigous configurations with some even earlier, expansion board based schemes...).
add a comment
|
Certainly not before standards for RAM enumeration (SPD serial presence detect) were introduced (with the SDRAM 168pin form factor). Earlier systems needed the memory check to established what memory was actually installed, and at which addresses (especially since there could even be discontigous configurations with some even earlier, expansion board based schemes...).
Certainly not before standards for RAM enumeration (SPD serial presence detect) were introduced (with the SDRAM 168pin form factor). Earlier systems needed the memory check to established what memory was actually installed, and at which addresses (especially since there could even be discontigous configurations with some even earlier, expansion board based schemes...).
answered Sep 9 at 10:59
rackandbonemanrackandboneman
4,09010 silver badges17 bronze badges
4,09010 silver badges17 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Retrocomputing Stack Exchange!
- 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%2fretrocomputing.stackexchange.com%2fquestions%2f12258%2fwhen-did-computers-stop-checking-memory-on-boot%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
17
POST (Power On Self Test) is still very much a thing. You may not be seeing memory checks because it's hidden on a lot of consumer PC's (...and likely set to an abbreviated/quick mode). I can assure you that memory is checked as a part of most boot operations. On modern servers it can take a fair amount of time to run through a check of hundreds of gigabytes (...or even several terabytes) of memory.
– rnxrx
Sep 7 at 3:21
I think I've already seen this question a while ago O_o
– motoDrizzt
Sep 7 at 7:46
2
@motoDrizzt POST often only checks a small bit of memory nowadays, although an option to check all the memory is usually available in BIOS settings (i.e. "fast boot").
– forest
Sep 8 at 1:00