Computer Troubleshooting

The troubleshooting and repair of computers have become a strong suit in recent years, especially since developing computer assembly knowledge through courses such as Computer Assembly and Config, Intro OS and Networking Tech, Network Setup and Config, and Help Desk Support.

The below examples showcase my understanding and abilities surrounding computer troubleshooting and research.

As a new IT consultant for a local church, I was introduced to their computer system but was informed to make repairs when necessary, otherwise focusing on keeping costs down. I've had a fair amount of phone calls regarding issues with their outdated computer system.

Outdated systems are more prone to having errors, issues, and failures when compared to their newer counterparts. When these errors arise, proper troubleshooting is the difference between a proper fix or throwing parts at it. 

The below examples showcase my troubleshooting abilities at work. Unfortunately, I did not think to take photos as I went, so this is primarily text-based recollection. 

Windows Sign-in Failure - Corrupted User Profile

-------

After receiving a text message with the below photo, I was informed that the computer started up normally and the secretary was able to sign in. However, when they attempted to open Microsoft Word to get started on weekly duties, they were met with the ominous pictured message. 

I guided the secretary through rebooting into safe mode, as I remembered that the computer had finished a new Windows update the week prior. They logged in and attempted to open Word, again being met with the message. I informed them that I knew what the problem was and would be there after hours to resolve it, suggesting they work on something else in the meantime. 

I researched the issue on Microsoft's Support site, finding the symptoms and a suggested fix - creating a new administrator account and migrating the corrupted user profile's settings and files to the new account. 

Once I arrived, I duplicated the issue and ran through the troubleshooting once more, just to confirm that I was still receiving the message.

Then I created the new account, giving it administrative privileges and beginning the process of copying the corrupted user profile's files to the new account's files. 

Next, with the secretary on a video call, I ensured that all of their installed programs still worked.

Lastly, I removed the corrupted user profile and its data so that the secretary would not accidentally sign into the corrupted profile. 

After completion, I took note of the likely causes - hard drive sector failure seemed likely, considering it was a 10-year-old system. I ran an HDD checker and received poor results, which supported my hypothesis. With this information included, I left a note for the secretary to suggest a new secretarial computer be brought up at the next board meeting. 

With my personal computer, roughly a month after it was completed, I completed my routine drive image prior to a Windows update. I approved the update and stepped away to cook dinner. When I returned, my computer was stuck on the dreaded blue screen. The error message told me that it didn't know what happened. 

I let diagnostic finish and rebooted it, again being met with a blue screen. This time, I rebooted and attempted to boot into safe mode. Again, a blue screen. I rebooted and entered my UEFI/BIOS menu in search of the boot order. During the update, the boot order was changed. After the update, it wasn't reverted back to the original values, leading to the blue screen issues. I corrected the boot order and was able to have a successful boot.