cover
PAVEL K.

PAVEL K.

Joined on 12/08/10

0
0

Product Reviews
product reviews
  • 2
Most Favorable Review

Fast reading but slow writing!

SanDisk 128GB Ultra Fit CZ43 USB 3.0 Flash Drive, Speed Up to 150MB/s (SDCZ43-128G-GAM46)
SanDisk 128GB Ultra Fit CZ43 USB 3.0 Flash Drive, Speed Up to 150MB/s (SDCZ43-128G-GAM46)

Pros: - Tiny flash drive - Reading up to 140MB/s (bigger 20GB files, smaller files are usually slower) - Consumes 224mA (shown by the USB controller)

Cons: - Writing only 25MB/s (bigger 20GB files, smaller files are usually slower) - same as USB2 - The cap is hard to open

Overall Review: - This flash drive is good for those who is OK to spend 1.5+ hours loading it with the data, once, and then read this data fast, multiple times - for example, load an OS (Windows, Linux) from it, store installation files and so on. - This flash drive gets warm but not as hot to worry about.

11/29/2016
Most Critical Review

Great potential though flaky BIOS

MSI PERFORMANCE GAMING X399 GAMING PRO CARBON AC sTR4 AMD X399 SATA 6Gb/s USB 3.1 ATX AMD Motherboard
MSI PERFORMANCE GAMING X399 GAMING PRO CARBON AC sTR4 AMD X399 SATA 6Gb/s USB 3.1 ATX AMD Motherboard

Pros: A lot of potential - 3xM.2, 8xSATA, 6xPCIE, 10xUSB3 on the back!

Cons: After a half an year since released, this motherboard still does not work smoothly/stable.

Overall Review: My server configuration: - MSI X399 Gaming Pro Carbon, BIOS 1.68 Beta (to support M.2 RAID0) - AMD Ryzen ThreadRipper 1950X 16-core - G.Skill TridentZ 3200 4 x 16GB First, after 3 months of the M.2 RAID0 released by AMD, the latest BIOS 1.60 still does not support it. I found leaked BIOS 1.63b, 1.66b and 1.68b somehow supporting the M.2 RAID0 though it is flaky. To make the M.2 RAID0 working you need to switch the SATA controller to the RAID mode, too. But this is not enough - you need to switch the OS mode to Windows-10 thus forcing the UEFI boot mode so no legacy boot from CD/DVD/USB and legacy OS'es after that. And then every other reboot be prepared to get stuck with the status code A0 - I believe the motherboard cannot initialize the M.2 RAID0. I found a way to pass the A0 by switching the SATA back to the AHCI and then to the RAID, and switch the OS mode to ALL and then back to Windows-10 - then it will possibly init the M.2 RAID. And this is just in case you are lucky to get to the BIOS configuration which is not always possible. If it is possible to get to the BIOS configuration then I just load my previously saved overclock profile thus re-init the BIOS settings. If it is not possible (very often) then the only quick way is to either remove 3 RAM sticks out of 4 (which does not always help) or restore the BIOS from the USB flash formatted as FAT32 (not FAT/FAT16/FAT12!) using the FlashBack feature and then load your previously saved overclock profile. In general, be prepared to restore the BIOS and its settings every reboot because it will most possibly get stuck with the status code 94 - usually there is no way to to pass this code using RESET button or switching off the power supply. Sometimes you can get to the BIOS after the status code 94 by pressing the motherboard switch off for 4 seconds but sometimes only the FlashBack helps. My everyday stuck status codes are 54, 55, 62, 64, 94, A0, C3 - only 1 time out of 10 I get a success with the reboot. Overclocking is way more complicated than making the M.2 RAID working! Be prepared to get stuck with various status codes - the "lovely" ones are 54 and 55 after any insignificant change in the BIOS settings! After that there is no way to get back to the BIOS configuration! You either remove all the memory but one, on hope it will boot to the BIOS configuration (assuming you have configured BIOS to go to the configuration on the memory amount changed), or use the FlashBack which will reset the settings, and then restore your settings from the overclock profile. The CMOS reset does not work at all once you stuck with a status code - you cannot clear it neither by shorting the predefined pins on the motherboard for 10 seconds, nor by pressing the CLEAR button on the back for 10 seconds (sure, after switching the power supply and waiting for all the lights went down). So usually only the FlashBack feature works to load the same BIOS again and again (thus wearing the BIOS PROM), or sometimes by removing all the memory but one (thus wearing the memory slots). So until there will be a stable BIOS released, please prepare a FAT32 flash drive with your BIOS version, and save your BIOS configuration to the overclock profile after each change - there will be no way to get to the BIOS configuration in case of any error status code. Well, you may probably have a success with this motherboard if you just put a less cores CPU, slow RAM, 1 HDD and planning no overclocking - then the default BIOS would probably work for you. But this is overclockers motherboard! Sad. Also please note, the Corsair H100i v2 does not work with my hardware configuration (see the config above) - the Corsairlink.Service consumes 30-50 new handles every second and does not release them thus making the computer responding very slow in just few hours followed by the Windows-10 crash after the CorsairLink.Service allocated 1,000,000 handles. As a solution, the Corsair's technical support requires to run CCleaner Registry Clean even on a fresh Windows-10 installation. Well, running CCleaner Registry Cleanup twice on a fresh Windows-10 installation before the CorsairLink installation and then twice after the CorsairLink installation does not help - every developer knows the root cause of this issue but the Corsair technical support keeps requesting to run CCleaner again and again for 10 days since December 19 as "the only way to get the CorsairLink working". So please do not use the CorsairLink on similar configuration (at least with the CorsairLink versions 4.9.3.24, 4.9.3.25, 4.9.3.28 I've tried) to avoid your Windows-10 crash and slowness. I would give Enermax TR4 a try - it does not require any software at all to work, and its pump and fan speed is configurable directly from the BIOS not by an application, and also it fully covers the AMD Ryzen ThreadRipper surface not just 50% or so thus giving a better overclocking potential - I will probably go this way and dump the Corsair H100i.

12/27/2017