

I will see what happens with the replacement drive in a few days (shipping delays!). The firmware update log file says that the update was successful as shown below, but it does not change the version when checked by various means (wmic command, Device Manager, Crystal Disk Info). It should be 26302039 after the update.Ĭ:\wmic diskdrive get caption, firmwarerevision Caption FirmwareRevision Current firmware is 25309039, as shown below and on the drive's sticker, which is what it was before running the firmware update and after running the update file. says that the firmware applies to my Vostro 5402. While waiting for the new PM991 to arrive and being bored out of my wits, I dug deeper on the drivers page and found both a newer BIOS (1.7.1, which I installed) than SupportAssist finds (1.6.0) and I found firmware for the PM991a NVMe. I talked to a ProSupport person on Friday and they are sending a replacement drive. Its specs are 2050 read and 1300 write, yet speed tests with ATTO show 1000 read and 130 write, WAY below specs. can change the benchmark results, but it might just be that it changes how the FPS is counted, rather than how fast the PC is in practice. Can we even trust a PC to benchmark itself any more?!" I am even more confused now.I have a Vostro 5402 that has a Samsung PM991 NVMe in it, part number MZ9LQ256HAJD-000D1.

No idea why.Įdit: Found out something even more interesting. I had a suspicion Windows is the cause.Įdit: I reinstalled NVME drivers and rechecked Magician, now I got 230k on Read and the same on Write, and in general on other tests "write" speeds have remained low (or dropped). So if someone has another advice, please do share. However my write speeds are being limited a lot and seem to fluctuate a lot. I still have low IOPS in magician, 150k and 130k while it should be around 400k, and at least 300k according to some pictures from other owners of 970 EVOs and similar. Increased the SSD performance by 50% in most tests. I had the same problem with my 970 EVO and disabling HPET in cmd (as admin) with the command:īcdedit /deletevalue useplatformclock (and rebooting)
