Microsoft has advised that the most recent version of Windows 10—version 1803, codenamed Redstone 4—is currently incompatible with the Intel SSD 600p and the related Intel SSD Pro 6000p. Windows 10 version 1803 can crash when attempting to update Windows 10 installed to an affected SSD. The Intel SSD DC P3100 and SSD E 6000p were not mentioned but are probably also affected as they share the same controller and firmware platform as the 600p.

The Intel SSD 600p consumer drive and its relatives for other market segments were Intel's first M.2 NVMe SSDs, a radical shift from the large Intel SSD 750 and its enterprise counterparts. The 600p family uses Intel's first-generation 32-layer 3D TLC NAND flash memory and a customized variant of the Silicon Motion SM2260 NVMe SSD controller. This combination made for the first low-end, (relatively) low-cost NVMe SSD, though more recent drives with controllers designed specifically for the entry-level NVMe market have now reached much lower prices than the 600p sold for when it was current. Intel's replacement for the 600p is the Intel SSD 760p, which uses a newer generation of 3D TLC NAND and a newer generation of controller from Silicon Motion. The 760p has not been reported to be affected by the same incompatibility as its predecessor.

It is not yet clear what is causing the incompatibility between the Intel 600p and Windows 10 version 1803, but the most likely culprit is a bug in the 600p's controller firmware. Intel has issued two firmware updates for the 600p family, each fixing several bugs including some that had the potential to cause data loss or corruption. The most common theme in the release notes for 600p firmware updates seems to be power management troubles, but those are unlikely to prevent Windows 10 v1803 from even installing to the 600p.

It is also possible that there's a bug with the 600p that cannot easily be fixed with a firmware update. The Linux NVMe driver has workarounds for two such issues with the 600p. The first workaround was for Linux to not attempt to use the deepest idle power state provided by the 600p; that was added about a year ago. The second workaround was added earlier this week. That issue is documented as affecting some P3100 drives but the workaround applies to everything in the 600p/P3100 family because they use the same PCI device IDs. The problem lies with the drive thinking that it has been instructed to use the optional weighted round robin method for deciding which queue to service commands from next, instead of the default simple round robin method. The workaround chosen by the Linux developers is to ensure that command submission queues on the 600p are assigned medium priority even when the driver doesn't intend to use the weighted priority feature.

For now, users with the Intel SSD 600p or one of its siblings are advised to not upgrade to Windows 10 version 1803, and Microsoft is working on a patch to allow version 1803 to work with the 600p. Owners of a 600p should also be on the lookout for a possible firmware update from Intel. The current version is 121 for the 600p, Pro 6000p and E 6000p, and version 119 for the P3100. A patch for this issue from either Microsoft or Intel would be sufficient to allow Windows 10 version 1803 to work with the 600p.

Other SSDs based on the SM2260 controller do not feature Intel's customized firmware, and historically have not been affected by the same bugs as the Intel 600p family.


Source: Microsoft

Comments Locked


View All Comments

  • StevoLincolnite - Friday, May 11, 2018 - link

    In Microsoft we trust, Amen.
  • Samus - Saturday, May 12, 2018 - link

    LMFAO I wish we still had ratings so this could get a 6
  • Azurael - Saturday, May 12, 2018 - link

    Of course! I forgot it's Microsoft and the Linux kernel developers' job to work around buggy hardware!
  • WinterCharm - Saturday, May 12, 2018 - link

    Steve Jobs is dying laughing in his grave right now.
  • Jhlot - Tuesday, May 15, 2018 - link

    "The good news is that Windows 10's flexible update policy allows end users a very high degree of individual choice when it comes to changes from Microsoft so issues like this aren't forced on a system once they become known. "

    You win the internet sir! Made my coffee go down the wrong way from laughing. Oh the burn!
  • HStewart - Friday, May 11, 2018 - link

    I have notice that Windows 10 has issues with older device, but this SSD not that old and it is storage drive

    Well my experience in with 10+ Year old Xeon 5160 and not the CPU but the sound driver - I work around the issue by removing the driver in safe mode.

    Windows need logic if driver crashes on boot - have a way to disable it - that would work great in my situation but if SSD is primary drive then that would be an issue.
  • ಬುಲ್ವಿಂಕಲ್ ಜೆ ಮೂಸ್ - Friday, May 11, 2018 - link

    Driver support that has been discontinued for older systems for Windows 10 and even Windows 8.1 can still be fixed in many cases

    After a clean install of Windows 10, just install the Windows 7 drivers
  • ಬುಲ್ವಿಂಕಲ್ ಜೆ ಮೂಸ್ - Friday, May 11, 2018 - link

    For HStewart
  • HStewart - Friday, May 11, 2018 - link

    I actually upgraded from Windows 7 and went to Windows 10 - because I have it on all systems. Even though I spent about $8000 on this system - it primary good storage area now - until Intel came out with the i7 - it was the fastest computer around - a 11 years dual Xeon 5160 is faster than my i5 Surface Pro. It has Dell 30 in monitor which is also outdated.

    I might consider reformatted it with Windows 7 - not sure how much I am going to used it now.
  • Nbarsotti - Friday, May 11, 2018 - link

    My Z370, i7-8700K, Intel 600p system has been working just fine on Windows 1803 for several weeks. I upgraded from 1709 as soon as the rumor hit that 17133 was going to be the finial build. So this problem does not affect all drives. Perhaps the mobo chipset has something to do with the differences.

Log in

Don't have an account? Sign up now