Forum Home
Press F1
 
Thread ID: 141732 2016-02-12 05:36:00 Windows File explorer opening by itself - suspect drive connection? Chikara (5139) Press F1
Post ID Timestamp Content User
1415969 2016-02-19 14:00:00 Hmm..ok the problem has just happened again, so I know it is not that cable. I'm out of ideas now. Any suggestions? Chikara (5139)
1415970 2016-02-19 19:49:00 Whats the brand/model of the motherboard? Or laptop whatever it is

Do you use Onedrive?
Speedy Gonzales (78)
1415971 2016-02-20 01:16:00 It's a desktop, Asus Maximum VIII Hero

I do use OneDrive, yes.

One other thing I have just tried too. I physically removed that drive, and put an old drive from my old PC in there instead. Now I know by doing this it won't be accessing any data on that new drive, as nothing is mapped to it - but I was curious if I might still get the same message.
(I assume even if no data is moving, a temp loss in connectivity would still give the same message?..)
I did this last night before I went to sleep. No errors yet in the morning. Although I don't always get the errors in such a short time.

But could it possibly be a hardware problem with the physical drive itself?
Chikara (5139)
1415972 2016-02-20 01:34:00 Hmm Onedrive maybe the cause. If ccleaner is installed go to startup / scheduled tasks. Find Onedrive Auto update. Click on it / disable it

Altho this may stop if from syncing whatever. You may have to do it manually, if you've got the option
Speedy Gonzales (78)
1415973 2016-02-20 01:54:00 OK I will try that. I will put the original HD back in and then change that setting.
Is there a known issue with OneDrive, Speedy?

Edit - OneDrive has nothing to do with the drive causing these problems. It doesn't have any sync destinations there. You still think that could be the cause?
Chikara (5139)
1415974 2016-02-20 03:46:00 Well on the MS forum, people have posted about this. And it does open folders by itself, if it's running. I dont use it myself

Whatever I want to back up, I put it on another partition (which is nothing). The only things I have are updates for programs
Speedy Gonzales (78)
1415975 2016-02-22 00:18:00 OK, the problem still continues even after trying that - I really am at a loss now what to try next. Chikara (5139)
1415976 2016-04-02 10:44:00 Hi all,
I finally think I solved this problem, so I thought I would post the solution that worked for me, in case anyone else came across this thread.
I noticed that in Device Manager, I had a ASmedia SATA controller driver installed. As it was listed on the MB support page (here: ) www.asus.com I thought it was a required driver. But as the problems I was having were somehow linked to my drive, I thought I would uninstall this driver and see what happened. Worst case scenario I could just reinstall it again if I needed it.
Turns out that has seemed to solve the problem. I did this about 2 weeks ago and have not had the problem re-occur since. So it seems this driver was not necessary and somehow caused a problem or conflict.

(Question - why would that driver be listed on the MB page? In what situations would it actually be needed??)
Chikara (5139)
1415977 2016-04-02 11:02:00 Did you connect anything to those SATA ports? There's probably Intel and Asmedia SATA ports on the mobo Speedy Gonzales (78)
1415978 2016-04-02 11:13:00 When I got this build, I chose the components, but the shop that supplied the parts assembled it for me. I can't visually see the Asmedia ATA port as the videocard is blocking it from view. I could double-check closer, but I don't believe anything is connected there, no. Everything else seems to work without problems (apart from a problem when I connect my phone via USB but that can't be related - but I will post about that seperately).

But, even if anything was plugged into that port, shouldn't the system know which driver to use and when?
Chikara (5139)
1 2