Windows XP

A Former User

Bird, to clarify, it is not a freeze-freeze, it is a non-connection-"freeze".

I would find the Administrative tools, I guess, then it's this "Russian translation": lots of things are hard to find having directions in one language and cramping in another :doh:
When then to open that thing, you're saying? Provided I find it*:)*

Just took a look. I guess I've found it: the translation, surprisingly, is not confusing, for a change

blackbird71

blackbird71

The event log should be a history of events that the system detects or that apps report to the system as events. Many of them will be normal starts or stops of services and such, but things that are somewhat abnormal get yellow warning flags and things that actually cause an error get a red 'x' flag. In most systems I've run into, there will always be a scattering of yellow flags in ordinary usage with a small number of occasional (and obscure) red errors that pop up in the history. The main usefulness is when an issue occurs that causes usage problems, one can go into the logs and sometimes find flagged events that happen just prior to and during the onset of the main issue's time of occurrance. These can sometimes provide clues about other programs or even hardware elements that might have misbehaved just before the main issue was noticed by the user.

While they're typically not as effective for pinpointing causes as a true crash log, they do occasionally provide clues to troubleshoot a problem - mainly because apps frequently don't create much, if any, crash log when they freeze. In any case, the event logs are present on all the Windows versions from XP onward, so they essentially "come free" and may sometimes be better than nothing in trying to figure out what happened. This is particularly true if multiple failures have occurred over time and similar related events happen to appear surrounding each in the event log.

A Former User

@joshl

Just following up on our Firefox discussion off-topic on another thread, if you are still using Flash to play Facebook videos on Firefox 52 ESR, are you aware that it's possible to get a plugin to allow it to use HTML5 video on XP, which in my opinion performs much better?
See here.

A Former User

Black, yesterday happened, Event Logger didn't have anything at all.

Dave, Facebook videos aren't a problem so ain't worth a breath. Thanks.

blackbird71

blackbird71

The Event Viewer is primarily useful in pointing at something whose failure it can capture. Lack of a recorded event doesn't necessarily prove there are no failures. Two of the areas that often go uncaptured are internal apps failures (eg: purely within Opera) and certain erratic hardware issues (eg: RAM chips).

Are you experiencing any kinds of repeating failures or issues with any other application software? If you run a different browser consistently for a while, does it ever show any similar problems to Opera's?

The idea is to isolate whether the problem is global in some way(s) or whether it might involve the system's interface elements with which the browser communicates. If neither is true, then you may be dealing with a defective Opera installation (including defective or rogue registry entries). It's much less likely that the version itself contains this kind of bug in its code, else there would have been many multiple reports of the same problem details by this point in time.

My long experience has been that over time, hardware deteriorates; likewise, software can and does sometimes deteriorate (due to file corruption, media errors, etc). There's kind of a Law of Entropy constantly at work in digital systems, such that the older the system, the more often certain things start to go wrong or fail to work. The cause(s) may or may not be easily traced back and repaired, and the older the system and software, the bigger the role that pure-guesswork/instinct/past-experience plays in resolving problems.

A Former User

Are you experiencing any kinds of repeating failures or issues with any other application software? If you run a different browser consistently for a while, does it ever show any similar problems to Opera's?

Nope.
Nothing similar even remotely. No.
(My messenger can very occasionally lose its connection, but it's incomparable and unclear why.)

blackbird71

blackbird71

Pulling out the technical problem flow in this thread's posts, you wrote (with my various emphases):

On April 22: Something wrong with this browser! (FF) There was no update since February, but right now recently - a couple of days - it started acting like it can't load stuff, some spinning cogwheels, bars about a page troubling the browser; I can't measure my speed with speedtest.net any more (doesn't load the laptop), having trouble playing videos even 240p, and the pornhub player won't even load. Right, took for granted, but it was the first thing: it started being slow right from the open (not as its usual 3-day session tired).

And again on April 22: There was one more thing. Our ISP changed something ^^THERE^^ right about the time. Of course I'm not sure. But this Firefox. It appeared when loading some sites, CPU hits the ceiling. Even looking at those pages (active tabs) made it go up significantly.

On May 2: *Lately I've been usually using Opera 36 for this site and Facebook, plus additional tasks if needed. Like most daily issues, but not games nor video. Right.
So it glitched time to time. Like when I hit these forums' speeddial right after the browser started, or hit my Facebook page the same way - like statistically it usually didn't load but kept "connecting". ... this morning my Opera 36 started to behave similarly, but then *it seemed to like break of sorts: I tried to stop and/or close the stuck tabs to try anew, or change something before the retry - like that Turbo... But it KINDA froze, the tabs' titles changed to blank "Loading...", the tabs didn't close... I tried to restart, but that didn't seem to help any much.

On May 3: Opera seems to be working today... I don't know... Perhaps it might be certain lags/delays in something starting etc... Anyway, I started the browser, then I went away for several minutes, then I hit whatever it was.

Again on May 3: Bird, to clarify, it is not a freeze-freeze, it is a non-connection-"freeze".

A possible pattern that seems to run thru this is that both FF and Opera 36 are having problems connecting to websites with your system. They may also (or alternatively) be having problems loading, initializing, and maintaining themselves on your system. With both browsers behaving this way, it would seem to point at either connection issues (your system or your ISP) or local file corruption (perhaps with the OS connectivity modules or your file system in general).

Ordinarily, I would also consider a possible intermittent RAM chip, but with only 2 programs showing issues, that is less likely. Similarly, one might suspect a corrupted browser profile folder, but with two browsers showing similar issues that would be much less likely - unless the file system (eg: hard drive) is failing.

In any case, one easy thing to try would be to test Opera 36 with a new profile folder (rename the current one to something else so you can get back to it later), and see if the Opera problems continue.

A Former User

Bird, about April 22 it might have been about the plug-in issues, at least considering the first piece...

They may also (or alternatively) be having problems loading, initializing, and maintaining themselves on your system. With both browsers behaving this way, it would seem to point at either connection issues (your system or your ISP) or local file corruption (perhaps with the OS connectivity modules or your file system in general).

After the said "macabration", it connects right away and stays stable. Some figures in speedtesting changed, but it's likely irrelevant.
What are the OS connectivity modules?

Actually, with this ESR52 Firefox is doing all right.
Well, there was some plug-in update quirk the other day, but it's another question: on the update page, it said I'd get some .171 or something version, I veered nowhere, all straight away fine, but the resulting file said version .140.
Good, it's working! Update's great! But still - what the ?

blackbird71

blackbird71

...
What are the OS connectivity modules?

It's just a term for the various code files and services found in the OS that an application uses to access the Internet. It's the plumbing between the app itself and the system's network interface card, all of whose handshaking must work perfectly for network communications to occur. Which modules/services that are used depends mainly on the app design and the Windows version... things like Winsock, etc. On occasion, I've seen such code modules or their registry settings become corrupted (either by a faulty apps software install, hard drive error/failure, or failed OS update). The result can be a sudden or erratic loss of connectivity. Another thing along the same line is erratic operation of the Network card (or chip) itself, but that usually will show up as connection issues involving anything on the system that has to talk or update from out on the network, of which browsers are usually just a few.

A Former User

@blackbird71 said in Questions and Confusions:

@joshl said in Questions and Confusions:

... No, I have not tried other browsers yet. And I'm not sure if I will: Chrome is buggy, outdated and dangerous, even perhaps infested; my Opera 36 gets me BSoD every exit now; the Good Old Opera 11 I won't even try; my Midori is, too, outdated, and even then when I used on OperaForums it had layout issues. So, perhaps Midori would be the only one I could try, but - considering it already had layout issues ...

You're up against a shrinking software availability selection, due to XP's increasing age/obsolesence. Many of the chromium-based and Firefox-derived browsers that are still updated will be deprecating their XP support by June 2018. The few remaining XP-specified candidates that offer some hope and hints of longer-term support and that might be worth installing and trying against this site are:

Advanced Chrome Custom-build (54.15.5320.0, based on Chrome, 3/13/17)
Slimjet 10 family (10.0.13.0, based on chromium 50, 2/8/17)
Otter - still in pre-release (0.9.92 release candidate 2, based on Qt, 11/1/17)
Lunascape (6.15.1.27563, based on 3 engines - but its Trident engine may be problematic, 5/27/17)

Even with these browsers, there are no guarantees regarding how long they will stick with XP-compatible updating, since the work and patching required to keep them secure and current will become ever more complex as chromium and Firefox engines further evolve without their own internal XP provisioning. One thing that will eventually cause problems for any browser on XP will be loss of browsing compatibility with secure SSL websites that are increasingly migrating to eliptical-curve cryptography - XP can't handle it in support of installed browsers.

Thank you for your heads-up, Blackbird.