Main Forum > General Computer Support

USB Disconnecting

(1/2) > >>

Mattaeus:
So, first of all, Iv tried A LOT of different fixes. Non have worked.

The problem is, that my Keyboard (wired), mouse (wired) and headset (USB) will all disconnect at the same time for a second, then reconnect and I have no clue why. My rig was working fine, up till about 2 and a half months ago. Then started doing this. It seems to be completely random.

Updated all drivers
Updated Bios
Uninstalled and reinstalled USB several times
Wiped drive (mostly because bios failed and I had to) and reinstalled Windows
Turned off Power saving
Waved a dead chicken over it...
MB is a MSI Gaming pro carbon, and Im running Win10.

Boggin:
It's possible that this could be caused by dissimilar metal corrosion from being plugged in a long time.

You may be able to get around this by cleaning the contacts.

Mattaeus:
Gave that a try. All the contacts are good, and I cleaned the inside as well. I wanted it to work lol, it didnt. Starting to think its the motherboard itself :/

Boggin:
Has Event Viewer or Reliability history recorded anything for when those disconnects occur ?

Mattaeus:
I believe this is it. But man, I have no clue how to read it.
Iv gone through and the time stamps seem to match up. Lucky it happened just before I came to the site, so it wasnt that hard to find lol

- System

  - Provider

   [ Name]  Microsoft-Windows-Kernel-EventTracing
   [ Guid]  {b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}
 
   EventID 3
 
   Version 1
 
   Level 2
 
   Task 2
 
   Opcode 14
 
   Keywords 0x8000000000000010
 
  - TimeCreated

   [ SystemTime]  2019-09-26T20:52:38.432530900Z
 
   EventRecordID 42
 
   Correlation
 
  - Execution

   [ ProcessID]  4
   [ ThreadID]  10864
 
   Channel Microsoft-Windows-Kernel-EventTracing/Admin
 
   Computer DESKTOP-E6HS2IB
 
  - Security

   [ UserID]  S-1-5-18
 

- EventData

  SessionName Circular Kernel Context Logger
  FileName C:\Windows\system32\WDI\LogFiles\ShutdownCKCL.etl
  ErrorCode 3221225864
  LoggingMode 41943168
  FailureReason 0

Navigation

[0] Message Index

[#] Next page

Go to full version