The G75VW USB 3.0 is Junk. Can't see purchasing the the G75VX or G75JX .

[emurach]

I tested my ARECA ARC-5040 box on the G75VW and the FIT-PC mini computer.

It's clear any type of Data push on the G75VW USB 3.0 bus and it locks up hard. (With the supplied and newest drivers). (Maybe there some hidden firmware fix for the Intel XHCI Controller). The owners have been hosed.

Mini Computer takes it fine. I have a few other issues with the TI USB 3.0 chip on the mini computer. But not data lockups. I see the fault is with ASUS and most likely their firmware.

I paid a lot of good money for this laptop. So far: Bad sound chip, dumb sub wolfer, they cripple thunderbolt, a mouse pad defect, and not working USB 3.0. And a lack of Win7 UASP. I just want to cry here.

The only way I see ASUS selling me the next G75xxxxx is to give an honest to god SAS and two External MINI SAS ports. Its the only way the owners are ever going to see high speed hard drive access in an external raid box.

Can't justify directing any more of the spending with ASUS. They're just not fixing the issues here. Two words Quality Control.

[john_from_ohio]

No problems at all with moving major amounts of data via usb 3 on my G75VW BBK5 ... running win 7 pro.

Nice backup performance ... it just flies!

[rewben]

here is my transfer speed using usb 3.0 external enclosure (7200rpm hdd), w8 with ms' built-in usb3.0 driver:


to me, that's fast enough. note that the source hdd might also contribute to the transfer speed, among other things.

if i used usb 2.0 enclosure, it will bring the speed down to around 30MB/s.

[emurach]

Ya that Win8 speed with its usb stack looks good in the picture. My question is the intel xhci stack drivers on win 7 platforms working and getting the same results as win 8 xhci stack. If load a win8 cd and do a speed test i'll have smoking gun to wether its hardware or software causing my issue. so far I've rolled bios versions up and down, tried different intel xhci driver versions and tried different usbstor.sys versions with no luck. It locks up the on pushing data to my raid box. Yet the raid box works my mini computer which uses the tti tusb7320 xhci stack. Only thing left to try is a whole nother usb xchi stack not made by intel. ie win 8.

[emurach]

Ok, done more testing. The G75VW usb 3.0 Ports are working. I tried a APICORN USB 3.0 SATA Wire 2.5 cable with Hitachi 2.5 5400 RPM 160GB and my SAMSUNG PM830 SSD. No USB 3.0 Drop outs.

I only get drop outs using the ARC-5040-1 Revision 1.1 Raid box which uses the JMICRON JMS539 chip.

Given all my testing on friday. Most likely not the cable, or speed, or signal breakdown. I think it a comminucation command issue between the two chips. The JMS539 and the Intel XCHI embedded controller. Most likely on the JMS539 side. The JMS539 is pre spec whereas the intel XCHI embedded is SPEC. I've emalled ARECA and asked for company to company inquiry if there is higher firmware then the one they already provided me which is highest found on the net. Originally the ARC-5040 would not even connect right prior to that JMS539 firmware upgrade.

Fridays testing also tested the Intel XHCI against WIN 8 XHCI stack. Got 15% better xfers in Win 8 XCHI Stack when tested in Crystal Mark.
Not ready to switch to win 8 yet. Did notice the install on Blank hard drive installed MBR vise UEFI. But my CD didn't boot UEFI either. Maybe thats why. Have to look in to that next weekend. I'll make sure my linux cd or win 7 cd can still boot up uefi on this 233 newest bios first.
It most like the win8 rtm cd image i was using for the XCHI tests was missing UEFI boot.

[emurach]

Ok. Issue has been fixed the Asus G75VW USB 3.0 is not junk. It was all Jmicron JMS539 firmware And I now have the solutuion.

My Areca ARC-5040 Raid Box is now working in full USB 3.0 with all 7 Volumes and Have an idea as to why the first JMS539 firmware update created the drop out issue in the first place with multiple volumes.

See ARECA sent me FwUpdateTool_v1_16_00_T2.exe and JMS539_PM_255.31.3.41.22_20100805.BIN

However, their bin was 37K in size like all others on the web. The Whole firmware area is 60K + 4K of NVRAM = 64K. ARECA's bin didn't update the whole Firmware area.
I bet there was stuff unchange in the NVRAM area on the update.

I finally got though to JMICRON in Taiwan. They sent me JMS539FwUpdateTool_v010.zip (unzipped: JMS539FwUpdateTool_v010.exe) (ie: Firmware 255.00.03.00.11) the lastest firmware for the end user. This fixed my usb 3.0 drop issue and I had good speed but created a new issue.
I now had only one volume vise seven in my Raid Stack. But it proved the connection drops were cause by the firmware.

Once I was done testing JMS539FwUpdateTool_v010.zip, I re-installed the 37K JMS539_PM_255.31.3.41.22_20100805.BIN ARECA had originally sent me to correct the "Device Failed to Load Code(10)" error in Windows 7 between the JMS539 bridging chip and the Intel XHCI USB 3.0 embedded controller. I Retested the Drive stack with Crystal Disk Mark 3.0.4, and low a behold the connection drop issue was gone. And all 7 of my raid volumes are working.

Here's the crystal mark scroes
-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

Sequential Read : 151.528 MB/s
Sequential Write : 173.147 MB/s
Random Read 512KB : 17.702 MB/s
Random Write 512KB : 48.779 MB/s
Random Read 4KB (QD=1) : 1.094 MB/s [ 267.2 IOPS]
Random Write 4KB (QD=1) : 2.100 MB/s [ 512.6 IOPS]
Random Read 4KB (QD=32) : 1.073 MB/s [ 262.0 IOPS]
Random Write 4KB (QD=32) : 2.143 MB/s [ 523.1 IOPS]

Test : 1000 MB [J: 55.6% (1035.8/1862.5 GB)] (x9)
Date : 2013/02/26 4:48:34
OS : Windows 7 Ultimate Edition SP1 [6.1 Build 7601] (x64)


Now this is important too a great many people with those External USB 3.0 Dual Slot port Drive docks using the JMS539.

My chip is:
JMS539
1012 LGBA1 A
5722U0012

First update the dock with JMS539FwUpdateTool_v010.zip . It re-writes the whole 64K firmware. You only get one volume. But, you fix the NVRAM area data. Then re-install the 37K JMS539_PM_255.31.3.41.22_20100805.BIN on top of that and you DOCK IS MOST LIKELY FIXED for dual hard drive support without connection drop outs just like my RAID STACK is now.