I dual boot between windoze 10 and Arch Linux and every time that I do, both clocks are all out of whack. Is there a way to stop this from happening?

Windows always used to require hardware clocks to be set to local time. I don't know if it still does; I haven't used Windows for years. But if you do need to do this, you must tell your Linux system that the clock is set in this way. The quickest way is to run the hwclock program with the -l or --localtime option. Once hwclock has been given this information, it should default to local time every time it runs.

Do you mean timezones? Or something similar?

I see that, and when I go into the time setting (GUI form), amazingly things clear up before I can change anything. This is a phenomena I see when swapping from one boot to the other. Like it understands my timezone and when I notice that my time is off, I go to fix it, and viola, it becomes all set as soon as I've started to try to fix it. Sort of like it knew, but didn't do a whoa-ohh! Until I myself noticed and started to intervene.

What hazel said accords with my experience.

Linux customarily sets the time zone to UTC (what used to be called "Greenwich Mean Time") and then adjusts the clock display to be consistent with the local time zone via the timezone setting.

Windows sets the clock to local time. In a dual boot situation, the two operating systems will reset the hardware clock to fit their individual preferences.

I once resolved this problem on a machine that was dual-boot Fedora and Windows, but it was so long ago I forget how.

I did learn my way around the date and hwclock commands. I would set the system time with the date command, then use hwclock -w to set the hardware clock to reflect the system clock.

One workaround would be to change the Linux clock to local time.

In addition the hardware clock UTC/local time setting is kept in /etc/adjtime file. To summarize what was said above here is the Arch guide.

https://wiki.archlinux.org/index.php/Time

another would be to tell windows to use UTC.
i hear this is possible with some registry tweak (shudder).

Quite a few distros nowadays have an ntp client that starts at boot. Debian does for a start.
When I started having all this trouble with my hardware clock, I noticed that Debian still always came up with the correct time showing on the LXDE panel. I investigated and found that it was using ntp. So I installed ntp on Crux and LFS, and now they all three set the clock correctly, though LFS takes a couple of minutes to so so for some unknown reason.