Sign in with
Sign up | Sign in
Your question

BSOD Help please

Tags:
  • Blue Screen
  • Processors
  • CPUs
October 10, 2014 11:10:08 AM

Hello guys,

I'm having some problems with a BSOD. The first time it crashed today was absolutely random but I have a program called "WhoCrashed" so I verified it and it said something about a secondary processor of a multi processor. This lead me to think about some problems I encountered a few months ago where everytime I started prime95 my PC crashed instantly. So I tried again to do that, I started prime95 and cinebench and unforunately it started crashing again. So I am thinking that there is a hardware related problem with my i7-2600k. It is not overclocked, only the turbo boost is enabled.

Can you guys think of what may be the reason ? I hope it is not problem related but I really don't know.
Here is the link where I attached the minidumps: http://we.tl/K307uVgw3I
Thank you very much for your help and support.

Here is what the my program called WhoCrashed says about the minidumps:

On Fri 10/10/2014 4:00:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101014-15272-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 10/10/2014 4:00:20 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Fri 10/10/2014 3:53:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101014-11622-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 10/10/2014 3:47:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101014-13603-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003102180, 0x6)
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 10/10/2014 2:41:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101014-16239-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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.

More about : bsod

!