Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: several lots of BSOD, about 70 a day!

17 May 2012   #1
aayushagra

Windows 7 ultimate x32
 
 
several lots of BSOD, about 70 a day!

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.

Code:
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.


My System SpecsSystem Spec
.
17 May 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Re 0x101
Please refer the link below...


STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
My System SpecsSystem Spec
Reply

 several lots of BSOD, about 70 a day!




Thread Tools




Similar help and support threads
Thread Forum
Lots of BSOD -.-
Windows 7 Original OS on Laptop OEM Version System if three months old Reformatted two months ago due to BSOD's Not sure BSOD's are showing in the rar I attached, one was caused by "overclocking" but BIOS defaults to 2% OC, tried with 0% OC and still BSOD's with the same...
BSOD Help and Support
Lots of bsod
I've been getting lots of bsod, i just reinstalled window 7 again and still get bsod. I attached the files. And Is Windows 7 . . . - x86 (32-bit) or x64 ? X64 the original installed OS on the system? Nope an OEM or full retail version? I got the os from my college - OEM = came...
BSOD Help and Support
Please Help...lots of BSOD's..Thank you!
I bought this laptop not too long ago and am getting a lot of crashes. Ive attached the required documents...and am in need of some help. I dont know what to do at this point and it crashes quite frequently and its really frustrating. Thank you so so so much in advance!!! Windows 7 Home x64...
BSOD Help and Support
Lots of BSOD & Hungup - Lots of Event17 WHEA-Logger
Hello everyone I've been getting this error again and again, and my computer is hungup or BSOD after awail...:mad: Do you know what can I do to fix it? Or what the problem is?? Thank you!! Asrock X58 Supercomputer bios 3.10 i7 920 (bloomfield) @2.67ghz -1.128vol.
BSOD Help and Support
Lots of BSOD's
Last week my computer died on me. I thought the Power supply was the culprit unfortunately it had also fried the motherboard so I replaced that, the cpu and memory. New settings can be seen in the system specs. With the new system I started to get a lot of BSOD's some of them were the 'irql no les...
BSOD Help and Support
Lots of BSOD's, seems all different causes. Help!
I have been experiencing a number of crashes since I installed Windows 7. I tried to teach my self a little about debugging but not enough it seems to solve my problems. The causes of the crash seem to be "irq not less or equal" with different culprits every time. I have checked to make sure...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:56.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App