• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Program Not Responding Timeout Reg Edit

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Guest
ugh this is driving me nuts. i hope someone can help.

i performed multiple googles. but for the life of me i can not find the regedit for the value that controls the timeout for programs that "appear" to be unresponsive.

the exact problem.
is that when a game is loading a map or something that like midway the games window title bar displays the Not Responding. and if you click it dulls out and window and brings up that prompt to end the program or wait for it to respond.

i know there is a regkey for a value somewhere that tells w/e windows uses to classify a program as not responsive in milliseconds. or some odd measure of time.

i just need the regkey for the timeout value. god i hope someone knows what i am talking about. xD i swear it exists! i can only prey someone out there can help :/ :/

lmao help. and thank you. :-x
 
Possible cause here.
1. A real time antivirus system memory scanner is running causing the delay, as it is checking what is loaded into memory as its loaded from the HD. Two firewalls may be running at the same time and one is blocking the running process.
2.You have to much running at the same time on the system taking up too many cpu cycles say 95% load on the cpu you and the program is in line till the cpu usage drops to execute the file.
In any case I would Ctrl,Alt,Del and check what is running and the total cpu usage. Drop the load on the Cpu by exiting programs or tasks using alot of Cpu time and see if it times out when loading the game ect. also try to run the program as an administrator by right clicking on the icon and run as admin also. It should then have a higher priority to load the file if it can. If you find you have alot of things running and loading just after windows has. In windows 7 click on the pearl and in the search bar at the bottom type msconfig.
A window will open and you will see a tab athe top saying start up, click on it and you will see a list of programs that want to auto start after windows has loaded, simply untick the programs you dont want to run at start up and click apply. Restart your pc see if that helps.
 



no no it is none of that. all my search results yielded exactly this sorta thing.

this is actually a more of a common issue with windows 7. it has something to do with Desktop Windows Manager.

it has been close to a year since i owned a PC. but i do know every time i ever installed windows 7 i had this problem. it was always fixed by a simple regedit.

all it is that DWM THINKS a program is unresponsive when it really is just loading. i need to change the regkey value that tells DWM how long to wait before considering a program unresponsive.

now don't get me wrong. i do really appreciate the time you take to respond to thread. and your advice is sound. it just does not apply.

any further help you can offer is still greatly appreciated. as we speak i have still been trying to google it.
 
just in-case i was not very clear on the unresponsive part. the app does not crash or anything. there is just this brief moment while loading that DWM will think it to be unresponsive. the game loads fine though. i just can not find this blasted regkey :/
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

FOUND IT! and here is the regedit for the solution.

http://technet.microsoft.com/en-us/library/cc978614.aspx

the default value in windows 7 appears to be 500. ( a mere half second) maybe a bug after an update. but just edit it something like 20000(20seconds) and no more hung apps. :)

if anyone is having same problem with windows or apps hanging and getting that Not Responding crap for no reason. then try this edit.


anyhow. thank you, weaselman. for stopping by. the AV thing was not the case here. however... i am not a hundred percent sure, but it is quite possible the game i was running(windowed) did top out the CPU during the load causing a fault or something. then because HungAppTimeout was set so low it would immediately ghost out the window and bring up the kill prompt. without ever giving the app time to recover from the stall/fault. how ever there is no REAL problem with the app. silly windows :non:

the ghosting of the window itself causes apps to LITTERALLY stop responding momentarily. by increasing the HungAppTimeout you can prevent this ghosting.