Table of Contents
Looking For Trouble
Thoughts about “methods” for identifying problems with a Windows computer. This page is the start of a framework for trouble shooting.
Looking For Trouble
Thoughts about “methods” for identifying problems with a Windows computer. This page is the start of a framework for trouble shooting.
The computer will not boot or will not present the Logon screen
This case may require an alternate bootable device. A thumb drive or CD that contains one of the following.
If you can get into the windows recovery environment fix_windows_boot may be helpful
- Hirens, as referenced on the Websites and Tools page.
- Linux, Many flavors of linux offer a download that can be booted from a thumb drive.
- A thumb drive containing Ventoy and any of 1 and 2 above can be easy to construct.
- Windows Installation media.
One reason for an alternate boot media is too determine if most of the hardware is functional. If the computer will boot from an alternate media then it is probable that the processor, memory, video and USB components are OK. Successful boot from Hirens will allow you to use gsmartcontrol and chkdsk.
If the computer boots and you can get past logon.
- Windows Task Manager. Does the system get “quiet/calm”? Is any process consuming more than 5% of CPU, Disk or Network? Use Resource Monitor to “drill down” to process level details. Focus on C drive in the Performance Tab of the Task Manager. Average response time with a HD should be 30 to 50 milliseconds. Hard drives that look OK from the perspective of SMART statistics can still be very slow. Response times greater that 100 milliseconds are VERY suspicious.
- GsmartControl. Are all disks healthy? Does the boot disk indicate any relocation events, positioning errors, uncorrectable errors?
- Use SFC (System File Checker) as indicated here.
- Boot time. Are there unnecessary boot time activities? Use the “Startup” tab in Task Manager to enable or disable boot time initiation of programs.
- Windows Event Viewer. Are there “Critical” or “Error” events?
- Windows Scheduler. Look for “suspicious” items. Similar to boot startup cleanup, but way more complex. This step is probably not necessary unless Task Manager indicates a suspicious process and the process is not started at boot time.
- Malwarebytes. Run it. Disable boot time initiation.
- CCleaner Run it. Disable boot time initiation.
- Superantispyware Run it. Disable boot time initiation.
Discussion