sw malfunction?

[caspertone2003]

I am trying to find a dependable and trustable sw for testing storage, either spinning, usb or SSD... not found yet, some look good but do not work with usb sticks, other not recognize ssds etc.
Best up to now is H2testw but has its issues.
Testing stressdisk....

I used the stressdisk with a USB connected half giga SSD. Windows 10 2004 x64. Several times. Full format between tests.
Did it in a unit that H2testw had no issue with it.

Had systematically two issues

a) created files are 954MB (1GiB?). as to the last end available space is less (774MB) stressdisk issues an error message, probably unrelated to media error.
2020/11/23 11:09:13 Writing file "o:TST_0511" size 1000000000
2020/11/23 11:09:19
Bytes read: 1204228 MByte ( 423.25 MByte/s)
Bytes written: 1734176 MByte ( 96.56 MByte/s)
Errors: 0
Elapsed time: 26m0.0010488s

2020/11/23 11:09:20 Error while writing "o:TST_0511"
2020/11/23 11:09:20 Removing incomplete file "o:TST_0511"
2020/11/23 11:09:20 Starting round 1
2020/11/23 11:09:20 Reading file "o:TST_0468", "o:TST_0129"

b) after having read almost ten times the storage (5111GB read), I get the error:
"Error while reading "o:TST_0099": read o:TST_0099: A device which does not exist was specified
then, stressdisk ends
TST_0099 had been read 9 times before without issue...
Operating system shows device, no issue... I can delete files, format it, and use it normally.
Similar outcome in the other stressdisk tests.

First one looks as a kind of bug.
Second one is weird.... could be perhaps a heating issue? could be a wrong message? could be a bug?

Otherwise, media looks working properly...

[ncw]

created files are 954MB (1GiB?). as to the last end available space is less (774MB) stressdisk issues an error message, probably unrelated to media error.

That is normal. stressdisk tries to fill the media up with 1G files until it gets an error.

after having read almost ten times the storage (5111GB read), I get the error:
"Error while reading "o:TST_0099": read o:TST_0099: A device which does not exist was specified
then, stressdisk ends

This is either the media or your OS dropping the USB port I think. So maybe the stick overheated or the OS had a problem or the USB driver is unreliable. I've seen similar problems in the past with unreliable USB drivers.

The fact it worked again after means the OS picked it up again straight away I think.

I suspect, if you could find the right Windows logs, you'd see something like that going on.