3

WARNING: This question arose from a buggy test software. After its fixing, the time required to copy a file, large 3.5 Gb, is best estimate between 45 and 60 sec, on heavy load. I'm sorry for disturbing you.

I have just assembled my new PC and I'm observing troubles with its five brand new hard disks. They are all extremely slow: it takes more than a minute to complete a command like

copy d:\file1 d:\file2

where file is 1.5 Mb large. HD are completely void, tested both just a minute and dozens of hours after boot completion and while no other program is running.

I have read Hard disk suddenly extremely slow, but it seems unlikely that all my disks are defective and DOA.

I have no idea of the possible reason; can you please provide any advice?

Please, see the screenshots below.

  • Mother board: omissis (supports SATA III)

  • Hard disks: omissis

  • Western Digital Data Lifeguard diagnostics short test: each passed after a few minutes

  • Western Digital Data Lifeguard diagnostics long test: each passed after 6 hours

  • Krystal Disk Info 7.9.3 x64 report: all healthy

  • OS: Windows 10.0.14393 booted from Hiren’s BootCD PE (Preinstallation Environment)

  • metal scratching sound: none

  • data partition: GPT

  • File system: NTFS

test screenshoots

closed as too broad by Ramhound, td512, Canadian Luke, Attie, fixer1234 Nov 10 '18 at 10:48

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    How long did you wait after boot? Windows and background programs continue to do a lot of activity in the background after it reaches the point where you can start doing things. Actions can be very slow for awhile. – fixer1234 Nov 8 '18 at 2:26
  • 1
    In a test I have waited approximately 40 hours. – glossa Nov 8 '18 at 5:01
  • 1
    Try starting in safe mode or clean mode to rule out the effect of anything else that might be running in the background. In fact, rule out Hiren's as the problem by doing as close a test as you can booting normally. – fixer1234 Nov 8 '18 at 5:17
  • 1
    I wasn't referring to installing anything, I'm suggesting to rule out a few potential causes. One is your measurement tool. Make sure it isn't giving you flaky results or causing them when you don't actually have a problem. Also, rule out other potential background activity. Do a clean boot or boot into safe mode; just a barebones startup with no Internet, no antivirus, no applications, nothing but the bare minimum needed to operate. Do some manual data transfer tests to see if you're in the same ballpark as what you've been seeing. If so, you've narrowed it to hardware. (Cont'd) – fixer1234 Nov 8 '18 at 7:44
  • 1
    I would also boot into a Linux live session and run similar manual tests. That will rule out anything related to Windows or drivers. If you still get very slow performance, it has to be hardware. – fixer1234 Nov 8 '18 at 7:46

Browse other questions tagged or ask your own question.