several lots of BSOD, about 70 a day!

[aayushagra]

Okay, the problem did not start recently.

i am having this problem since almost a year ago when i was running xp, but it was very rare and over the recent few months the occurances have multiplied to a extreme amount.

i get several different form of system hangs, followed sometimes by BSOD's

1. The PC may just freeze forever(Sometimes followed by a BSOD)
2. The PC freezes and gives off a BZZZZZZZZZZZZZZZZZZZZZ sound on the voice output.(most frequent of the three)(Sometimes followed by a BSOD)
3. A clear BSOD just pops up

I downloaded whocrashed and it says all sorts of different causes, but the common cause is the clock interrupt watchdog timeout not recieved during allocated time.

This is getting more and more frequent, 2 days ago i got it about every 30 minutes, now im lucky if 10-15 mins dont pass by with me having to restart.

This is ofcourse more frequent while playing video games or watching media, but it is so common that video games are just unplayable.

On Thu 17/05/2012 4:31:45 AM GMT your computer crashed
crash dump file: E:\Windows\Minidump\051712-24460-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF86305120, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: E:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time. 


On Thu 17/05/2012 4:31:45 AM GMT your computer crashed
crash dump file: E:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF86305120, 0x6)
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. It is suggested you look for an update for the following driver: ntkrpamp.exe . 
Google query: ntkrpamp.exe CLOCK_WATCHDOG_TIMEOUT




On Thu 17/05/2012 3:55:35 AM GMT your computer crashed
crash dump file: E:\Windows\Minidump\051712-21200-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x59A7) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF86229120, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: E:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time. 


On Wed 16/05/2012 1:52:22 PM GMT your computer crashed
crash dump file: E:\Windows\Minidump\051612-16848-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF807F1120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: E:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time

I updated the chipset graphics and audio drivers aswell.

 

[JMH]

Re 0x101
Please refer the link below...


http://www.sevenforums.com/crash-lo..._watchdog_timeout-troubleshtg.html#post567135