H2testw would take 4 hrs to test the above Samsung microSD.
it took 2 mins to test a Samsung EVO 128gb microSD, and 1 min to test and detect a fake 32gb microSD. I have tried to google the ‘problem’ hoping to find similar cases, but no luck there. 1 H2testw is highly recommended but it's just too slow. FakeFlashTest tries to fix the main issue with H2testw which is the long time it takes for the process to complete on larger or slower flash drives. So what’s going on with FakeFlashTest? Is the message a false positive or is there something fishy about my cards? Anyone got a clue? The thing is though, both cards pass h2testw with a write speed of 40MB/s & read speed of 80MB/s for the entire 64gb of storage. So the cards work fine, the read/write performance is good too, except for bad 4K writes on one of them. Well FakeFlashTest reports this BAD MEMORY from sector 107859 (52.0MiB) to sector 77624659 (37,902.0Mib) I get a similar message from the other card, only from 1000’ishMiB to 37,902.0MiB. I’ve also tried loading them up with 64gb worth of media and all the media seems to work fine. The thing is though, both cards pass h2testw with a write speed of 40MB/s & read speed of 80MB/s for the entire 64gb of storage.ĬrystalDiskMark benchmarks results are also great, except for one of the cards that has extremely bad random 4k writes, like 0.008 MB/s. I get a similar message from the other card, only from 1000’ishMiB to 37,902.0MiB. I always like to test my sd cards before I put them to use, so I run FakeFlashTest, H2testw & CrystalDiskMark to benchmark them.īAD MEMORY from sector 107859 (52.0MiB) to sector 77624659 (37,902.0Mib) I’ve even bought from this seller before without issues. I recently bought two 64gb micro sd cards (SanDisk Ultra) from Ebay, the seller’s called ‘atmemory’, he has an excellent rating & many sales. I am hoping someone might understand what’s going on here and be able to explain to me if my cards are fine or not.
0 kommentar(er)
