CLOCK WATCHDOG TIMEOUT and svchost BSOD

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.

I was just surfing the net and that happened.

I have ran Malwarebytes and no viruses found.

I have analyzed the the minidump using DTW

I need help resolving this issue and the BSOD's are coming quite frequent now.

Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23677.amd64fre.win7sp1_ldr.170209-0600
Machine Name:
Kernel base = 0xfffff800`03200000 PsLoadedModuleList = 0xfffff800`03442730
Debug session time: Tue Apr 11 19:17:06.685 2017 (UTC + 8:00)
System Uptime: 0 days 1:05:16.233
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, fffff880009e8180, 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e8180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 7601.23677.amd64fre.win7sp1_ldr.170209-0600

SYSTEM_MANUFACTURER: To be filled by O.E.M.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 4.6.5

BIOS_DATE: 05/09/2012

BASEBOARD_MANUFACTURER: Emaxx Technology.,Ltd

BASEBOARD_PRODUCT: EMX-A55GT-iCafe

BASEBOARD_VERSION: Ver:2.0

DUMP_TYPE: 2

BUGCHECK_P1: 61

BUGCHECK_P2: 0

BUGCHECK_P3: fffff880009e8180

BUGCHECK_P4: 1

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

CPU_COUNT: 2

CPU_MHZ: a87

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 12

CPU_MODEL: 1

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: PC1

ANALYSIS_SESSION_TIME: 04-11-2017 19:24:24.0088

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:
fffff880`07c29468 fffff800`032c9cf9 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx
fffff880`07c29470 fffff800`03279ce7 : 00000000`00000000 fffff800`00000001 00000000`00001389 fffff880`07c29580 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`07c29500 fffff800`037f0895 : fffff800`03816460 fffff880`07c296b0 fffff800`03816460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`07c29600 fffff800`0326b993 : fffff800`033eee80 00000000`00000001 fffffa80`049620c0 fffff800`03200001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`07c29630 fffff800`03245e8d : fffff880`11191a1b fffffa80`06f56000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`07c297c0 fffff800`03580e0f : 00000000`00000000 fffff880`07c29ca0 00000000`00000000 00001f80`00c20290 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`07c29830 fffff800`0358146d : 00000000`03aa4de0 fffff800`0356bc5e 00000000`00000000 00000000`00000000 : nt!ExpQuerySystemInformation+0x13af
fffff880`07c29be0 fffff800`0326e6d3 : fffffa80`08840000 00000000`00000000 ffffffff`ffff3cb0 000007fe`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`07c29c20 00000000`7712c09a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`016ef378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7712c09a


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 6d95badf1be53614f0d8f7a3bd93e36b9d535511

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 275f4c6dd2a5be0a2dd9c4e16fb1695b21b162d3

THREAD_SHA1_HASH_MOD: a26ad7c9d9ba9aa18bf16a1fe637d46a447e1e89

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_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

PRIMARY_PROBLEM_CLASS: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

TARGET_TIME: 2017-04-11T11:17:06.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-02-09 23:57:17

BUILDDATESTAMP_STR: 170209-0600

BUILDLAB_STR: win7sp1_ldr

BUILDOSVER_STR: 6.1.7601.23677.amd64fre.win7sp1_ldr.170209-0600

ANALYSIS_SESSION_ELAPSED_TIME: 70d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_clock_watchdog_timeout_2_proc_analysis_inconclusive

FAILURE_ID_HASH: {f1d742c8-d2bd-7559-9a14-2cd83aa3aa50}

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