- Obtained from: Amazon
- Price paid: $12.99
- Advertised capacity: 128GB
- Protected area: 134,217,728 bytes (inaccessible)
- Speed class markings: Class 10*, U3, V30, A1
- CID data:
- Manufacturer ID:
0x27
** - OEM ID:
0x5048
(ASCII:PH
) - Product name:
0x5344313238
(ASCII:SD128
) - Product revision:
0x60
- Manufacturer ID:
* The Class 10 mark appears on the product packaging, but does not appear on the card itself.
** This manufacturer ID/OEM ID combination is pretty well known to be associated with Phison.
Discussion
This card, along with the PNY Elite-X 64GB, are the first PNY-branded cards that I’ve purchased as part of this project — which, honestly, seems like an oversight on my part. (How could I forget about PNY?)
Performance-wise, this card performed pretty well — it looks like it doesn’t support the enhanced speeds that SanDisk’s cards do — which meant that sequential read speeds were only slightly above average — but it did exceptionally well with sequential write speeds, putting them in the 95th percentile. Random read and write speeds were all more than one standard deviation above average, with two of the three samples getting random write speeds that were more than two standard deviations above average. The worst of the three random write scores would put it into the 87th percentile in this category, while the worst of the random read scores would put it into the 85th percentile. In fact, the worst performance measurement between all three samples would put this card into the 84th percentile.
This card carries the U3, V30, and A1 markings. Additionally, the package carries the Class 10 marking. All three samples performed well enough to qualify for all of these markings. (Well done, PNY!)
All three samples are currently undergoing endurance testing:
- Sample #1’s first error was…well, I don’t know what to make of it. It was a data mismatch error of some sort that only affected one sector during round 589 — but it only affected the last four bytes of the sector (where I store the CRC for that sector). And on top of that, the CRC check passed — which tells me that either something was wrong with the CRC check, or the data I reconstructed was wrong. I’m not sure what to make of it. At any rate, it has survived 2,001 read/write cycles in total so far.
- Sample #2’s first error was a single bit flip, in a single sector, during round 1,400. It has survived 1,995 read/write cycles in total so far.
- Sample #3’s first error was a single bit flip, in a single sector, during round 387. It has survived 1,894 read/write cycles in total so far.
November 4, 2024 (current number of read/write cycles is updated automatically every hour)