Jump to content
Corsair Community

Issue with Flash Voyager USB 3.0 64GB.


Svarog

Recommended Posts

First of all, i know Haswell has a USB 3.0 bug, but this was only suppost to happen when coming OUT of the Sleep Mode. Since i'm NOT USING Sleep Mode at all i don't know what's going on.

 

Devices used:

 

Flash Voyager USB 3.0 64GB

Flash Voyager USB 2.0 16GB

WD Elements USB 3.0 HDD 1TB

Gigabyte Z87X-OC (Bios F3)

Front Panel USB 2.0 and 3.0

Back Panel USB 2.0 and 3.0

 

What's happening:

 

When i plug in my Flash Voyager USB 3.0 in one of my USB 3.0 ports and start transfering files to it after about 10-15 seconds the Flash Drive disappears from the list. Windows pops up a message that the location is no longer available. The drive still shows up Device Manager but there arn't any errors. When i use the same Flash Voyager USB 3.0 in a USB 2.0 port and do the same, it's working as it should.

 

Using the Flash Voyager USB 2.0 in one of the USB 3.0 ports and transfer files works just fine, same for the WD Elements USB 3.0 HDD.

 

So what's going on? Haswell or Flash Drive problem?

Link to comment
Share on other sites

I tried the F4 Bios aswell, but that didn't make any difference.

 

Transfering files FROM the Flash Drive to somewhere else works fine while it's connected to a USB 3.0 Port.

 

The Flash Drive itself works just fine so i'm guessing it's a conflict between Haswell and the Flash Drive while trying to transfer.

Link to comment
Share on other sites

Gonna leave this for what it is.

 

It's been 5 days now since i have posted here and not a single reaction from the support. If this is how Corsair Support works ill make sure to NEVER EVER buy a Corsair product again.

Link to comment
Share on other sites

  • Corsair Employees

I am sorry but there is someone else reporting the same issue on this series of MB. I would suggest checking with Gigabyte for the latest MB USB Controller driver.

But if you can test the flash drive on another system using an Intel USB controller that will help to verify if it is a problem with the drive or with the MB Controller driver?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...