issues with razer huntsman mini HELP! | Razer Insider

issues with razer huntsman mini HELP!

  • 5 February 2021
  • 31 replies

ok my issue is this one

every time I start windows my computer freeze after pin input then i have to go to task manager to restart windows explorer for the system to work.

it happened just when i have the huntsman mini cause if i change keyboard don't happened
reliability log

Faulting Application Path: C:\\Program Files (x86)\\Razer\\Razer Services\\GMS\\GameManagerService.exe

Problem signature
Problem Event Name: CLR20r3
Problem Signature 01: GameManagerService.exe
Problem Signature 02:
Problem Signature 03: 5fc5fa92
Problem Signature 04: System.Management
Problem Signature 05: 4.8.4084.0
Problem Signature 06: 5dda3e36
Problem Signature 07: 8c
Problem Signature 08: 3f
Problem Signature 09: System.Management.Management
OS Version: 10.0.19042.
Locale ID: 1033
Additional Information 1: 2beb
Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3: 078b
Additional Information 4: 078b0a27cefed7847512e263dc12b78f

Extra information about the problem
Bucket ID: 7cc3713dc305dd452d9f5a3d27eb6b48 (2134523967106149192)


windows explorer

A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\\Windows\\explorer.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: explorer.exe
Application Version: 10.0.19041.746
Application Timestamp: ca234864
Hang Signature: a874
Hang Type: 134217728
OS Version: 10.0.19042.
Locale ID: 1033
Additional Hang Signature 1: a874dcbb81c64c2f212e8b48deac6aaa
Additional Hang Signature 2: 4ded
Additional Hang Signature 3: 4dedb159c4f84815d72e51a672453453
Additional Hang Signature 4: a874
Additional Hang Signature 5: a874dcbb81c64c2f212e8b48deac6aaa
Additional Hang Signature 6: 4ded
Additional Hang Signature 7: 4dedb159c4f84815d72e51a672453453

Extra information about the problem
Bucket ID: 0d875e3203746c4a6ad36dc6695c8b86 (1933009364010699654)

my system

OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor AMD Ryzen 9 3900X 12-Core Processor, 3800 Mhz, 12 Core(s), 24 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3402, 1/13/2021
SMBIOS Version 3.3
Embedded Controller Version 255.255
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product ROG STRIX X570-F GAMING
BaseBoard Version Rev X.0x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\\Windows
System Directory C:\\Windows\\system32
Boot Device \\Device\\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name DESKTOP-H2J6IRP\\ricar
Time Zone SA Pacific Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 17.5 GB
Total Virtual Memory 36.9 GB
Available Virtual Memory 19.8 GB
Page File Space 5.00 GB
Page File C:\\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

the huntasman is new
note: is the second one i got cuase the first one gave me the same issue and i send it to replace and this one is giving me the same issue

This topic has been closed for comments

31 Replies

Userlevel 7
Badge +1
Small update, I've got an information that they're aware of the issue on AMD platform on these keyboards, and they'll release fix (both for Synapse and FW update for keyboards), but they can't provide any timeline for it, when it'll be released.
So stay tuned.
Hi, disabling the HID-compliant devices seem to solve the problem with me. I have a blackwidow v3 mini hyperspeed.

If you view device manager as "devices by connection" it's a lot easier to narrow down which HID's are causing the issues. Your keyboard in it's entirety should be shown as "USB Composite Device". Navigate within this folder to locate all HID-compliant devices.
On any HID-compliant device, if you go into properties>events tab, under the information section the first thing you should see under "Device HID" is sort of a unique "id" ending with 000n (n for any number). The ones ending with 0000 seemed to be the ones causing problems for me. Disabling these fixed everything. If I connected wirelessly I had 2 HIDs that needed to be disabled, 1 if wired.

In my setup I actually have 2 identical keyboards connected, same thing with both. You can see how it looks with both keyboards connected wirelessly in device manager here :
Any update on this ? I just randomly had windows become unresponsive again, For a whole week I was using the Corsair K65 Mini, Zero issues, Plug the Huntsman Mini back in and over the last 2 days I've had random windows lock ups that needed hard reboots.
Userlevel 7
Badge +1
Any update on this ? I just randomly had windows become unresponsive again, For a whole week I was using the Corsair K65 Mini, Zero issues, Plug the Huntsman Mini back in and over the last 2 days I've had random windows lock ups that needed hard reboots.

Still waiting for some info from support, they told me, that they'll post some update when it'll be done.
Cooleo thanks for the reply.
For me everything was fine with the Huntsman Mini until the 21H1 Update of Windows was installed June/July 2021. Since then I have often a frozen Taskbar after login and I need to klick to make Windows reactive again. But even this does not solve the issue always.
When change users on Windows the issue happens in 100% of the cases and also klicking does not resolve the issue.
The FW Update to 1.12 does not change anything.