BSOD ISSUES AND SOLUTIONS

 

BSOD ISSUES AND SOLUTIONS

        - It all needs the Win XP OS CD and you have to be in Recovery Console. Listed are commands you have to type in after entering Recovery Console. Don't forget to hit ENTER every after command.

1) NTLDR is missing or corrupt

        Solution:

                1. ~Recovery Console

                2. cd \

                3. map (to know the drive name where XP CD is)

                4. copy d:\i386\ntldr (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

2. Continuous Restart

        Solution:

                1. ~Recovery Console

                2. cd \

                3. map (to know the drive name where XP CD is)

                4. copy d:\i386\ntdetect.com (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

3. Stop: C0000135 - kernel32.dll missing or corrupt

        Solution:

                1. ~Recovery Console

                2. cd system32

                3. map

                4. expand d:\i386\kernel32.dl_ (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

4. windows\system32\config missing or corrupt

        Solution:

                1. ~Recovery Console

                2. cd \

                3. dir (Look for System Volume Information. If it's there, proceed to Step 5, if not, continue with Step 4)

                4. attrib -h -s "system volume information" (this will unhide the System Volume Information.)

                5. cd "system volume information"

                6. cd _resto~1

                7. dir (Look for the RP numbers and what date it corresponds to for restoring it back to a working date, i.e.RP158 - 08/25/2006)

                8. cd RP# (i.e. RP158)

                9. cd snapshot

                10. dir (Look for the presence of entries like _registry_machine_software c:\windows\system32\config\system and others)

                11. copy _registry_machine_system c:\windows\system32\config\system

                12. exit

               

                ***Note: If you want to fully restore not only the system file, you can also do the SAM, SECURITY and SOFTWARE by typing:

                copy _registry_machine_sam c:\windows\system32\config\sam

                copy _registry_machine_security c:\windows\system32\config\security

                copy _registry_machine_software c:\windows\system32\config\software - (this can be useful if error has been caused by a software installed/changed)

5. hal.dll missing or corrupt

        Solution 1 (try first):

                1. ~Recovery Console

                2. bootcfg /rebuild

                3. Press y

                4. ms home /fastdetect (name the OS)

                5. exit

        Solution 2 (if first one doesn't work):

                1. ~Recovery Console

                2. cd system32 (to go to c:\windows\system32)

                3. map

                4. expand d:\i386\hal.dl_ (D: can change depending on the CD drive letter you saw when you mapped.)

                5. exit

6. boot.ini / could not read from the selected boot disk / check boot path

        Solution is the same with the hal.dll error's Solution 1.

7. black screen after the Windows XP splash screen

        Solution:

                1. ~Recovery Console

                2. cd \

                3. dir (Look for System Volume Information. If it's there, proceed to Step 5, if not, continue with Step 4)

                4. attrib -h -s "system volume information" (this will unhide the System Volume Information.)

                5. cd "system volume information"

                6. cd _resto~1

                7. dir (Look for the RP numbers and what date it corresponds to for restoring it back to a working date, i.e.RP158 - 08/25/2006)

                8. cd RP# (i.e. RP158)

                9. cd snapshot

                10. dir (Look for the presence of entries like _registry_machine_software c:\windows\system32\config\software and others)

                11. copy _registry_machine_software c:\windows\system32\config\software

                12. exit

 

How to resolve Blue Screen Of Death 0xEA

0xED & 0x7B

0xEA

STOP 0x000000EA (THREAD_STUCK_IN_DEVICE_DRIVER)

This Blue Screen error indicates that a device driver-almost always a video card driver-is stuck waiting for something (usually a hardware operation) to happen. Most of you have probably seen nv4_disp.sys associated with this Blue Screen.

Things to check:

1   Ensure the video drivers are updated to the latest Dell version.

2   The system BIOS is fully up-to-date.

3   If both the video driver and the system BIOS are fully up-to-date, check with the manufacturer for recent driver updates.

4   As a last resort, try exchanging the video card.

Reinstalling Windows is not likely to prevent this error from reoccurring.

How to resolve Blue Screen Of Death 0xED & 0x7B

Stop 0x000000ED (UNMOUNTABLE_BOOT_VOLUME)

Stop 0x0000007B (INACCESSIBLE_BOOT_DEVICE)

These two errors have similar causes and the same troubleshooting steps apply to both of them. These stop codes always occur during the startup process. When you encounter one of these stop codes, the following has happened:

1   The system has completed the Power-On Self-Test (POST).

2   The system has loaded NTLDR and transferred control of the startup process to NTOSKRNL (the kernel).

3   NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the file system at the location it believes it is stored.

When troubleshooting this error, your task is to find out why the Windows kernel is confused and fix the cause of the confusion.

Things to check:

The SATA controller configuration in the system BIOS If the SATA controller gets toggled from ATA to AHCI mode (or vice versa), then Windows will not be able to talk to the SATA controller because the different modes require different drivers. Try toggling the SATA controller mode in the BIOS.

RAID settings You may receive this error if you've been experimenting with the RAID controller settings. Try changing the RAID settings back to Autodetect (usually accurate).

Improperly or poorly seated cabling Try reseating the data cables that connect the drive and its controller at both ends.

Hard drive failure Run the built-in diagnostics on the hard drive. Remember: Code 7 signifies correctable data corruption, not disk failure.

File system corruption Launch the recovery console from the Windows installation disc and run chkdsk /f /r.

Improperly configured BOOT.INI (Windows XP). If you have inadvertently erased or tinkered with the boot.ini file, you may receive stop code 0x7B during the startup process. Launch the recovery console from the Windows installation disc and run BOOTCFG /REBUILD