System Information (local)
--------------------------------------------------------------------------------

computer name: FREDPC
windows version: Windows 8 , 6.2, build: 9200
windows dir: D:\Windows
Hardware: GA-970A-D3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-8120 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17176973312 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: D:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 28/07/2015 18:58:38 GMT your computer crashed
crash dump file: D:\Windows\Minidump\072815-26785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x2, 0xFFFFF88011E0A190, 0xFFFFF88011E0A0E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 28/07/2015 18:58:38 GMT your computer crashed
crash dump file: D:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DpiGetDxgAdapter+0x2AAD)
Bugcheck code: 0x139 (0x2, 0xFFFFF88011E0A190, 0xFFFFF88011E0A0E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: D:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: The kernel has detected the corruption of a critical data structure.
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 27/07/2015 16:15:13 GMT your computer crashed
crash dump file: D:\Windows\Minidump\072715-25786-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880079A86F1)
Bugcheck code: 0xD1 (0x1E8, 0xB, 0x0, 0xFFFFF880079A86F1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: D:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Mon 27/07/2015 15:25:54 GMT your computer crashed
crash dump file: D:\Windows\Minidump\072715-23415-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x7F (0x8, 0xFFFFF88002A6EDB0, 0xFFFFF880121E9FE0, 0xFFFFF802E433483F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27/07/2015 15:20:34 GMT your computer crashed
crash dump file: D:\Windows\Minidump\072715-27783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0xFFFFF8035CF5BC90, 0x2, 0x0, 0xFFFFF80358C8D86F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25/07/2015 10:11:54 GMT your computer crashed
crash dump file: D:\Windows\Minidump\072515-30310-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802124B0A9D, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 14/07/2015 19:53:39 GMT your computer crashed
crash dump file: D:\Windows\Minidump\071415-20872-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF6E060DFDFD8, 0x0, 0xFFFFF8016D8FE94C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 02/07/2015 12:23:21 GMT your computer crashed
crash dump file: D:\Windows\Minidump\070215-22074-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF8800B22B740)
Bugcheck code: 0xD1 (0xFFFFF80100000091, 0x2, 0x0, 0xFFFFF8800B22B740)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: D:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode 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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 01/07/2015 19:35:08 GMT your computer crashed
crash dump file: D:\Windows\Minidump\070115-43181-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002BC6180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: D:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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.



On Fri 19/06/2015 07:43:52 GMT your computer crashed
crash dump file: D:\Windows\Minidump\061915-19000-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF803D5E1B227)
Bugcheck code: 0x3D (0xFFFFF803D5BBAB40, 0x0, 0x0, 0xFFFFF803D5E1B227)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: D:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check appears very infrequently.
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
--------------------------------------------------------------------------------

10 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:

atikmdag.sys (ATI Radeon Kernel Mode 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 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