Hi, I have owned a T560 issue for about 4 years and about 7-8 months ago it began having random freeze-ups and BSOD's while running Windows 10. It also has had consistent problems recognizing at bootup the Intel Pro 2500 series SSD 180 GB SATA (not M.2) drive I have installed. I am consistently booting into the Windows Boot Manager multiple times where the BIOS detects it as a Sandforce 200026BB drive before after maybe 6-7 or more reboots it finally correctly detects the SSD drive and loads Windows 10. Initially kind of being clueless about this and the Devsleep issue I focused on the Windows freeze-up problem first and did all the requisite checks ... e.g., I made sure all the drivers were updated, all Windows and Lenovo updates were applied, updated the BIOS to the latest version, extensively checked for viruses, ran SFC /scannow as well as running lots of hardware diagnostics checking everything I could find. I also fiddled with the power settings disabling link management and also monitored CPU temps and make sure the fan was working properly. No apparent issues were found and the freeze-ups persisted. It then dawned on me the boot-up problem and the freeze-up issue were probably connected and that's when I stumbled across the Devsleep issue that seems to affect my drive series as well as the 530 & 535 series of drives. The symptoms I've been experiencing really seem to fit the profile of the Devsleep issue and at this point I'm about 99% sure that has to be the root problem. For those unfamiliar with it basically what happens is the SSD drive enters into a very low power state and the BIOS is unable to wake up the drive. The way Intel describes the problem is "the cause of the detection issue could be related to the DevSleep feature of these SSDs. This happens when the motherboard is unable to wake the drive from the deep sleep state." They recommend updating the BIOS to the latest version which I have already done (ver 1.38) and I even tried rolling back the BIOS as far as I could (ver 1.20) and neither BIOS change had any effect. Intel also recommends that if changing the BIOS doesn't fix the problem to update the firmware on the SSD. I did see another post online with someone who the problem with the 530 series drive and the firmware update tool did work effectively in their case. I was hopeful this would fix my problem but unfortunately after trying to upgrade my SSD firmware their update tool said I was already at the latest firmware version (LUsi). Intel also describes a separate firmware upgrade tool specifically designed to turn on or off the Devsleep feature on these drives (https://downloadcenter.intel.com/download/25348
) however when I tried that tool it basically just said again my firmware was already up to date and their was nothing to change. I kind of thought it would give me the option to turn the Devsleep feature on or off my drive but again it would only tell me my firmware is up to date and gave me no options to change anything. So anyway, I'm pretty much feel I am a stopping point now, their is nothing else I can see to do unless someone knows of a way to turn off the Devsleep feature on my Intel Pro 2500 series SSD. If that's not possible then I think I'm pretty much looking at just having to get a new SSD drive. Also, as sidenote, Intel is blaming this problem on BIOS implementations but I don't really buy that, it worked fine for approximately 3 1/2 years, something must have changed hardware-wise for this problem to suddenly develop. I ran extensive tests and diagnostics on my SSD drive without any reported issues but maybe it's the hard drive controller beginning to fail that's causing this problem, that's my best guess. Anyway, if anyone has any thoughts or suggestions I would really appreciate it.