How to get prepared for the inevitable in Windows XP – Part I

Well, we’ve all heard about it – it seems like it’s been happening to all the people around us. However, for some strange reason we have a deeply-rooted belief that this can only affect anyone else but us… Especially after having switched to Windows XP, an operating system that is far more stable and predictable than its predecessors (at least the ones that ran in a home environment), we do not anticipate that there can be a day of doom around any corner; a day when we will not be able to boot successfully in XP or we will be greeted by repulsive blue screens or ciphered error messages.

And yet this day inevitably arrives (sometimes repeatedly) but, since we did not expect it, we are totally unprepared. And so we find ourselves running like a dog behind its tail, trying to resolve issues the understanding of which we usually do not fully comprehend. To be utterly protected from XP glitches or challenges is a delusion – and nobody can guarantee you this. However, to avoid facing such an occurrence unprepared is something feasible – and highly advisable.

Please, do not take me wrong - I am not a doomsayer, and I do not want to cause you unnecessary and unjustified concerns. Windows XP is a stable and user-friendly operating system overall, but this provides you no assurance of absolutely no adversities. Typically, Windows XP will in fact be "not guilty" in most Stop Error occurences; the actual culprit being a failing component, an inferior psu, a corrupt driver or an incompatible third-party program... And even if the culpable element is part of Windows (like e.g. the Registry), its corruption could very well be the ultimate result of a user's actions (or inactions).

However, due to the relatively ciphered way that the error messages are presented by Windows XP to the user (e.g. the message IRQL_NOT_LESS_OR_EQUAL means that "a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt Request Level that was too high", and PAGE_FAULT_IN_NONPAGED_AREA means "the requested data were not in memory; an invalid system memory address was referenced"), the user has to be fully prepared to undertake and execute some amount (usually minimal) of troubleshooting.

Always keep in your mind this: any operating PC will eventually experience component deterioration to some degree, so it is inevitable that stop errors and blue screens will appear to signal this - and they will disappear when the issue gets resolved. Don't forget: luck favors the prepared! So, here’s a checklist of necessary steps to be taken by the learned and prudent:


1. Maintain a folder for your computer.

a. Preparation for the inevitable calls for your being elementarily organized. So, get a folder where all the necessary documentation and data regarding your computer will be contained.

b. Keep this folder sufficiently updated, at least as far as your installed hardware, peripherals and drivers are concerned.

c. To the extent humanly possible, avoid losing this folder – and replace it if it gets lost for any reason.

d. Have this folder always handy or, if you opt to store it somewhere, remember where this location is.


2. Collect all the information regarding your PC

a. Click on the Start menu, select Run, type msinfo32 and press OK. The System Information utility is launched.


(If you cannot locate the Run command on the Start menu, press simultaneously the Windows Key and the letter R key.)

b. On the File menu, click Save and select a name and a location for the file to be saved. The saved file has an .NFO extension, it is not a small file (it is ~5.5MB) and can be opened by any PC running XP or Server 2003. If you want to maintain compatibility with legacy operating systems (pre-XP), then select in the “Save as type” box the Version 5.0/6.0 NFO. It is suggested that you keep this file in a removable storage media (CD-ROM, USB drive, etc).

c. Alternatively (or if you are either unsure about compatibility or you wish to be able to copy and use parts of the report), you can save the file in text format. To do so, either on the File menu click Export, or at the Run command use the /report {Path} switch (you have to use a .txt extension in Path). Although not advisable (due to its length – it is 360 pages when you have MS Office installed), you can also Print the report from the File menu.

d. Having this report in hand, you have a very accurate snapshot of your PC configuration. You have access to your version of Windows, your CPU type, the amount of memory and system resources, your BIOS version, your boot device (if multiple devices are present on the computer) and the path to the Page file. If your PC is proprietary (e.g. Dell, HP, IBM), you will also be able to see its model and type. Moreover, you can see hardware-specific settings [such as assigned or used interrupt requests (IRQs), input/output (I/O) addresses, and memory addresses], all your installed components (including the status of your device drivers, network components and multimedia software) and all the software loaded in your computer's memory (including drivers, running processes, modules, startup programs and various .ini files). Additionally, if you have Internet Explorer and/or MS Office installed, you are getting analytical information for them, as well.

e. A commonly overlooked need for always having a current msinfo32 report safely kept is the fact that, if your computer denies booting normally, then when you run it in Safe Mode you will not be able to access any hardware information at all. When System Information is run in Safe mode, it is limited to displaying information only about system components and the software environment.

f. Do not forget that keeping an eye on msinfo32 can also help you monitor the history of your Hardware Resources, Components and Software Environment, because you are able to view all changes to your computer since a certain date and time. And, the prepared have also to know where the System Information keeps all these data: They are stored in the Extensible Markup Language (XML) data files located in Windows\PCHealth\HelpCtr\Datacoll. So, even if XP will not boot at all, these data can be retrieved and reviewed for troubleshooting purposes.

g. As a matter of fact, msinfo32 in general is far more than a powerful reporting utility. It gives you troubleshooting functionality by providing direct access to tools and control panels like Backup, Network Connections, the Hardware Wizard, Disk Cleanup, System Restore, Network Diagnostics, the File Signature Verification Tool, the DirectX Diagnostics Tool and Dr. Watson. However, the usage of aforementioned tools is beyond the scope of this article, and is dealt with in separate TSF articles that present the phases beyond getting prepared; and that is backing up data and resolving generic and specific XP issues.

h. Notwithstanding the fact that msinfo32 is so powerful, it still lacks one extremely important element – and that is it won’t report to you the motherboard of your PC. Actually, since it does report the BIOS version, it is possible in some cases to link this piece of information to the motherboard – however this is hard to do and not at all predictable if it will be done successfully. For example in the picture above, the reported “Award Software International, Inc. F5” means “Intel i875P AGPSet BIOS for 8KNXP AWARD BIOS” and “GBT” in the System Manufacturer means “Gigabyte”; which reveals that we are dealing with a Gigabyte 8KNXP motherboard. Yet, the truth remains that this is definitely not the way to go; so you will need to move on the next step in order to deal with this matter.

i. References
Description of Windows XP System Information (Msinfo32.exe) Tool
How to Use System Information (MSINFO32) Switches
You Cannot Open Certain System Information (.nfo) Files (applies to pre-SP2 XP)