|
BSOD CLOCK_WATCHDOG_TIMEOUT (101) |
Post Reply 
|
| Author |
 Share Topic Printable Version Delicious Digg Facebook Furl Google MySpace Newsvine reddit StumbleUpon Translate Twitter Windows Live Yahoo Bookmarks Topic Search  Topic Options
|
molotov 
Moderator Group 
Joined: 04 October 2006 Online Status: Offline Posts: 17492 |
 Post Options
 Quote Reply
 Topic: BSOD CLOCK_WATCHDOG_TIMEOUT (101)Posted: 02 April 2008 at 4:18pm |
Wonder if this may be related somehow to the problem... Wonder how many systems these days don't have audio capabilities (either add-in, or integrated)...
|
|
|
Daily affirmation:
net helpmsg 4006 |
|
 |
|
|
pafonk
Newbie 
Joined: 23 March 2008 Location: Netherlands Online Status: Offline Posts: 10 |
Post Options
Quote Reply
Posted: 02 April 2008 at 12:40pm |
|
Sorry for the long delay. We have managed to stabilize the systems. It's still a workaround but people can do their jobs without crashing Take a look at this line of the crashdump analyze: 005cfc68 006d148a 00000001 00307b4c 00000000 mmcss!CsServiceMain+0x4a mmcss is the Microsoft Multimedia Class Scheduler service. We have it now for a few days disabled. Because it depends on the Audio Service we had to disable that on too. From than we didn’t get this bug check anymore. This workaround involved that the hole sound system stopped working. The funniest thing about it is that there is fiscal no soundcard inside all those workstations. People are connecting with a thin client that’s getting the sound from a RDP (version 6) channel. Suggestions are welcome to get bold services back alive. Edited by pafonk - 02 April 2008 at 1:24pm |
|
|
|
|
molotov
Moderator Group
Joined: 04 October 2006 Online Status: Offline Posts: 17492 |
Post Options
Quote Reply
Posted: 23 March 2008 at 4:09pm |
|
I can't say I've got any idea... Not sure if it would be a software or a hardware issue at this point, though if it was a hardware issue I guess I would expect the documentation to be more explicit about it. That said, there isn't much that indicates how to tell what software (driver) may be causing the problem, either...
 
Nonresponsive would seem to suggest hardware; deadlocked would seem to suggest software.
Are / were all affected systems imaged from the same source?
How many systems, and how often does each system experience the problem (each one roughly weekly? Or for all systems one experiences the problem in a week?)?
Are you able to upload a dump somewhere? No promises that I will be able to dig anything out of it...
This bugcheck seems rather rare, and there does not seem to be much information about it.
Can you disable one core on one system that regularly experiences the problem and run it that way for a while to see if it helps? From the description of the bugcheck, it should...
Do the systems have the latest BIOS update?
If you submit the crash to Microsoft's OCA, do you get any results? Does Vista's "Problem Reports and Solutions" feature help?
|
|
|
Daily affirmation:
net helpmsg 4006 |
|
|
|
|
pafonk
Newbie
Joined: 23 March 2008 Location: Netherlands Online Status: Offline Posts: 10 |
Post Options
Quote Reply
Posted: 23 March 2008 at 12:02pm |
|
Thanks for helping on this on
I diden't overclock. The system specifications are:
AMD Athlon 64 X2 Dual Core Processor 3000+
ATI Radeon Xpress 1270
80 GB Samsung HD
No Soundcard.
Latest bios version.
Vista RTM patched with all updates and hotfixes.
All indentical systems have the same bugcheck code. It happens almost every week. The times are total random. All dumps process the same Basic fault information with WINDbg.
Here is the data:
0: kd> dt nt!_kprcb 82460120 nt!_KPRCB +0x000 MinorVersion : 1 +0x002 MajorVersion : 1 +0x004 CurrentThread : 0x8571fd78 _KTHREAD +0x008 NextThread : (null) +0x00c IdleThread : 0x82464170 _KTHREAD +0x010 Number : 0x1 '' +0x011 NestingLevel : 0x1 '' +0x012 BuildType : 0 +0x014 SetMember : 2 +0x018 CpuType : 15 '' +0x019 CpuID : 1 '' +0x01a CpuStep : 0x6801 +0x01a CpuStepping : 0x1 '' +0x01b CpuModel : 0x68 'h' +0x01c ProcessorState : _KPROCESSOR_STATE +0x33c KernelReserved : [16] 0 +0x37c HalReserved : [16] 0xe18000 +0x3bc CFlushSize : 0x40 +0x3c0 PrcbPad0 : [88] "" +0x418 LockQueue : [33] _KSPIN_LOCK_QUEUE +0x520 NpxThread : (null) +0x524 InterruptCount : 0xeb4aa9 +0x528 KernelTime : 0xd1541 +0x52c UserTime : 0xc747 +0x530 DpcTime : 0x3a9 +0x534 DpcTimeCount : 0 +0x538 InterruptTime : 0x3c2 +0x53c AdjustDpcThreshold : 4 +0x540 PageColor : 0x2b26 +0x544 SkipTick : 0x1 '' +0x545 DebuggerSavedIRQL : 0 '' +0x546 NodeColor : 0 '' +0x547 PollSlot : 0 '' +0x548 NodeShiftedColor : 0 +0x54c ParentNode : 0x81cf8280 _KNODE +0x550 MultiThreadProcessorSet : 3 +0x554 MultiThreadSetMaster : 0x81cf4820 _KPRCB +0x558 SecondaryColorMask : 7 +0x55c DpcTimeLimit : 0x282 +0x560 CcFastReadNoWait : 0 +0x564 CcFastReadWait : 0x34047 +0x568 CcFastReadNotPossible : 0 +0x56c CcCopyReadNoWait : 0x63bab +0x570 CcCopyReadWait : 0x4e167 +0x574 CcCopyReadNoWaitMiss : 0xba1 +0x578 MmSpinLockOrdering : 0 +0x57c IoReadOperationCount : 884811 +0x580 IoWriteOperationCount : 880978 +0x584 IoOtherOperationCount : 2511449 +0x588 IoReadTransferCount : _LARGE_INTEGER 0x79354e60 +0x590 IoWriteTransferCount : _LARGE_INTEGER 0x1b217316 +0x598 IoOtherTransferCount : _LARGE_INTEGER 0xbb4aff0 +0x5a0 CcFastMdlReadNoWait : 0 +0x5a4 CcFastMdlReadWait : 0 +0x5a8 CcFastMdlReadNotPossible : 0 +0x5ac CcMapDataNoWait : 0 +0x5b0 CcMapDataWait : 0xa3805 +0x5b4 CcPinMappedDataCount : 0x2ef73 +0x5b8 CcPinReadNoWait : 0 +0x5bc CcPinReadWait : 0xe4f9 +0x5c0 CcMdlReadNoWait : 0 +0x5c4 CcMdlReadWait : 0x1a7 +0x5c8 CcLazyWriteHotSpots : 0xd8d +0x5cc CcLazyWriteIos : 0x32e7 +0x5d0 CcLazyWritePages : 0xa70a +0x5d4 CcDataFlushes : 0xc6c8 +0x5d8 CcDataPages : 0x216aa +0x5dc CcLostDelayedWrites : 0 +0x5e0 CcFastReadResourceMiss : 0 +0x5e4 CcCopyReadWaitMiss : 0xafc6 +0x5e8 CcFastMdlReadResourceMiss : 0 +0x5ec CcMapDataNoWaitMiss : 0 +0x5f0 CcMapDataWaitMiss : 0x136d +0x5f4 CcPinReadNoWaitMiss : 0 +0x5f8 CcPinReadWaitMiss : 0x320 +0x5fc CcMdlReadNoWaitMiss : 0 +0x600 CcMdlReadWaitMiss : 0 +0x604 CcReadAheadIos : 0x1b3fb +0x608 KeAlignmentFixupCount : 0 +0x60c KeExceptionDispatchCount : 0xc66c +0x610 KeSystemCalls : 0x8d5070c +0x614 PrcbPad1 : [3] 0 +0x620 PPLookasideList : [16] _PP_LOOKASIDE_LIST +0x6a0 PPNPagedLookasideList : [32] _GENERAL_LOOKASIDE_POOL +0xfa0 PPPagedLookasideList : [32] _GENERAL_LOOKASIDE_POOL +0x18a0 PacketBarrier : 0 +0x18a4 ReverseStall : 95 +0x18a8 IpiFrame : 0x9d02ab9c +0x18ac PrcbPad2 : [52] "" +0x18e0 CurrentPacket : [3] (null) +0x18ec TargetSet : 0 +0x18f0 WorkerRoutine : 0x81cb20f8 void nt!KiFlushTargetMultipleRangeTb+0 +0x18f4 IpiFrozen : 2 +0x18f8 PrcbPad3 : [40] "" +0x1920 RequestSummary : 0 +0x1924 SignalDone : (null) +0x1928 PrcbPad4 : [56] "" +0x1960 DpcData : [2] _KDPC_DATA +0x1988 DpcStack : 0x8244d000 +0x198c MaximumDpcQueueDepth : 4 +0x1990 DpcRequestRate : 2 +0x1994 MinimumDpcRate : 3 +0x1998 DpcInterruptRequested : 0 '' +0x1999 DpcThreadRequested : 0 '' +0x199a DpcRoutineActive : 0 '' +0x199b DpcThreadActive : 0 '' +0x199c PrcbLock : 0 +0x19a0 DpcLastCount : 0x305870 +0x19a4 TimerHand : 0 +0x19a8 TimerRequest : 0 +0x19ac PrcbPad41 : (null) +0x19b0 DpcEvent : _KEVENT +0x19c0 ThreadDpcEnable : 0x1 '' +0x19c1 QuantumEnd : 0 '' +0x19c2 PrcbPad50 : 0 '' +0x19c3 IdleSchedule : 0 '' +0x19c4 DpcSetEventRequest : 0 +0x19c8 Sleeping : 1 +0x19cc PeriodicCount : 0 +0x19d0 PeriodicBias : 0 +0x19d4 PrcbPad5 : [6] "" +0x19dc TickOffset : 100211 +0x19e0 CallDpc : _KDPC +0x1a00 ClockKeepAlive : 0 +0x1a04 ClockCheckSlot : 0 '' +0x1a05 ClockPollCycle : 0x64 'd' +0x1a06 PrcbPad6 : [2] "" +0x1a08 DpcWatchdogPeriod : 1924 +0x1a0c DpcWatchdogCount : 1267 +0x1a10 ThreadWatchdogPeriod : 0 +0x1a14 ThreadWatchdogCount : 0 +0x1a18 PrcbPad70 : [2] 0 +0x1a20 WaitListHead : _LIST_ENTRY [ 0x85199d10 - 0x86c71a18 ] +0x1a28 WaitLock : 0 +0x1a2c ReadySummary : 0 +0x1a30 QueueIndex : 1 +0x1a34 DeferredReadyListHead : _SINGLE_LIST_ENTRY +0x1a38 StartCycles : 0x7f0`d7ef1f1b +0x1a40 CycleTime : 0x4e76 +0x1a48 PrcbPad71 : [3] 0 +0x1a60 DispatcherReadyListHead : [32] _LIST_ENTRY [ 0x82461b80 - 0x82461b80 ] +0x1b60 ChainedInterruptList : (null) +0x1b64 LookasideIrpFloat : 0 +0x1b68 MmPageFaultCount : 5339539 +0x1b6c MmCopyOnWriteCount : 56445 +0x1b70 MmTransitionCount : 2251543 +0x1b74 MmCacheTransitionCount : 0 +0x1b78 MmDemandZeroCount : 2713671 +0x1b7c MmPageReadCount : 221248 +0x1b80 MmPageReadIoCount : 30371 +0x1b84 MmCacheReadCount : 0 +0x1b88 MmCacheIoCount : 0 +0x1b8c MmDirtyPagesWriteCount : 26796 +0x1b90 MmDirtyWriteIoCount : 123 +0x1b94 MmMappedPagesWriteCount : 1600 +0x1b98 MmMappedWriteIoCount : 224 +0x1b9c CachedCommit : 0xfc +0x1ba0 CachedResidentAvailable : 0x80 +0x1ba4 HyperPte : 0x82439002 +0x1ba8 CpuVendor : 0x2 '' +0x1ba9 PrcbPad9 : [3] "" +0x1bac VendorString : [13] "AuthenticAMD" +0x1bb9 InitialApicId : 0x1 '' +0x1bba CoresPerPhysicalProcessor : 0x2 '' +0x1bbb LogicalProcessorsPerPhysicalProcessor : 0x2 '' +0x1bbc MHz : 0x63b +0x1bc0 FeatureBits : 0xa00d7fff +0x1bc8 UpdateSignature : _LARGE_INTEGER 0x0 +0x1bd0 IsrTime : 0 +0x1bd8 SpareField1 : 0 +0x1be0 NpxSaveArea : _FX_SAVE_AREA +0x1df0 PowerState : _PROCESSOR_POWER_STATE +0x1ed0 DpcWatchdogDpc : _KDPC +0x1ef0 DpcWatchdogTimer : _KTIMER +0x1f18 WheaInfo : 0x858ce764 +0x1f1c EtwSupport : 0x84b5d3d0 +0x1f20 InterruptObjectPool : _SLIST_HEADER +0x1f28 HypercallPagePhysical : _LARGE_INTEGER 0x0 +0x1f30 HypercallPageVirtual : (null) +0x1f34 RateControl : 0x86913b10 +0x1f38 Cache : [5] _CACHE_DESCRIPTOR +0x1f74 CacheCount : 3 +0x1f78 CacheProcessorMask : [5] 0 +0x1f8c LogicalProcessorsPerCore : 0x1 '' +0x1f8d PrcbPad8 : [3] "" +0x1f90 PackageProcessorSet : 3 +0x1f94 CoreProcessorSet : 2 Edited by pafonk - 23 March 2008 at 12:54pm |
|
|
|
|
molotov
Moderator Group
Joined: 04 October 2006 Online Status: Offline Posts: 17492 |
Post Options
Quote Reply
Posted: 23 March 2008 at 7:45am |
|
Hi Peter,
Not sure it will turn up anything, but what's the output of dt nt!_kprcb 82460120? (Presumably, you are given the address of the PRCB with this BSOD because it will be helpful.)
Does the problem happen repeatedly, or did it just happen once?
Are you overclocking?
|
|
|
Daily affirmation:
net helpmsg 4006 |
|
|
|
|
pafonk
Newbie
Joined: 23 March 2008 Location: Netherlands Online Status: Offline Posts: 10 |
Post Options
Quote Reply
Posted: 23 March 2008 at 7:01am |
|
Hello,
I try to analyze following dumpfile. But can't trace the fault to any driver. I downloaded the newest drivers and still no luck
 Microsoft (R) Windows Debugger Version 6.8.0004.0 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Temp\MEMORY.DMP] Kernel Complete Dump File: Full address space is available Symbol search path is: C:\Windows\Symbols;SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\Windows\System32;C:\Windows\System Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6000.16575.x86fre.vista_gdr.071009-1548 Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10 Debug session time: Fri Mar 21 15:10:04.693 2008 (GMT+1) System Uptime: 0 days 3:56:15.780 Loading Kernel Symbols ....................................................................................................................................... Loading User Symbols ................................................................................................................................................ Loading unloaded module list ......Unable to enumerate user-mode unloaded modules, NTSTATUS 0xC0000147 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, 82460120, 1}
*************************************************************************
*** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: kernel32!pNlsUserInfo *** *** *** ************************************************************************* Probably caused by : ntkrpamp.exe ( nt!KeFlushProcessWriteBuffers+61 ) Followup: MachineOwner
--------- 0: kd> !analyze -v
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 00000000, 0. Arg3: 82460120, The PRCB address of the hung processor. Arg4: 00000001, 0. Debugging Details:
------------------ *************************************************************************
*** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: kernel32!pNlsUserInfo *** *** *** ************************************************************************* DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 81c284fc to 81cd8681
STACK_TEXT:
91d438ec 81c284fc 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e 91d43920 81c906ad 81e8251b 000000d1 91d439b0 nt!KeUpdateRunTime+0xd4 91d43920 81c11cac 81e8251b 000000d1 91d439b0 nt!KeUpdateSystemTime+0xed 91d439b0 81e82540 00000001 91d4860c 00000053 nt!KeFlushProcessWriteBuffers+0x61 91d43d4c 81c8caaa 00000053 00307d70 00000010 nt!NtQuerySystemInformation+0x2232 91d43d4c 77d30f34 00000053 00307d70 00000010 nt!KiFastCallEntry+0x12a 005cf884 77d2ffe0 751b13a8 00000053 00307d70 ntdll!KiFastSystemCallRet 005cf888 751b13a8 00000053 00307d70 00000010 ntdll!ZwQuerySystemInformation+0xc 005cf8cc 751b155c 751b8000 005cf928 00000000 mmcss!CiSchedulerWait+0x9c 005cf914 77d30dfd 00000000 00000000 00000000 mmcss!CiSchedulerApc+0x26e 005cfc60 751b3964 00307b40 006d148a 00000001 ntdll!KiUserApcDispatcher+0x25 005cfc68 006d148a 00000001 00307b4c 00000000 mmcss!CsServiceMain+0x4a 005cfc94 76ddb9f6 00000001 00307b4c 00000000 svchost!ServiceStarter+0x17a 005cfca8 77e73833 00307b40 005cfcf4 77d0a9bd ADVAPI32!ScSvcctrlThreadA+0x21 005cfcb4 77d0a9bd 00307b40 005c6a8d 00000000 kernel32!BaseThreadInitThunk+0xe 005cfcf4 00000000 76ddb9d5 00307b40 00000000 ntdll!_RtlUserThreadStart+0x23 STACK_COMMAND: kb FOLLOWUP_IP:
nt!KeFlushProcessWriteBuffers+61 81c11cac 85c9 test ecx,ecx SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeFlushProcessWriteBuffers+61
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 470c2f52
FAILURE_BUCKET_ID: 0x101_nt!KeFlushProcessWriteBuffers+61
BUCKET_ID: 0x101_nt!KeFlushProcessWriteBuffers+61
Followup: MachineOwner
--------- |
|
|
|
|
Post Reply
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
