Crash Dump Analysis
________________________________________
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 1/23/2017 4:37:57 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\012317-5562-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F665)
Bugcheck code: 0x19 (0x20, 0xFFFF8F8ED7FAA420, 0xFFFF8F8ED7FAA440, 0x4020008)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Mon 1/23/2017 4:37:57 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6BF3)
Bugcheck code: 0x19 (0x20, 0xFFFF8F8ED7FAA420, 0xFFFF8F8ED7FAA440, 0x4020008)
Error: BAD_POOL_HEADER
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).
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: mwac.sys .
Google query: mwac.sys BAD_POOL_HEADER
On Sun 1/22/2017 11:39:14 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\012217-5281-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F665)
Bugcheck code: 0x19 (0x20, 0xFFFFDF87A8D44DB0, 0xFFFFDF87A8D44DD0, 0x4020008)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Sun 1/22/2017 11:32:43 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\012217-5250-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F665)
Bugcheck code: 0x19 (0x20, 0xFFFFAB0005DF9940, 0xFFFFAB0005DF9960, 0x402000C)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Sun 1/22/2017 11:20:20 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\012217-5203-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F665)
Bugcheck code: 0x19 (0x20, 0xFFFFD30E0E1D2300, 0xFFFFD30E0E1D2320, 0x402000D)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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
________________________________________
8 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
mwac.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.