Razer Huntsman Mini - Explorer.exe Hanging

Hey guys,

Bought a Huntsman mini early Jan as a treat to myself for my birthday, been enjoying it for the most part other than the fact that the keyboard appears to be causing my windows explorer and windows in general to hang.

I have just contacted support about this but wanted to see if anyone else has experienced the same.

So the issue, after sign in, explorer.exe crashes and restarts immediately, only when the keyboard is plugged in, I'm on the latest Win10 20H2 build. Fresh install of windows too so no funky business there.

After explorer restart it appears to work fairly well, however during gaming after a random period of time (could be instant could be after 12 hours, the pc will just hang and crash. Doesn't happen with my old keyboard.

If I unplug and re-plug the keyboard at any point (found while I testing it) it will cause windows explorer to crash and I have to manually restart it in task manager.

Now my specs are:
CPU: Ryzen 5 3600
MB: MSI B450i Gaming Plus Ac
GPU: RXT3080 FE
Ram: Corsair Vengeance 16GB

I have however just gone and plugged it into my little brother W10 Machine on an old 4th gen i5 and i can't seem to replicate the issue there. (did not install synapse however)

I have removed and re-installed driver and synapse with no luck I also done the same with the keyboard driver including a rollback. Can anyone shine some light on what could be going on?
Any other keyboard works fine, just this huntsman causing the issue.

 

Tried without synapse installed?
Can you post a screenshot of the error (from windows event viewer)?

 

Sure! The ones I attached are the explorer.exe and device related ones it seems. Since the device set up manager error only appears with the k/b plugged in.

 

Yes, I have the exact same issue as you. There is multiple threads on this problem. All we keep hearing for months is they are aware of the issue but no ETA. It should not take months to correct a software issue. The keyboard itself is great, but I don’t know if I want to sit and wait for a company that apparently has software development issues.

 

Deactivate all "HID compatible devices" in the "device manager" and restart. Problem fixed! Now, wait a new firmware

 

Just thought I'd update this thread. As of last night I had a reply from Senior support team from my ticket and I was asked to update the firmware to the new firmware (1.12.00) and after a quick restart it appear that has fixed the initial issue of explorer.exe crashing on start up! I'll keep you guys posted if i get any crashing in game.

 

I received a link to the updated firmware as well. However, my keyboard is saying it's already installed and I still have the issue. I keep getting the same dumb questions over and over from support that I've already stated multiple times in my ticket. This is becoming more work than it's worth, to be honest. Sad considering all my peripherals are Razer just sort of happened over the years. Although this is my first bad experience doesn't help its been with the second most expensive Razer product I have.

 

Hi, can you send me the link for the new firmware ?

Thank you

 

maybe it's the same firmware because they didn't say anything and in the synapse software update recently they didn't fix anything from hunstman mini lineup

 

Hey guys, the firmware was different from the firmware on the support documentation so could be unreleased firmware that they are still testing. But in hope it helps others this is the link that support provided me: https://rzr.to/XmKWq it updated the firmware to 1.12.00 which was different to what mine came with from new purchased around late Jan.

Hope it works for you guys.

 

Thank you !

 

I didn't have an issue until I updated the firmware to 1.0.1, or whatever is found here:
Firmware installation instructions (razerzone.com)

I'm assuming the newer keyboards ship with this firmware and that's what's causing issues.

I will give the newer firmware that was mentioned in this thread and report back.

EDIT: I've ran the updater and rebooted, shutdown & booted my machine a few times. It appears that the Firmware 1.01 was the culprit.