| Windows 7: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg |
13 Feb 2010
|
#1 | | Win7 x64 + x86 Southeastern CT, USA |
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg Info on the STOP 0x101 error: BSOD Index
Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-d...tml#post356791 )
Here's another good article: http://www.sysnative.com/forums/show...x101-Bugchecks Quote: What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...) ?I wonder about CPU defect also)
- H2SO4 So, check the drivers ( http://www.carrona.org/verifier.html )
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests Quote: Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/ Quote: FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit Try this free stress test: Free Software - GIMPS Quote: Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.
Recently it was found (here: http://www.sevenforums.com/crashes-d...ml#post1869800 ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy to do and it may fix things). Thanks to writhziden for pointing this out!
Last edited by usasma; 23 May 2012 at 05:38 AM..
Reason: added SFC.EXE recommendation - thanks to writhziden!
| My System Specs |
| System Manufacturer/Model Number Home built (x64), Lenovo x61s Tablet, Samsung Netbook OS Win7 x64 + x86 CPU Intel i7 920, other Intel chips, and the Atom in the netbook Motherboard Asus P6T Deluxe Memory 12 gB; 4 gB Lenovo; 1 gB Samsung netbook Graphics Card ATI 4870 Sound Card Yes, I have one of these Monitor(s) Displays 32" Sharp Aquos TV Screen Resolution 800x600 - I have vision issues Keyboard Microsoft Natural Mouse Logitech Trackman PSU 1000 watt (can't recall the brand) Case Antec 300 Cooling Big honking cooler that was rated highly at Toms Hardware Hard Drives 4 - 150 gB Velociraptors in RAID 5
Promise controller Internet Speed Cable Other Info GeekSquad UPS
CyberPower UPS
DLink DNS-323 NAS (2 tB)
Netgear wireless router as an access point
Netgear wired router FSV-318
Home network consists of
4 desktop computers (2 Vista, 2 Win7)
1 netbook (Win7)
4 laptop computers (XP, 2-Vista, Win7)
Wii and XBox 360 |
15 Feb 2010
|
#2 | | Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit |
Great info John ...!!! Thank You !! | My System Specs | | System Manufacturer/Model Number Samsung NP550P5C-S02IN OS Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit CPU Intel® Core™ i7 Processor 3,610QM (2.30Hz, 6MB L3 Cach Memory 8 GB Graphics Card NVIDIA® GeForce® GT 650M 2GB Graphics, Optimus™ techno Sound Card SoundAlive™ JBL 3 Speakers (With sub-Woofer) Monitor(s) Displays 39.62cm (15.6) SuperBright 300nit HD+ LED Display Screen Resolution 1,600 x 900, Anti-Reflective Hard Drives 1TB S-ATA II Hard Drive (5,400RPM) |
17 Feb 2010
|
#3 | | Win 8 Release candidate 8400 |
Last edited by zigzag3143; 16 Apr 2012 at 01:35 AM..
| My System Specs | | System Manufacturer/Model Number HP Pavillion dv-7 1005 Tx OS Win 8 Release candidate 8400 CPU 2@2.4 Memory 4 gigs Graphics Card Nvidia 9600M Sound Card HD built-in Monitor(s) Displays 17" Wxga Screen Resolution 1440x900 Cooling none Internet Speed 45Mb down 5Mb up |
01 May 2011
|
#4 | | |
On every forum where I have seen this solved, it was done by either finding & turning off a bad core in BIOS or with a some software program, OR by getting an RMA on the CPU/Processor, or just buying a new CPU/Processor. The full error message tells you a secondary processor (dual, triple, quad core) caused the error. My AMD 955 BE worked fine on windows XP x32 (32 bit), but soon as I upgraded that very same computer to Windows 7 X64 (64 bit) system, this BSOD started. The same one every time it does it. Sometimes it will run for a day or two, other times will get this error multiple times in one day. Just depends on whether that bad CPU CORE gets hit in its weak spot or not. I have already ordered a Phenom II X4. Just after buying this defective Phenom 9600 BE, I started seeing all kinds of posts with problems with it. Too bad the posts were not there for me to see before I bought it. AMD seems to be the worst, but Intel dual & 4 core etc., can have this same problem. If you are under warranty, get yours replaced. If not, then start saving up your money for a replacement. The replacement I ordered has nothing but glowing reviews this time & has been out for quite a long time so it should be safe.
IMHO
isepiq | My System Specs | | System Manufacturer/Model Number Home Built OS Windows 7 Ultimate 64bit CPU AMD x4 Motherboard Gigabyte Memory Corsair Graphics Card ATI Sound Card Realtek HD Monitor(s) Displays Hyundai LCD PSU Corsair 750w Case Lian Li PC60 Hard Drives Samsung 1TB x4 |
08 Jul 2011
|
#5 | | Windows 7 Home Premium 64bit. |
I was directed here from here: http://www.sevenforums.com/crashes-d...ml#post1479599
So I'm assuming I have this problem. First off, I have a new system, so dust isn't an issue. I've looked at temperatures, and they seem okay, but what temps should I be aiming at roughly? When I check the BIOS, my CPU is at about 35 degrees. I run the case fans at full speed, and I have no GPU (right now), but I've still had BSOD without it.
Here's some other stuff from my Bios, not sure what is/isn't necessary, so here's the lot:
CPU Core Voltage - 1.176v
CPU Load Line Calibration - Level 5
IGPU Voltage +0mV
IGPU VDROOP - With
DRAM - 1.500v
PCH Voltage - 1.059v
CPU PLL Voltage - 1.832v
VTT Voltage - 1.051v
VCCSA Voltage - 0.925
-
VCore +1.176
+12.00v - +12.355v
+5/00v - +5.016v
+3.30 - +3.392v
-
CPU Temp - 35
MB Temp - 27
Any idea on if these temps/voltages are right? and if so, how would I proceed to 'check' my drivers?
Thanks for any help! | My System Specs | | OS Windows 7 Home Premium 64bit. CPU Intel i5 2500k Motherboard ASRock Z68 Extreme4 Memory G Skill Ripjaws X 8GB Graphics Card EVGA GTX 580 PSU Seasonic X Series 760W Case Cooler Master HAF X Cooling Noctua NH-D14 Hard Drives OCZ Vertex 2 60GB SSD
Samsung Spinpoint F3 1TB HDD |
10 Jul 2011
|
#6 | | |
Replaced AMD 4 core cpu. Error 101 BSOD now gone. CPU was under warranty. AMD did an RMA. They checked it at their end & found it defective. They sent a new one.
IMHO
isepiq | My System Specs | | System Manufacturer/Model Number Home Built OS Windows 7 Ultimate 64bit CPU AMD x4 Motherboard Gigabyte Memory Corsair Graphics Card ATI Sound Card Realtek HD Monitor(s) Displays Hyundai LCD PSU Corsair 750w Case Lian Li PC60 Hard Drives Samsung 1TB x4 |
25 Mar 2012
|
#7 | | windows 7 ultimate 64 bit |
hi, i was also directed here, i have a new pc, and each time im playing a game, it goes to blue screen after 1 to like 15 minutes of playing.
error 0x00000101
specs
motherboard m5a97evo
video sapphire 7770 1gb
corsair 800w
16gb ram 1600
amd fx 8150 core
wd 2tb hard drive caviar black
all inside a coolermaster 690 II advance | My System Specs | | OS windows 7 ultimate 64 bit |
26 Mar 2012
|
#8 | | |
I usually don't find interest in backseat moderating, but please don't post your issue multiple times, especially as a reply to a thread that's designed as an article to educate, and not as a means to service people's needs. If you fragment your case like this then it makes it very difficult for you and those wishing to assist you, and it also clutters the forums unnecessarily.
I know you were directed here, but the intent was to give you steps with information to help you find the cause of the crashes, as well as to provide information for us. It's not a thread to request assistance in. Make sure to mention any updates or any new information in the original thread you made. | My System Specs | | STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg problems? All times are GMT -5. The time now is 10:51 AM. | |