My games crashing and windows blue screening

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Diego_22

Prominent
Mar 21, 2017
49
0
530
My games are crashing and windows is too. My CPU is not overheating and neither is my graphics card. Please tell me how to send u guys my dmp files thank you
 

Diego_22

Prominent
Mar 21, 2017
49
0
530
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_GetHciMn+0xFDC6)
Bugcheck code: 0xFE (0x5, 0xFFFFAF0FADD7F1A0, 0x80861C26, 0xFFFFAF0FAEF77C38)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.

 

Diego_22

Prominent
Mar 21, 2017
49
0
530
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
 

Diego_22

Prominent
Mar 21, 2017
49
0
530
Got these:

crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltReleaseFileNameInformation+0x34)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80E4F038E14, 0xFFFFDB800B32A7A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.



On Fri 9/29/2017 7:23:48 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\092917-30906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x19 (0x20, 0xFFFF8801C32D4500, 0xFFFF8801C32D4590, 0x4090019)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.