--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 7/15/2014 3:36:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071514-24180-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4C3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800164D3C9, 0xFFFFF880039A0D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 Tue 7/15/2014 3:36:23 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4C3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800164D3C9, 0xFFFFF880039A0D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 Mon 7/14/2014 3:20:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071414-28080-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4613)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000D4613, 0xFFFFF88008127070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiusuário
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 Sun 7/13/2014 5:27:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071314-22417-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x7A447)
Bugcheck code: 0xD1 (0xFFFFF88102949AE0, 0x2, 0x1, 0xFFFFF8800167C447)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 Wed 7/2/2014 10:58:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-23119-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x4C3C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800164E3C9, 0xFFFFF88009FA9D20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 Wed 7/2/2014 3:17:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-18907-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xBFB61)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880014F8B61, 0xFFFFF8800319A738, 0xFFFFF88003199FA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Wed 7/2/2014 3:08:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070214-31949-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A270128, 0xFFFFF8800A26F990, 0xFFFFF800032F22A9)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver do Sistema de Arquivos NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 Wed 7/2/2014 1:11:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-27268-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5BA35)
Bugcheck code: 0xD1 (0xFFFFF8810EE5DAE0, 0x2, 0x1, 0xFFFFF8800165DA35)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 Tue 7/1/2014 12:40:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-26036-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xBE45C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880014D545C, 0xFFFFF88009B9D738, 0xFFFFF88009B9CFA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Tue 7/1/2014 3:01:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-25287-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x10A85)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000650A85, 0xFFFFF88005BFEAF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 10 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:
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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.
Facebook
Twitter
Instagram