none
Computer BSOD often, can't seem to work out whats wrong RRS feed

  • Question

  • Hey there! 

    I was wondering if anyone would be able to help me with my problem and after looking through the dump files myself (first time) I cant seem to work out whats wrong.

    My computer has been crashing displaying the error Clock Watchdog Timeout and will sometimes get caught in loops. I've reset my windows and reinstalled drivers and it's still happening, ill attach the dump file below.

    I would really appreciate any and all help I can get!

    https://mega.nz/#!VvQ2WSaa!AUPbucvvIF1K_xKNo_a-nhk-lmEta8kCvsofHalvoU0

    Sunday, January 5, 2020 8:50 AM

Answers

  • Hi

    Due to the dump analysis: the BUGCHECK id is 0x101 and the specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

    Below is the stack, from the stack we could not find anything useful, because the dump is the mini dump, we could not get more stack information.

    nt!KeBugCheckEx

    nt!KeAccumulateTicks

    nt!KiUpdateRunTime+0x56

    nt!KeClockInterruptNotify+0x44f

    hal!HalpTimerClockInterrupt+0x56

    nt!KiCallInterruptServiceRoutine+0x87

    nt!KiInterruptSubDispatchNoLockNoEtw+0xea

     nt!KiInterruptDispatchNoLockNoEtw+0x37

    Besides, according to the forum's security policy, please understand that we do not provide analysis of dump/log files.

    If you want to get deeper analysis, you’d better to create a support request:

    https://support.microsoft.com/en-gb/hub/4343728/support-for-business

    Hope can help you. Have a nice day!

    Best Regards

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, January 6, 2020 7:50 AM

All replies

  • The Dump File log suggests it is happening due to High Definition Audio Bus Driver file i.e. HDAudBus.sys driver.

    Uninstall,reinstall and update the related driver.


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP

    Monday, January 6, 2020 1:23 AM
  • Hi

    Due to the dump analysis: the BUGCHECK id is 0x101 and the specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

    Below is the stack, from the stack we could not find anything useful, because the dump is the mini dump, we could not get more stack information.

    nt!KeBugCheckEx

    nt!KeAccumulateTicks

    nt!KiUpdateRunTime+0x56

    nt!KeClockInterruptNotify+0x44f

    hal!HalpTimerClockInterrupt+0x56

    nt!KiCallInterruptServiceRoutine+0x87

    nt!KiInterruptSubDispatchNoLockNoEtw+0xea

     nt!KiInterruptDispatchNoLockNoEtw+0x37

    Besides, according to the forum's security policy, please understand that we do not provide analysis of dump/log files.

    If you want to get deeper analysis, you’d better to create a support request:

    https://support.microsoft.com/en-gb/hub/4343728/support-for-business

    Hope can help you. Have a nice day!

    Best Regards

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, January 6, 2020 7:50 AM
  • the dump was from "Windows 10 Kernel Version 10586": that was 1511.
    This is no longer supported, you need to update.
    Monday, January 6, 2020 7:50 AM
  • Hi,

    Just checking in to see if the information provided was helpful.

    Please let us know if you would like further assistance.

    Best Regards,

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 7, 2020 1:30 AM
  • Thank you for the help, sorry for breaking the rules.
    Tuesday, January 7, 2020 10:42 AM
  • You are welcome~

    Have a nice day!
    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, January 8, 2020 1:36 AM