DPC_WATCHDOG_VIOLATION caused by Creative Cloud?

Report · Jun 25, 2025

I got 3 BSODes this month. All of them were when the PC was idle and I only knew that because I found my PC restarted by itself and then through event viewer and minidump.

I tried to use WinDbg to investigate the minidump, and all of them are related to Creative Cloud. I won't rule out it could be other hardware or driver issue, but it's just strange that all are related to Creative Cloud.

If there's any hint or help that could solve the issue, would appreciate. I already tried most common solutions online and would try to get help from other sources as well.

My 1st and 3rd crashs (there are slight difference in some number and versions, but overall are same)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Creative Cloud.exe

STACK_TEXT:  
ffffa101`b0598a58 fffff805`a3826bc6     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffffa101`b0598a60 fffff805`a3826111     : fffff805`a45c43b0 00000000`030c2409 00000000`00000000 ffffa101`b0529180 : nt!KeAccumulateTicks+0x596
ffffa101`b0598ad0 fffff805`a3825e0e     : 00000000`00000018 00000000`01d10009 00000000`0000000d 00000000`030c240a : nt!KiUpdateRunTime+0xb1
ffffa101`b0598c90 fffff805`a38253d1     : 00000000`00000000 ffffa101`b0598ed9 ffffa101`b0529180 ffffb585`8bcf9000 : nt!KiUpdateTime+0x35e
ffffa101`b0598e50 fffff805`a38a9dac     : ffffb585`8b571a60 ffffb585`8b571b10 fffff805`a458e260 ffffa101`0000000d : nt!KeClockInterruptNotify+0x2e1
ffffa101`b0598f40 fffff805`a3ca67ae     : ffffb107`6e7c7a02 ffffb585`8b571a60 000a767e`ff302425 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffffa101`b0598fb0 fffff805`a3ca6fbc     : ffffb107`6e7c7760 00000000`00ffffff fffff805`a4415540 00000000`00ffffff : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffb107`6e7c7720 fffff805`a3a3af4f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffb107`6e7c78b0 fffff805`a38dac43     : 00000000`00000000 00000000`00000000 ffffa101`b0529180 00000000`00000000 : nt!KxWaitForLockOwnerShipWithIrql+0x6f
ffffb107`6e7c7930 fffff805`a390febd     : 00000000`00000080 ffffb107`6e7c7a71 ffffb585`ed6a9b20 00000000`00000000 : nt!KiAcquireQueuedSpinLockInstrumented+0x73
ffffb107`6e7c7970 fffff805`a391070e     : ffff8e76`5ef80f44 000a766d`d75d5297 ffffa101`b0529180 ffffb585`8bcf9cf8 : nt!KiAbEntryGetLockedHeadEntry+0x57d
ffffb107`6e7c79e0 fffff805`a39442f7     : ffffb585`00000000 ffffb585`ed6a9080 ffffb107`6e7c7b20 ffffa101`b05322f8 : nt!KiAbProcessThreadLocks+0x44e
ffffb107`6e7c7ad0 fffff805`a38e6173     : ffffb107`6e7c7e20 00000000`00000004 00000744`04d9aec6 ffffb586`0840d080 : nt!KiExecuteAllDpcs+0x4c7
ffffb107`6e7c7d20 fffff805`a3cac3b5     : 0e576036`8e30a9ed ffffa101`b0529180 ffffb586`0840d080 ffffa101`b0529180 : nt!KiRetireDpcList+0x333
ffffb107`6e7c7fb0 fffff805`a3cac35f     : ffffb107`88917800 fffff805`a38ae583 00000000`00000000 ffffa101`b0669180 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffb107`88917740 fffff805`a38ae583     : 00000000`00000000 ffffa101`b0669180 ffffa101`b0669180 00000000`0000000d : nt!KiPlatformSwapStacksAndCallReturn
ffffb107`88917750 fffff805`a3cab7ef     : ffffb585`ddc72d70 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
ffffb107`88917780 fffff805`a394de98     : 00000000`00000001 ffffb107`00000001 ffffb586`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffffb107`88917910 fffff805`a3a1e661     : 00000000`00000000 0000029c`c1ab6f28 0000029c`c1ab6f01 ffffa101`b0529180 : nt!KiExitDispatcher+0xc8
ffffb107`88917970 fffff805`a3fab323     : ffffb586`0840d080 ffffb107`88917aa0 ffffb585`ed6a9080 00000000`0000001b : nt!KeAlertThreadByThreadIdEx+0x61
ffffb107`889179b0 fffff805`a3cb7c55     : ffffb586`0840d080 ffffb107`88917aa0 00000000`0000001b 0000029c`c1ab6f28 : nt!NtAlertThreadByThreadIdEx+0x1d3
ffffb107`88917a20 00007ff8`d5682934     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d0`903ff658 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`d5682934


SYMBOL_NAME:  nt!KeAccumulateTicks+596

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.4343

STACK_COMMAND: .process /r /p 0xffffb585ddc72080; .thread 0xffffb5860840d080 ; kb

BUCKET_ID_FUNC_OFFSET:  596

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner

My 2nd crash has different process, but node.exe is under C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs\, and the parameter of this process is "C:\Program Files\Adobe\Adobe Creative Cloud Experience\js\main.js"

PROCESS_NAME:  node.exe

STACK_TEXT:  
ffffc801`a7d65a58 fffff805`93c26bc6     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffffc801`a7d65a60 fffff805`93c26111     : fffff805`949c43b0 00000000`0115290c 00000000`00000000 ffffc801`a7d49180 : nt!KeAccumulateTicks+0x596
ffffc801`a7d65ad0 fffff805`93c25e0e     : 00000000`00000018 00000000`00a53350 00000000`0000000d 00000000`0115290d : nt!KiUpdateRunTime+0xb1
ffffc801`a7d65c90 fffff805`93c253d1     : 00000000`00000000 ffffc801`a7d65ed9 ffffc801`a7d49180 ffff920f`80ed0000 : nt!KiUpdateTime+0x35e
ffffc801`a7d65e50 fffff805`93ca9dac     : ffff920f`805708a0 ffff920f`80570950 fffff805`9498e1a0 ffffc801`0000000a : nt!KeClockInterruptNotify+0x2e1
ffffc801`a7d65f40 fffff805`940a67ae     : ffffb30a`05f67a02 ffff920f`805708a0 0003b79e`64c22ad7 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffffc801`a7d65fb0 fffff805`940a6fbc     : 00000000`00200000 00000000`00ffffff fffff805`94815540 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffb30a`05f67720 fffff805`93e3af4f     : ffff920f`80dce040 fffff805`93dfc84e 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffb30a`05f678b0 fffff805`93cdac43     : 000001a0`b46b0e00 00000000`00000000 ffffc801`a7d49180 00000000`00000000 : nt!KxWaitForLockOwnerShipWithIrql+0x6f
ffffb30a`05f67930 fffff805`93d0feec     : 000001a0`b46b0e18 ffff920f`d5997d90 ffff920f`ea9f7b20 ffff920f`ed998b20 : nt!KiAcquireQueuedSpinLockInstrumented+0x73
ffffb30a`05f67970 fffff805`93d1070e     : 00000000`00000080 ffffb30a`05f67a71 00000000`00000000 ffff920f`80df50b8 : nt!KiAbEntryGetLockedHeadEntry+0x5ac
ffffb30a`05f679e0 fffff805`93d442f7     : ffff920f`00000000 ffff920f`ea9f7080 ffffb30a`05f67b20 ffffc801`a7d522f8 : nt!KiAbProcessThreadLocks+0x44e
ffffb30a`05f67ad0 fffff805`93ce6173     : ffffb30a`05f67e20 00000000`00000004 00000294`ccb60846 ffff920f`e1721080 : nt!KiExecuteAllDpcs+0x4c7
ffffb30a`05f67d20 fffff805`940ac3b5     : 00000000`00000000 ffffc801`a7d49180 ffff920f`e1721080 ffffc801`a7d49180 : nt!KiRetireDpcList+0x333
ffffb30a`05f67fb0 fffff805`940ac35f     : ffffb30a`1e307800 fffff805`93cae583 00000000`00000000 ffffc801`a7e89180 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffb30a`1e307740 fffff805`93cae583     : 00000000`00000000 ffffc801`a7e89180 ffffc801`a7e89180 00000000`0000000a : nt!KiPlatformSwapStacksAndCallReturn
ffffb30a`1e307750 fffff805`940ab7ef     : fffff805`23e30180 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
ffffb30a`1e307780 fffff805`93d4de98     : 00000000`00000001 ffffb30a`00000001 ffff920f`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffffb30a`1e307910 fffff805`93e1e661     : 00000000`00000000 000001a0`b46b0e18 000001a0`b46b0e01 ffffc801`a7d49180 : nt!KiExitDispatcher+0xc8
ffffb30a`1e307970 fffff805`943ab323     : ffff920f`e1721080 ffffb30a`1e307aa0 ffff920f`ea9f7080 00000000`00000000 : nt!KeAlertThreadByThreadIdEx+0x61
ffffb30a`1e3079b0 fffff805`940b7c55     : ffff920f`e1721080 ffffb30a`1e307aa0 00000000`00000000 000001a0`b46b0cf0 : nt!NtAlertThreadByThreadIdEx+0x1d3
ffffb30a`1e307a20 00007ffb`e1482934     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000089`36dff458 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`e1482934


SYMBOL_NAME:  nt!KeAccumulateTicks+596

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.4343

STACK_COMMAND: .process /r /p 0xffff920fd5997080; .thread 0xffff920fe1721080 ; kb

BUCKET_ID_FUNC_OFFSET:  596

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner

For all of them (exact number slightly different)

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000500, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff805949c43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

Report · Jun 25, 2025

time for a win 11 computer.

Report · Jun 25, 2025

This is Windows 11. If you don't believe, go to C:\Windows\System32 of your Windows 11 PC and right click on any system files to see it's version, they are all 10.0.2xxxx. If it's Windows 10, it would be 10.0.1xxxx.

Report · Jun 25, 2025

your error message shows win 10

Report · Jun 26, 2025

I have explained already, the error message means it's Win 11, as the version is 10.0.2xxxx.

I'm a software engineer and familiar with Windows. You can check https://en.wikipedia.org/wiki/Windows_11_version_history#:~:text=It%20carries%20the%20build%20number... to understand Windows 11 version.

The BSOD happened for the 4th time and it's similar to the 2nd crash (node.exe). So far all crashes root back to creative cloud.

I'm going to disable creative cloud, and if the issue would not happend, it probably means it is Creative Cloud that is broken.

Report · Jun 26, 2025

OSNAME:  Windows 10

is win 11?

Report · Jun 26, 2025

Yes, exactly, Windows 11 is basicly Windows 10 with UI and other changes, the system version is still Windows 10.

If you don't believe, check your Windows 11 PC, open regedit, and check the value under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProductName, you will find your Windows 11 is actually Windows 10.

Report · Jun 26, 2025

i don't have a ProductName key under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion

did you upgrade your win 10 to win 11?

Report · Jun 26, 2025

It's weired that you don't have it, and I actually suspect you may check it wrong (e.g., checked HKEY_CURRENT_USER, or Windows, not WIndows NT). I have checked 5 Windows 11 PC so far, personal PC, PC from company, and latest Surface Pro (ARM) which only supports Windows 11, and all of them shows Windows 10 as the ProductName in registry, with different suffix (Home, Pro, Enterprise, etc.).

Regarding your question about upgrade, no. This is a new PC bought more than 2 months ago. It came with Win11 Home, but I bought Win 11 Pro license myself and did a clean install using image created from Microsoft media creation tool (from official website in case you may doubt). In another word, it's a clean Windows 11 installation.

Based on file timestamp, the clean installation and installation of Adobe software happened around 5/5, and the issue only started from 6/8. However, I can see the latest Adobe Creative Cloud update was 6/6 (6.7.0.278), which was just 2 days before the first crash.

Considering all 4 crashes are related to Creative Cloud exes, and it started right after latest updates, all clues I have link to this program. I don't rule out that maybe my new PC has hardware issue but I already did all hardware checks.

Report · Jun 27, 2025

Report · Jun 27, 2025

Report · Jun 27, 2025

ah, right you are:

Report · Jun 27, 2025

Anyway, I disabled auto start option, 2 startup apps, and 1 task scheduler task that starts these processes. I still need to manually kill or restart PC after each time using Photoshop or they would run background again.

I would like to see if I will still get crash without Creative Cloud related processes running, or it's gone (at least for one month).

If you have any contact with Adobe, or Adobe engineer could see this post, please help investigate. I would happy to provide data or help debugging if time permit.

I know next week is break week for Adobe so it probably would be a long wait.

Report · Jun 27, 2025

@Shivangi_Gupta

Report · Jun 27, 2025

I see the same as kglad

Report · Jul 10, 2025

I am experiencing exactly the same problem here on Win 11, and have been sporadically since May 25th of this year. The sporadic DPC_WATCHDOG_VIOLATIONs, when they can be traced back to a specific app, always seem to originate in Creative Cloud. This is a huge problem and majorly impacts the stability of my OS. Please investigate this.

Report · Jul 10, 2025

try disabling security software to see if that stops the crashes.

Report · Jul 10, 2025

I do not have any third-party security software running on this computer at all.

Report · Jul 11, 2025

Hi @Ethan330163914y0a,

Thanks for reaching out! Could you please tell us the version of your operating system and the Creative Cloud Desktop app you're using? Also, could you share a screen recording of the issue you're seeing?

Please share the logs from your device, upload them to cloud storage, and share that link with us so we can download them and investigate further. For more information on how to generate logs check this link- https://adobe.ly/4eOTiYS

Regards,

Tarun

Report · Jul 11, 2025

Hi Tarun! My Creative Cloud version is 6.7.0.278, and I'm currently running Windows 11 Pro (though I just upgraded from Home) 24H2, build 26100.4652.

Regrettably a screen recording of this issue is not possible, as it is not a typical app crash. It causes Windows BugCheck events/"blue screens of death" that immediately shut down the computer and it also occurs in an almost completely unpredictable manner every few days, generally when the computer is not in any sleep mode but has been idle for hours.

Here is a Google Drive link to a general device log produced by the Log Collector program you just linked to me: https://drive.google.com/file/d/1O2rIugTkC-dca8mrBFU-Pj7Sm4AKYJcq/view?usp=drive_link

Below I have attached some excerpts from my most recent blue-screen memory dump (the full file is unfortunately no longer available) that I believe could be somewhat useful to Adobe engineers in diagnosing the issue.

Report · Jul 11, 2025

Thanks @Ethan330163914y0a for echoing my post. I suspect this issue is much more widespread than we two, but as it happens randomly (even if user is not in front of PC), most average user may not know their PC was crashed, or what's the error code, and can't trace it back to Adobe Creative Cloud. They may ignored unexpected restart from crash, or think it's Windows, hardware or other issues.

That said, I'm disappointed that community export tried to blame users for Windows version or security software. My first reaction would not be that any advanced user who has skills to trace the cause of the issue would make beginner's mistake.

You and me have same version of Creative Cloud, but your issue started about 2 weeks before me, which is interesting. Based on release note Release notes for the Adobe Creative Cloud desktop app this version was released on 6/11, but mine was installed on 6/6, so I doubt that release note is accurate. Could you check your install date? If that's right before your first issue, it could further increase the chance that the latest update introduced the issue. Otherwise there maybe other factors.

Report · Jul 14, 2025

Sadly I'm not sure that it is as simple as just the latest release having caused the error, after digging a little more. I can confirm that I indeed did experience a CC-related DPC_WATCHDOG_VIOLATION on May 25th, when I would have had to have been on CC version 6.6.0.611. It's possible that there may have been interactions with Windows updates in late April and mid-May (KB5055627, KB5058411) that might have triggered this.

Report · Jul 15, 2025

I woudl like to add on to this and say I am getting Adobe Creative cloud as the source of my DPC watchdog violation as of 2 weeks ago, seems like an error with this version of CC. Any ideas on a fix?

Report · Jul 15, 2025

you might be able to install an older version but that may cause more problems. and it might be easier to reinstall (or, at least repair) your os and reset and/or repair the cc app.

Report · Jul 15, 2025

I do not believe this is a os problem. I checked any system updates and made sure I had the latest drivers and BIOS updates for the entire system. The issue still persists with the origin coming from Creative Cloud.

If you could point me to an older version of the creative cloud desktop app I can attempt installing that