On Thu 12/22/2016 12:37:25 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122216-5812-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF80B01304670)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF80B01304670)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Thu 12/22/2016 12:37:25 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x104670)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF80B01304670)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sat 12/17/2016 12:07:22 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121716-8937-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF80F7AE8C9CC)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF80F7AE8C9CC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sat 12/3/2016 12:21:15 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\120316-5843-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF801BCEF4670)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF801BCEF4670)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sat 11/19/2016 1:35:36 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\111916-5781-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF804A2534670)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF804A2534670)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.