Flickering Programs

This is an archive of the mabination.com forums which were active from 2010 to 2018. You can not register, post or otherwise interact with the site other than browsing the content for historical purposes. The content is provided as-is, from the moment of the last backup taken of the database in 2019. Image and video embeds are disabled on purpose and represented textually since most of those links are dead.

To view other archive projects go to https://archives.mabination.com

Skye wrote on 2011-11-29 01:35

This is what's happening on my computer.
[video=youtube;n7apP3M6fcQ]http://www.youtube.com/watch?v=n7apP3M6fcQ[/video]

The video description has a fix, but I don't wanna mess with anything if it screws my computer up.
So, basically, is this
[SPOILER="Spoiler"]
Sollution:
1. create a text file
2. rename it .reg instead of .txt
3. add this text into it

REGEDIT4
[HKEY_CURRENT_USER\Control Panel\Desktop]
"WaitToKillAppTimeout"="5000"
"HungAppTimeout"="5000"

[HKEY_LOCAL_MACHINE\SYSTEM\Cur*rentControlSet\Control]
"WaitToKillServiceTimeout"="5000"

[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
"WaitToKillAppTimeout"="5000"
"HungAppTimeout"="5000"

4. run your new file
5. restart PC
[/SPOILER]
a legit fix, or should I try something else?
Kueh wrote on 2011-11-29 01:37

I don't know if it'll work, but it doesn't look like you'll mess things up by doing it.

It would also be undo-able if it did go jank.
Bakuryu wrote on 2011-11-29 01:39

From that fix it seems the problem comes from windows thinking the program froze, so it turns the whole window gray (or completely white) like it usually does, except this time it only lasts very little time, which you see as the flickering.
That .reg file seems to make windows have to wait longer before considering a program as frozen, which would fix the problem.
So, yes, I'd try it.
Skye wrote on 2011-11-29 01:54

Alright. Seems to have stopped, so hopefully it's all good now. \o/
Thank you~
Yoorah wrote on 2011-11-29 02:03

You can always try, but I don't know if it'll help. Here's what the registry settings actually do, according to MSFT:

WaitToKillServiceTimeout:
Determines how long the system waits for services to stop after notifying the service that the system is shutting down. This entry is used only when the user issues a shut-down command by clicking the Shut Down button on the Windows 2000 Security dialog box or by selecting Shut down from the Shut Down Windows dialog box.

When the value of this entry expires, the system notifies the user that the service has not stopped. The user can either force the service task to stop or continue to wait. If the user waits, this value specifies the interval between repeated user notices that the service has not stopped.

If all services stop before this value expires, the system shuts down; it does not wait for this value to expire.

Note

Some services increase the value of this entry to provide more time for cleanup tasks.

WaitToKillAppTimeout:
Determines how long the system waits for user processes to end after the user attempts to log off or to shut down Windows 2000. When the time specified in this entry expires, the End Task dialog box appears, stating that the process did not respond. If the value of AutoEndTasks is 1, the system ends the process automatically.

HungAppTimeout:
Specifies how long the system waits for user processes to end after the user clicks the End Task command button in Task Manager . If this threshold is exceeded, the End Task dialog box appears, stating that the process did not respond.

These are from the Win 2k reference, but they are probably the same for Win 7, except for the default values.

EDIT: Er, glad it worked, regardless. xD Pretty strange.