Hello, first time posting here and I'm not sure if this is the right area of the forums. I've tried searching everywhere, but I can't find a solution. I have an issue with my mouse that keeps freezing for a couple of seconds and I can't figure out why. It makes the sound that occurs when plugging in a usb device.
Here's the only thing I could find in Event Viewer when this happens:
Diagnostic module {282396b2-6c46-4d66-b413-70b0445df33c} (%SystemRoot%\system32\diagperf.dll) detected a problem for scenario {186f47ef-626c-4670-800a-4a30756babad}, instance {d86a92b6-54fe-461b-a96b-661523f3b7f6}, original activity ID {00000000-0000-0000-0000-000000000000}.
Diagnostic module {282396b2-6c46-4d66-b413-70b0445df33c} (%SystemRoot%\system32\diagperf.dll) started troubleshooting scenario {186f47ef-626c-4670-800a-4a30756babad}, instance {d86a92b6-54fe-461b-a96b-661523f3b7f6}, original activity ID {00000000-0000-0000-0000-000000000000}.
Diagnostic module {282396b2-6c46-4d66-b413-70b0445df33c} (%SystemRoot%\system32\diagperf.dll) finished troubleshooting scenario {186f47ef-626c-4670-800a-4a30756babad}, instance {d86a92b6-54fe-461b-a96b-661523f3b7f6}, original activity ID {00000000-0000-0000-0000-000000000000}. No resolution was set by the diagnostic module.
It's the same 3 messages every time and they're all logged at the same time. I can post the XML view of these if needed, but I didn't want a big wall of text that might've been unnecessary.
Here's the only thing I could find in Event Viewer when this happens:
Diagnostic module {282396b2-6c46-4d66-b413-70b0445df33c} (%SystemRoot%\system32\diagperf.dll) detected a problem for scenario {186f47ef-626c-4670-800a-4a30756babad}, instance {d86a92b6-54fe-461b-a96b-661523f3b7f6}, original activity ID {00000000-0000-0000-0000-000000000000}.
Diagnostic module {282396b2-6c46-4d66-b413-70b0445df33c} (%SystemRoot%\system32\diagperf.dll) started troubleshooting scenario {186f47ef-626c-4670-800a-4a30756babad}, instance {d86a92b6-54fe-461b-a96b-661523f3b7f6}, original activity ID {00000000-0000-0000-0000-000000000000}.
Diagnostic module {282396b2-6c46-4d66-b413-70b0445df33c} (%SystemRoot%\system32\diagperf.dll) finished troubleshooting scenario {186f47ef-626c-4670-800a-4a30756babad}, instance {d86a92b6-54fe-461b-a96b-661523f3b7f6}, original activity ID {00000000-0000-0000-0000-000000000000}. No resolution was set by the diagnostic module.
It's the same 3 messages every time and they're all logged at the same time. I can post the XML view of these if needed, but I didn't want a big wall of text that might've been unnecessary.
Facebook
Twitter
Instagram