The system has been constrained to a periodic tick due to legacy hardware, System Event Log, Event ID 14
Thanks for your posting.
According to my research, event ID 14 relates to I/O. Since this is not a "Warning" or "Error", it is likely just an informative stating it made some adjustments to compensate for the I/O method your hardware is using.
Hope this helps.
- Edited by Vivian_WangMicrosoft contingent staff, Moderator Friday, February 21, 2014 6:00 AM
That was useful.
However we would really like to know more about this specific message which worded differently then the info in the URL you provided.
What is Windows indicating by "The system has been constrained to a periodic tick due to legacy hardware"?
What adjustment is made by Windows? What are the implications here?
A broader question: how do we get more detail for error messages generated by Windows like this one? I've tried to use the Event Viewer Online help feature and it does not help.
The message above is an information indicating that the dynamic ticks feature will not work and is being disabled
What is it ?
In short, it allows the periodic clock timer tick (which occurs every 15.6ms) to be deferred till the next due software timer in the system if all processors go idle
How it helps ?
This is a power management feature that lets the processor to stay in low power states for longer periods of time and not woken up by the timer interrupts.
If not supported on the specific hardware you will see that being detected by HAL and reported in the event logs.
This is a new feature in windows 8 and there is no public document from Microsoft at this point.
However, the below may provide some help.
3.2 Platform Timer Resolution
The operating system uses the Platform Timer to wake up the CPU and schedule processes. On Windows 7 this timer is usually triggered every 15.6ms while on Windows 8 the Operating System dynamically sets the timer resolution based on scheduling needs. Both Operating Systems allow applications to change the platform timer resolution so that they can better handle any time-critical tasks. For example, a video conferencing application may change the timer resolution to 1ms so that it can receive and decode frames as soon as possible. In general, a higher platform timer resolution will consume more power because the CPU is woken up more frequently. Use BLA to look at the platform timer resolution and to see if your application is changing it while idle and/or active.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.