I keep getting this errors too. But mostly getting the Clock_watchdog error
I just updated my drivers with driver genius. and installed the current windows update.
I uploaded the current dump files
http://www.sendspace.com/file/wqf7xs
I just updated my drivers with driver genius. and installed the current windows update.
I uploaded the current dump files
http://www.sendspace.com/file/wqf7xs
On Tue 12/4/2012 10:45:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120412-13437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF8800325E180, 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 Tue 12/4/2012 10:13:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120412-16578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF8800325E180, 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 Tue 12/4/2012 8:44:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120412-16703-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x2600)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88006B53600, 0x0, 0x8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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.
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 12/4/2012 8:31:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120412-16796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF880032D1180, 0x3)
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 12/4/2012 8:25:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120412-17140-01.dmp
This was probably caused by the following module: intelppm.sys (0xFFFFF88006BE3977)
Bugcheck code: 0x50 (0xFFFFF880080E3000, 0x0, 0xFFFFF88006BE3977, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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.
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 12/4/2012 5:45:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-16562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xA (0x2800000033F, 0x2, 0x1, 0xFFFFF8029DCB47DA)
Error: 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 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 Mon 12/3/2012 10:19:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-5625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF88002A5E180, 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 Mon 12/3/2012 8:49:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-8546-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80028CE7040)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF88000A5E180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT
On Mon 12/3/2012 8:49:08 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80028CE7040)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFF88000A5E180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT