Driver conflicts on my Windows 11PC

Clock jumps of hours or days are more commonly caused by the time source, virtualization integration, firmware, or software calling the Windows time API than by a generic driver conflict. Confirm the time zone and time settings, then run w32tm queries for status, source, peers, and configuration. At the next jump, review the System and Windows Time Service logs and record the old time, new time, source, and initiating event. Compare the firmware clock after a full shutdown. If the PC is domain joined, it should follow the Active Directory time hierarchy rather than a configured public server. If it is a virtual machine, compare the host clock and hypervisor time synchronization. Install BIOS and chipset updates from the manufacturer. Do not disable drivers. If the source changes unexpectedly or reports the local CMOS clock, repair the Windows Time configuration based on that evidence or escalate with the event logs.