CLOCK_WATCHDOG_TIMEOUT 101 BSOD on cold boot

Hi, I am a system administrator in the company I work for.
One user's pc has a frequent BSOD error (see title).
Most of the time BSODs happen in the morning, when the user turns on the pc, but sometimes he gets BSOD also during the day.
The pc has Windows 10 Pro x64 (upgraded from Windows 7).
I uploaded the data collected with DM Log collector.
The pc model is Dell Studio XPS 435 MT.
PS: I just run the sfc /scannow command, but the command didn't found any problem.

Both dumpfiles are:

Code:

  *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {18, 0, ffffd00130c79180, 3}

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

As you can read the dump file does not point to something specific.
Usual causes of this bugcheck: Device driver, BIOS bug, hardware defect (see Significant Posts section below)

Your real aim is to give yourself the best possible chance of discovering a software cause for the target processor to go unresponsive, and thereby avoid the most obvious conclusion - that the processor is periodically unresponsive because of hardware-level defects

I can confidently tell you that the browsers, apps, and games cannot be the root cause of this problem, even though I don't doubt your observation that the operation of certain software seems to more easily trigger the crash. What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
- H2SO4

Bios: you have already the latest version 1.1.4. but it is from 2009!

Drivers:
Looking through your driver modules:
tpg64win7 Wed Nov 23 16:00:40 2011
Driver Description: TP-link Gigabit PCI Express network adapter driver
Driver Update Site: Support - Welcome to TP-LINK or OEM

ccSetx64 Tue Sep 24 05:58:04 2013
Ironx64 Mon Dec 01 18:53:06 2014
SYMEVENT64x86 Fri Jan 16 03:53:56 2015 (54B87D44)
SYMNETS Fri Oct 03 00:14:05 2014
All drivers related to Norton/symentics but there also drivers from may 2016 from symentec.
Where there recently a install/update of Norton/Symentec products without maybe removing old drivers.
So the installation may become corrupted.
Remove/uninstal with Norton Removal Tool and reinstall.

Hope this will get you starting and hopefully it will stop the BSOD.

lifetec said:

Both dumpfiles are:

Code:

  *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {18, 0, ffffd00130c79180, 3}

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

As you can read the dump file does not point to something specific.
Usual causes of this bugcheck: Device driver, BIOS bug, hardware defect (see Significant Posts section below)


Bios: you have already the latest version 1.1.4. but it is from 2009!

Drivers:
Looking through your driver modules:
tpg64win7 Wed Nov 23 16:00:40 2011
Driver Description: TP-link Gigabit PCI Express network adapter driver
Driver Update Site: Support - Welcome to TP-LINK or OEM

ccSetx64 Tue Sep 24 05:58:04 2013
Ironx64 Mon Dec 01 18:53:06 2014
SYMEVENT64x86 Fri Jan 16 03:53:56 2015 (54B87D44)
SYMNETS Fri Oct 03 00:14:05 2014
All drivers related to Norton/symentics but there also drivers from may 2016 from symentec.
Where there recently a install/update of Norton/Symentec products without maybe removing old drivers.
So the installation may become corrupted.
Remove/uninstal with Norton Removal Tool and reinstall.

Hope this will get you starting and hopefully it will stop the BSOD.

Thank you.
So, the latest BIOS update that I can find on Dell support page is that already installed.
I just updated the TP-LINK PCI network adapter(TG-3468) to the latest version(from august 2013) , and I also removed Symantec Endpoint Protection with the Norton Removal Tool, now I am installing the free version of Avira.
I will post again if the user willl experience other BSODs

Today I've got another blue screen with the same error code.

Did you already checked your pc for gathered Dust and cleaned it and what are the temperatures of your system, voltages etc.

Start with diagnosing your hardware.
Dell has a hardware test Product Support | Dell US


Also you can do this hardwaretests.
.Please start with diagnosing the system RAM first.
You can use the free tool "Memtest86+"to stress test the RAM.
MemTest86+ - Test RAM - Windows 10 Forums
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory DiagnosticTool
You can stop the test even if a single error is found during the test.Otherwise continue the test for 7-10 passes and post a screenshot with next reply. 7 passes is the recommended bare minimum but more passes will give better result.

Run "Prime95"stability test.
Prime95 - Stress Test Your CPU - Windows 10 Forums
Choose"SmallFFT" test and also select "Round off Checking"from "Advanced" menu (read reply #1). Run the test for 3-4hours and upload the "Result.txt" file it creates.


Intel Processor Diagnostic Tool (works in Windows)
x64 - http://downloadcenter.intel.com/Deta...mples&lang=eng
x86 - http://downloadcenter.intel.com/Deta...mples&lang=eng

So, yesterday evening I launched Prime95 and I let it run for about 4 hours, without errors apparently.
I am uploading "result.txt" from Prime95, a screenshot of the CPU/GPU temperatures during the stress test (I didn't found dust) and lastly a minidump of 06/06/16.

I analyzed a minidump with WinDBG and the analysis shows that the BSOD could be cause by the process "mbae64.exe" (MalwareBytes Anti-Exploit).
Now I am going to remove this software from the pc.

axe0 said:

Please remove either of the sticks models, running mixed memory can cause problems.

Thank you, I just replaced some of the memory sticks so all the sticks are from the same brand.
I also removed MalwareBytes Anti-Malware.