Repairing A Home Office PC Which Cannot Start Up Correctly By Using Reimage 0
Anyone working from a home office realizes if their computer breaks down then it is up to them to attempt a repair. This article highlights a repair process when fatal blue screen errors occur, culminating with a Reimage review to exhibit how this software automates computer repair and maintenance.
My home office computer recently crashed with a blue screen error stating an exception code 0xc0000218. Online research showed this to mean the registry hive (a group of configuration keys for a specific user) had been corrupted.
The following logical sequence of repairs should be attempted to repair the registry.
- Try logging in under another Windows account. The theory being that their accounts registry hive may be unaffected
- Boot up in safe-mode and roll back the registry to an earlier back up version (if available).
- Start the computer from the Windows boot disks and run the hardware/system scans. The theory is that something like a disk fault could potentially corrupt the registry.
In my situation, the blue screen code occurred as Windows booted so I ultimately had to resort to using Reimage PC maintenance software.
The product can boot a failing Windows PC from a boot disk (the boot application can be downloaded from their website and burnt to CD for this purpose).
Once Windows is running, Reimage is started from within Internet Explorer as the application is an online service. This means that the service scans your registry and file system for faults using their online knowledge base of healthy PC configurations. The application reports its findings within about 30 minutes. In my case the registry had dozens of faults, most likely due to previously removing some older applications.
As a home office worker it is an imperative to be capable of running computer repair and maintenance for yourself. The above sequence of repairs should help anyone experiencing a blue screen error due to registry problems.
subscribe to comments RSS
There are no comments for this post