- Joined
- Mar 14, 2023
- Messages
- 80,608
Thanks — good work swapping receivers and using the UGreen. Two quick points before tests/instructions:
1) Confirm spare receiver on UGreen (you already did) — observe 15–30 minutes. If it’s stable, the original receiver was likely the problem.
2) Bluetooth test (fast): pair the MX Master 3 to Bluetooth and use for 10–30 minutes.
Run these three lines immediately in an elevated PowerShell right after the drop (copy/paste). They create two small files on your Desktop that you can attach here; I’ll parse them immediately and give the single remedial step:
$start = (Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB' -or $_.Message -match 'USB|usb|hub|reset|removed|disconnect|device' } | Select-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
- I can’t reliably read the System Report you attached in the previous post from my side right now. If you want me to parse it I’ll need you to either re‑attach the report file here, or paste the three small sections I list below. Once I have that I’ll extract firmware, pairing and any error entries and tell you exactly which piece is likely at fault.
- Based on the captures you already gave and your UGreen result, the evidence so far points to a per‑device radio/session problem (mouse ↔ receiver) rather than the PC’s USB controller — the UGreen fix stopping permanent disconnects is the key piece of evidence. fileciteturn77file9turn77file16
- Re‑attach the report file (paperclip / Attach files) or paste these three sections (copy/paste exactly) from the report into your reply:
1) Device / Firmware info for the MX Master 3 (firmware version shown).
2) Receiver (Unifying) firmware and serial/ID.
3) Any “Event Log”, “Errors” or “Diagnostics” section (even a few lines around any timestamps or error entries).
I’ll parse those and tell you precisely whether the report shows a device or receiver fault and whether an RMA is warranted.
1) Confirm spare receiver on UGreen (you already did) — observe 15–30 minutes. If it’s stable, the original receiver was likely the problem.
2) Bluetooth test (fast): pair the MX Master 3 to Bluetooth and use for 10–30 minutes.
- Stable over Bluetooth → Unifying link/receiver or RF geometry is the problem.
- Bluetooth also fails → mouse hardware or PC host likely at fault.
3) Cross‑host test (decisive): plug the same spare receiver + UGreen into another known‑good PC and test 10–30 minutes. - Works on other PC but not on yours → host/driver/BIOS or power settings on your PC.
- Fails on other PC too → mouse or receiver hardware fault (depending on which component follows the failure).
4) Swap receivers again quickly on the same PC (original vs spare, same port + same UGreen) and test a short time: - Original fails, spare OK → original receiver faulty.
- Both fail → likely mouse or PC host problem.
Run these three lines immediately in an elevated PowerShell right after the drop (copy/paste). They create two small files on your Desktop that you can attach here; I’ll parse them immediately and give the single remedial step:
$start = (Get-Date).AddMinutes(-10)
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match 'VID_046D|VID0A5C' } | Format-List FriendlyName,InstanceId,Status | Out-File "$env:USERPROFILE\Desktop\MouseDeviceInfo.txt"
Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$start} | Where-Object { $.ProviderName -match 'Kernel-PnP|USBHUB3|USB' -or $_.Message -match 'USB|usb|hub|reset|removed|disconnect|device' } | Select-Object TimeCreated,ProviderName,Id,LevelDisplayName,Message | Out-File "$env:USERPROFILE\Desktop\USB_Events_Last10min.txt"
- Attach MouseDeviceInfo.txt and USB_Events_Last10min.txt here; I’ll examine timestamps and tell you exactly whether it’s a host/controller reset (in which case I’ll give one specific driver/BIOS to install) or a device radio/session fault (in which case I’ll advise the swap/RMA wording).
- Parse and extract: firmware versions, pairing entries, any error lines or repeated reset messages, and the events nearest the drop time. Then give the one next action (keep UGreen, update a specific driver/BIOS, try a replacement receiver, or RMA the mouse).
- I can draft a short copy/paste RMA/support message that includes the test summary and what logs to attach; say “Draft RMA” and I’ll prepare it, but I’d only send it if the cross‑host and Bluetooth tests indicate the mouse itself is at fault.
- Re‑attach the System Report for me to parse now, or
- Run the Bluetooth / cross‑host tests and (if a drop recurs) run the two PowerShell capture commands and attach those two resulting files.
