Heya folks, Ned here again. A few customers have reported this known issue on Windows 11 machines & you may see this event at boot up and perhaps occasionally afterwards. In the Event Log, in the Sys...
Updated Nov 07, 2022
Version 4.0
Blog Post
jimmyc2365 I managed to replicate the error and few other errors that show up in Windows 11, on Windows 10 by activating a single thing... There's this error with the powering of WiFi, the DCOM error, when DCOM server can't be accessed, and another one with nvvddm failing. I managed to replicate them with the nvidia gaming driver 512.15 on ASUS TUF FX15 FX507ZM, with an Intel Core i7 12th Gen, 16 GB DDR5, RTX 3060 and an Intel SSD M.2 NVMe 512 GB by activating HDR from advanced display settings on an external display Huawei MateView GT 34" connected via Thunderbolt 4 with USB-c to DP adapter. However, these issues don't show up if I use the HDMI connector on laptop. Also, I can't go to 165Hz refresh rate on DP anymore, but only to 144Hz after crashing. That is weird AF and I need to address it with nVidia too and try it with the Studio driver but also with older drivers. It seems that the drivers offered by Intel for Thunderbolt port and the nVidia drivers conflict with Windows somehow. Still looking into what actually happens. Some registry tempering is going on right before the crash and it happens in browsers too if you use hardware acceleration, not only when exiting games of After Effects. Will get back to you as soon as I find something new. Also, try deleting the virtual wifi adapter from registry. I had 2 of them for some reason (?) in the registry and deleted (2) but left (1) and I don't get that powering off error anymore. Anyhow, anywho and anyway... will keep pushing it to the limit and see how things go.