Windows 10 PC frequently crashing with errir : CLOCK_WATCHDOG

Windows 10 PC frequently crashing with errir : CLOCK_WATCHDOG_TIMEOUT

up vote
0
down vote

favorite

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 16299 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`56a0d000 PsLoadedModuleList = 0xfffff801`56d6eff0

Debug session time: Fri Dec 22 06:48:32.282 2017 (UTC - 5:00)

System Uptime: 0 days 0:01:31.548

*******************************************************************************

*                                                                             *

*                        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: ffffd28085f5e180, The PRCB address of the hung processor.

Arg4: 0000000000000003, 0.



Debugging Details:

------------------





OVERLAPPED_MODULE: Address regions for 'srv2' and 'dump_storpor' overlap



BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT



PROCESS_NAME:  iPodService.ex



CURRENT_IRQL:  d



STACK_TEXT:  

fffff801`58e64bc8 fffff801`56b9e586 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd280`85f5e180 : nt!KeBugCheckEx

fffff801`58e64bd0 fffff801`56a5cb98 : fffff801`55a66180 fffff801`55a66180 00000000`000016e3 00000000`00000000 : nt!KeAccumulateTicks+0x140186

fffff801`58e64c30 fffff801`572e24c6 : 0000004f`d149a472 00000000`00000000 ffffbc8c`fb1dadf0 00000000`00000001 : nt!KeClockInterruptNotify+0x5f8

fffff801`58e64f40 fffff801`56aabda5 : fffff801`57335550 fffff801`56b723fc fffff801`58e56b50 ffffd280`864cb780 : hal!HalpTimerClockInterrupt+0x56

fffff801`58e64f70 fffff801`56b727fa : ffffbc8c`fb1dae70 fffff801`57335550 00000000`00000000 ffffbc8c`fb1db128 : nt!KiCallInterruptServiceRoutine+0xa5

fffff801`58e64fb0 fffff801`56b72c47 : 00000000`6820c3bc 00000000`00001f40 ffffab07`00060000 fffff801`56b5405c : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffbc8c`fb1dadf0 fffff801`56a62a40 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffab07`480db010 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffbc8c`fb1daf80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x2a0





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

---------

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

asked Dec 22 '17 at 12:53

shrikant shirude

1

What have you tried? What has your research found? Has anything changed with your PC? When did this start?
– Mokubai♦
Dec 22 '17 at 13:26

re-installed OS , updated drivers ,fresh OS , no other application installed only GPU is added to my PC
– shrikant shirude
Dec 22 '17 at 13:39

Have you tried taking out the GPU? How often does it happen? How frequent is frequent? Is it once a month or every 5 minutes? edit your question to provide real details about your problem.
– Mokubai♦
Dec 22 '17 at 13:41

Yes, even if I remove the GPU BSOD is observed, every now and then the issues occurs. No pattern found for the issue
– shrikant shirude
Dec 22 '17 at 13:45

add a comment |

up vote
0
down vote

favorite

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 16299 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`56a0d000 PsLoadedModuleList = 0xfffff801`56d6eff0

Debug session time: Fri Dec 22 06:48:32.282 2017 (UTC - 5:00)

System Uptime: 0 days 0:01:31.548

*******************************************************************************

*                                                                             *

*                        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: ffffd28085f5e180, The PRCB address of the hung processor.

Arg4: 0000000000000003, 0.



Debugging Details:

------------------





OVERLAPPED_MODULE: Address regions for 'srv2' and 'dump_storpor' overlap



BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT



PROCESS_NAME:  iPodService.ex



CURRENT_IRQL:  d



STACK_TEXT:  

fffff801`58e64bc8 fffff801`56b9e586 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd280`85f5e180 : nt!KeBugCheckEx

fffff801`58e64bd0 fffff801`56a5cb98 : fffff801`55a66180 fffff801`55a66180 00000000`000016e3 00000000`00000000 : nt!KeAccumulateTicks+0x140186

fffff801`58e64c30 fffff801`572e24c6 : 0000004f`d149a472 00000000`00000000 ffffbc8c`fb1dadf0 00000000`00000001 : nt!KeClockInterruptNotify+0x5f8

fffff801`58e64f40 fffff801`56aabda5 : fffff801`57335550 fffff801`56b723fc fffff801`58e56b50 ffffd280`864cb780 : hal!HalpTimerClockInterrupt+0x56

fffff801`58e64f70 fffff801`56b727fa : ffffbc8c`fb1dae70 fffff801`57335550 00000000`00000000 ffffbc8c`fb1db128 : nt!KiCallInterruptServiceRoutine+0xa5

fffff801`58e64fb0 fffff801`56b72c47 : 00000000`6820c3bc 00000000`00001f40 ffffab07`00060000 fffff801`56b5405c : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffbc8c`fb1dadf0 fffff801`56a62a40 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffab07`480db010 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffbc8c`fb1daf80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x2a0





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

---------

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

asked Dec 22 '17 at 12:53

shrikant shirude

1

What have you tried? What has your research found? Has anything changed with your PC? When did this start?
– Mokubai♦
Dec 22 '17 at 13:26

re-installed OS , updated drivers ,fresh OS , no other application installed only GPU is added to my PC
– shrikant shirude
Dec 22 '17 at 13:39

Have you tried taking out the GPU? How often does it happen? How frequent is frequent? Is it once a month or every 5 minutes? edit your question to provide real details about your problem.
– Mokubai♦
Dec 22 '17 at 13:41

Yes, even if I remove the GPU BSOD is observed, every now and then the issues occurs. No pattern found for the issue
– shrikant shirude
Dec 22 '17 at 13:45

add a comment |

up vote
0
down vote

favorite

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 16299 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`56a0d000 PsLoadedModuleList = 0xfffff801`56d6eff0

Debug session time: Fri Dec 22 06:48:32.282 2017 (UTC - 5:00)

System Uptime: 0 days 0:01:31.548

*******************************************************************************

*                                                                             *

*                        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: ffffd28085f5e180, The PRCB address of the hung processor.

Arg4: 0000000000000003, 0.



Debugging Details:

------------------





OVERLAPPED_MODULE: Address regions for 'srv2' and 'dump_storpor' overlap



BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT



PROCESS_NAME:  iPodService.ex



CURRENT_IRQL:  d



STACK_TEXT:  

fffff801`58e64bc8 fffff801`56b9e586 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd280`85f5e180 : nt!KeBugCheckEx

fffff801`58e64bd0 fffff801`56a5cb98 : fffff801`55a66180 fffff801`55a66180 00000000`000016e3 00000000`00000000 : nt!KeAccumulateTicks+0x140186

fffff801`58e64c30 fffff801`572e24c6 : 0000004f`d149a472 00000000`00000000 ffffbc8c`fb1dadf0 00000000`00000001 : nt!KeClockInterruptNotify+0x5f8

fffff801`58e64f40 fffff801`56aabda5 : fffff801`57335550 fffff801`56b723fc fffff801`58e56b50 ffffd280`864cb780 : hal!HalpTimerClockInterrupt+0x56

fffff801`58e64f70 fffff801`56b727fa : ffffbc8c`fb1dae70 fffff801`57335550 00000000`00000000 ffffbc8c`fb1db128 : nt!KiCallInterruptServiceRoutine+0xa5

fffff801`58e64fb0 fffff801`56b72c47 : 00000000`6820c3bc 00000000`00001f40 ffffab07`00060000 fffff801`56b5405c : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffbc8c`fb1dadf0 fffff801`56a62a40 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffab07`480db010 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffbc8c`fb1daf80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x2a0





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

---------

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

asked Dec 22 '17 at 12:53

shrikant shirude

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 16299 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 16299.15.amd64fre.rs3_release.170928-1534

Machine Name:

Kernel base = 0xfffff801`56a0d000 PsLoadedModuleList = 0xfffff801`56d6eff0

Debug session time: Fri Dec 22 06:48:32.282 2017 (UTC - 5:00)

System Uptime: 0 days 0:01:31.548

*******************************************************************************

*                                                                             *

*                        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: ffffd28085f5e180, The PRCB address of the hung processor.

Arg4: 0000000000000003, 0.



Debugging Details:

------------------





OVERLAPPED_MODULE: Address regions for 'srv2' and 'dump_storpor' overlap



BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC



CUSTOMER_CRASH_COUNT:  1



DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT



PROCESS_NAME:  iPodService.ex



CURRENT_IRQL:  d



STACK_TEXT:  

fffff801`58e64bc8 fffff801`56b9e586 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd280`85f5e180 : nt!KeBugCheckEx

fffff801`58e64bd0 fffff801`56a5cb98 : fffff801`55a66180 fffff801`55a66180 00000000`000016e3 00000000`00000000 : nt!KeAccumulateTicks+0x140186

fffff801`58e64c30 fffff801`572e24c6 : 0000004f`d149a472 00000000`00000000 ffffbc8c`fb1dadf0 00000000`00000001 : nt!KeClockInterruptNotify+0x5f8

fffff801`58e64f40 fffff801`56aabda5 : fffff801`57335550 fffff801`56b723fc fffff801`58e56b50 ffffd280`864cb780 : hal!HalpTimerClockInterrupt+0x56

fffff801`58e64f70 fffff801`56b727fa : ffffbc8c`fb1dae70 fffff801`57335550 00000000`00000000 ffffbc8c`fb1db128 : nt!KiCallInterruptServiceRoutine+0xa5

fffff801`58e64fb0 fffff801`56b72c47 : 00000000`6820c3bc 00000000`00001f40 ffffab07`00060000 fffff801`56b5405c : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffffbc8c`fb1dadf0 fffff801`56a62a40 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffab07`480db010 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffbc8c`fb1daf80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x2a0





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

---------

windows windows-10

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

asked Dec 22 '17 at 12:53

shrikant shirude

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

asked Dec 22 '17 at 12:53

shrikant shirude

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

edited Dec 22 '17 at 13:26

Mokubai♦

55.9k16131150

asked Dec 22 '17 at 12:53

shrikant shirude

asked Dec 22 '17 at 12:53

shrikant shirude

asked Dec 22 '17 at 12:53

shrikant shirude

1

What have you tried? What has your research found? Has anything changed with your PC? When did this start?
– Mokubai♦
Dec 22 '17 at 13:26

re-installed OS , updated drivers ,fresh OS , no other application installed only GPU is added to my PC
– shrikant shirude
Dec 22 '17 at 13:39

Have you tried taking out the GPU? How often does it happen? How frequent is frequent? Is it once a month or every 5 minutes? edit your question to provide real details about your problem.
– Mokubai♦
Dec 22 '17 at 13:41

Yes, even if I remove the GPU BSOD is observed, every now and then the issues occurs. No pattern found for the issue
– shrikant shirude
Dec 22 '17 at 13:45

add a comment |

1

What have you tried? What has your research found? Has anything changed with your PC? When did this start?
– Mokubai♦
Dec 22 '17 at 13:26

re-installed OS , updated drivers ,fresh OS , no other application installed only GPU is added to my PC
– shrikant shirude
Dec 22 '17 at 13:39

Have you tried taking out the GPU? How often does it happen? How frequent is frequent? Is it once a month or every 5 minutes? edit your question to provide real details about your problem.
– Mokubai♦
Dec 22 '17 at 13:41

Yes, even if I remove the GPU BSOD is observed, every now and then the issues occurs. No pattern found for the issue
– shrikant shirude
Dec 22 '17 at 13:45

What have you tried? What has your research found? Has anything changed with your PC? When did this start?
– Mokubai♦
Dec 22 '17 at 13:26

re-installed OS , updated drivers ,fresh OS , no other application installed only GPU is added to my PC
– shrikant shirude
Dec 22 '17 at 13:39

Have you tried taking out the GPU? How often does it happen? How frequent is frequent? Is it once a month or every 5 minutes? edit your question to provide real details about your problem.
– Mokubai♦
Dec 22 '17 at 13:41

Yes, even if I remove the GPU BSOD is observed, every now and then the issues occurs. No pattern found for the issue
– shrikant shirude
Dec 22 '17 at 13:45

add a comment |

active

oldest

votes

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1279376%2fwindows-10-pc-frequently-crashing-with-errir-clock-watchdog-timeout%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Argthtjtr