Embedded Files
Post date: Apr 1, 2018 5:37:02 AM
After asking questions or listening to symptoms, my first go-to troubleshooting check is to see what programs and processes that are running and what all that is up to. In "no tools" troubleshooting I basically begin with task manager in windows or call up the current running programs in Linux. Since its more prone to issues, the windows environment has really enhanced diagnostic tools. Task manager will show most of the current status of its running programs but it does not give a complete picture of the running process. That is why I use Process Explorer by Mark Russinovich. This tool will bring you all the way down to threads. It also shows you graphically how much resources are being used. The closest thing to the windows version is the Linux Process Explorer. which does alot but its still not a mature program. So now that I can see each process and get all its vital statistics and for windows even the tcp ip connection information. So now we can see into the problem and note anything that looks like a resource hog or killer or even a suspended process. From here its really up to what is wrong but once you see the actual issue finding the cure is relatively easy. When you use tried and tested techniques computing troubleshooting is like fixing anything in life. Simpler.
~ Robert "Tux" Tucker, 04-01-2018
Google Sites
Report abuse