# Error: Synchronization Failure **URL:** \ **Category:** Programming Help\ **Tags:** windows\ **Created:** [January 6, 2022, 1:05pm UTC](https://psychtoolbox.discourse.group/t/error-synchronization-failure/4176 "2022-01-06T13:05:35Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [January 9, 2022, 7:11pm UTC](https://psychtoolbox.discourse.group/t/error-synchronization-failure/4176/6 "2022-01-09T19:11:09Z")
That setting may help against broken hardware vsync, at drastically increased cpu load, but can not generally work around triple-buffering. Your “consistent one frame lag” will not be consistent at all in many common scenarios, so if that worked for you, it was a lucky special case - or you fooled yourself, depending on how you verified it. I am not aware of a generally working solution for triple-buffering or n-buffering with n != 2 wrt. reliable timing, and i thought a lot about that in the past as well. Your detection script may work to detect its presence in many cases if n == 3, but your workaround is not recommended to anybody reading this, unless they have a deep understanding of how modern gpu’s + drivers work and how that interacts with their paradigm. On Linux, PTB can reliably detect triple-buffering if that is a problem, thanks to OS mechanisms that help. On recommended hw + drivers, n-buffering doesn’t matter at all for reliability and can be even used for performance/stability enhancement. The advice for most people with timing or reliability needs is the same: Upgrade to Linux whenever possible, but especially for Intel graphics. Back to vacation… -mario --- _[View the full topic](https://psychtoolbox.discourse.group/t/error-synchronization-failure/4176)._