This are the crashes I get.
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 6-10-2013 14:08:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-33353-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x23C5C)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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. CUSTOM_ERROR
On Sun 6-10-2013 10:39:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-37143-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800821D259)
Bugcheck code: 0x50 (0xFFFFF8070F1D71F8, 0x0, 0xFFFFF8800821D259, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 3-10-2013 19:02:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-26722-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D71E288, 0xFFFFF8800D71DAE0, 0xFFFFF800030B06DA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
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 Thu 3-10-2013 17:41:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-26254-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800C5859B8, 0xFFFFF8800C585210, 0xFFFFF800030E66DA)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
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 Thu 3-10-2013 15:14:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-33961-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xE3 (0xFFFFFA80115144B0, 0xFFFFFA800F2994D0, 0x0, 0x2)
Error: RESOURCE_NOT_OWNED
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 thread tried to release a resource it did not own.
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 Mon 9-9-2013 13:56:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090913-30919-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFF8A810881CA0, 0x0, 0xFFFFF8000337636C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 5-9-2013 15:54:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090513-38360-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800353F1E8, 0xFFFFF8800353EA40, 0xFFFFF80003088B02)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
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 Sun 1-9-2013 18:07:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090113-33618-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xAFA30)
Bugcheck code: 0x50 (0xFFFFF85114C67B38, 0x1, 0xFFFFF8800717CFBD, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\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 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.
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. PAGE_FAULT_IN_NONPAGED_AREA
On Thu 29-8-2013 11:26:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-33119-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20EC8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88008357EC8, 0xFFFFF880040B3568, 0xFFFFF880040B2DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 27-8-2013 13:24:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082813-27643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFFA811CC06DB8, 0x0, 0xFFFFF800030A86EB, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Tue 27-8-2013 9:12:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082713-25584-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFFA0E10CFB868, 0x0, 0xFFFFF800033831AC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Sun 18-8-2013 13:11:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081813-29796-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20EC8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88008372EC8, 0xFFFFF8800A5B8568, 0xFFFFF8800A5B7DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Sat 17-8-2013 13:34:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081813-23649-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800741D29B)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x0, 0xFFFFF8800741D29B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 15-8-2013 15:10:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-30544-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800701BFD4)
Bugcheck code: 0x50 (0xFFFFF8C42A5B1B18, 0x0, 0xFFFFF8800701BFD4, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 14-8-2013 15:49:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-33477-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9123)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031C3123, 0xFFFFF880035546B8, 0xFFFFF88003553F10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.