the problem only happens when i am gaming after 10 seconds when the match starts the mouse is still on but not responding to my moves? after some seconds windows 10 crash saying critical process died, sometimes doesn't say what the problem is and the pc just shuts down and if i try to turn it on it wont do anything unless i turn off the psu and then turn it back on,
before writing this i was playing and the mouse didn't respond but the pc didn't BOSD or turn off because it didn't last more than 5 seconds but it was doing it for almost 1 minute then it stopped and i could play the entire match with no problem the game doesn't freeze when this is happening,
yesterday i had a BOSD but it was an error about the USB and both the mouse and the kb turned off and seconds later windows 10 bsod but i don't remember the name of the error it was usb. something
i'm trying to upload the memory.dmp in drive it wont let me
if i get better connection i will upload it but for now this is all i have
Problem Event Name: BlueScreen
Code: ef
Parameter 1: ffff90898fa6c7c0
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_15063
Service Pack: 0_0
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffff90898fa6c7c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3c768869-2104-477e-b0db-caa59f1abe34.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xffffe48724036a18, 0xffffffffc0000185, 0x00000000bcbcc860, 0xfffff80ed8419ee4). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 12d7e8b4-4833-4cbd-ae8f-c600e05e6f03.
edit
On Wed 7/26/2017 8:01:31 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\072617-64937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xEF (0xFFFF90898FA6C7C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/26/2017 8:01:31 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x795)
Bugcheck code: 0xEF (0xFFFF90898FA6C7C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Mon 7/24/2017 4:11:27 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\072417-48312-01.dmp
This was probably caused by the following module: usbccgp.sys (usbccgp+0x29EE4)
Bugcheck code: 0x7A (0xFFFFE48724036A18, 0xFFFFFFFFC0000185, 0xBCBCC860, 0xFFFFF80ED8419EE4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\usbccgp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Common Class Generic Parent Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
ntdll.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
here is the 3 mini dump files
https://drive.google.com/open?id=0BzEc79JEfPhiQTRkaGF6QzhQNW8
before writing this i was playing and the mouse didn't respond but the pc didn't BOSD or turn off because it didn't last more than 5 seconds but it was doing it for almost 1 minute then it stopped and i could play the entire match with no problem the game doesn't freeze when this is happening,
yesterday i had a BOSD but it was an error about the USB and both the mouse and the kb turned off and seconds later windows 10 bsod but i don't remember the name of the error it was usb. something
i'm trying to upload the memory.dmp in drive it wont let me
if i get better connection i will upload it but for now this is all i have
Problem Event Name: BlueScreen
Code: ef
Parameter 1: ffff90898fa6c7c0
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_15063
Service Pack: 0_0
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffff90898fa6c7c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3c768869-2104-477e-b0db-caa59f1abe34.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xffffe48724036a18, 0xffffffffc0000185, 0x00000000bcbcc860, 0xfffff80ed8419ee4). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 12d7e8b4-4833-4cbd-ae8f-c600e05e6f03.
edit
On Wed 7/26/2017 8:01:31 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\072617-64937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xEF (0xFFFF90898FA6C7C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 7/26/2017 8:01:31 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x795)
Bugcheck code: 0xEF (0xFFFF90898FA6C7C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Mon 7/24/2017 4:11:27 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\072417-48312-01.dmp
This was probably caused by the following module: usbccgp.sys (usbccgp+0x29EE4)
Bugcheck code: 0x7A (0xFFFFE48724036A18, 0xFFFFFFFFC0000185, 0xBCBCC860, 0xFFFFF80ED8419EE4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\usbccgp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Common Class Generic Parent Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
ntdll.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
here is the 3 mini dump files
https://drive.google.com/open?id=0BzEc79JEfPhiQTRkaGF6QzhQNW8