More Errors and their Causes
This is the final installment of BSOD errors. Start by clicking on the blue screen image for a larger view.
Generally, at the very top of the screen there is a line with the label *** STOP: followed by a series of numerical codes, called parameters, and a text description of the crash. The codes are used to provide additional information about the crash and vary from error to error. Below that is usually a list of the services and drivers running at the time of the crash, and the memory address of the crash (which isn't too useful unless you're a programmer).
Some of the information may seem technical however, if you find yourself with a BSOD we will need to know what it says in order to assist in fixing the problem.
Here's a couple of the more common BSODs, their corresponding error information, and some possible resolutions.
This is generally one of the worst possible BSOD errors, usually reported during boot. The Registry, the system's repository of settings and system data, could not be loaded for some reason. Sometimes this is due to a simple communications problem with one of the hard disks (a faulty or unplugged cable), although it may also be due to data corruption. A corrupted Registry needs to be recovered through the use of the Emergency Recovery Disk, or via a System State backup. If you have no backup copy of the Registry, you'll need to reinstall Windows -- another reason to make Recovery Disks and System State backups
Another possible disk-corruption or drive-cabling problem, this happens when the checksum for a system file doesn't match the data in the file itself. If in fact the file in question is damaged (and you'll get a report as to which file threw the error), you can often replace it by simply booting to the Recovery Console and copying out a clean copy from the CD-ROM. Alternatively, you can boot the Emergency Recovery Disk to perform the repair. Bad RAM can also cause this kind of data corruption. If you get this error a lot with different files, there may be something fundamentally wrong with the system's hardware, since you're probably looking at a widespread data corruption condition
That's it for this topic. It is somewhat technical however, if and when you see a BSOD you will likely be a little less concerned and have a bit more of an idea as to what you can do to remedy the problem on your own.
Should you have any questions about any of our tips, your computer or the internet, do not hesitate in picking up the phone or writing... better to contact me and be sure.
Tom @ Tata Computers