New
#1
BSOD occurrence on a regular basis
For the past few days, I have encountered a lot of BSODs on my computer with windows 7 64x whereas they didn't occur at all in the past. The computer also tends to freeze at some point.
For the past few days, I have encountered a lot of BSODs on my computer with windows 7 64x whereas they didn't occur at all in the past. The computer also tends to freeze at some point.
Hi,
The dump you've attached unfortunately provides an inconclusive analysis probable fault. At this point, I would recommend enabling Driver Verifier. Driver Verifier will force a BSOD once it finds the faulting driver (if this is software / driver related). If Driver Verifier doesn't show anything, we'll move onto further testing.
Drivers that need to be updated:
Code:BugCheck 101, {31, 0, fffff88002f63180, 2} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002f63180, The PRCB address of the hung processor. Arg4: 0000000000000002, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffff880`0319a528 fffff800`02cf28c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx fffff880`0319a530 fffff800`02ca5497 : fffffa80`00000000 fffff800`00000002 00000000`00002711 fffffa80`039efb60 : nt! ?? ::FNODOBFM::`string'+0x4e2e fffff880`0319a5c0 fffff800`03211895 : fffff800`03237460 fffff880`0319a770 fffff800`03237460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0319a6c0 fffff800`02c97173 : 00000000`1c6f7a7a fffff800`02e10e80 fffffa80`043b06a0 fffff8a0`097d8740 : hal!HalpHpetClockInterrupt+0x8d fffff880`0319a6f0 fffff800`02ca07a6 : fffff800`02e10e80 fffffa80`00000001 00000000`00000000 fffff880`0319a978 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0319a880 fffff800`02cdf7ac : fffff880`0319ac58 00000000`00000000 00000000`00000000 fffff880`02f63180 : nt!KeFlushMultipleRangeTb+0x266 fffff880`0319a950 fffff800`02cdc5e1 : fffffa80`039efb60 00000000`00000000 fffff880`0319ac58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0 fffff880`0319aa50 fffff800`02cdff76 : fffffa80`03e4ac78 00000000`00000001 fffffa80`00000001 00000000`00001000 : nt!CcFlushCache+0x561 fffff880`0319ab50 fffff800`02ce0938 : fffff880`00000000 fffff880`0319ac58 fffffa80`067217f0 fffffa80`03d11d40 : nt!CcWriteBehind+0x1c6 fffff880`0319ac00 fffff800`02ca5001 : fffffa80`039e4ee0 fffff800`02f91901 fffff800`02e9c8c0 00000000`00000003 : nt!CcWorkerThread+0x1c8 fffff880`0319acb0 fffff800`02f35fee : 00000020`00001dee fffffa80`039efb60 00000000`00000080 fffffa80`039d9040 : nt!ExpWorkerThread+0x111 fffff880`0319ad40 fffff800`02c8c5e6 : fffff880`02f63180 fffffa80`039efb60 fffffa80`03a03b60 22549da0`f2d6e70e : nt!PspSystemThreadStartup+0x5a fffff880`0319ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner
I ran the verifier test as you said and this dump file came in...
The dump you've attached is an inconclusive analysis. I recommend keeping Driver Verifier enabled and trying again, as we cannot do much currently with the dump provided, unfortunately.
Drivers that need to be updated:
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Icarus\Downloads\Dumps\022812-26442-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e5c670 Debug session time: Tue Feb 28 06:24:48.453 2012 (UTC - 5:00) System Uptime: 0 days 0:13:14.248 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff880009eb180, 1} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009eb180, The PRCB address of the hung processor. Arg4: 0000000000000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: msnmsgr.exe CURRENT_IRQL: d IRP_ADDRESS: ffffffffffffff88 STACK_TEXT: fffff880`0a92d318 fffff800`02ceb8c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009eb180 : nt!KeBugCheckEx fffff880`0a92d320 fffff800`02c9e497 : 00000000`00000000 fffff800`00000001 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e fffff880`0a92d3b0 fffff800`0320a895 : fffff800`03230460 fffff880`0a92d560 fffff800`03230460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0a92d4b0 fffff800`02c90173 : 00000000`7b70182a fffff800`02e09e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d fffff880`0a92d4e0 fffff800`02ca3792 : fffff800`02e09e80 00000000`00000001 00000000`00000000 fffff980`247ecfe0 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0a92d670 fffff800`02d3cf66 : 00000000`00000000 fffff800`02e09e80 fffff980`247ecfe0 fffff800`02cbf5db : nt!KiIpiSendRequestEx+0xb2 fffff880`0a92d6b0 fffff800`02d95b29 : 00000000`00000001 fffff880`0a92d770 fffff6fc`c0123f60 fffff980`247ecfe0 : nt!KeFlushSingleTb+0x126 fffff880`0a92d730 fffff800`02dc193b : fffff800`02c17000 00000000`20206f49 ffffffff`ffdd3226 fffffa80`0659b090 : nt!MmFreeSpecialPool+0x349 fffff880`0a92d880 fffff800`02ca909e : fffffa80`05433060 fffff800`02c964da fffff880`0a92d9d0 fffff800`02c91e7d : nt!ExDeferredFreePool+0xf33 fffff880`0a92d930 fffff800`02c872f7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x5ce fffff880`0a92da00 fffff800`02c9913d : fffff880`02f683c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7 fffff880`0a92da80 fffff800`02c9b74f : 00000000`00000dec 00000000`7ef1d000 fffff880`000000f2 00000000`0edeeb98 : nt!KiCommitThreadWait+0x3dd fffff880`0a92db10 fffff800`02f8a44e : fffff880`0a92dc00 fffffa80`00000006 00000000`00000001 fffff880`04136001 : nt!KeWaitForSingleObject+0x19f fffff880`0a92dbb0 fffff800`02c92ed3 : fffffa80`05433060 00000000`7fffffff fffff880`0a92dbf8 fffffa80`0545a060 : nt!NtWaitForSingleObject+0xde fffff880`0a92dc20 00000000`73df2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0edeeb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73df2e09 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
In addition to my friend ePeen's excellent advice, please take a look at STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg for the crash you received.