What might be causing my blue screen - WIN32K_POWER_WATCHDOG_TIMEOUT

Martin Svoboda 26 Reputation points
2021-06-09T11:51:47.3+00:00

Dear Microsoft folk,
During the last two weeks, my work laptop had died (blue screen) and pointed out an error of WIN32K_POWER_WATCHDOG_TIMEOUT. I am not sure what driver might cause this as I have been in process of installing our work-related tools and such, so going back and uninstalling one by one is the last option for me. Is there any other way to pinpoint the potential culprit?
The issue happened after I closed my laptop and then put it to the docking station when instead of booting up the computer threw the error.

I include my latest .dmp file (I have changed the extension to .log, so I could upload it here, hope it works). Any help is highly appreciated, thanks in an advance.!

103850-060921-15390-01.log

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,709 questions
Accepted answer
  1. Docs 15,146 Reputation points
    2021-06-10T08:53:25.513+00:00

    1) Uninstall or uninstall and reinstall Crowdstrike

    2) Uninstall and reinstall igdkmd64.sys
    Intel GPU drivers

    start end module name
    fffff8004c690000 fffff8004c890000 csagent (no symbols)
    Loaded symbol image file: csagent.sys
    Image path: \??\C:\Windows\system32\drivers\CrowdStrike\csagent.sys
    Image name: csagent.sys
    Browse all global symbols functions data
    Timestamp: Wed Nov 25 13:06:32 2020 (5FBEC758)
    CheckSum: 001FC122
    ImageSize: 00200000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    2 people found this answer helpful.
    0 comments

9 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Docs 15,146 Reputation points
    2021-06-10T02:59:14.013+00:00

    Please run the V2 log collector so that files can be troubleshooted > post a share link into this thread

    https://www.windowsq.com/resources/v2-log-collector.8/
    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    1 person found this answer helpful.
    0 comments
  2. Docs 15,146 Reputation points
    2021-06-10T07:40:01.26+00:00

    Please post separate share links for:

    a) C:\Windows\LiveKernelReports\DripsWatchdog-20210608-1044.dmp
    b) C:\Windows\MEMORY.DMP

    LastWriteTime Size (MB) FullName

    08-Jun-21 10:44:44 AM 1786.99 C:\Windows\LiveKernelReports\DripsWatchdog-20210608-1044.dmp

    LastWriteTime Size (MB) FullName

    09-Jun-21 1:28:10 PM 2023.05 C:\Windows\MEMORY.DMP

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    1 person found this answer helpful.
    0 comments
  3. Docs 15,146 Reputation points
    2021-06-10T17:28:50.517+00:00

    How is the computer running?

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    1 person found this answer helpful.
    0 comments
  4. Martin Svoboda 26 Reputation points
    2021-06-09T11:52:14.073+00:00

    Probably a wrong tag, but I couldn't figure out which one to put.

    0 comments