BSOD once a day. Both ingames and out of games

Hello, Sakzi. I have looked at your dump files. Both list the same cause. First I would like you to put your detailed system specs in a better place.

Code:

use !analyze -v to get detailed debugging information.
BugCheck 139, {3, fffff8028814a5d0, fffff8028814a528, 0}
Probably caused by : USBXHCI.SYS ( USBXHCI!Isoch_Transfer_CompleteCancelable+b5 )
Followup: MachineOwner

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, fffff8028814a5d0, fffff8028814a528, 0}
Probably caused by : USBXHCI.SYS ( USBXHCI!Isoch_Transfer_CompleteCancelable+b5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff8028814a5d0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff8028814a528, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

That is the USB XHCI Driver (USB Extensible Host Controller Interface)






I would like to try a couple of things first. Please uninstall all of the MSI Utilities you have installed. You are receiving several errors from them.

Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.