More Errors and their Causes
Here we have a couple more BSOD errors.
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 happens if Windows can't read from its own pagefile. Hard drive errors -- bad cabling or a disk defect -- are the usual suspects for this one. Cables actually develop defects more often than hard drives do, so try changing out your cables. ("Rounded" hard drive cables are apparently far less error-prone than "ribbon"-style cables, and clutter the inside of your system less, too.)
As the name implies, this error comes up when Windows can't find the hard disk used to boot the system. This usually happens if someone has tampered with the drives or cabling, or if the device driver that handles I/O to the boot drives is not loading. If you've installed a newer version of your disk controller drivers, for instance, you might get this if they're not working correctly; boot to Safe Mode and roll the drivers back. Newly-added hardware might be conflicting with the controller or trying to usurp its functions
We'll give you a couple more next time but until then, should you have any questions about your computer, do not hesitate in picking up the phone or writing... better to contact me and be sure.
Tom @ Tata Computers