BSOD, error 0x00000101

wimnagy · 16 Mar 2015

Hi,

Recently, my SSD crashed and couldn’t be detected again in the bios. Therefore, I replaced the SSD with a regular HDD and installed Windows 7 again. But now I have some BSOD with error 0x00000101 on a regular base.

Attached you can find my dump file and the zip file:

Code:

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd5180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
fffff880`086e4458 fffff800`02d25d0a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02fd5180 : nt!KeBugCheckEx
fffff880`086e4460 fffff800`02cd8647 : 00000000`00000000 fffff800`00000003 00000000`00002711 fffff800`02ce0b3e : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`086e44f0 fffff800`02c1a895 : fffff800`02c40460 fffff880`086e46a0 fffff800`02c40460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`086e45f0 fffff800`02cca413 : fffff800`02e4ae80 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`086e4620 fffff800`02ca391f : ffff0074`0cd8a800 fffffa80`00000000 00000000`00000000 fffffa80`0f5950f0 : nt!KiInterruptDispatchNoLock+0x163
fffff880`086e47b0 fffff800`02c9acb3 : 00000000`00000000 fffff880`086e4c06 00000000`00000000 fffffa80`0ff59640 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`086e4820 fffff800`02fbf330 : fffffa80`0d84b060 fffff880`086e4ca0 00000000`00000006 fffff880`00000004 : nt!KeSetPriorityAndQuantumProcess+0xd3
fffff880`086e48d0 fffff800`02ccd153 : fffffa80`0ff59640 fffff880`086e4ca0 00000000`7efad000 fffffa80`0fe43c90 : nt!NtSetInformationProcess+0x8bf
fffff880`086e4c20 00000000`7785147a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`009fe6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7785147a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_8_proc_analysis_inconclusive

FAILURE_ID_HASH:  {b37a9ee0-e89a-8796-d6e1-c509c7ba4f05}

Followup: MachineOwner
---------

Could anyone please help me finding the problem? I also noted that the temperature of my GPU is 65°C. So maybe it a problem of overheating my GPU. But before I change the ventilation in my case, I want to be sure if that’s going to solve the problem.

Boozad · 16 Mar 2015

Avast is causing issues. Uninstall Avast and install MS Security Essentials and MalwareBytes.

Note

Make sure you uncheck the 'Enable Free Trial' box when installing Malwarebytes.

Code:

fffff880`086e4ad8  fffff880`040c73dfUnable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x283df

wimnagy · 16 Mar 2015

Thank you for the fast reply. I never thought my avast was causing the problem. I will follow your recommendations.

Boozad · 16 Mar 2015

Virtually every AV suite has caused BSODs at some time or another, we recommend testing with MSE as it's never caused a BSOD so at least we can rule the AV out. As it was the only thing to show in your logs it seems more than likely. Let us know how you get on.