Question Blue screen problem help me attached dmp details

May 14, 2019
9
0
10
0
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051319-9515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff804478a2000 PsLoadedModuleList = 0xfffff80447cbd730
Debug session time: Mon May 13 14:14:48.425 2019 (UTC - 7:00)
System Uptime: 0 days 3:09:24.172
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
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: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8080ec779180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3001

BIOS_DATE: 03/09/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: A88XM-A

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffff8080ec779180

BUGCHECK_P4: 3

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 3

PROCESS_NAME: DCS.exe

CPU_COUNT: 4

CPU_MHZ: ffa

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 13

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DESKTOP-HGAUV2Q

ANALYSIS_SESSION_TIME: 05-14-2019 05:50:25.0437

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff80447aceba6 to fffff80447a557e0

STACK_TEXT:
fffff80449c6dba8 fffff80447aceba6 : 0000000000000101 0000000000000030 0000000000000000 ffff8080ec779180 : nt!KeBugCheckEx
fffff80449c6dbb0 fffff80447986df4 : 0000000000000000 0000000000000000 00000000000b190b fffff80446666180 : nt!KeAccumulateTicks+0x144c76
fffff80449c6dc10 fffff8044780c332 : 0000000000000000 fffff8044786fc48 ffffb6851be97680 0000000000000002 : nt!KeClockInterruptNotify+0x604
fffff80449c6df30 fffff804479d5195 : 0000001a76d89f22 fffff80447872850 fffff80447872900 ffff8080ecaf1280 : hal!HalpTimerClockInterrupt+0xf2
fffff80449c6df60 fffff80447a571da : ffffb6851be97680 fffff80447872850 0000000000000118 fffff80447872850 : nt!KiCallInterruptServiceRoutine+0xa5
fffff80449c6dfb0 fffff80447a57727 : 0000000000000000 ffffb6851be97680 fffff80447872850 ffffb98f943682d8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb6851be97600 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


THREAD_SHA1_HASH_MOD_FUNC: 5e958d63ed6cce864bfe4c595207e0e484aa7e7c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a64f57604a1652c6bc6ee0bc46df3a70888cf2be

THREAD_SHA1_HASH_MOD: e2266a530ca7fbace00cfa9add8dc0ac4504d759

FOLLOWUP_IP:
nt!KeAccumulateTicks+144c76
fffff804`47aceba6 cc int 3

FAULT_INSTR_CODE: cb8b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeAccumulateTicks+144c76

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17763.475

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 144c76

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

TARGET_TIME: 2019-05-13T21:14:48.000Z

OSBUILD: 17763

OSSERVICEPACK: 475

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 1b625

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}
 

PC Tailor

Estimable
I am running this through a debugger as we speak and will see if i can find what point the IRQL wasn't processed.

Are you still encountering an issue? Are you having any other issues after this BSOD? Or is it just a one off that you want to understand?
 

PC Tailor

Estimable
I have ran this through a debugger and found the following:

View full report here (including 3rd party drivers and now timestamps): https://pste.eu/p/5j1M.html

BugCheck 101, {30, 0, ffff8080ec779180, 3}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+144c76 ) OR hal.dll

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.

FAULTING_PROCESSOR: 3
PROCESS_NAME: DCS.exe

Meaning: The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

It seems you have the most up to date BIOS. This is likely caused by a driver. This can be caused by Microsoft drivers not being up to date also.
This CAN be caused by a hardware problem also.

Are you running any OC at all?
Have you ensured all Windows Updates have been installed?
Have you updated your NVIDIA drivers? - Your NVIDIA audio drivers are a couple of months old but the Video driver appears to be up to date.


It will also be apt to wait for someone elses input.
@Colif @gardenman (please both of you tell me if you'd rather I not attach you to these threads)
 
May 14, 2019
9
0
10
0
I am running this through a debugger as we speak and will see if i can find what point the IRQL wasn't processed.

Are you still encountering an issue? Are you having any other issues after this BSOD? Or is it just a one off that you want to understand?
1.yes i still facing this problem
2.no other problem i having only this issue blue screen or stuttering especially while on gaming or any multi tasking ,some times open the explorer its getting some time to read.
3.i do not over clock anything
4.my windows is retail version so its updating some times but i cant sure its updated everything.
5.yes my nividia driver is up to date but i m using asus xonar sound card so dont know and want nvidia sound driver .
6.i cant judge this problem what is causing ...if you want any other details i can provide help me
Thanks
 
May 14, 2019
9
0
10
0
I have ran this through a debugger and found the following:

View full report here (including 3rd party drivers and now timestamps): https://pste.eu/p/5j1M.html

BugCheck 101, {30, 0, ffff8080ec779180, 3}

*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+144c76 ) OR hal.dll

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.

FAULTING_PROCESSOR: 3
PROCESS_NAME: DCS.exe

Meaning: The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

It seems you have the most up to date BIOS. This is likely caused by a driver. This can be caused by Microsoft drivers not being up to date also.
This CAN be caused by a hardware problem also.

Are you running any OC at all?
Have you ensured all Windows Updates have been installed?
Have you updated your NVIDIA drivers? - Your NVIDIA audio drivers are a couple of months old but the Video driver appears to be up to date.


It will also be apt to wait for someone elses input.
@Colif @gardenman (please both of you tell me if you'd rather I not attach you to these threads)
Hey bro i got another BSOD problem DPC_WATCHDOG_VIOLATION
Here with i attached another .dmp file

https://drive.google.com/open?id=11Il_4hoOzqFrl9PabuO53lFjok3MsVuf
 

PC Tailor

Estimable
I'm putting this through the debugger now.

I noticed this crash occured whilst you were opening or running Darksiders. This could be to do with VCRuntime140.dll.

Do the crashes occur in certain circumstances? I.e. does it only occur when you go to play games for example?
 

PC Tailor

Estimable
I'm putting this through the debugger now.

I noticed this crash occured whilst you were opening or running Darksiders. This could be to do with VCRuntime140.dll.
I also notice this is an Exception rather than a straightforward bugcheck.

Do the crashes occur in certain circumstances? I.e. does it only occur when you go to play games for example?
Have you ensured everything in Windows is updated?
Have you made any recent hardware changes? Can you also post you're entire system spec.
Have you run a FULL system antivirus / antimalware scan?


I would firstly recommend that your run an SFC/SCANNOW and a CHKDSK in an elevated command prompt.

Edit:
See report of UE4Minidump here: https://pste.eu/p/a174.html

THIS REPORT HAS FOUND AN EXCEPTION - EXCEPTION ANALYSIS PERFORMED
Probably caused by : VCRUNTIME140.dll ( VCRUNTIME140!MoveSmall+4a )

Just for the record, I don't believe this is the minidump relating to your WATCHDOG VIOLATION.
 
Last edited:

PC Tailor

Estimable
Your SFC found corrupt files.
You can look in the appropriate log files to see what it has repaired - if it's simple, then that could potentially be the cause of your problems. And the SFC should have repaired them, but we will have to see.

I would also run the previous recommendations in my earlier post:

Do the crashes occur in certain circumstances? I.e. does it only occur when you go to play games for example?
Have you ensured everything in Windows is updated?
Have you made any recent hardware changes? Can you also post you're entire system spec.
Have you run a FULL system antivirus / antimalware scan?
 

Satan-IR

Honorable
Apr 18, 2014
818
31
11,390
135
PC Tailor is right with that DLL being probably the cause. I ran it and get "Unable to verify timestamp for VCRUNTIME140.dll".

What is the latest MS Visual C++ Redistribution you have installed?

Installing the latest version or reinstalling if you have the latest might help.
 
Reactions: PC Tailor

Colif

Titan
Moderator
its unusual for a dll to cause a bsod... in that I can't remember last time it did. Its likely a driver is at the heart of the problem still.

clock watchdog timeout is error called by CPU but not necessarily caused by it. It can be software or hardware.

Do you have AI Suite installed? Remove it, Otherwise I would use autoruns to disable ASio.sys from running at startup - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns


@PC Tailor should sort 3rd party drivers in date order by year, its generally older drivers that cause BSOD, its not often the new ones (unless they from Nvidia). Any driver prior to July 2015 isn't win 10, so could be the reason for crashes.

The drivers for the logitech wingman are all from 2010, I would try to get updates for them as they not win 10 drivers.
 
May 14, 2019
9
0
10
0
I'm putting this through the debugger now.

I noticed this crash occured whilst you were opening or running Darksiders. This could be to do with VCRuntime140.dll.
I also notice this is an Exception rather than a straightforward bugcheck.

Do the crashes occur in certain circumstances? I.e. does it only occur when you go to play games for example?
Have you ensured everything in Windows is updated?
Have you made any recent hardware changes? Can you also post you're entire system spec.
Have you run a FULL system antivirus / antimalware scan?


I would firstly recommend that your run an SFC/SCANNOW and a CHKDSK in an elevated command prompt.

Edit:
See report of UE4Minidump here: https://pste.eu/p/a174.html

THIS REPORT HAS FOUND AN EXCEPTION - EXCEPTION ANALYSIS PERFORMED
Probably caused by : VCRUNTIME140.dll ( VCRUNTIME140!MoveSmall+4a )

Just for the record, I don't believe this is the minidump relating to your WATCHDOG VIOLATION.
yes still continuing this problem
blue screen or stuttering especially while on gaming and any multi tasking ,
some times open the explorer its getting some time to read.
my windows is retail version so its updating some times but i cant sure its updated everything.
i dont have any specific antivirus software only having windows defender still i dont scan entire computer (can i scan with windows defender or you recommend me some other)?
And i reinstall every VCredist till latest version


MY SPECS:

A-10 6800K CPU
A88XMA MB
DEEP COOL GAMEX processor cooler
G SKILL RIPJAW 2133 mhz 4GBx4=16GB RAM
corsair 550WATTS PSU
Zotac GTX 1060 6 GB GPU
Asus xonar DG sound card
Crucial MX 300 SSD
WD 1 TB HDD
TOSHIBA 1TB HDD (3 months before added)
LG DVD
 
May 14, 2019
9
0
10
0
its unusual for a dll to cause a bsod... in that I can't remember last time it did. Its likely a driver is at the heart of the problem still.

clock watchdog timeout is error called by CPU but not necessarily caused by it. It can be software or hardware.

Do you have AI Suite installed? Remove it, Otherwise I would use autoruns to disable ASio.sys from running at startup - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns


@PC Tailor should sort 3rd party drivers in date order by year, its generally older drivers that cause BSOD, its not often the new ones (unless they from Nvidia). Any driver prior to July 2015 isn't win 10, so could be the reason for crashes.

The drivers for the logitech wingman are all from 2010, I would try to get updates for them as they not win 10 drivers.
This problem suddenly came at that time i dont have AI suite ,Then i format and reinstall windows 10 pro, after that only i install AI suite for monitoring CPU
OK again i uninstall AI suite and try
 

Similar threads


ASK THE COMMUNITY

TRENDING THREADS