- Oct 27, 2014
- 41
- 0
- 4,530
Hello 
I Hope im posting this in the right place.
I've been having BSODs when playing games or watching videos for the past couple of months (Since I got this PC).
After alot of looking online for the answer, im giving up and hoping someone here could save me.
I tried using memtest which didnt find any problems.
So my PC Specs are:
Hardware: Z87-HD3, Gigabyte Technology Co., Ltd.
CPU:Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
RAM: 8MB
Graphic Card: AMD Radeon R9 290
I've ran the program WhoCrashed and this is the analysis:
I've also read online that you could help me by using my dump files, so il upload the 4 most recent ones.
https://mega.co.nz/#!mF4lkbYT!LLweVU1RgmKNhhkus6D6qfapUzBSV0TenGcXTH5_J34
I'd love it if anyone could take a moment out of his/her time and help me out.
I Hope im posting this in the right place.
I've been having BSODs when playing games or watching videos for the past couple of months (Since I got this PC).
After alot of looking online for the answer, im giving up and hoping someone here could save me.
I tried using memtest which didnt find any problems.
So my PC Specs are:
Hardware: Z87-HD3, Gigabyte Technology Co., Ltd.
CPU:Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
RAM: 8MB
Graphic Card: AMD Radeon R9 290
I've ran the program WhoCrashed and this is the analysis:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 26/10/2014 18:44:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102614-5007-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003165180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 24/10/2014 10:14:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102414-7378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 Tue 07/10/2014 15:55:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100714-5522-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 03/10/2014 06:55:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100314-5600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 01/10/2014 17:13:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-5740-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80077A98F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem 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 Thu 25/09/2014 15:53:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092514-4867-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 Tue 16/09/2014 14:21:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091614-4914-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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 Thu 11/09/2014 21:05:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-5584-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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 07/09/2014 09:12:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-4914-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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 Sat 23/08/2014 14:03:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082314-4976-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
23 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.
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 26/10/2014 18:44:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102614-5007-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003165180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 24/10/2014 10:14:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102414-7378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 Tue 07/10/2014 15:55:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100714-5522-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 03/10/2014 06:55:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100314-5600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 01/10/2014 17:13:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-5740-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80077A98F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem 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 Thu 25/09/2014 15:53:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092514-4867-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 Tue 16/09/2014 14:21:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091614-4914-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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 Thu 11/09/2014 21:05:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-5584-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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 07/09/2014 09:12:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-4914-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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 Sat 23/08/2014 14:03:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082314-4976-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28E5E)
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
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
23 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.
I've also read online that you could help me by using my dump files, so il upload the 4 most recent ones.
https://mega.co.nz/#!mF4lkbYT!LLweVU1RgmKNhhkus6D6qfapUzBSV0TenGcXTH5_J34
I'd love it if anyone could take a moment out of his/her time and help me out.
Facebook
Twitter
Instagram