Om installerat men ingen förbättring. System Information (local)
--------------------------------------------------------------------------------
computer name: GARMSTER
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: GA-970A-D3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Six-Core Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 8586776576 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 2015-05-16 00:58:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-22015-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1E946A)
Bugcheck code: 0xF7 (0x55F56A47602E6580, 0x5BCC9CD48C73, 0xFFFFD466D2205DCD, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 a driver has overrun a stack-based buffer.
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_OVERRAN_STACK_BUFFER
On Sat 2015-05-16 00:58:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1E946A)
Bugcheck code: 0xF7 (0x55F56A47602E6580, 0x5BCC9CD48C73, 0xFFFFD466D2205DCD, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 a driver has overrun a stack-based buffer.
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_OVERRAN_STACK_BUFFER
On Sat 2015-05-16 00:51:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-22765-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x883FB8)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8002251EFB8, 0x1, 0x4C)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.
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. KMODE_EXCEPTION_NOT_HANDLED
On Fri 2015-05-15 22:32:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-24734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xAB3AC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFE00119C0C005, 0xFFFFD00021434A48, 0xFFFFD00021434250)
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.
On Fri 2015-05-15 11:53:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051515-61781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000A8E912F0, 0xFFFFD000A8E91248, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\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 2015-02-10 18:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021015-26906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0xD1 (0xFFFFF804503681C0, 0x2, 0x1, 0xFFFFD00065A176B6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 2015-02-05 18:07:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020515-31296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0xD1 (0xFFFFE0013A43D430, 0x2, 0x0, 0xFFFFE0012B357AEC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 2015-02-05 16:19:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020515-24468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x1A (0x41287, 0x79, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.
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 2014-12-29 16:30:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122914-24562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFE000465708BA, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Mon 2014-12-29 14:37:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122914-27890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0)
Bugcheck code: 0xFC (0xFFFFE0001B479A88, 0x80000001C26009E3, 0xFFFFD00024940040, 0x4)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 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:
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 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.
Skickades från m.sweclockers.com
