We're all familiar with Error Messages under windows. Ever since Windows 3.11 we've grown to accept them as part and parcel of daily PC use. However, we generally also
find it's a mystery what they actually mean, some of them being downright unhelpful and obscure. Windows XP, the latest from the Microsoft Stables, has brought even more weird and wonderful error messages.

To help us understand what they mean, it helps to actually be able to view them. Windows XP has introduced a feature that re-boots a PC should a BSOD (Blue screen of Death) be encountered. Not helpful if you want to know what's going on. To change this, right click "My Computer", Properties, Advanced and look to the startup and recovery section. Then click settings and under "System Failure" untick the option to automatically restart. If you do encounter a BSOD then your first port of call should always be http://support.microsoft.com . While somewhat
difficult to navigate at first, there is a wealth of solutions and explanations that cover 99% of encountered problems.
Now that we're all ready, we can cover the basics of error messages.

Blue Screens Of Death (BSOD): One of the most familiar of error messages, one that's been with us since Windows 95. In most cases this is a driver error, however,
in Windows 9x it can also be an IRQ conflict or problems with your startup files.

Fatal Exception Error: Basically this error occurs when the CPU cannot process an instruction and as a result hangs. This is usually due to poorly compiled code or unworkable maths within a program. It can also be an indication of faulty memory as data is written to an unworkable area and then lost. Fortunately a Fatal Exception Error also usually includes information on the source of the error, which will allow you to search the Microsoft Knowledge base.

Windows Protection Errors: These are more difficult to classify, and can be caused my many different factors. Invariably they occur when booting and carry a "While initializing device xxx" tag. This can help, as long as you know what device xxx is. Most commonly this is a result of a driver being incorrectly loaded.

VxD Errors: VxD's are virtual device drivers and errors such as these can regularly appear under Windows 9x operating systems. If you see a VxD Error, make a note of it's name and then search for the file on your HDD. The directory it's stored in may yield some hint as to it's function. If not, right click the file and select properties as this may also hold information. Also try re-booting the system into safe mode and see if the problem disappears, if it does, try uninstalling the program associated with the VxD or check the System.ini file for reference to that file and remove it.

Invalid Page Faults: These are memory errors which occur when two or more programs attempt to use the same area of memory at the same time. These are rather tricky to fix but often a patch for the program in question can help. These errors can also occur when having very little free memory (too many open programs at once) and when running with low free space on your HDD.
Microsoft Knowledge Base article Q286180 has lots of information on this topic.

Windows XP STOP Errors: These are confined to versions of Windows XP and are related to Driver problems. Windows XP uses drivers in a different way to previous versions of Windows and as a result it is always preferable to use "Signed Drivers". Lots of devices still do not use signed drivers so in many cases it might be necessary to risk it. Once again, there is more on STOP Errors on the Microsoft site.