CrystalDiskMark crash and blue screen when benchmarking SSD

[johnx125]

So yesterday I installed CrystalDiskMark 6.0.0 just to check my hard drive's and SSD's speeds. First I ran a benchmark on the HDD (WD Green 2TB)... everything was fine. Then I started a benchmark on the SSD (Corsair Force LE 120GB). At first everything seemed fine, but after a few minutes I noticed the programm was stuck on preparing something -I don't really remember- and the drive activity LED was solid on, not blinking. So then I decided to open Task Manager to see what is going on... and that's when my computer froze. Completely. I coundn't even move the cursor. Nothing was working. I waited for a minute to see if it would do anything and... I got a blue screen with stop code "DPC_WATCHDOG_VIOLATION". After a minute or two my computer rebooted and now everything seems fine. But I can't understand why this happened... what was the cause? Does anyone know?

 

[johnbl]

You should not do write bench marks on solid state drives, they have very limited write endurance per block. If you do write tests the block will be marked bad and the ssd firmware has to relocate the block. After a few minutes the firmware can get behind on the process and take longer than 30 seconds to respond which triggers a bug check. watchdog timeout

New drives can have a worse case write endurance of 300 writes before the block becomes read only and data has to be copied to a new block and the old remarked as bad. (And your drive space is reduced by the amount of space that is marked as bad)

 

[johnx125]

You should not do write bench marks on solid state drives, they have very limited write endurance per block. If you do write tests the block will be marked bad and the ssd firmware has to relocate the block. After a few minutes the firmware can get behind on the process and take longer than 30 seconds to respond which triggers a bug check. watchdog timeout

New drives can have a worse case write endurance of 300 writes before the block becomes read only and data has to be copied to a new block and the old remarked as bad. (And your drive space is reduced by the amount of space that is marked as bad)

Holy crap I had no idea! So I've probably damaged some parts of the SSD I tested?