Hello DD,
This is a sophisticated interoperability issue involving the Windows 11 Desktop Window Manager (DWM) composition engine and the WDDM 3.x driver model, which handles pixel format negotiation and swapchains differently than Windows 10. To answer your question regarding a supported execution switch or registry key: there is currently no documented registry value or Group Policy exposed by Microsoft that explicitly disables temporal dithering at the DWM level in Windows 11. The operating system creates a composition surface, often at a higher bit-depth (FP16 or 10-bit) to accommodate transparency and HDR-ready pipelines, and relies on the GPU driver to downsample the final frame to the monitor's capability. This process can introduce the modulation or "dithering" you are perceiving if the DWM forces a presentation model that requires it.
Since you have already disabled Multiplane Overlay (MPO) via the registry, the most effective method to force the OS back to a legacy composition behavior is to disable the modern presentation features that rely on the new "Flip" model. You need to navigate to Settings > System > Display > Graphics > Change default graphics settings and strictly turn Off both Hardware-accelerated GPU scheduling (HAGS) and Optimizations for windowed games. Disabling these features forces the DWM to revert to legacy resource management and often forces the "Legacy Blt" presentation model instead of the modern "Flip" model. This change reduces the complexity of the composition pipeline and can stop the specific frame modulation associated with modern DWM rendering paths. A system restart is mandatory for these changes to apply to the kernel.
Furthermore, you must ensure the OS is not internally composing at a higher bit depth despite your driver settings. Even if you set the NVIDIA driver to 8 bpc, Windows 11 DWM may read the monitor's EDID (Extended Display Identification Data) and see "Advanced Color" or 10-bit readiness, prompting it to compose in high precision and dither down. Check Settings > System > Display > Advanced display. If the "Bit depth" line says anything other than a flat "8-bit" (for example, "8-bit with dithering" or "10-bit"), the OS is overriding your driver preference. To resolve this, you may need to strip the EDID extension blocks that advertise 10-bit or HDR support using an EDID override tool, forcing Windows to see the device strictly as a legacy 8-bit panel. This removes the DWM's trigger to apply downsampling algorithms.
If these steps do not alleviate the physical symptoms, the behavior is intrinsic to the current WDDM 3.x kernel implementation in Windows 11 and cannot be disabled without future updates from the product engineering team.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
VP