Quote:
The problem is that there are a lot of "hit and run" users of this forum. They post their issue / problem and then wait for help and then once received they don't come back.
Rather rude in my opinion if you ask me. But that's the way society is today, I WANT IT NOW!
|
I don't consider that rude. When I take my car to a shop, I don't stick around and socialize until the next time it breaks down. In fact, I would rather I never have to visit that shop again. It is not fair to expect everyone who seeks help to become a "regular".
And if these posters "
wait for help" I see no problem with that either. The ones that are rude are those that post a question (possibly in multiple forums), wait 30 minutes then "bump" the thread complaining that no one has helped them yet. Now that's rude! But of course, if you don't understand "forum etiquette" you may not know it is rude.
***
The problem with creating a "universal" sticky for "Windows Freezes" problems is there are simply too many potential causes - not to mention many "levels" of freezing that may or may not point to a single cause. Freezing can be caused by heat, bad power, malware, corrupt/conflicting anti-malware programs, bad driver, failing RAM, failing CPU, failing motherboard, corrupt data/HD, failing graphics, and who knows what else.
And the symptoms of freezing are just as varied. Sometimes you get a BSOD, sometimes you don't. Some times Ctrl-Alt Del works, some times the keyboard is locked too. Some times the mouse pointer can be moved, some times it is locked too. Some times you can access the machine remotely, some times not. Some times you can hit the reset or power button, some times you have to pull the plug.
Most problems are simple to fix. It is figuring out exactly what is broken (the actual troubleshooting part) that is the most difficult and time consuming. This often is because troubleshooting is typically accomplished by eliminating all possible causes (seeing what is still working) and seeing what's left.
There have been many attempts at this before, some valiant and exhaustive with all kinds of flowcharts and what ifs. But regardless the extent, they are all "generalizations" and because of that, none of those attempts have been very successful.
A quick Google search of
troubleshoot Windows freeze problems shows many solutions, but none come close to being a fix all.
It is a great idea, but I just don't think the results, regardless the sincerity of the attempt, can ever be very practical - not for some a general, nondescript problem such as freezing.
That would be as difficult as doing one for "crashing" - whatever that is!