 | |
| |
| 19 Oct 2010 | #1 |
| | Clock_watchdog_timeout Hello! This error Quote: This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F64180, 0x2) Error: CLOCK_WATCHDOG_TIMEOUT Dump file: C:\Windows\Minidump\101610-27783-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System -sfc/ scannow made -drivers checked with verifier -bios updated -no viruses/malwares -temperatures less than 40 ° C -memtest passed 100% with no errors Is Windows 7 . . . -x64 - the original installed OS on the system? Win 7, this - What is the age of system (hardware)?Less than 1 year - What is the age of OS installation//less than 1 year |
My System Specs | |
| 19 Oct 2010 | #2 |
| | 
Quote: Originally Posted by Ryu84  Hello! This error Quote: This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F64180, 0x2) Error: CLOCK_WATCHDOG_TIMEOUT Dump file: C:\Windows\Minidump\101610-27783-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System -sfc/ scannow made -drivers checked with verifier -bios updated -no viruses/malwares -temperatures less than 40 ° C -memtest passed 100% with no errors Is Windows 7 . . . -x64 - the original installed OS on the system? Win 7, this - What is the age of system (hardware)?Less than 1 year - What is the age of OS installation//less than 1 year There are several causes. You AOL drivers are more than half of the recent ones. the rest mostly blamed on hardware. Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try You also have a file sptd.sys (a virtual drive app like daemon tools/alcohol) which is a known problem it should be removed. Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads [/quote] You can use MagicDisc as an alternative. Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview Run a system file check SFC /SCANNOW Command - System File Checker Update drivers Code: adfs.SYS fffff880`07c71000 fffff880`07c89000 0x00018000 0x490f2b4e 11/3/2008 12:48:14 sptd.sys fffff880`01082000 fffff880`011b6000 0x00134000 0x49c63097 3/22/2009 08:35:35 AsIO.sys fffff880`03f2c000 fffff880`03f32000 0x00006000 0x49d9ad64 4/6/2009 03:21:08 ararli7e.SYS fffff880`03fa4000 fffff880`03fe6000 0x00042000 0x49db7a24 4/7/2009 12:07:00 Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050210-26145-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`03053e50
Debug session time: Sun May 2 03:41:40.047 2010 (GMT-4)
System Uptime: 0 days 0:00:11.186
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8006a8d268, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
--------- |
| My System Specs |
| 19 Oct 2010 | #3 |
| | i am doing... Thanks! Ah..what is the "ararli7e.SYS" ? |
| My System Specs |
| . |
| |
| 22 Oct 2010 | #4 |
| | It seems to be all ok now - i have resolved the sptd.sys //uninstalling daemon -updated the sys that you have shown there ( arali7e.sys NO ,, i have not understoden what it is) -repaired the win 7 with the repair tool of win 7 disc by booting on it So very thank to you Zig. |
| My System Specs |
| 24 Oct 2010 | #5 |
| | update: I had uninstalled my sidewinder x8 mouse...just to try about the issue.. Now (yesterday) i have reinstalled those drivers,and today the clock bsod is coming out again..after about 3 days that everything was ok. Now i think that the drivers of mouse are the problem..i am unistalling them now,and i'll see for the next days  |
| My System Specs |
 |
Clock_watchdog_timeout problems?
| Thread Tools | |
| Similar help and support threads for: Clock_watchdog_timeout | ||||
| Thread | Forum | |||
| BSOD when surfing web CLOCK_WATCHDOG_TIMEOUT | BSOD Help and Support | |||
| BSOD playing videos, CLOCK_WATCHDOG_TIMEOUT (101) | BSOD Help and Support | |||
 Bsod 101 clock_watchdog_timeout | BSOD Help and Support | |||
| STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg | Crash and lockup debug 'How To' | |||
| BSODs Bad_pool_caller and Clock_watchdog_timeout Win7 64bit | BSOD Help and Support | |||
All times are GMT -5. The time now is 01:58 AM.
