+ Reply to Thread
Page 1 of 4 1 2 3 ... LastLast
Results 1 to 10 of 36

Thread: Trouble with asmedia USB 3.0 ports, RIVE

  1. #1
    ROG Enthusiast TacticalTimbo +10
    Join Date
    Sep 2012
    Posts
    30

    Trouble with asmedia USB 3.0 ports, RIVE

    Does anybody get issues with there asmedia USB 3.0 ports randomly disconnecting/reconnecting, on their Rampage IV Extreme? I'm using 2105 btw.

  2. #2
    ROG Guru: Brown Belt HalloweenWeed +75 HalloweenWeed's Avatar
    Join Date
    Dec 2011
    Location
    Maine, USA
    Posts
    1,466

    Rampage IV Extreme Bios 2105 Issues

    They list several different fixes for your prob.
    Last edited by HalloweenWeed; 10-08-2012 at 05:18 AM.
    i7-3930K; Asus RIVE; G.SKILL Ripjaws Z 4x4GB DDR3 1866; MSI 7870 2GD5/OC; Crucial M4 SSD 256GB;
    Corsair 1000HX; Corsair H100, 4x Excalibur 120mm PWM CPU Fan p-p, AS5; SB X-Fi Titanium Fata1ity Pro;
    Dell U2412m IPS 1920x1200; Cooler Master HAF 932 case; Tripp-Lite OMNIVS1500 UPS fully Line-interactive.
    (EVGA site: ) And I have a second (wife's) computer, Eve.

    Overclocking is useless to me if it is not rock stable.

  3. #3
    ROG Guru: Comunist Dartmaul +30 Dartmaul's Avatar
    Join Date
    Jan 2012
    Location
    Moscow, Russia
    Posts
    831

    Quote Originally Posted by HalloweenWeed View Post
    Unfortunately, I think you cannot go back to 1404, srry.
    You can.
    http://rog.asus.com/forum/showthread...untry=&status=
    Quote Originally Posted by HiVizMan
    To Flash back to 1xxx.ROM, Rename 1xxx.rom to ERALL.ROM and Use USB Flashback

  4. #4
    ROG Guru: Brown Belt HalloweenWeed +75 HalloweenWeed's Avatar
    Join Date
    Dec 2011
    Location
    Maine, USA
    Posts
    1,466

    Quote Originally Posted by Dartmaul View Post
    Yeah, I just edited that out as you posted, reading that thread I linked to showed several fixes, and apparently BIOS version may not be one of them.
    i7-3930K; Asus RIVE; G.SKILL Ripjaws Z 4x4GB DDR3 1866; MSI 7870 2GD5/OC; Crucial M4 SSD 256GB;
    Corsair 1000HX; Corsair H100, 4x Excalibur 120mm PWM CPU Fan p-p, AS5; SB X-Fi Titanium Fata1ity Pro;
    Dell U2412m IPS 1920x1200; Cooler Master HAF 932 case; Tripp-Lite OMNIVS1500 UPS fully Line-interactive.
    (EVGA site: ) And I have a second (wife's) computer, Eve.

    Overclocking is useless to me if it is not rock stable.

  5. #5
    Super Moderator - Coderat Nodens +200 Nodens +200 Nodens +200 Nodens's Avatar
    Join Date
    Mar 2012
    Location
    Greece
    Posts
    4,275

    The are actually a million reasons why this could happen. In the order of probability: bad device connected (not necessarily the one that gets disconnected), bad or corrupted drivers, corrupted windows installation, bad PSU, bad Mobo, short related to USB...

    Reinstall the Asmedia drivers, run a "sfc checknow" to verify drivers and windows installation. Then start troubleshooting the devices. Use only 1 device connected. See if it still does it. If it doesn't start adding devices one by one. Also check event viewer for related errors like I/O errors or disconnection ones. If all that fails and it still happens with 1 device on a verified by sfc windows installation and reinstalled driver I'll tell you how to pull an xperf trace so I can take a look.
    RAMPAGE Windows 8/7 UEFI Installation Guide - Patched OROM for TRIM in RAID - Patched UEFI GOP Updater Tool - ASUS OEM License Restorer
    There are 10 types of people in the world. Those who understand binary and those who don't!

    RealBench Developer.

  6. #6
    ROG Enthusiast TacticalTimbo +10
    Join Date
    Sep 2012
    Posts
    30

    Can I refer to another thread I started here: http://www.overclock.net/t/1311154/r...ive-disconnect

    I've already been through a lot of trouble shooting and as you will see, I've also tried several USB devices. I did believe my troubles were solely with the front 19-pin headers and changing the front panel cable/connectors did change their behaviour...the disconnections seemed to stop altogether at the front. However I have now had a USB 3.0 HDD disconnect/reconnect at the back; obviously the issues goes a bit deeper than just a dodgy front panel cable.

    Another issue is that at start up the mouse & keyboard are unresponsive for a noticeably long while, during which time the pc is seemingly communicating with the USB 3.0 devices connected to the ports; unlike other win7 PCs I've used the auto-run boxes pop up upon start up...this suggests the chipset isn't live until well into start up (this is with full usb connectivity/normal boot enabled in bios). One thing to note is that the 32gb SanDisk extreme USB3.0 pen drive I've only just bought, seems to cause the majority of the prolonged unresponsiveness (if no usb3.0 devices are connected, there is no unresponsiveness.

    I realize that there maybe several issues at play here, this is why I ask if others are experiencing issues with there asmedia ports; the feedback would quickly allow me to gauge if this was a widespread thing, or if indeed I'm on my own. I'm shifting towards the idea that I possibly have a faulty board, or that there is a BIOS/firmware/driver issue. This wouldn't be the first time I'd of had an issue with an Asus board, in fact my two previous boards from them were faulty...a R3E and most recently the first RIVE I had was DOA with totally buggered Intel SATAIII ports!

  7. #7
    ROG Enthusiast TacticalTimbo +10
    Join Date
    Sep 2012
    Posts
    30

    Quote Originally Posted by Nodens View Post
    The are actually a million reasons why this could happen. In the order of probability: bad device connected (not necessarily the one that gets disconnected), bad or corrupted drivers, corrupted windows installation, bad PSU, bad Mobo, short related to USB...

    Reinstall the Asmedia drivers, run a "sfc checknow" to verify drivers and windows installation. Then start troubleshooting the devices. Use only 1 device connected. See if it still does it. If it doesn't start adding devices one by one. Also check event viewer for related errors like I/O errors or disconnection ones. If all that fails and it still happens with 1 device on a verified by sfc windows installation and reinstalled driver I'll tell you how to pull an xperf trace so I can take a look.
    Totally don't get the attachment system on this forum...apparentley a .txt file is an invalid file type wtf?!

    Anyway, here's the results from the sfc checknow scan:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc scannow

    Microsoft (R) Windows (R) Resource Checker Version 6.0
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    Scans the integrity of all protected system files and replaces incorrect version
    s with
    correct Microsoft versions.

    SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>]
    [/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory>
    ]

    /SCANNOW Scans integrity of all protected system files and repairs files
    with
    problems when possible.
    /VERIFYONLY Scans integrity of all protected system files. No repair operati
    on is
    performed.
    /SCANFILE Scans integrity of the referenced file, repairs file if problems
    are
    identified. Specify full path <file>
    /VERIFYFILE Verifies the integrity of the file with full path <file>. No re
    pair
    operation is performed.
    /OFFBOOTDIR For offline repair specify the location of the offline boot dire
    ctory
    /OFFWINDIR For offline repair specify the location of the offline windows d
    irectory

    e.g.

    sfc /SCANNOW
    sfc /VERIFYFILE=c:\windows\system32\kernel32.dll
    sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDI
    R=d:\windows
    sfc /VERIFYONLY

    C:\Windows\system32>sfc /verifyonly

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>


    Finally, here's a vid (sorry for quality) of the unresponsiveness at start up
    https://www.dropbox.com/s/w066946gvo...2000.41.34.mp4

  8. #8
    Super Moderator - Coderat Nodens +200 Nodens +200 Nodens +200 Nodens's Avatar
    Join Date
    Mar 2012
    Location
    Greece
    Posts
    4,275

    Windows installation checks out. It's quite possible that attaching a device on a faulty usb header to damage the board. It could be that your front panel header messed up. Can you check the PSU and also check the board doesn't make contact with anything metallic?
    RAMPAGE Windows 8/7 UEFI Installation Guide - Patched OROM for TRIM in RAID - Patched UEFI GOP Updater Tool - ASUS OEM License Restorer
    There are 10 types of people in the world. Those who understand binary and those who don't!

    RealBench Developer.

  9. #9
    ROG Enthusiast TacticalTimbo +10
    Join Date
    Sep 2012
    Posts
    30

    Quote Originally Posted by Nodens View Post
    Windows installation checks out. It's quite possible that attaching a device on a faulty usb header to damage the board. It could be that your front panel header messed up. Can you check the PSU and also check the board doesn't make contact with anything metallic?
    What are you saying, that a bad 19-pin to 2xUSB header could have damaged the board permanently? Would it have damaged the rear ports as well; I pretty sure they're on separate controllers?

    The PSU is an almost brand new Corsair AX850, so I doubt it's at fault, plus the system seems to function okay otherwise. As for the motherboard, I made sure that I installed it with the brass stand-offs that came supplied with the case and all the cables are pu coated, so I think its unlikely it a short.

    Do you still think it would be of benefit to send you that report you were talking of.

    Again I ask, does anybody out there own the RIVE and have issues with the USB 3.0 ports?

  10. #10
    Super Moderator - Coderat Nodens +200 Nodens +200 Nodens +200 Nodens's Avatar
    Join Date
    Mar 2012
    Location
    Greece
    Posts
    4,275

    Yes it's possible to have damaged the board. There is only 1 USB 3 controller. I have not seen any issues on USB 3 myself and I haven't seen any disconnection reports on the forum either apart from this one.

    The fact that the PSU is new is irrelevant. Sometimes it happens that you get something faulty right out of the box.

    Download Windows Software development kit and install the performance tools. Then run ina command window:
    " xperf -on latency -stackwalk profile -buffersize 1024 -FileMode Circular && timeout -1 && xperf -d trace.etl"

    and in another window:
    "Logman start Usbtrace -p Microsoft-Windows-USB-USBPORT -o usbtrace.etl -ets -nb 128 640 -bs 128"
    "Logman update Usbtrace -p Microsoft-Windows-USB-USBHUB –ets"

    Plug the usb 3 device and wait until disconnect. the stop both loggers by runnign these commands "Xperf –stop" and "Logman stop Usbtrace -ets"

    Compress the trace files: usbtrace.etl, trace.etl (saved in the directories you run the commands from) and C:\kernel.etl (they will be big depending on how long it took to reproduce the issue), upload them somewhere and send me a pm with the link.
    RAMPAGE Windows 8/7 UEFI Installation Guide - Patched OROM for TRIM in RAID - Patched UEFI GOP Updater Tool - ASUS OEM License Restorer
    There are 10 types of people in the world. Those who understand binary and those who don't!

    RealBench Developer.

+ Reply to Thread
Page 1 of 4 1 2 3 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts