Frequent error when running surface test

Post here if you encounter any problems or bugs with the software.
6Ho@
Posts: 1
Joined: 2019.05.09. 23:51

Frequent error when running surface test

Post by 6Ho@ »

I often get error 5 when I try to run a surface test, which I generally do in repair mode. I will upload a copy of what I see on the screen. The solution is generally to reboot the computer. I am running xp sp3 still. Any ideas as to what is causing this problem?
Attachments
PSWorks-01668.jpg
PSWorks-01668.jpg (301.68 KiB) Viewed 2955 times
User avatar
hdsentinel
Site Admin
Posts: 3128
Joined: 2008.07.27. 17:00
Location: Hungary
Contact:

Re: Frequent error when running surface test

Post by hdsentinel »

Seems so interesting. Generally there should be no problems with XP, XP SP3 is supported as well.

The interesting is that I see the message "The system cannot find the path specified" which may indicate a missing file / component. But if things work after a complete restart, then I suspect this is not the case, the software installed and working.

Can you please write me when did you exactly see this problem?
Is it related always to same disk drive or maybe same removable (USB) dock/enclosure?
Does it happen when you previously start one (or more) such Disk menu -> Surface test -> Disk Repair test(s)?

Generally the Disk menu -> Surface test -> Disk Repair test should run on only one drive at any given time.
Other tests can be used on multiple disk drives at the same time, but the Disk Repair works on only one disk drive at any given time. Should work of course on a different when the previous test completes.

Would be nice if we can connect to something and know exactly when the issue happens and what may be related. This way I can examine, reproduce and check what can cause.

I'd suggest to please use Report menu -> Send test report to developer option.
This helps to check the actual situation, examine the "raw" response and possible error code when accessing the disk drive. Maybe you can use multiple times:
1) use Report menu -> Send test report to developer option when you encounter similar next time
and then
2) use Report menu -> Send test report to developer option after reboot (when the test starts)

Investigating these may help, may give some ideas to check.
Post Reply