Strange repeatable USB issue on RVE10

[jsarver]

Any of you guys having USB problems? I have done 1502 and 1503 and both require me to turn full USB initialization on to bypass q code b4 on boot. The strange thing is that I only get b4 when I restart from within windows and attempt to access the bios by pressing delete key. I never have issues from a shutdown, forced off situation, or a restart without an attempt to reach the bios.

*When the splash screen appears from a restart I hit delete, the keyboard flashes once, and the mb goes into a b4 state where it just hangs. I have no old USB devices plugged in and I have had repeatable issue with and without stock settings on ram and/or processor.

*Any ideas here guys? Is this a bad motherboard or just x99 being a total pain in the ass? Just updated from a rampage extreme to the edition 10. Old board with all identical parts didn't have this issue. Why would I only be effected on restarts and not a cold boot from an totally off state?*

[Hopper64]

Is this a Logitech keyboard? Seems like I saw something about this problem previously.

List all your hardware.

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

[jsarver]

I have a Logitech g403 wireless mouse, razer naga, razer chroma x keyboard, deathadder elite, Logitech 902 camera,firefly mousepad. Doesn't matter what combo I plug things in as soon as I start to populate two or more of the USB 3.0 slots at the top of the board this bug kicks in. Device doesn't matter as along as two or more are occupied.*

My main concern is wanting to know if this is a motherboard issue. If it's just a bug I can live with it but if it's a bad board I want to swap it and get what I paid for. What is different from a cold boot then a restart? What's handled differently that could explain this and why does full initialize fix it?*

Internal hardware
6850
16 dom plat ram
multiple ssds

No USB hubs no external hard drives *

[jsarver]

Based on all the other issues I have read about mine seems to be more about what is being initialized as opposed to a legacy USB error. My devices are all very new have no issues when all are forced to fully initialize. When I hit the delete key it causes the led keyboard lights and connected mouse lights to turn off for a second it's like the signal was losed for second then right into b4.*

[Chino]

Sounds more like a USB issue than a motherboard issue.

[rolldog]

I'm having the same issue. If I install any updates or just do a warm boot, I get the BSOD and a MACHINE_CHECK_EXCEPTION error. If I turn my PC off at the PSU and let it sit for a little while, when I turn it back on it posts with no problem. It's odd because I only get the error with a warm boot.

[Darren_Stevens]

It's not a MB problem, try turning off fast start up in Windows,*Search for and open “Power options” in the Start Menu. Click “Choose what the power buttons do” on the left side of the window. Click “Change settings that are currently unavailable.” Under “Shutdown settings” make sure “Turn on fast startup” is disabeld, uncheck the box, save changes, see if this helps.

[rolldog]

Darren Stevens wrote:
It's not a MB problem, try turning off fast start up in Windows,*Search for and open “Power options” in the Start Menu. Click “Choose what the power buttons do” on the left side of the window. Click “Change settings that are currently unavailable.” Under “Shutdown settings” make sure “Turn on fast startup” is disabeld, uncheck the box, save changes, see if this helps.

THANK YOU!
I've been dealing with this since November, and I think this finally fixed it. All morning, I've been updating my MB drivers, rebooting, and I haven't got this error once. It's very nice to be able to reboot my PC and not have to take an hour break before turning it back on. I wonder why Fast Boot cases this? I've always used Asus MBs, I've always had fast boot enabled, but I've never had this problem before. I'm just glad it's fixed!

[Darren_Stevens]

rolldog wrote:
THANK YOU!
I've been dealing with this since November, and I think this finally fixed it. All morning, I've been updating my MB drivers, rebooting, and I haven't got this error once. It's very nice to be able to reboot my PC and not have to take an hour break before turning it back on. I wonder why Fast Boot cases this? I've always used Asus MBs, I've always had fast boot enabled, but I've never had this problem before. I'm just glad it's fixed!

Glad it worked, It has littel to do with the MB, more to do with ram I think, lots of things will effect it, Fast start up works by saving the operating system state to a hibernation file, when Fast Startup is enabled your computer doesn’t perform a regular shut down, this works great but not always, there are way more qualified people on here that could explain it to you a lot better but For me the more I play around with & over clock my ram the more trouble I have with fast start up in Windows 10, also the type of OS install you have IE: UEFI OR legacy install, BIOS settings like CSM enabled or disabled can effect Win 10 Fast start up, if u have a lot of USB devices connected & the type of devices may also effect Win 10 fast start up, it can sometimes also make it hard to get into your BIOS using the del key, for me on my system I'm forever playing around updating drivers, updating software, firmware, overclocking & trying different settings, in & out of the BIOS changing CPU & RAM speeds ECT, it works perfectly with it disabled & on my system it doesn't make it boot any faster anyway, cheers. *