Today’s SSD analysis takes a look at a new SSD to the market, this being the Kingston SSDNow V300 SATA 3 SSD.
The V300 is a unique Kingston SSD introduction as it is their first product using the new Toshiba 19nm NAND flash memory process, but also, this SSD is ‘SandForce Driven by LSI’ and a key example of the success that can be had when two companies work closely together.
It is no secret that the established ‘best practice’ with respect to consumer SSDs has become that of ‘more for less’. Getting more value, and potentially more capacity, to the consumer is key and manufacturers are finding ways to do this using memory that has a smaller overall footprint. The Kingston V300 seems to be an ideal example of this value, at least on the outside, so let’s take a closer look at where technology seems to be heading.
The Kingston SSDNow V300 SSD is available in capacities of 60 and 120GB capacity and a quick check of Amazon has the V300 priced at roughly $77 and $109 with pricing just a bit higher with the included full migration kit. Specifications list 240GB as being an included capacity, however, we aren’t seeing any online at Kingston or Amazon as of yet. Performance for the V300 is listed at 450MB/s read and write with a high of 85,000 IOPS at low 4k aligned random write disk access and a standard 3 year warranty is included with the V300.
Kingston has done a great job with design of the new V300 packaging, highlighting such things as the massive performance improvement from a typical hard drive and ease of migration. Our review sample is the SSDNow V300 120GB capacity with complete desktop SSD upgrade kit.
The kit includes an adapter, power and data cables as well DVDs for installation and cloning your present system to the new V300. These SSDs are probably the best example of ease of installation we have seen to date. The first Kingston Installation SSD is no more than a video that walks you through the complete process for both desktop and notebook systems whereas the second DVD is a PDF Guide that is very well written, as well as a copy of Acronis True Image HD Cloning Software’
SSDNOW V300 COMPONENTS
The Kingston SSDNow V300 is of a grey gunmetal look exterior, only 7mm thick for ultrabook installations, and secured by four screws on the bottom of the drive, one which of course is covered by security tape and would void the warranty if tampered with. A quick click on any of our pictures will bring up a higher resolution photo.
The exterior casing protects the PCB which houses the SandForce SF-2281 flash storage processor (FSP)and 16 modules of Toshiba’s brand new 19nm 8GB MLC Toggle Mode NAND flash memory. Following recent trends in the SSD industry, Kingston has rebranded the FSP and memory with their own branding. This is actually the first time we have ever seen such with the LSI SandForce FSP.
There is actually 128GB of total NAND flash memory displayed (16x8GB), however, 8GB are reserved for SF over provisioning needs which explains the 120GB advertised capacity. Once formatted, only 112GB of available capacity is available to the consumer.
If you look closely at the memory on the back of the PCB, you will notice a residue left on each. This is the result of the pink material shown above that both increases the shock absorption of the SSD, as well as dissipating heat to the exterior of the drive.
What exact optimizations did you make in BIOS?
Is there anything you recommend doing on a Gigabyte Z77 UEFI BIOS without disabling the SLEEP function?
work optimizations on hyperx 3k ????
I’m having issues installing an operating system on the SSD. Doesn’t show up in diskpart or windows disk manager, tried it by external enclosure and swapping it out for my laptop HDD. Shows up in BIOS, but not in disk manager or diskpart when using windows 7 setup cd and windows 7 setup USB.
It could be defective, but statistically most issues are human ones or hardware incompatibilities.
I am not sure where you have gone with this. Have you tried a simple install to check if the SSD was recognized during the W7 installation process? I have installed ….crap must be over a thousand W7 systems by now…and have never encountered a situation where the drive was recognized in the bios but not during initial installation.
Nevermind, fixed it.
Next question is how’d you tweak to get the final performance you did?
Ok, but what was the issue?
hello please how to tweak to get the final performance you did?
Les, great article. One question though… why do you state “112 GB” after formatting? This is a continued misrepresentation of hard drive advertising. As you probably know, manufacturers sell drives using a base-10 system (1 GB = 10^9 bytes), whereas Windows sees the size with base-2 (1 GiB = 2^30 bytes), now known as “Gibibytes” or GiB to avoid confusion. This conversion leaves us at 111.75 GiB from 120 GB, what you call the difference due to formatting.
I apologize if I sound a bit frustrated but we explain things in a VERY simple way and using GiB does nothing more than to confuse the consumer CONSIDERABLY. It is a VERY simple method to explain the RAW total, advertised total and available total as we do, especially since 99.99999% of consumers haven’t a clue as to what you speak. They JUST want to know how much space is available. Thanks ahead Dan!
I have two 120GB V300s.
The first has 505 firmware which works at it should.
The second has 506 firmware and is way slower.
Could you check a new one with 506 to see if there are differences or is something wrong with mine?
I have same issue, 506 is significantly slower. Can someone check it? Or retest with new FW will be more than helpful.
For me the AS SSD numbers (on SATA 2) are the following Read | Write 505,506.
Seq 256 , 175 | 158 , 133
4K 14 , 11 | 45 , 26
4K-64 123 , 91 | 109 , 114
Acc 0.138 , 0.195 | 0.321 , 0.405
Here is you answer….
A follow-up review on the current asynchronous version might be helpful.
I think this review needs to be updated to reflect how Kingston changed the ssd from what they sent out for reviewing to what is being sold now. It’s a big story that this website should have caught onto but it appears not. Instead I shall share with you a link to some up to date information.