I said theres no tools available to troubleshoot. the whole system of troubleshooting for computers is based on trying random things until something works. most of the time troubleshooting fails. and a full system reinstall solves the problem.
unlike cars that a diagnostic can be run on a car to show where the problem is. theres no tools available for typical consumer that can be ran or active in the background to show what exactly is causing a freeze or slowdown.
Sorry mate, but there's PLENTY of tools available for troubleshooting.
Just like cars, you have to use the right tool for the right job. In fact, here's a good one to start with (and guess what? It's free and most of the tools are even open source):
Ultimate Boot CD - Overview
TONS of tools available for troubleshooting / diagnostics. If you pay attention to any error codes you can, 99% of the time you can research that error code and figure out what it's in reference to. BSOD's are the easiest to troubleshoot because they tell you exactly what the problem is 90% of the time, especially if you have the minidump file available to dig deeper with, using WinDbg and the Debugging Symbols.
As for "most of the time troubleshooting fails" - what's wrong with failing? Even if the step you took didn't actually SOLVE the issue, it rules out a specific piece of hardware or software (or even a process), and confirms that that part is NOT the issue. That, and add in the fact that troubleshooting gives you experience for the future so that you know what to look for. You think we all just know exactly what to look for right away? No, that's why we troubleshoot. Same goes with mechanics - they troubleshoot by looking at different areas of the car, asking questions ("what sound does it make?" "what were you doing when X started happening?" "how long has it been happening?", etc.), and performing diagnostics / testing on certain components and areas of the car.
And sorry, but a system reinstall IMO is not a solution unless absolutely necessary. At most it's a band-aid (especially if there's a hardware problem), and add on the fact that you gain NO troubleshooting knowledge. That's like buying a new car when you have a flat tire.
its pretty much hit and miss. just look at this forum. most of the time theres no solution.
About the only time there's no solution on here is when the OP abandons the thread - and half the time that's because they posted the same question on multiple sites and got an answer on another site before we were able to help.
heres google search for g62 laptop.
https://www.google.com/search?q=g62+freezing&btnG=Google+Search&gws_rd=ssl
its been goin on for years and still no solid answer why they freeze so often on that model. HP is just waiting it out until people say **** it and upgrade to newer model... they got our money and people are to lame to go and ask for their money back for ****ty product.
HP makes ****ty consumer products - that's why they freeze so much. Low quality parts with tons of bloatware make for a system with lots of issues.
my laptop started freezing after i ran windows update. it haven't been updated for a while and had 79 important updates. ( please don't say oh theres your problem) because other computers i installed over 100 updates at once with no issues 99% of the time.
Why do you wait so long to do updates? That DEFINITELY could be part of your issue. You shouldn't wait until you have hundreds of update queued up... People that do **** like that are why I'm glad Win10 is FORCING updates on Home users - so they don't queue up tons of important updates.
g62 will boot up and if i don't start moving a mouse right away it will freeze at startup.
i uninstalled mouse drivers from touchpad synaptics and used a usb mouse.
it worked while iobit was scanning the system as soon as it was done it froze again.
if i stop moving the mouse for about a minute it will freeze
before updates it would sit for few hours with no programs running or with programs and freeze
theres no memory issues or hard drive errors
if i could run any diagnostic i would but it freezes most of the time before diagnostic has a chance to finish.
it freezes in safe mode right away. no chance to do anything there either
Run diagnostics software that's independent of the Windows OS and tests the hardware directly, i.e. Linux LiveCD's and tools on UBCD to test components. If it fails in those environments, then you know there's a hardware issue causing your issues. Otherwise it's software or related. Guess what? I just did gave some simple instructions to troubleshoot your issue beyond just testing memory, HDD, or reinstalling drivers.
