Kingston NV2 1 TB M.2 NVMe SSD

[Chrispy_]

Problem in many cases is availability. i do agree that its completly wrong what they do, but we need to understand that these manufacturers they just buy these ICs for their SSDs when they manufacturer themselves, not considering "white labeling".
The problem is that they can't get an infinite number of batches for a single product, in my opinion, they should be transparent about it, saying that it could change and list in details all the different variants

They get away with it, to some extent, by listing the official specs very conservatively and omitting some specs altogether.
When they need to switch to inferior NAND or controller, they baked enough wiggle-room into the original spec to still meet them all.

Sadly, real-world performance doesn't care about a select few specs on a marketing spec-sheet, which is why the bait-and-switch re-reviewed products always look bad.

 

[GabrielLP14]

They get away with it, to some extent, by listing the official specs very conservatively and omitting some specs altogether.
When they need to switch to inferior NAND or controller, they baked enough wiggle-room into the original spec to still meet them all.

Sadly, real-world performance doesn't care about a select few specs on a marketing spec-sheet, which is why the bait-and-switch re-reviewed products always look bad.

true

 

[kapone32]

true

Sounds like exactly what Corsair does with their RAM.

 

[uBaH]

Strange things are happening to my 2TB NV2, approx. 10 months after the purchase, so I have decided to share the information. Another person is having exactly the same issues with his 2TB NV2, so I guess it won't be an isolated case.

Just to clarify before everything else - my NV2 has perfect SMART, just 2,3TB of writes and under 500 power-on hours for these 10 months since its purchase. I have used it just for file storage (family photos and videos), as a second drive installed on the motherboard's second (Gen.3 x4 M.2 slot).
With this type of usage (occasional incremental writes), I am not sure since when I have the problem. It could have been there right from the beginning...

Now the problem - accessing the information already stored on this SSD takes ages! Anything from just clicking on folder properties, photos / videos thumbnails visualization, to opening and copying files is happening waay too slow. Is is OK, sometimes, and not OK most of the time.
The copy process starts, usually fast, then goes to 0MB/s, stays there for 5-10-15 seconds, 2-3-5 minutes, then goes up again and so on. The SSD's access time is seconds, sometimes tens of seconds. The "Disk active time" in Task Manager shows 100% almost all the time.
This happens no matter whether I try to copy files from the NV2 to an external USB drive or to the other SSD in the system.

I have noticed the problem yesterday. My system has been through a lot of software changes, driver removals / updates etc. for the last 12 months since Win10 was installed, so I have decided to do a clean OS install last night, but unfortunately this did change anything.

The system's specs are:
Win10 22H2, all current updates installed
AMD chipset drivers from MSI's web site
Kingston SSD manager, latest drive firmware installed
MSI B550A-Pro MoBo
Kingston NV2 in the MoBo's second (chipset) M.2 slot
Seagate FireCuda 530 in the MoBo's first (CPU) M.2 slot

In the System Event Viewer I have lots of warnings "Reset to device, \Device\RaidPort2, was issued" which correspond to the "pauses" in my file copy attempts.

The SMART status of the NV2 appears to be OK too:

Would you suggest any further steps, which will ensure that the SSD is the culprit (before attempting a RMA)?


PS. The other guy, who is having the same issues with his NV2, has already tried switching the NV2 with his main SSD (switching both M.2 slots on his motherboard) and a different motherboard, but the problem still exists.

 

[Cecy]

Strange things are happening to my 2TB NV2, approx. 10 months after the purchase, so I have decided to share the information. Another person is having exactly the same issues with his 2TB NV2, so I guess it won't be an isolated case.

Just to clarify before everything else - my NV2 has perfect SMART, just 2,3TB of writes and under 500 power-on hours for these 10 months since its purchase. I have used it just for file storage (family photos and videos), as a second drive installed on the motherboard's second (Gen.3 x4 M.2 slot).
With this type of usage (occasional incremental writes), I am not sure since when I have the problem. It could have been there right from the beginning...

Now the problem - accessing the information already stored on this SSD takes ages! Anything from just clicking on folder properties, photos / videos thumbnails visualization, to opening and copying files is happening waay too slow. Is is OK, sometimes, and not OK most of the time.
The copy process starts, usually fast, then goes to 0MB/s, stays there for 5-10-15 seconds, 2-3-5 minutes, then goes up again and so on. The SSD's access time is seconds, sometimes tens of seconds. The "Disk active time" in Task Manager shows 100% almost all the time.
This happens no matter whether I try to copy files from the NV2 to an external USB drive or to the other SSD in the system.

I have noticed the problem yesterday. My system has been through a lot of software changes, driver removals / updates etc. for the last 12 months since Win10 was installed, so I have decided to do a clean OS install last night, but unfortunately this did change anything.

The system's specs are:
Win10 22H2, all current updates installed
AMD chipset drivers from MSI's web site
Kingston SSD manager, latest drive firmware installed
MSI B550A-Pro MoBo
Kingston NV2 in the MoBo's second (chipset) M.2 slot
Seagate FireCuda 530 in the MoBo's first (CPU) M.2 slot

In the System Event Viewer I have lots of warnings "Reset to device, \Device\RaidPort2, was issued" which correspond to the "pauses" in my file copy attempts.

The SMART status of the NV2 appears to be OK too:

Would you suggest any further steps, which will ensure that the SSD is the culprit (before attempting a RMA)?


PS. The other guy, who is having the same issues with his NV2, has already tried switching the NV2 with his main SSD (switching both M.2 slots on his motherboard) and a different motherboard, but the problem still exists.

Hi, I've been having similar issues with my Kingston NV2 recently and hundreds of Event 129 - I am using it as my main OS drive and quite often it throttles down to unbearably low speeds and the system hangs. It's very frustrating. Initially I was thinking that it is overheating but the temps on my side are not that high. Highest I've seen was like 42C which should not be a problem. I am considering formatting it and not using it as a OS drive ever again. Turned out to be such a shitty SSD

 

[djsolidsnake86]

Strange things are happening to my 2TB NV2, approx. 10 months after the purchase, so I have decided to share the information. Another person is having exactly the same issues with his 2TB NV2, so I guess it won't be an isolated case.

Just to clarify before everything else - my NV2 has perfect SMART, just 2,3TB of writes and under 500 power-on hours for these 10 months since its purchase. I have used it just for file storage (family photos and videos), as a second drive installed on the motherboard's second (Gen.3 x4 M.2 slot).
With this type of usage (occasional incremental writes), I am not sure since when I have the problem. It could have been there right from the beginning...

Now the problem - accessing the information already stored on this SSD takes ages! Anything from just clicking on folder properties, photos / videos thumbnails visualization, to opening and copying files is happening waay too slow. Is is OK, sometimes, and not OK most of the time.
The copy process starts, usually fast, then goes to 0MB/s, stays there for 5-10-15 seconds, 2-3-5 minutes, then goes up again and so on. The SSD's access time is seconds, sometimes tens of seconds. The "Disk active time" in Task Manager shows 100% almost all the time.
This happens no matter whether I try to copy files from the NV2 to an external USB drive or to the other SSD in the system.

I have noticed the problem yesterday. My system has been through a lot of software changes, driver removals / updates etc. for the last 12 months since Win10 was installed, so I have decided to do a clean OS install last night, but unfortunately this did change anything.

The system's specs are:
Win10 22H2, all current updates installed
AMD chipset drivers from MSI's web site
Kingston SSD manager, latest drive firmware installed
MSI B550A-Pro MoBo
Kingston NV2 in the MoBo's second (chipset) M.2 slot
Seagate FireCuda 530 in the MoBo's first (CPU) M.2 slot

In the System Event Viewer I have lots of warnings "Reset to device, \Device\RaidPort2, was issued" which correspond to the "pauses" in my file copy attempts.

The SMART status of the NV2 appears to be OK too:

Would you suggest any further steps, which will ensure that the SSD is the culprit (before attempting a RMA)?


PS. The other guy, who is having the same issues with his NV2, has already tried switching the NV2 with his main SSD (switching both M.2 slots on his motherboard) and a different motherboard, but the problem still exists.

is tlc or qlc?

 

[uBaH]

@djsolidsnake86 - it is a TLC one. Confirmed earlier in this thread.

As an update to my post above, I can write that after a quick format, my 2TB NV2 is working, as there have never been any problems with it. Writing / reading - everything works as it should.
I have given it to my father and he is using it as a system drive now with no issues.

 

[djsolidsnake86]

@djsolidsnake86 - it is a TLC one. Confirmed earlier in this thread.

As an update to my post above, I can write that after a quick format, my 2TB NV2 is working, as there have never been any problems with it. Writing / reading - everything works as it should.
I have given it to my father and he is using it as a system drive now with no issues.

problem can happen again

 

[uBaH]

For sure it can

I have advised my father to keep a copy of his files on his mechanical drive (which is still in the system). In addition to that, I have kept his original 128GB system SATA drive, with the OS, settings and all his data.
In case the NV2 fails again, I should be able to have his system up and running in almost no time.

PS. Using this NV2 as an everyday, system drive should highlight its problems much faster than my type of use (data backup drive, accessed from time to time).

 

[reb0rn]

Kingston 4tb ver: 015.A03G

 6: (KINGSTON SNV2S4000G
Please select drive number:4
Drive   : 4(NVME)
Driver  : W10(4:3)
Model   : KINGSTON SNV2S4000G
Fw      : ELFK1N.1
HMB     : 65536 - 65536 KB (Enabled, 64 M)
Size    : 3815447 MB [4000.8 GB]
LBA Size: 512
Firmware lock supported [03 01] [P101] [0000]
Handshake error: 0
Drive unlocked [03 03]
F/W     : ELFK1N.1
P/N     : 10034737
Bank00: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank01: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank02: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank03: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank04: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank05: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank06: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank07: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank08: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank09: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank10: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank11: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank12: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank13: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank14: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Bank15: 0x98,0x49,0x99,0x3,0x7a,0xe4,0x8,0x16 - Toshiba 112L BiCS5 TLC 16k 2048Gb/CE 1024Gb/die 2Plane/die
Controller    : PS5021-E21
CPU Clk       : 980
Flash CE      : 16
Flash Channel : 4
Interleave    : 4
Flash CE Mask : [++++++++ ++++++++ -------- --------]
Flash Clk,MT  : 10
Die per CE    : 2
Block per CE  : 12888
Page per Block: 1344
Bit Per Cell  : 3(TLC)
PMIC Type     : PS6103
PE Cycle Limit: 50000/3000
SLC cache     : 0x100000/0x60000
Defects Early Read Prog Erase
Bank00:   24    0    0    0
Bank01:   24    0    0    0
Bank02:   35    0    0    0
Bank03:   36    0    0    0
Bank04:   61    0    0    0
Bank05:   24    0    0    0
Bank06:   39    0    0    0
Bank07:   28    0    0    0
Bank08:   79    0    0    0
Bank09:   54    0    0    0
Bank10:   36    0    0    0
Bank11:   27    0    0    0
Bank12:   37    0    0    0
Bank13:   50    0    0    0
Bank14:   33    0    0    0
Bank15:   37    0    0    0
Total :  624    0    0    0