DPC_WATCHDOG_VIOLATION caused by Creative Cloud?

[Mullen Studio]

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

[kglad]

well, there's some reason such a small minority of users see this while the rest of us do not.

and i do not recommend the following for this problem, but here it is:

uninstall every cc app including preferences per https://helpx.adobe.com/creative-cloud/help/uninstall-remove-app.html

then uninstall the cc desktop app, again using the correct uninstaller per https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html#sa_src=web-mes...

clean your computer of cc files per http://www.adobe.com/support/contact/cscleanertool.html

reinstall the cc desktop app using the "alternative download links" at the bottom of the page at https://helpx.adobe.com/download-install/kb/creative-cloud-desktop-app-download.html

[Ethan330163914y0a]

All I can say is that when three people independently come in one after another to report the exact same somewhat uncommon Windows BSoD code that can be traced back to one piece of software, my experience from years of triaging bugs as a software engineer leads me to regard it as a serious problem. This isn't the same deal as, say, the many random MEMORY_ACCESS_VIOLATIONs reported in recent years that have been traced back to hardware degradation on recent Intel CPU models; it is a stop code that is occurring quite consistently and originating from the same place every time for different people. Some investigation by Adobe is needed, even if the outcome is that there is some sort of hardware issue or problem with a Windows update patch. I'm sure I could eventually figure it out if they provided me with their debug symbols, but they cannot show me any proprietary code, so they need to investigate this.

[Mullen Studio]

My PC was new when started to have that problem, and I have very strict management regarding which apps could be installed especially at that time. Please don't shift the blame.

[Ethan330163914y0a]

Digging a little more through this, I've noticed that the crashes specifically originate from node.exe, version 20.18, present in the libs folder for the Creative Cloud Content Manager (CCXProcess.exe), version 6.6.6.4. Hope that's helpful.

[rosmo01]

I'm experiencing the excact same thing (Windows 11  (10.0.26100.4652)), so this is clearly a problem.

Finding the link requires knowledge of debugging dumpfiles, and also time, as this is intermittent, so likely more will report as time goes by.

Disabling CC related processes is a viable workaround until a fix is provided - so would be great with an update here if still working since Jul 11.

This definitely needs to be addressed by Adobe.

[Ethan330163914y0a]

Unfortunately, the timing of one of these BSoDs really messed up my OS during a scheduled update and I had to do an in-place network-based Windows reinstall (the only time this notoriously finicky option has ever worked for me, indicating yet again that my hardware is perfectly fine) to use my computer again. Since then I have avoided installing any Adobe products on the machine, using CC apps only on my MacBook Pro if/when I've had to use them. Lo and behold, no crashes at all in at least three weeks, and certainly no DPC_WATCHDOG_VIOLATIONs. Out of the very many content creation apps I use on the machine in its current iteration – and I really put it through its paces – Adobe CC apps are the only ones that have ever given me problems.

I've noticed that many of the machines experiencing this issue seem to contain Asus-branded Z890 Intel chipset motherboards and Intel Core Ultra 9 285K CPUs. I myself have that exact CPU in my machine, and use an Asus ROG MAXIMUS Z890 APEX motherboard. Not sure how helpful that is, but there you go.

[Mullen Studio]

Mine is Alienware, so it's not Asus to blame (I have other Asus or ROG products BTW).

So far interesting all PCs are 285k, not a single AMD or other Intel model. Can't say if that's deciding factor (please don't be another Intel CPU issue) as sample size is still small.

Could I assume your GPU is RTX 50 series as well? I think it’s unlikely to buy/build a PC with high-end CPU but without GPU, or Intel CPU with AMD GPU, or last gen GPU with latest CPU unless for specific reason.

[Mullen Studio]

Also update my latest status. After I disabled all Creative Cloud related processes, no BSDO so far for more than 2 weeks. However that is not long enough since 2 of my previous crashes were 14 days apart.

[kglad]

are you still able to start adobe apps without the background processes restarting?

[Mullen Studio]

Could still run Adobe apps without background processes, in which case when an Adobe app runs, some of the background processes will start automatcially, which means I would need to end them manually or restart the system again after using any Adobe apps to make sure my PC won't BSOD randomly.

[Mullen Studio]

Thanks @aaron.thomas and @rosmo01 for echoing the issue as well, and if any other users saw this post having the issue as well, please don't be silents, we need your +1 to convence community expert that this is a serious issue.

As @Ethan330163914y0a  and @rosmo01 pointed out, this is not a simple issue that average user could find where to blame, and it's so random that some PC may encounter that in the future. Even if it's already BSODed on 100,000 PCs, it's still possible that only 10 users have the willing and ability to find the root cause. Please let software engineering engage in it, it's beyond the knowledge requirement of tech support.

Btw, for all other users who are affected, would you mind if sharing hardware config in case the issue could be related to specific hardware? As I believe you all on latest software / system update / drivers / firmware so those information. Mine is Ultra 9 285k + RTX 5080.

I was on vacation in the past weeks which is why I was silent, but my PC was on during that time with Adobe background processes disabled. No BSOD for 5 weeks now. I'm planning to upgrade to a Gen 5 SSD this or next week, and will install clean OS then. So far I have not decided if I want to install Creative Cloud, or if I will disable all background processes.

[rosmo01]

My system is at latest end-to-end:

Asus ROG Maximus Z890 HERO, 

Corsair Vengeance DDR5 6400MHz 96GB, 

Intel Core Ultra 9 285K CPU,

Samsung 990 PRO NVMe M.2 SSD 2TB

ASUS PRIME GeForce RTX 5070 Ti OC

[robotlandman]

Chiming in with this exact same frustrating problem. I only have Illustrator, Acrobat, Audition, and Media Encoder installed from Creative Cloud Desktop on this Windows 11 PC. Everything is running the latest version of software. I've had 5 of these DPC_WATCHDOG_VIOLATION blue screens so far in the past two months. Sometimes it happens while the computer is idle and sometimes while I am using it. Each time the culprit is either the Creative Cloud process or the node.exe process associated with Creative Cloud. The PC hardware is:

• ASUS ProArt Z890-Creator WiFi Motherboard
• Intel Core Ultra 9 285K CPU
• Corsair Vengeance DDR5 5600 128GB RAM
• Crucial T700 Gen 5 NVMe M.2 4TB SSD
• MSI NVIDIA GeForce RTX 5090 Gaming Trio OC GPU

Here are the relevant crash details pulled from WinDbg for each one:

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

Loading Dump File [C:\Windows\Minidump\060925-14156-01.dmp]
Debug session time: Mon Jun  9 15:00:09.146 2025 (UTC - 4:00)
System Uptime: 15 days 3:54:01.265

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: fffff804ee7c33b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

Debugging Details:
------------------
BUGCHECK_CODE:  133
BUGCHECK_P1: 0
BUGCHECK_P2: 500
BUGCHECK_P3: 500
BUGCHECK_P4: fffff804ee7c33b0
FILE_IN_CAB:  060925-14156-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc18b3aaf4080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

PROCESS_NAME:  Creative Cloud

STACK_TEXT:  
ffffe600`e2f9dc28 fffff804`eda6df66     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffffe600`e2f9dc30 fffff804`eda6d49a     : fffff804`ee7c33b0 00000000`00000000 fffff780`00000320 ffffe600`e2f81180 : nt!KeAccumulateTicks+0x596
ffffe600`e2f9dca0 fffff804`eda6c871     : 00000bea`2d716cbb ffff8e05`07507700 ffffe600`e2f81180 ffff8e05`00000017 : nt!KiUpdateRunTime+0xca
ffffe600`e2f9de60 fffff804`eda56beb     : ffffc18a`b1578ae0 00000000`00000000 ffffc18a`b1578b90 fffff804`ee78e2d0 : nt!KeClockInterruptNotify+0x431
ffffe600`e2f9df50 fffff804`edea71fe     : ffff8e05`07507a02 ffffc18a`b1578ae0 00112854`f310ae3e 00000bea`2d747a85 : nt!KiCallInterruptServiceRoutine+0x31b
ffffe600`e2f9dfb0 fffff804`edea7a0c     : 00000000`00023ff0 00000000`00038000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffff8e05`07507760 fffff804`eda1281f     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffff8e05`075078f0 fffff804`edb7476d     : 000001d3`4ade84d8 ffffc18b`301beb20 ffffc18a`f74f0b20 ffffc18a`b1ad8000 : nt!KxWaitForLockOwnerShip+0x5f
ffff8e05`07507970 fffff804`edb74e9e     : 00000000`00000080 ffff8e05`07507a71 00000000`00000000 ffffc18a`b1dd6d58 : nt!KiAbEntryGetLockedHeadEntry+0x69d
ffff8e05`075079e0 fffff804`eda62b27     : ffffc18b`00000000 ffffc18b`301be080 ffff8e05`07507b20 ffffe600`e2f8a2f8 : nt!KiAbProcessThreadLocks+0x44e
ffff8e05`07507ad0 fffff804`edb6d956     : 00000000`00000000 00000000`00000000 00000bea`2eb1f83b ffffc18b`3aaf4080 : nt!KiExecuteAllDpcs+0x4c7
ffff8e05`07507d20 fffff804`edeace05     : 00000000`00000000 ffffe600`e2f81180 ffff8e05`1adc9740 00000000`00000000 : nt!KiRetireDpcList+0x326
ffff8e05`07507fb0 fffff804`edeacdaf     : ffff8e05`1adc9800 fffff804`eda5b343 00000000`00000000 ffffe600`e28a0180 : nt!KxSwapStacksAndRetireDpcList+0x5
ffff8e05`1adc9740 fffff804`eda5b343     : 00000000`00000000 ffffe600`e28a0180 ffffe600`e28a0180 ffffc18b`1b77db68 : nt!KiPlatformSwapStacksAndCallReturn
ffff8e05`1adc9750 fffff804`edeac23f     : 00000000`00960100 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
ffff8e05`1adc9780 fffff804`edac671e     : ffffc18b`00000001 00000000`00000001 ffffc18b`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffff8e05`1adc9910 fffff804`edc29cf1     : 00000000`00000000 000001d3`4ade84d8 000001d3`4ade8401 ffffc18b`301be080 : nt!KiExitDispatcher+0xce
ffff8e05`1adc9970 fffff804`ee1abc73     : ffffc18b`3aaf4080 ffff8e05`1adc9aa0 ffffc18b`301be080 000001d3`4ade83b0 : nt!KeAlertThreadByThreadIdEx+0x61
ffff8e05`1adc99b0 fffff804`edeb8655     : ffffc18b`3aaf4080 ffff8e05`1adc9aa0 000001d3`564df430 000001d3`4ade8510 : nt!NtAlertThreadByThreadIdEx+0x1d3
ffff8e05`1adc9a20 00007ffd`95e42da4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000c8`7a7ff828 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`95e42da4

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

Loading Dump File [C:\Windows\Minidump\071925-14609-01.dmp]
Debug session time: Sat Jul 19 00:35:10.866 2025 (UTC - 4:00)
System Uptime: 7 days 12:33:26.328

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: fffff8069c1c43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

Debugging Details:
------------------
BUGCHECK_CODE:  133
BUGCHECK_P1: 0
BUGCHECK_P2: 500
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8069c1c43b0
FILE_IN_CAB:  071925-14609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff8085d7b7e080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

PROCESS_NAME:  Creative Cloud

STACK_TEXT:  
ffff9580`d32fda68 fffff806`9b489236     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffff9580`d32fda70 fffff806`9b48876a     : fffff806`9c1c43b0 ffff8085`7d59c000 fffff780`00000320 ffff9580`d32e1180 : nt!KeAccumulateTicks+0x596
ffff9580`d32fdae0 fffff806`9b48843c     : 00000000`00000018 00000000`00000001 00000000`017a5a7d ffff9580`d32e1180 : nt!KiUpdateRunTime+0xca
ffff9580`d32fdca0 fffff806`9b48ecc9     : ffff8085`7d59bfa0 ffffd604`4c2e7700 ffff9580`d32e1180 00000000`0000000f : nt!KiUpdateTime+0x37c
ffff9580`d32fde60 fffff806`9b48f76b     : ffff8085`7d59bfa0 00000000`00000000 ffff8085`7d59c050 fffff806`9c18e678 : nt!KeClockInterruptNotify+0x2e9
ffff9580`d32fdf50 fffff806`9b8a782e     : 00000000`00000002 ffff8085`7d59bfa0 00088361`0451b5db 000005e9`69f9ac1c : nt!KiCallInterruptServiceRoutine+0x31b
ffff9580`d32fdfb0 fffff806`9b8a803c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffd604`4c2e77b0 fffff806`9b497962     : 00000000`00000020 00000000`00000000 00000000`00000000 00000000`00000202 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffd604`4c2e7940 fffff806`9b496188     : 0000022b`f73b2cf8 ffff8085`ac302db8 ffff8085`e4f0cb20 ffff8085`7dbd1000 : nt!ExpWaitForSpinLockSharedAndAcquire+0x62
ffffd604`4c2e7970 fffff806`9b42904e     : 00000000`00000080 ffffd604`4c2e7a71 00000000`00000000 ffff8085`7ddfa638 : nt!KiAbEntryGetLockedHeadEntry+0x4f8
ffffd604`4c2e79e0 fffff806`9b42a337     : ffff8085`00000000 ffff8085`e4f0c080 ffffd604`4c2e7b20 ffff9580`d32ea2f8 : nt!KiAbProcessThreadLocks+0x44e
ffffd604`4c2e7ad0 fffff806`9b4c7916     : 00000000`00000000 00000000`00000000 000005e9`690edc46 ffff8085`d7b7e080 : nt!KiExecuteAllDpcs+0x4c7
ffffd604`4c2e7d20 fffff806`9b8ad435     : 00000000`00000000 ffff9580`d32e1180 ffffd604`57e3f740 00000000`00000000 : nt!KiRetireDpcList+0x326
ffffd604`4c2e7fb0 fffff806`9b8ad3df     : ffffd604`57e3f800 fffff806`9b478243 00000000`00000000 00000000`00000002 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffd604`57e3f740 fffff806`9b478243     : 00000000`00000000 00000000`00000002 ffff9580`d26a8180 0000022b`fc0f7de0 : nt!KiPlatformSwapStacksAndCallReturn
ffffd604`57e3f750 fffff806`9b8ac86f     : ffff9580`d26a8180 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
ffffd604`57e3f780 fffff806`9b42663e     : 00000000`00000001 ffff9580`00000001 ffff8085`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffffd604`57e3f910 fffff806`9b666419     : 00000000`00000000 0000022b`f73b2d28 0000022b`f73b2d01 ffff8085`e4f0c080 : nt!KiExitDispatcher+0xce
ffffd604`57e3f970 fffff806`9bbb5703     : ffff8085`d7b7e080 ffffd604`57e3faa0 ffff8085`e4f0c080 00000000`00000000 : nt!KeAlertThreadByThreadIdEx+0x61
ffffd604`57e3f9b0 fffff806`9b8b8d55     : ffff8085`d7b7e080 ffffd604`57e3faa0 0000022b`8a5e4870 0000022b`f73b2c00 : nt!NtAlertThreadByThreadIdEx+0x1d3
ffffd604`57e3fa20 00007ffd`5b962c04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000038`64aff608 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`5b962c04

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

Loading Dump File [C:\Windows\Minidump\072725-14687-01.dmp]
Debug session time: Sun Jul 27 00:54:46.389 2025 (UTC - 4:00)
System Uptime: 8 days 0:18:51.140

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: fffff806ecdc43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

Debugging Details:
------------------
BUGCHECK_CODE:  133
BUGCHECK_P1: 0
BUGCHECK_P2: 500
BUGCHECK_P3: 500
BUGCHECK_P4: fffff806ecdc43b0
FILE_IN_CAB:  072725-14687-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff98861cf8c240

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

PROCESS_NAME:  node.exe

STACK_TEXT:  
ffffad00`a3efda68 fffff806`ec089236     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffffad00`a3efda70 fffff806`ec08876a     : fffff806`ecdc43b0 00000000`00000000 fffff780`00000320 ffffad00`a3ee1180 : nt!KeAccumulateTicks+0x596
ffffad00`a3efdae0 fffff806`ec08843c     : 00000000`00000018 00000000`00000001 00000000`0192fd61 ffffad00`a3ee1180 : nt!KiUpdateRunTime+0xca
ffffad00`a3efdca0 fffff806`ec08ecc9     : ffff9885`b559bfa0 ffff8702`2e6e7700 ffffad00`a3ee1180 00000000`0000000f : nt!KiUpdateTime+0x37c
ffffad00`a3efde60 fffff806`ec08f76b     : ffff9885`b559bfa0 00000000`00000000 ffff9885`b559c050 fffff806`ecd8e630 : nt!KeClockInterruptNotify+0x2e9
ffffad00`a3efdf50 fffff806`ec4a782e     : ffff8702`2e6e7a02 ffff9885`b559bfa0 00091148`25b23e73 0000064b`f5877325 : nt!KiCallInterruptServiceRoutine+0x31b
ffffad00`a3efdfb0 fffff806`ec4a803c     : 00000000`00000000 00000000`00000000 ffff9885`f2bb9080 ffffad00`a35e5180 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffff8702`2e6e7760 fffff806`ec05645f     : ffffad00`a35e5180 00000000`00000000 ffffad00`a35e5180 ffffad00`a35e5180 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffff8702`2e6e78f0 fffff806`ec09632d     : 000001ea`ecb927f8 ffff9886`05adcb60 ffff9886`1f098b60 ffff9885`b5fe4000 : nt!KxWaitForLockOwnerShip+0x5f
ffff8702`2e6e7970 fffff806`ec02904e     : 00000000`00000080 ffff8702`2e6e7a71 00000000`00000000 ffff9885`b5ddff38 : nt!KiAbEntryGetLockedHeadEntry+0x69d
ffff8702`2e6e79e0 fffff806`ec02a337     : ffff9886`00000000 ffff9886`05adc0c0 ffff8702`2e6e7b20 ffffad00`a3eea2f8 : nt!KiAbProcessThreadLocks+0x44e
ffff8702`2e6e7ad0 fffff806`ec0c7916     : ffff9886`1cf8c240 00000000`00000000 00000000`00000000 ffff9886`1cf8c240 : nt!KiExecuteAllDpcs+0x4c7
ffff8702`2e6e7d20 fffff806`ec4ad435     : 00000000`00000000 ffffad00`a3ee1180 ffff8702`3c1af740 00000000`00000000 : nt!KiRetireDpcList+0x326
ffff8702`2e6e7fb0 fffff806`ec4ad3df     : ffff8702`3c1af800 fffff806`ec078243 ffffad00`a31c0180 00000000`00000002 : nt!KxSwapStacksAndRetireDpcList+0x5
ffff8702`3c1af740 fffff806`ec078243     : ffffad00`a31c0180 00000000`00000002 ffffad00`a3ad1180 000001ea`8179ac00 : nt!KiPlatformSwapStacksAndCallReturn
ffff8702`3c1af750 fffff806`ec4ac86f     : ffffad00`a3ad1180 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
ffff8702`3c1af780 fffff806`ec02663e     : 00000000`00000001 ffff8702`00000001 ffff9886`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffff8702`3c1af910 fffff806`ec266419     : 00000000`00000000 000001ea`ecb927f8 000001ea`ecb92701 ffff9886`05adc0c0 : nt!KiExitDispatcher+0xce
ffff8702`3c1af970 fffff806`ec7b5703     : ffff9886`1cf8c240 ffff8702`3c1afaa0 ffff9886`05adc0c0 00000000`00000000 : nt!KeAlertThreadByThreadIdEx+0x61
ffff8702`3c1af9b0 fffff806`ec4b8d55     : ffff9886`1cf8c240 ffff8702`3c1afaa0 00000000`00000000 000001ea`ecb926d0 : nt!NtAlertThreadByThreadIdEx+0x1d3
ffff8702`3c1afa20 00007ff9`bed02c04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000002`27dff438 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`bed02c04

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

Loading Dump File [C:\Windows\Minidump\080425-14375-01.dmp]
Debug session time: Mon Aug  4 19:59:39.352 2025 (UTC - 4:00)
System Uptime: 8 days 19:04:06.500

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: fffff804b4fc43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

Debugging Details:
------------------
BUGCHECK_CODE:  133
BUGCHECK_P1: 0
BUGCHECK_P2: 500
BUGCHECK_P3: 500
BUGCHECK_P4: fffff804b4fc43b0
FILE_IN_CAB:  080425-14375-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb781f82f9080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

PROCESS_NAME:  node.exe

STACK_TEXT:  
ffffa601`d65edc28 fffff804`b4289236     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffffa601`d65edc30 fffff804`b428876a     : fffff804`b4fc43b0 00000000`00000000 fffff780`00000320 ffffa601`d67e5180 : nt!KeAccumulateTicks+0x596
ffffa601`d65edca0 fffff804`b428ee11     : 000006e9`27cebc94 ffffa508`61107700 ffffa601`d67e5180 ffffa508`00000007 : nt!KiUpdateRunTime+0xca
ffffa601`d65ede60 fffff804`b428f76b     : ffffb781`985916e0 00000000`00000000 ffffb781`98591790 fffff804`b4f8e690 : nt!KeClockInterruptNotify+0x431
ffffa601`d65edf50 fffff804`b46a782e     : ffffa508`61107a02 ffffb781`985916e0 0009f3a5`643924fc 000006e9`27d1ca5b : nt!KiCallInterruptServiceRoutine+0x31b
ffffa601`d65edfb0 fffff804`b46a803c     : 000006e9`1be4d23c 00000000`00030000 09101313`13130000 00000000`00000913 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffa508`61107760 fffff804`b425645f     : ffffb781`98dd3040 ffffb781`98be7090 00000000`00000400 fffff804`b4364c1b : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffa508`611078f0 fffff804`b429628a     : 00000000`00000080 ffffb781`fe8ebb20 00000000`00000000 ffffb781`98bcf000 : nt!KxWaitForLockOwnerShip+0x5f
ffffa508`61107970 fffff804`b422904e     : 00000000`00000f44 0009f394`39cb4ce2 00000000`00000000 ffffb781`98df0838 : nt!KiAbEntryGetLockedHeadEntry+0x5fa
ffffa508`611079e0 fffff804`b422a337     : ffffb781`00000000 ffffb781`fe8eb080 ffffa508`61107b20 ffffa601`d67ee2f8 : nt!KiAbProcessThreadLocks+0x44e
ffffa508`61107ad0 fffff804`b42c7916     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb781`f82f9080 : nt!KiExecuteAllDpcs+0x4c7
ffffa508`61107d20 fffff804`b46ad435     : 456d4a00`456cc0a0 ffffa601`d67e5180 ffffa508`73eef740 457088f9`456ffdad : nt!KiRetireDpcList+0x326
ffffa508`61107fb0 fffff804`b46ad3df     : ffffa508`73eef800 fffff804`b4278243 00000000`00000000 00000000`00000002 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffa508`73eef740 fffff804`b4278243     : 00000000`00000000 00000000`00000002 ffffa601`d6e61180 000002e5`11e69f30 : nt!KiPlatformSwapStacksAndCallReturn
ffffa508`73eef750 fffff804`b46ac86f     : ffffa601`d6e61180 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
ffffa508`73eef780 fffff804`b422663e     : 00000000`00000001 ffffa601`00000001 ffffb781`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffffa508`73eef910 fffff804`b4466419     : 00000000`00000000 000002e5`0e6631b8 000002e5`0e663101 ffffb781`fe8eb080 : nt!KiExitDispatcher+0xce
ffffa508`73eef970 fffff804`b49b5703     : ffffb781`f82f9080 ffffa508`73eefaa0 ffffb781`fe8eb080 00000000`00000000 : nt!KeAlertThreadByThreadIdEx+0x61
ffffa508`73eef9b0 fffff804`b46b8d55     : ffffb781`f82f9080 ffffa508`73eefaa0 000002e5`122c1ba0 000002e5`0e663080 : nt!NtAlertThreadByThreadIdEx+0x1d3
ffffa508`73eefa20 00007ffb`f0882c04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000fe`93fff528 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`f0882c04

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

Loading Dump File [C:\Windows\Minidump\080625-15656-01.dmp]
Debug session time: Wed Aug  6 15:38:01.186 2025 (UTC - 4:00)
System Uptime: 1 days 19:37:53.625

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: fffff803d91c43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

Debugging Details:
------------------
BUGCHECK_CODE:  133
BUGCHECK_P1: 0
BUGCHECK_P2: 500
BUGCHECK_P3: 500
BUGCHECK_P4: fffff803d91c43b0
FILE_IN_CAB:  080625-15656-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd70774f56080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

PROCESS_NAME:  Creative Cloud

STACK_TEXT:  
ffffc300`054c7a68 fffff803`d8489236     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
ffffc300`054c7a70 fffff803`d848876a     : fffff803`d91c43b0 00000000`00000000 fffff780`00000320 ffffc300`054a8180 : nt!KeAccumulateTicks+0x596
ffffc300`054c7ae0 fffff803`d848843c     : 00000000`00000018 00000000`00000001 00000000`005b6dcb ffffc300`054a8180 : nt!KiUpdateRunTime+0xca
ffffc300`054c7ca0 fffff803`d848ecc9     : ffffd707`1158cea0 fffff902`2b267700 ffffc300`054a8180 00000000`0000000f : nt!KiUpdateTime+0x37c
ffffc300`054c7e60 fffff803`d848f76b     : ffffd707`1158cea0 00000000`00000000 ffffd707`1158cf50 fffff803`d918e5e8 : nt!KeClockInterruptNotify+0x2e9
ffffc300`054c7f50 fffff803`d88a782e     : 00000000`00000002 ffffd707`1158cea0 00020eb1`0972029e 0000016d`b730488a : nt!KiCallInterruptServiceRoutine+0x31b
ffffc300`054c7fb0 fffff803`d88a803c     : 00000000`00000001 fffff803`d8426cdc 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff902`2b2677b0 fffff803`d8497962     : 00000000`00000020 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff902`2b267940 fffff803`d8496188     : 00000125`2e79c168 ffffd707`470c8d90 ffffd707`74f5eb20 ffffd707`11ff8000 : nt!ExpWaitForSpinLockSharedAndAcquire+0x62
fffff902`2b267970 fffff803`d842904e     : 00000000`00000080 fffff902`2b267a71 00000000`00000000 ffffd707`11df0998 : nt!KiAbEntryGetLockedHeadEntry+0x4f8
fffff902`2b2679e0 fffff803`d842a337     : ffffd707`00000000 ffffd707`74f5e080 fffff902`2b267b20 ffffc300`054b12f8 : nt!KiAbProcessThreadLocks+0x44e
fffff902`2b267ad0 fffff803`d84c7916     : 00000000`00000000 00000000`00000000 0000016d`b624fc8f ffffd707`74f56080 : nt!KiExecuteAllDpcs+0x4c7
fffff902`2b267d20 fffff803`d88ad435     : 00000000`00000000 ffffc300`054a8180 fffff902`3ddaf740 00000000`00000000 : nt!KiRetireDpcList+0x326
fffff902`2b267fb0 fffff803`d88ad3df     : fffff902`3ddaf800 fffff803`d8478243 00000000`00000000 00000000`00000002 : nt!KxSwapStacksAndRetireDpcList+0x5
fffff902`3ddaf740 fffff803`d8478243     : 00000000`00000000 00000000`00000002 ffffc300`057e5180 00000000`00000000 : nt!KiPlatformSwapStacksAndCallReturn
fffff902`3ddaf750 fffff803`d88ac86f     : 00000000`00000100 00000000`00000020 00000000`00000000 00000000`00000020 : nt!KiDispatchInterrupt+0x63
fffff902`3ddaf780 fffff803`d842663e     : ffffd707`00000001 fffff902`00000001 ffffd707`00000001 00000000`00000000 : nt!KiDpcInterrupt+0x39f
fffff902`3ddaf910 fffff803`d8666419     : 00000000`00000000 00000125`2e79c168 00000125`2e79c101 ffffd707`74f5e080 : nt!KiExitDispatcher+0xce
fffff902`3ddaf970 fffff803`d8bb5703     : ffffd707`74f56080 fffff902`3ddafaa0 ffffd707`74f5e080 00000000`0000001b : nt!KeAlertThreadByThreadIdEx+0x61
fffff902`3ddaf9b0 fffff803`d88b8d55     : ffffd707`74f56080 fffff902`3ddafaa0 00000000`0000001b 00000125`2e79c1a0 : nt!NtAlertThreadByThreadIdEx+0x1d3
fffff902`3ddafa20 00007ff8`6b402c04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000015`b35ff578 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`6b402c04

 Happy to troubleshoot, provide more data, etc. if that is helpful to the root cause and fix.

[J21958590duv6]

+1 this issue.  I built a new computer earlier this year and started getting this exact BSOD related to Creative Cloud/node.exe shortly after installing CC.  I uninstalled CC after and was stable for a long time but eventually needed photoshop again.

I was able to get some semblance of stability with CC by renaming all the node.exe files to node.bak  but eventually the product updated and repaired those exe and now it's crashing again

I see crashes typically within 48 hours and not always when the computer is Idle.  when it first started happening I would get BSOD in the middle of a game.  I chased general forums on watchdog errors for weeks now before finding this thread. did memory tests, driver updates everything. 

Unfortunately I'm also a RTX 50xx and Intel CoreUltra 9 285K computer so while I do think this is an issue with Creative Cloud (nothing else causes this) likely the problem is endemic to this hardware.  Given the popularity and broader adoption of the RTX 50xx series cards i'm leaning towards this being a bad interaction with the CPU.  

I don't see Adobe or Intel fixing this any time soon, at least not directly.  Though perhapse narrowing it to CPU might help find a workaround, maybe disabling some CPU features via BIOS or whatnot will stop the issue. 

[Mullen Studio]

Actually the idea of renaming node.exe is interesting. I'm wondering if you could try to create a empty file like node.txt, renaming it to name.exe, and changing the property to read-only? Maybe in that way it can stop updating, if that would not lead to any error.

[J21958590duv6]

Hmm, I hadn't thought about replacing it with a fake.  I just created a quick AutoIt script that will pop up a message when run and display any arguments passed to it. then compiled it to a Node.exe. Should let me know when it's kicked off.

For now i've also renamed some CC executibles to prevent them from running at all since I don't need photoshop right now. hoping I can at least not crash in the times i'm not actively using PS. 

Some other thoughts though. It's not clear that Node is actually the problem directly,  I suspect it's Creative Cloude.exe that's really the issue and maybe it's not what it's doing but how it's starting or accessing node. It's possible is that it's a power/background-thread issue and it's not waking up correctly before the watchdog timeout occurs. 

One workaround may be finding the CC or Node process and giving it above normal priority in Task Manager, that may allow it to operate without triggering a sleep state that causes the timeout (assuming that's the issue at all)

[codeymj]

I also get this crash every few days, but only if I have Creative Cloud installed. PC is less than a year old. Tech support at the company that built the PC are the ones who pointed out to me that Creative Cloud was behind the crashes. For 4 weeks I uninstalled CC and had no crashes. Then I reinstalled CC and immediately crashes started again. Like for the OP, they usually happen when the PC is not being used.

There was a point at which these crashes did not happen but I'm not sure how long ago it was or which version of CC did not cause crashes. It has been like this for a few months.

PC specs:

Intel Core Ultra 9 285K @ 3.70 GHz

Kingston FURY BEAST RGB 64 GB RAM

ASUS ROG STRIX Z890-E gaming motherboard

NVIDIA GeForce RTX 4090 Founders Edition 24 GB

OS drive Kingston FURY Renegade 4TB

Data drive Kingston FURY Renegade 4TB

Windows 11

Latest crash reports via WhoCrashed:

On Thu 8/28/2025 11:42:34 AM your computer crashed or a problem was reported

Crash dump file:	C:\WINDOWS\Minidump\082825-8968-01.dmp (Minidump)
Bugcheck code:	0x133(0x0, 0x500, 0x500, 0xFFFFF80588BC43B0)
Bugcheck name:	DPC_WATCHDOG_VIOLATION
Bug check description:	The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
Analysis:	This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck.

On Thu 8/28/2025 11:42:34 AM your computer crashed or a problem was reported

Crash dump file:	C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x133(0x0, 0x500, 0x500, 0xFFFFF80588BC43B0)
Bugcheck name:	DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred:	fffff805`87e91dd3 : 00000279`2bbd2648 ffff8081`103c5b30 ffff8081`103c5b40 ffffb281`647b5180 : nt.sys (fffff805`87e91dd3 : 00000279`2bbd2648 ffff8081`103c5b30 ffff8081`103c5b40 ffffb281`647b5180 : nt!KeA...)
Bug check description:	The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
Analysis:	This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck.
Google query:	fffff805`87e91dd3 : 00000279`2bbd2648 ffff8081`103c5b30 ffff8081`103c5b40 ffffb281`647b5180 : nt DPC...

[Mullen Studio]

Thanks, and your example rules out Geforece 50 series and further confirmed that it may be compatibility issue with 285k.

I hope the many instances we have so far can get some attentions from Adobe engineers. Let me tag @Tarun Saini who had replied this thread to try our luck. I'm sure everyone here are willing to and likely capable to help investigate the issue, and we don't want to leave our new high-end PCs unstable or stop using Adobe softwares forever.

[Lloyd_mcse]

Hi everyone,

+1 on this, I haven't read through the whole thread but, WinDbg has come back with node.exe and Creative Cloud as the faulting process every time.

I first thought it was node.exe from the Nvidia Driver, so have been shutting down the Nvidia app which has seemed to help in that the BSOD has occurred betwen 4 and 6 days uptime instead of 2 days. And 

The last time I had anything like this was around the time of the Nvidia GTX 770, and Nvidia's driver would cause a crash after, I think it was 36 hours, and that was a DPC_WATCHDOG_VIOLATION.

Back on topic, I too am running an Intel Core Ultra 9 285K, along with an Asus ProArt Z890, and RTX 5060 Ti 16GB, but I was getting exactly the same on my RTX 3060 so ruled that out.

Anyway, I hope Adobe get this issue sorted asap!