cancel
Showing results for 
Search instead for 
Did you mean: 

Rampage V Windows lockup fault codes fd and 61 solved!

AquaRelliux
Level 8
Hello everyone

I would like to share some research I did on this board. I have notcied that many users seem to have problems with thier windows hanging on loading screen. This is my previous post about it:

http://rog.asus.com/forum/showthread.php?54591-Windows-boot-uo-hangs-with-fault-codes-fd-61-system-i...

Here are some more users with the same problem:

http://rog.asus.com/forum/showthread.php?53759-Rampage-V-Extreme-won-t-boot-with-2-SLI-GeForce-Titan...
http://rog.asus.com/forum/showthread.php?54976-Rampage-V-Extreme-X99-and-Thrustmaster-Warhog-HOTAS

I have seen more threads about this but I can't seem to find them now. The solution to my windows hanging seems to be disconnecting my USB 2.0 hub that goes to my Dell u2412m screen. After that the problem seems to have vanished. But I am wondering why this is happening and not every boot but just randomly. It always hangs on fd or 61 error codes when it hangs.

Really to me this board seems like it is still in the beta phase, there is so many bugs on glitches that it should not have been released. I am considering switching to EVGA since my friend has that board and it works just flawlessly even with the usb 2.0 hub on his screen. Could Asus please release a bios that fixes this? I have owned all Rampage boards since the II for x58 and I have never had so many problems like I have had with this one.

//AquaRelliux
22,488 Views
33 REPLIES 33

simfreak101
Level 7
I get teh 61 code every few boots; i am running all defaults, no overclock and have no usb devices plugged in except for a keyboard and mouse (obviously both are not powered);
So i dont necessarily think this is a DC USB issue.

simfreak101 wrote:
I get teh 61 code every few boots; i am running all defaults, no overclock and have no usb devices plugged in except for a keyboard and mouse (obviously both are not powered);
So i dont necessarily think this is a DC USB issue.


Certain codes can manifest under more than one type of scenario (device or instability) -so there is nothing conclusive either way about how one person gets a given code for failed POST or BOOT over others.

Your post is fine but there is a going trend online for people to jump into threads and say "me too", or to draw conclusions. Most of the time such posts are lacking vital info such as the parts used and when or how issues manifest.

For anyone using a legacy USB device such as older controllers, flightsticks etc: Legacy USB devices may not sit well with XHCI - those that do not will need a firmware update from the device vendor. If that is not available, then one needs to disable XHCI to get the device to work, or find an alternative device.

Raja@ASUS wrote:
Certain codes can manifest under more than one type of scenario (device or instability) -so there is nothing conclusive either way about how one person gets a given code for failed POST or BOOT over others.

Your post is fine but there is a going trend online for people to jump into threads and say "me too", or to draw conclusions. Most of the time such posts are lacking vital info such as the parts used and when or how issues manifest.

For anyone using a legacy USB device such as older controllers, flightsticks etc: Legacy USB devices may not sit well with XHCI - those that do not will need a firmware update from the device vendor. If that is not available, then one needs to disable XHCI to get the device to work, or find an alternative device.


Raja-Would putting a legacy USB device behind and updated USB 3.0 hub address the issue? I have a new Acer Gsync monitor with a USB hub that may solve the problem.
MZ790AE Bios 1801, GSkill F5-8400J4052G24GX2-TR5S, 14900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.1 Noctua Edition, Asus Strix 4090 w/ HK block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Crucial T705, Windows 11 Pro

Hopper64
Level 16
But it has always bugged me that my OC on this machine was stable with some very stressful benchmarking applications, yet it can't get into windows?? That makes no sense to me, thinking something else was going on. Then, I had a machine at default with a fresh install of windows and I still had a 61 Q code with the USB devices connected. I now have my original OC going without the USB in the equation. I will just have to watch it and report back.
MZ790AE Bios 1801, GSkill F5-8400J4052G24GX2-TR5S, 14900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.1 Noctua Edition, Asus Strix 4090 w/ HK block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Crucial T705, Windows 11 Pro

Raja
Level 13
Depends what the issues is. Disabling XHCI will revert things to legacy level. You need to do some debugging there -- see what you find and then make a post about the findings. Your first post on the previous page eluded to doing that but the subsequent posts don't contain any such info:

http://rog.asus.com/forum/showthread.php?55569-Rampage-V-Windows-lockup-fault-codes-fd-and-61-solved...

I would see that course of action through before making any further posts as nobody knows from a remote location what the issue is.

Hopper64
Level 16
My plan now is simply to watch my OC without the USB devices in keeping with AquaRelliux's findings for the next few weeks. But I am thinking long term. Plug in a legacy USB device only when needed vs. putting that device behind a USB 3.0 hub?
MZ790AE Bios 1801, GSkill F5-8400J4052G24GX2-TR5S, 14900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.1 Noctua Edition, Asus Strix 4090 w/ HK block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Crucial T705, Windows 11 Pro

Raja
Level 13
Whichever method you use, you need to see if you can pin it on the device/hub or whatever else. It's a process of elimination and repeat testing to confirm without any additional variables such as the overclock in the way.

The final post here would then contain all relevant info pertaining to the findings. If a USB issue is found the post would detail the device model plus any revision numbers (if available). There would also be info of which ports were tested and if other USB devices have an effect on the scenario or not.

Hopper64
Level 16
Don't know if this is significant. On bios 0901, sometimes the post report has the machine with 4 USB hubs and sometimes 6. I only have a keyboard and mouse connected currently. There's an external USB 3.0 hard drive, but I don't keep it powered on, so the USB socket is occupied by a device that's not running.

I know that it is recommended that the machine not be OC, but I had a 61 code like AquaRelliux is describing with no OC at all. I am now at 4.3 on this CPU with Vcore 1.24 Adaptive, passed RealBench and LinX without issue at that voltage. It has worked fine today without any problems, but I don't have any legacy USB devices installed. I will watch it like this a few days. I think AquaRelliux is right, but I need a few more days of testing. Rebooted multiple times today with no problems, and I never got to that point of flawless reboots until now with the only difference being the lack of USB devices.
MZ790AE Bios 1801, GSkill F5-8400J4052G24GX2-TR5S, 14900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.1 Noctua Edition, Asus Strix 4090 w/ HK block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Crucial T705, Windows 11 Pro

BTW-The MS FF2 joystick has been out of production for years. I doubt a firmware update is a possibility.
MZ790AE Bios 1801, GSkill F5-8400J4052G24GX2-TR5S, 14900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.1 Noctua Edition, Asus Strix 4090 w/ HK block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Crucial T705, Windows 11 Pro

Hopper64
Level 16
My machine is now stable with either multiplier 43 @ Vcore 1.220 Adaptive or 42 @ Vcore 1.170 Adaptive. I have had no 61 or F6 Q codes since removing an old, nonpowered USB 2.0 hub and the Microsoft FF2 controller from the equation. I had a few crashes when trying to reach stability with the OC which was not unexpected.

I think AquaRelliux is correct. I tried installing a 3.0 USB hub (nonpowered), but I got an F6 Q code after 2 reboots.

Is this fixable with a powered USB hub? Or disable XHCI in the bios??

This was an issue all along with USB and not my OC. I was increasing the Vcore of my OC as I thought these F6 and 61 Q codes were a sign of instability. I was causing the machine to be more unstable by increaing the Vcore when it wasn't necessary. Without the USB legacy devices, these Q codes are no longer an issue. Noticed a 61 Q code too with the machine at default but with the USB devices attached.
MZ790AE Bios 1801, GSkill F5-8400J4052G24GX2-TR5S, 14900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.1 Noctua Edition, Asus Strix 4090 w/ HK block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Crucial T705, Windows 11 Pro