System wont turn on with two mice attached. | Razer Insider

System wont turn on with two mice attached.

  • 14 April 2021
  • 0 replies
  • 6 views

I originally posted this on the Reddit weekly thread, but support has gone dark and hasn't replied to me in a week. Post: https://www.reddit.com/r/razer/comments/mhhzdg/april_technical_support_sticky/gt5xmk9?utm_source=share&utm_medium=web2x&context=3

Problem: Razer Trinity is causing No POST scenario on Maximus VIII Hero when two mice are attached.

If I try and boot with both the Trinity and any other Razer mouse the system will not complete POST. It hard locks on the Maximus splash screen.

Mobo is set to UEFI.


  • Tried with USB legacy support on, as well as off with no change


  • Disabled/Enabled USB boot


  • Two separate Maximus VIII motherboards.


  • Tried the mouse in other USB ports


  • Tried in USB 2.0


  • Tried in USB 3.0


  • Tried connected via USB hub


  • Tried connected directly to motherboard


  • Synapse is up to date, not sure how (if at all) that would affect the POST process with the OS/UEFI communication.


I have tried the following hardware combinations with the issue persisting:


  • A different Trinity (to exclude the mouse having failed)


  • Different "side panels" for the Trinity


  • Lancehead + Trinity


  • Basilisk Ultimate + Trinity


  • Naga Hex + Trinity


  • Tried swapping my black widow Elite for a Ornata to rule out the off chance its the motherboard


I reinstalled the OS (Win 10) and issue persists

System will boot fine with just the Trinity attached, but no other mouse.

System boots fine with Basilisk + Lancehead



My gut is that when two mice are attached the system is for some reason forcing the mouse to go into boot loader mode and is trying to boot off the mouse, but I can't confirm that since the system is hard locking when it occurs. If I remove the mouse when it is locked I have to do a hard reset to get the system to boot. This might also be related to the issues outlined with the Charging Dock as they seem similar:





Any idea if there is some sort of firmware update for the mouse to fix this?

This topic has been closed for comments