This page covers the wear-out and the data loss of floating-gate flash (NOR and planar NAND) and charge-trap flash (SONOS, TANOS and 3D NAND): oxide damage and charge trapping from program/erase cycling, stress-induced leakage, retention loss including the early retention loss of 3D NAND, read disturb, cell-to-cell interference and layer-to-layer variation. The cell physics is on the Floating Gate Flash and Charge Trap Flash device pages, the oxide breakdown and trap models on the CMOS Logic Transistors page and the lifetime statistics on the Failure Rate page; controller algorithms are outside the scope of the vault and are named only where they set the device requirement.
1. Why It Happens
- Trigger: Program and erase pulses that drive Fowler-Nordheim tunnelling through the tunnel oxide (Cai et al.); storage time, especially at high temperature (Viking; Swissbit); reads of other pages in the same block (Cai et al. DSN 2015); programming of neighbouring cells (Cai et al.).
- Mechanism, wear-out: Cycling traps electrons in the tunnel oxide, which shifts and widens the threshold distributions, and at high cycle counts trapped charge forms percolation paths; the trapped charge grows about as the square root of the cycles (Cai et al.; Swissbit).
- Mechanism, retention: Stored electrons leak by trap-assisted tunnelling and stress-induced leakage current (SILC) through the damaged oxide, high states move down and the erased state moves up (Cai et al.); trapped oxide charge detraps with a logarithmic time dependence (Swissbit); in charge-trap cells charge also moves vertically to the substrate and laterally along the continuous trap layer to neighbours at different levels (Saikia and Mahapatra).
- Mechanism, disturb and interference: The pass voltage on unread word lines weakly programs their cells, the lower states most (Cai et al. DSN 2015); capacitive coupling shifts a cell when its neighbours are programmed (Cai et al.).
- What sets the rate: The number of cycles and the cycling rate, since damage partly recovers between cycles (Viking; Swissbit); the temperature, with 1.1 for detrapping but a negative activation energy for SILC (Viking); the read count and the pass voltage (Cai et al. DSN 2015); the cell size, with only about 100 electrons per 1x-nm cell (Cai et al.); the layer position in 3D NAND (Luo et al.).
- Failure criterion: A raw bit error rate beyond the ECC limit, about to , which leaves an uncorrectable rate above the target (Cai et al.); retention shorter than 10 years at below 10 per cent of the rated cycles or 1 year at the rated cycles (Viking; Swissbit).
2. Where to Look
- Location: The tunnel oxide under the storage node (Cai et al.); the gaps between cells along the bit line of 3D NAND, where lateral migration occurs (Saikia and Mahapatra); the middle and lower layers of a 3D NAND string, which have the highest error rates (Luo et al.); the most-significant-bit pages (Luo et al.).
- Signature: Threshold distributions that shift right and widen with cycling (Cai et al.); high states that move down and erased cells that move up with retention time (Cai et al.); an error rate that rises by an order of magnitude within hours after programming in 3D NAND (Luo et al.); errors that grow with the read count in the lower states (Cai et al. DSN 2015).
- Confirm with: Threshold-distribution measurements by read-voltage sweeps (Cai et al.); retention bakes for detrapping plus a 25 test for SILC after cycling (Viking); read-disturb tests with reads of a neighbouring word line (Cai et al. DSN 2015).
- Look-alikes: Early failures caused by a qualification test that cycles too fast for the oxide to recover, which does not represent use (Viking; Swissbit); program interference, which appears at programming of the neighbours rather than with time (Cai et al.); temporary early retention loss in 3D NAND, which looks like a weak block (Luo et al.).
3. Prevention
- Design: Leave ECC margin above the end-of-life raw error rate, since the codeword failure rate rises steeply near the limit (Cai et al.); use the rated retention at the rated cycles, 1 year, not the 10 years of a fresh device (Viking).
- Material and process: Reduce cell-to-cell coupling, which nearly doubled from 2y-nm to 1x-nm (Cai et al.); limit lateral migration in the continuous trap layer of 3D NAND (Saikia and Mahapatra; background knowledge).
- Operation: Keep the P/E count below the rating and store devices at room temperature or cooler (Viking); lower the pass voltage where the ECC margin allows (Cai et al. DSN 2015); adapt read voltages to retention age and layer (Luo et al.).
- Screening and test: Spread cycling in qualification so that the oxide recovers, for example by reaching the rated cycles at +85 in about 1000 rather than in a few days (Swissbit; Viking); test retention after cycling both with a bake and at 25 (Viking).
Endurance and Error Correction
| Name | Formula | Related Formulae | Variables/Constants |
|---|---|---|---|
| Endurance and charge build-up with cycling | |||
| Threshold step per stored electron | |||
| Codeword failure probability with ECC |
Retention
| Name | Formula | Related Formulae | Variables/Constants |
|---|---|---|---|
| Arrhenius acceleration of a retention bake | |||
| Early retention loss of 3D NAND | |||
| Field-assisted detrapping from the charge-trap layer |
Disturb, Interference and Layer Variation
| Name | Formula | Related Formulae | Variables/Constants |
|---|---|---|---|
| Read disturb against read count and pass voltage | |||
| Cell-to-cell program interference | |||
| Layer-to-layer variation in 3D NAND |
Important Questions
Ques: Why did flash endurance fall from 150 000 cycles to about 1000?
Because the cells shrank and store more levels. Cai et al. give about 150 000 cycles for older SLC, about 10 000 per block for 5x-nm MLC and about 3000 and 1000 for 1x-nm MLC and TLC, a 50-fold loss from SLC to 1x-nm MLC (computed). Each cycle traps electrons in the tunnel oxide, which shifts and widens the threshold distributions, and Swissbit states that the trapped charge grows about as the square root of the cycles. A 1x-nm MLC cell stores only about 100 electrons, so with an assumed 3 window each electron moves the threshold by about 30 , and a few lost or trapped charges are enough to cross a state boundary (computed). TLC packs eight states into the same window, so its margins are even smaller. Reference: Y. Cai, S. Ghose, E. F. Haratsch, Y. Luo and O. Mutlu, ‘Error Characterization, Mitigation, and Recovery in Flash-Memory-Based Solid-State Drives’, Proceedings of the IEEE (September 2017), arXiv:1706.08642v3, with the companion survey arXiv:1711.11427 (fetch-tool summaries); Swissbit, ‘NAND flash endurance testing’, Application Note AN2107en, Rev. 1.0 (2022) (fetch-tool summary).
Ques: How many hours at 85 degrees Celsius equal one year of retention, and is that consistent with ‘a few days’ at end of life?
With the 1.1 activation energy that Viking gives for detrapping, the acceleration factor to 85 is 643 from 30 and 168 from 40 , so one year of storage equals 13.6 or 52 at 85 (computed). Swissbit states that at end of life the retention at +85 is only a few days, while the JEDEC requirement quoted by both notes is one year at the rated cycles. The two agree if the one year applies at about 40 , where it equals 2.2 days at 85 (computed, my reading). The calculation holds only for detrapping, since SILC does not accelerate with temperature, so a bake alone cannot confirm the year. Reference: Viking Technology, ‘Flash Data Retention’, Application Note AN0011, Rev. B (2011, revised 2017) (fetch-tool summary); Swissbit, ‘NAND flash endurance testing’, Application Note AN2107en, Rev. 1.0 (2022) (fetch-tool summary).
Ques: Why can a high-temperature bake not prove the retention of a cycled flash cell?
Because the two charge-loss mechanisms respond to temperature in opposite ways. Viking states that bake conditions are chosen for an activation energy of 1.1 , which accelerates the detrapping of oxide charge strongly, but that stress-induced leakage current has an activation energy below 0 . SILC can therefore only be marginally accelerated, or is even reduced, at high temperature, and a cycled cell that passes a bake can still lose charge through a leaky oxide at room temperature. The qualification flow therefore adds a 25 retention test after the cycling. Cai et al. describe how trapped charge forms a path that strengthens SILC, so the leak grows with the cycle count, and the test must be done at the rated cycles, not on fresh devices. Reference: Viking Technology, ‘Flash Data Retention’, Application Note AN0011, Rev. B (2011, revised 2017) (fetch-tool summary); Y. Cai, S. Ghose, E. F. Haratsch, Y. Luo and O. Mutlu, ‘Error Characterization, Mitigation, and Recovery in Flash-Memory-Based Solid-State Drives’, Proceedings of the IEEE (September 2017), arXiv:1706.08642v3, with the companion survey arXiv:1711.11427 (fetch-tool summaries).
Ques: Does the speed of cycling during a test change the measured endurance?
Yes, and a fast test is pessimistic. Viking states that retention is inversely related to the rate of P/E cycling, because the damage partly recovers between cycles, and that a qualification that reaches the rated count in a few days builds up trapped charge that can cause failures during cycling or in the following retention test. Swissbit adds that in use the cycles are spread over at least three years, so a stress test must leave time for recovery through breaks, a lower write speed or a higher temperature. As an example it reaches the rated cycles at +85 within 1000 , and it warns against stress that reaches the specified life in only a few days. Both cite the JEDEC EEPROM and flash stress test methods. Reference: Viking Technology, ‘Flash Data Retention’, Application Note AN0011, Rev. B (2011, revised 2017) (fetch-tool summary); Swissbit, ‘NAND flash endurance testing’, Application Note AN2107en, Rev. 1.0 (2022) (fetch-tool summary).
Ques: Does the 3D NAND error rate rise tenfold in three hours, or twofold as the fitted model gives?
Luo et al. write that the retention error rate of a 3D NAND block rises by an order of magnitude within about 3 hours, and they fit to measurements from 7 minutes to 24 days. With their MSB parameters at 10 000 cycles, , the fit rises only 2.0 times from 7 minutes to 3 hours (computed). The fit reproduces the long-term level well, at 11.6 days against an average of (computed). The likely explanation is that the order of magnitude is counted from the moment after programming, before the first 7 minute point, when most of the fast detrapping happens (my reading). For refresh planning the measured statement is the more relevant one, and for later times the fit. Reference: Y. Luo, S. Ghose, Y. Cai, E. F. Haratsch and O. Mutlu, ‘Improving 3D NAND Flash Memory Lifetime by Tolerating Early Retention Loss and Process Variation’, Proc. ACM Meas. Anal. Comput. Syst. (SIGMETRICS) 2018, arXiv:1807.05140v2 (fetch-tool summary).
Ques: Is the middle layer of a 3D NAND string 21 or 6 times worse than the best layer?
Luo et al. give both numbers. Section 4.2 reports that the MSB page in the middle layer, at normalized layer 55, has 21 times the raw error rate of layer 0, while the introduction says the middle layer can be 6 times worse than the top layer. Both can be true if layer 0 is the best layer and the top layer is not, since the paper also reports that the upper half of the layers has lower error rates than the lower half (my reading). The 21 times value, from the detailed measurement against the best layer, is the more likely worst case. The variation matters because the lifetime is set by the worst page: LI-RAID cut the worst-case RBER from to and all their techniques together gave 85 per cent more lifetime. Reference: Y. Luo, S. Ghose, Y. Cai, E. F. Haratsch and O. Mutlu, ‘Improving 3D NAND Flash Memory Lifetime by Tolerating Early Retention Loss and Process Variation’, Proc. ACM Meas. Anal. Comput. Syst. (SIGMETRICS) 2018, arXiv:1807.05140v2 (fetch-tool summary).
Ques: How does reading a NAND block damage data that is not being read?
Every read applies a pass voltage of about +6 to the unread word lines of the block, against about +15 for programming, which weakly programs their cells and shifts the lower states up most. Cai et al. found that the raw error rate rises about linearly with the read count, faster in worn blocks, and that the onset fell from about reads for SLC to for early MLC and for 2Y-nm MLC, a 50-fold drop (computed). Lowering the pass voltage by 2 per cent cut the error rate at reads by up to half, and the tolerable reads grow exponentially as it falls, but too low a value leaves unread cells off. Their Vpass Tuning gained 21 per cent endurance, and Read Disturb Recovery removed up to 36 per cent of errors. Reference: Y. Cai, Y. Luo, S. Ghose, E. F. Haratsch, K. Mai and O. Mutlu, ‘Read Disturb Errors in MLC NAND Flash Memory: Characterization, Mitigation, and Recovery’, Proc. DSN 2015 (summary version arXiv:1805.03283, fetch-tool summary); Y. Cai, S. Ghose, E. F. Haratsch, Y. Luo and O. Mutlu, ‘Error Characterization, Mitigation, and Recovery in Flash-Memory-Based Solid-State Drives’, Proceedings of the IEEE (September 2017), arXiv:1706.08642v3, with the companion survey arXiv:1711.11427 (fetch-tool summaries).
Ques: Why does program interference grow as NAND cells shrink?
Because the coupling between the storage nodes of neighbouring cells grows as the spacing falls. Cai et al. give coupling coefficients of 0.060 to the word-line neighbour, 0.032 to the bit-line neighbour and 0.012 diagonally for 2y-nm cells, and 0.110, 0.055 and 0.020 for 1x-nm cells. The victim shift is the sum of the coefficients times the neighbours’ threshold changes, so a 2 change of the word-line neighbour moves the victim by 0.12 at 2y-nm and 0.22 at 1x-nm (computed). With several neighbours programmed, the shift reaches about 0.4 (computed, assumed pattern), comparable to the state spacing of MLC. Programming order and neighbour-cell-assisted correction, which extended the lifetime by 33 per cent, limit the effect. Reference: Y. Cai, S. Ghose, E. F. Haratsch, Y. Luo and O. Mutlu, ‘Error Characterization, Mitigation, and Recovery in Flash-Memory-Based Solid-State Drives’, Proceedings of the IEEE (September 2017), arXiv:1706.08642v3, with the companion survey arXiv:1711.11427 (fetch-tool summaries).
Ques: How close to the ECC limit can the raw error rate get?
Not very close, because the codeword failure probability is a binomial tail that rises steeply. For an assumed 9000 bit codeword that corrects 40 errors, the probability of an uncorrectable codeword is at a raw error rate of , at , at and 0.22 at (computed). The margin therefore closes within a factor of two to three in raw error rate. Cai et al. state that ECC engines handle raw rates of about to against a JEDEC target of after correction, and Luo et al. use a limit of . Since cycling, retention and read disturb all raise the raw rate together, the end-of-life raw rate must include all three. Reference: Y. Cai, S. Ghose, E. F. Haratsch, Y. Luo and O. Mutlu, ‘Error Characterization, Mitigation, and Recovery in Flash-Memory-Based Solid-State Drives’, Proceedings of the IEEE (September 2017), arXiv:1706.08642v3, with the companion survey arXiv:1711.11427 (fetch-tool summaries); Y. Luo, S. Ghose, Y. Cai, E. F. Haratsch and O. Mutlu, ‘Improving 3D NAND Flash Memory Lifetime by Tolerating Early Retention Loss and Process Variation’, Proc. ACM Meas. Anal. Comput. Syst. (SIGMETRICS) 2018, arXiv:1807.05140v2 (fetch-tool summary); Failure Rate and the Bathtub Curve page of this vault.
Related pages in this vault: Floating Gate Flash Memory (NOR and NAND), Charge Trap Flash Memory (SONOS, TANOS and 3D NAND), Static and Dynamic Random Access Memory (SRAM and DRAM), Ferroelectric Random Access Memory (FeRAM, PZT and HfO2), Magnetoresistive Random Access Memory (Toggle and STT-MRAM), CMOS Logic Transistors, EPROM, EEPROM and Legacy Non-Volatile Cells (FAMOS, FLOTOX, Split-Gate), Nanocrystal Memory (Discrete Nanodot Storage), SiC and Ga2O3 Power Devices.