DDR stands for Dual data rate, if you think of data being transmitted on a frequency, that's a sine wave, DDR transmits on rise and fall, not just rise like the old SD-Ram (single data). Cpu-z, Windows (now) and a few other programs report the Data Rate, not the Dual data rate, so cpu-z saying 533MHz really means 1066MHz according to the ram.
Timings are a range per speed. You'll see that with xmp or jadec tables. The slower the Hz, the smaller the timings. 1600 was often 9-9-9-27, but the same ram at 1866 would have been 10-11-10-30 instead. Tightening the timings would be 1866 at 9-10-9-27. It's all relative. Corsair Dominator ram was the cats meow, it'd run 1600 at 6-7-6-21 etc. So the timings aren't tighter as such, just smaller, per respective speed.
1600 cl9 was a very small hair slower than 1866 cl10, but 1600 cl8 was the same amount faster than 1866 cl10.
Everything takes time. The timings are like the time it takes to open the door, how many paces to cross the room, open the next door. The speed is how fast your feet move. So even if you move your feet very fast, if the timings are really loose, that's a lot of very short steps, (think geisha). You can have really slow moving feet instead that uses less paces (giant steps) to cross the room, so ends up faster overall.
If all your errors are occurring after a long time period, all day, I'd suspect a memory leak more than a hardware issue. A memory leak is badly implemented software that's running, but not releasing the ram when it's done with a command.
So if you open a tab, and it uses 100mb of ram to open, that ram is reserved for that tab opening. When you close it, it cancels the reservation and the ram returns to the pool. With a memory leak, the reservation isn't canceled. That 100mb is still reported as being in use, so the next service or process to run has your 32Gb, minus 100mb. If it's a constantly used service, like Antivirus checker that's pulling 100Mb at a time, and not releasing it, it won't take long before that 32Gb gets used up, reserved for the Antivirus service, and then runs out of resources, leaving windows with zip for ram, so crashes.
What you do is wait 10 hours or so, then check ram use and available ram, figure out what program is soaking it all up. After that disable the program, reinstall it, update it, do whatever it requires to fix it.