This is Part Three of this series.

In Part 1 we went to the Windows Advanced Options Menu…

… And we tried using the “Last Known Good Configuration (your most recent settings that worked)” option. This sometimes, (Usually in my experience.) does the trick, but not always.

In Part 2 we looked at something else we could do if that doesn’t solve the issue: If it doesn’t solve the problem it usually means that one of the drivers is bad/corrupt/dodgy; so we looked at removing that driver by booting into Safe Mode.

What we didn’t look at was what to do if your XP computer doesn’t crash, but rather just boots and goes tits up; to put not too fine a point on it.

If you get a scrambled picture then ‘chances are that your graphics driver is playing up and needs removing and reinstalling, and/or your graphics card is either crap or has developed a fault. Some motherboards just don’t like some graphics cards: I have an Asus mobo that just hates a certain Asus nVidia graphics card. There’s nothing wrong with the graphics card; it works fine in other computers, but it just won’t work properly with this one board.

OK so we’ve covered a lot so far in parts 1 & 2; but there may be a couple more things that’s preventing XP from starting: –

These are operating system/data corruption and/or file system corruption.

Operating system corruption can result from too much buggering about and trying to be clever; – The usual scenario in my case. – or from a phenomenon (specific to Windows – ?) known as “software rot”. For whatever reason, Windows moves things around, writes, copies, deletes, all in normal operation. Eventually it makes a tiny error; which can go unnoticed. – But when a number of tiny errors build up over months of operation, then a big error happens, and things start to go downhill from there: A cascade of errors causing errors, until eventually the system becomes inoperable.

The above can take years and stay unnoticed until the machine simply stops working, or it can happen suddenly. File system corruption is much the same: The NTFS, or in some cases, the FAT32, file system, is the storage medium’s file storage structure on the disc. In short the computer stores tiny bits of data made up of a few bytes in many tiny storage areas on the disk. These are marked out before the data is added to the disk: It’s accomplished by process called “formatting”; which is the first thing that needs to be done if a new hard-drive is installed, or if the old one needs to be wiped. Also in the file system are indexes of these little areas of data; which can also be prone to error.

Since we’re on the subject of the file system; the way to correct a file system error is by using the chkdsk function built into Windows. In Windows XP this can be activated from the command prompt as well as the GUI. Open a command prompt (Start>Run and type “cmd”.) and type “chkdsk C: /f”. (Assuming that C: is the disc that you want to check for file system errors.) This instructs Windows to run chkdsk on drive C:, and the parameter f instructs the operating system to check specifically for file system errors and repair them.

Similarly; chkdsk can also check the disc for file system and data errors, and repair them. To instruct Windows to do this, open a command prompt, (Start>Run and type “cmd”.) and type “chkdsk C: /r” (Assuming that C: is the disc that you want to check for errors.) Using the parameter r instructs the operating system to repair any errors it finds on the disc: These include file system errors, corrupt data, and bad sectors. As you may imagine; this can be a long process on some occasions.

While chkdsk attends to disc errors, there is another process that checks further for data errors in the essential operating system files. This process is called the system file checker. To run it; first insert your (original) XP CD into the optical drive, then open a command prompt, (Start>Run and type “cmd”.) and type “sfc /scannow”. This instructs the operating system to run the system file checker, check the crucial system files that Windows needs in order to be able to operate, check their parity, and, if there are any errors; delete the file and replace it from the files on CD. – Short of performing a repair reinstallation, this is the best way to clear operating system corruption.

So that’s covered pretty much everything. If you’ve done everything suggested and it still won’t boot, then you have a choice of a repair reinstall or a disk-format-and-reinstall.

Before you do that, though, try pulling out all the USB plugs and other peripherals and seeing if the machine boots with no peripherals connected. If it does then you have a faulty peripheral device. Plug things back in one by one and boot after every device you plug in. When your computer fails to boot you’ll know that the last peripheral device you plugged in is faulty.

“ – After I’ve spent hours doing all that, from Part 1, 2 and 3; and now you tell me it’s a faulty peripheral device!”

- Don’t worry: You’ve just given your machine a full software service, and it’ll work a lot better as a result.