DeathAdder V2 causes B4 boot erorr / hangs before WIN10 load | Razer Insider
Skip to main content

DeathAdder V2 causes B4 boot erorr / hangs before WIN10 load

  • October 14, 2021
  • 1 reply
  • 112 views
M
Bought a shiny new DeathAdder V2 a few days ago. Unfortunately it seems that it causes the PC to hang with a B4 motherboard error code, just before loading into windows. To fix have to hard shut down the PC via button, start it again, which seems to allow it to boot into windows. Quick google search shows that this is a known issue which hasn't been fixed yet. What I have tried: (Mouse has latest firmware. PC motherboard is Maximus VII Ranger) - Reinstall chipset drivers on motherboard (inc USB drivers) - Messed around in bios with various legacy usb / uefi power / boot settings - Installed synapse, tried different settings, and deleted it If I plug in the old DeathAdder Elite - everything works fine, so it is 100% that DeathAdder V2 is causing the boot error / hang. Been using a Razer product for a mouse, as long as I remember, first time there is a problem. Anyone else come across this / found any solutions?
Did this topic help you find an answer to your question?
This topic has been closed for replies.

1 Reply

Razer.Speedcr0ss
Mafiah
Bought a shiny new DeathAdder V2 a few days ago. Unfortunately it seems that it causes the PC to hang with a B4 motherboard error code, just before loading into windows. To fix have to hard shut down the PC via button, start it again, which seems to allow it to boot into windows. Quick google search shows that this is a known issue which hasn't been fixed yet. What I have tried: (Mouse has latest firmware. PC motherboard is Maximus VII Ranger) - Reinstall chipset drivers on motherboard (inc USB drivers) - Messed around in bios with various legacy usb / uefi power / boot settings - Installed synapse, tried different settings, and deleted it If I plug in the old DeathAdder Elite - everything works fine, so it is 100% that DeathAdder V2 is causing the boot error / hang. Been using a Razer product for a mouse, as long as I remember, first time there is a problem. Anyone else come across this / found any solutions?
That's a bummer. Is the mouse firmware version is on 1.02.00_r1? Does the behavior happen while the mouse is connected to another USB port or computer? Please reset the mouse via Razer Synapse 3.0's settings and see if that helps. I’ll be locking this thread now. Feel free to send me a PM anytime or visit our self-help options should you have other questions or concerns.
CookiesCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings