New
#21
they don't occur any more, I mean the number is now stable at 1368 and log showed that was before the date of fixing OneDrive.
they don't occur any more, I mean the number is now stable at 1368 and log showed that was before the date of fixing OneDrive.
Hi, Question: do you get the same message consistently irrespective of Onedrive?
I said:
That's good, but HDS is reporting communication problems. That will most likely result in degraded (slower) or erratic communication, and should be investigated. Try swapping connections/cables.
Also ensure Onedrive is not running and there is no significant disk activity when redoing the check.
The problems of communication have never occurred until I updated OneDrive to the latest version, which included the synchronization of the Desktop.
I noticed that after a few seconds of the boot up there was a freezing in the Taskbar, then the whole computer froze for a few minutes. that led to see if there was anything wrong with the hard disk using HDS, which reported communication problems.
HDS reported communication problems right after the boot up, that is, when OneDrive starts working (it was always showing "OneDrive is updating files" all the time, it displayed "all set" then disappeared quickly). I disabled it and see no more freezing or errors reported. I just reset and the problem with OneDrive stopped and the same for the hard disk. no more communication problems.
the number 1368 of errors occurred during the running of OneDrive and before resetting it.
I eventually found the genuine culprit. Yes, the rest of Onedrive solved the problem, but it was back again three days ago. I had to disabled all the running application at the startup to check, but the same.
the problem was using HD Sentinel Portable version display Performance 98% now, while the installed on displays 100%.
I have the Portable version inside a folder of that belongs to Onedrive.
Hi, does that mean you see performance/health = 100%, but you still have communication errors?
Thanks - would be interested if you manage to resolve that e.g. with better cable or whatever proves appropriate- I've seen such a report by HDS 3 or 4 times in threads now. One was resolved.