Workaround for Windows 8 freezing issues
Posted: Sun Jul 28, 2013 9:58 am
As I was searching some tech info aout windows 8, I've found something that can maybe very helpful for some DAW users one day if win8 has freezing issue :
http://withinwindows.com/2012/06/28/wor ... ng-issues/
http://rog.asus.com/forum/showthread.ph ... zing-issue
The feature in itself is useless. It is supposed to "stop" the clock while the PC is idlying, in order to save power. The power you can actually save by doing so is laughable which makes this feature a joke for desktop computers (now for mobile devices it's another story and mobile applications will probably be built with dynamic tick in mind) . The reason why it's not working properly is because of what it is supposed to do. A great many deal of applications and drivers actualy depend on an accurate clock and "stopping" the clock kind of breaks that accuracy causing a gazzilion of problems. Forget fixing the damn thing and just disable it.
More explanations:
http://techmell.net/windows-tips/facing ... -solution/
http://techtrickz.com/how-to/fix-non-re ... ew-how-to/
According to Microsoft, this problem is due to an issue in the interaction between the state-machine driving dynamic tick transitions and the state-machine-driving clock rate changes.
You can solve the issue by disabling dynamic tick. [To disable dynamic tick, type the command “bcdedit /set disabledynamictick yes” at an elevated command prompt and press Enter]. However, this method will reduce the battery life and power optimizations of your PC.
Must try, who knows
http://withinwindows.com/2012/06/28/wor ... ng-issues/
http://rog.asus.com/forum/showthread.ph ... zing-issue
The feature in itself is useless. It is supposed to "stop" the clock while the PC is idlying, in order to save power. The power you can actually save by doing so is laughable which makes this feature a joke for desktop computers (now for mobile devices it's another story and mobile applications will probably be built with dynamic tick in mind) . The reason why it's not working properly is because of what it is supposed to do. A great many deal of applications and drivers actualy depend on an accurate clock and "stopping" the clock kind of breaks that accuracy causing a gazzilion of problems. Forget fixing the damn thing and just disable it.
More explanations:
http://techmell.net/windows-tips/facing ... -solution/
http://techtrickz.com/how-to/fix-non-re ... ew-how-to/
According to Microsoft, this problem is due to an issue in the interaction between the state-machine driving dynamic tick transitions and the state-machine-driving clock rate changes.
You can solve the issue by disabling dynamic tick. [To disable dynamic tick, type the command “bcdedit /set disabledynamictick yes” at an elevated command prompt and press Enter]. However, this method will reduce the battery life and power optimizations of your PC.
Must try, who knows
