Adrynalyne
12-09-07, 22:54
At some point, many of you will experience a stop error (BSOD) that seemingly has no fixable solution. Safe Mode doesn't work, Last Known Good Configuration doesn't work, and so on. Sometimes, there is no solution aside from reinstalling your OS, or replacing faulty hardware.
However, there are times when it can be resolved. If the BSOD consistently lists a specific filename at each boot attempt then (ruling out hardware failure) we have something we may be able to fix.
Each service (which is usually run by drivers, or visa versa) is listed in the registry, with different start states. Some load at boot, some load on demand, etc. Using the Recovery Console, we can modify such states.
The first step is to boot into the Recovery Console. This will require your Windows 2K/XP/2003 CD. Boot floppies can also be used if the CD is not available. In our example, we will use the fictional icrashyou.sys driver as our culprit.
First we boot to the Recovery Console. To do so, we put in our OS CD, and reboot the machine. Assuming the boot order in the BIOS has been setup correctly, we then Press a key on the keyboard when prompted. Then when setup is done loading, we press 'R' for Recovery Console. Upon logging in with your Administrator password (or none if one isnt set), then we are presented with the C:\Windows prompt.
First Step (optional)
At this prompt, we type:
Listsvc
Press Enter.
This will list each and every service and driver that can be disabled from here. We then locate the filename in question in the list to verify it can be disabled.
For example, the BSOD is caused by icrashyou.sys file. Then, under the list of services, we would attempt to locate icrashyou.
Second Step
At the C:\Windows prompt, type:
Disable icrashyou
Press Enter.
If you receive no errors, it worked. If you do receive an error, check your spelling, and verify the service/driver was listed under listsvc. We then type 'Exit' to reboot.
Attempt to boot your OS again. You might be pleasantly surprised to have access to Windows again.
However, there are times when it can be resolved. If the BSOD consistently lists a specific filename at each boot attempt then (ruling out hardware failure) we have something we may be able to fix.
Each service (which is usually run by drivers, or visa versa) is listed in the registry, with different start states. Some load at boot, some load on demand, etc. Using the Recovery Console, we can modify such states.
The first step is to boot into the Recovery Console. This will require your Windows 2K/XP/2003 CD. Boot floppies can also be used if the CD is not available. In our example, we will use the fictional icrashyou.sys driver as our culprit.
First we boot to the Recovery Console. To do so, we put in our OS CD, and reboot the machine. Assuming the boot order in the BIOS has been setup correctly, we then Press a key on the keyboard when prompted. Then when setup is done loading, we press 'R' for Recovery Console. Upon logging in with your Administrator password (or none if one isnt set), then we are presented with the C:\Windows prompt.
First Step (optional)
At this prompt, we type:
Listsvc
Press Enter.
This will list each and every service and driver that can be disabled from here. We then locate the filename in question in the list to verify it can be disabled.
For example, the BSOD is caused by icrashyou.sys file. Then, under the list of services, we would attempt to locate icrashyou.
Second Step
At the C:\Windows prompt, type:
Disable icrashyou
Press Enter.
If you receive no errors, it worked. If you do receive an error, check your spelling, and verify the service/driver was listed under listsvc. We then type 'Exit' to reboot.
Attempt to boot your OS again. You might be pleasantly surprised to have access to Windows again.