You will then need to restart your computer. #FIREFOX 40.0.3 FLASH VIDEO CHOPPY WINDOWS#Then go to the tab that says "start up" You will want to uncheck EVERYTHING there except for "Microsoft windows operating system"" OK to find out what is running in the backround, and what is at startup, all you have to do is click the windows icon, the in the "search" bar type in "msconfig" (without quotations) I am an average user, so please keep things in simple terms. I would also like some help figuring out what is running in the background and starting up when I turn my computer on if turning off those things could help. Unfortunately, I didn't save a restore point at that time, so I can't go back. #FIREFOX 40.0.3 FLASH VIDEO CHOPPY DRIVERS#I did try to update some drivers (I think one was my video driver) and my Flash Player and some other things I can't remember around the time this happened. My wife actually has the exact same computer and her videos are fine at the same time mine are choppy and slow. I do have multiple computers and other things on my wireless internet connection, but this problem does not happen on the other computers. I also see what appear to be larger pixels in the middle of the video I am watching, almost like a picture-in-picture scenario. Up until a month or so ago, I had no problems watching internet videos on my computer. As for "ncolow", I don't recall seeing it before, and not sure what this is - Google is quite cryptic about it.Hello, I have a Toshiba laptop with windows 7圆4 and a dsl internet connection. Makes sense to presume they were not removed because the closures were forced (ie- symptom), but could be an indication that something else was wrong (ie- cause). I understand from problems with FF37 through FF39 that the FF stubs should NOT exist after FF is closed. In both cases, I manually END-TASK'd all FF stubs, and in both cases, "ncolow" quit itself when the last FF was ended. On the tower, seven or eight FF stubs and one "ncolow". On the laptop, Task Manager showed two FF stubs (typically about 2700 kb), with a single instance of "ncolow". Specifically, Firefox and something called "ncolow", neither of which were obviously open. #FIREFOX 40.0.3 FLASH VIDEO CHOPPY PATCH#It so happens that a routine update of my Norton Security program needed to apply a patch on each machine and waited for certain programs to close on each. #FIREFOX 40.0.3 FLASH VIDEO CHOPPY PC#I recently encountered FF non-responses on two PC machines (tower and laptop, both running Windows 7), including today. (Then usually cancel the Windows search for solution because nothing comes up anyway.) Occasionally, if I wait long enough, FF might eventually respond, but usually, I end up with the standard Windows "close program" / "wait for respond" popup, and close the program. I don't recall that clearing history made any difference. For example, a click-bait sequence of pages invariably results in a hang, where closing and restarting FF resumes and continues for a few more pages before hanging again. And re-visit doesn't seem to make a difference - sometimes a hang, sometimes not. But there is no rhyme or reason to the hangs - just sometimes they happen, other times not. The problematic sites for me are generally news & info sites (known lots of Flash there), but also various garden-variety sites that don't obviously/prominently use Flash but of course might do so. I saw somewhere (don't recall where) during the recent buzz over Flash vulnerabilities that FF may (or does) disable Flash, and that this may cause problems certain Flash-dependent pages. I've had several strange "FF not responding" situations since FF 40, and I was hoping it was fixed in the newly installed FF 41.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |