The problem you are reporting seems hardware issue. Defective USB port precisely, but before come to that conclusion, you may need to check some things here.
1. Is USB3.0 enabled at BIOS level?
2. Did you test another USB3.0 hard drive on same ports?
The fact you are saying that you connected to front and rear panel, it seems to be a hardware problem with USB 3.0 controller but try following steps above.
My USB 3.0 controller is enabled with legacy support: https://dl.dropbox.com/u/18623997/usb.png
I tried every USB 3.0 port on my motherboard and every front USB 3.0 port but none work at USB 3.0 speeds.
I also downloaded the Intel USB 3.0 driver from Asrock and from Intel's website but none work.
The rare thing is that I can see the USB 3.0 controller in device manager and Windows reports my HDD as USB 3.0.
I am sorry for posting this late, I thought every new message was sent to my email.
De HDD inside the Verbatim is a Samsung HD204UI.
Verbatim Model # 47659
This is the only USB 3.0 device I have, I yet tried this model in a brand new laptop the Dell inspirion 15R with Intel HM77 chipset but it also doesn't work at superspeed, while it is plugged in the USB 3.0 superspeed port.
I am sure Dell provided this laptop with the best drivers and everything was preinstalled so could not have messed up anything.
I think this drive is incompatible with Intel USB3.0 controllers.
I will try to test it on a Asmedia chipset soon.
I bought myself a WD My Book Essential USB 3.0, and it works at both computers at USB 3.0 speeds!
My Verbatim still doesn't work on my computers but it does work with the showmodel PC's (Realtek USB3.0 controller) in the store.
And it does work on a PC off my friend with Asmedia USB 3.0 controller.
I think I found a solution, although it isn't a real solution.
Because my Verbatim HDD was full with obsolete back-ups I did a full format, after that I did new back-up of my system and saw that the write speed was above 100MBps!
But after 100GB the transfer speed slow down again to USB 2.0 transfer speeds.
This issue appears to be Verbatim's fault and not Intel's.