BIOS Startup Error Messages and Solutions
At the point when a framework has issues beginning, it may show blunder messages at startup. These messages may come from the framework BIOS (ROM BIOS or UEFI firmware) or may be produced by Windows. Commonplace mistake messages showed by the BIOS incorporate the accompanying:
- Invalid framework plate
- Boot disappointment
- Hard plate blunder
- NT boot loader missing
- Missing working framework
These and comparable messages demonstrate that the BIOS or UEFI firmware chip on the motherboard can't find startup documents for your working framework. Potential reasons can incorporate the accompanying:
- A nonbootable drive containing media is recorded first in the boot request (BIOS/UEFI).
- The PC's framework drive isn't appropriately distinguished (BIOS/UEFI).
- Information or force links from the inward hard plate to the motherboard are free or have fizzled (equipment).
- The drive has fizzled (equipment).
- These are recorded arranged by probability. As usual, start with the least complex chance: You've left a USB thumb drive connected to your PC.
- Disengaging USB Drives
On the off chance that your framework is arranged to utilize USB drives as the primary bootable gadget and you leave a nonbootable USB streak drive connected to your framework (either straightforwardly or into a USB center point associated with your framework), your framework won't boot. Arrangement? Unplug the drive and restart your framework.
In the event that your framework restarts accurately, you have several options:
Try not to leave USB streak drives connected to your framework when you shut down the PC. Change your BIOS or UEFI firmware settings to skip USB drives as bootable gadgets.
Checking and Changing Drive Boot Order
Would it be a good idea for you to change the boot request? It depends. An ever increasing number of demonstrative projects can be run from bootable USB streak drives, and you can likewise put in new
working frameworks from bootable USB streak drives. Be that as it may, you can likewise utilize your framework's DVD or BD (Blu-beam) drive for these assignments. Along these lin
We suggest changing the boot request on Windows 7 PCs
if You use USB streak drives to accelerate your framework utilizing the Windows ReadyBoost include. You regularly use USB streak drives to carry data between PCs.
You every now and again use USB streak drives for different reasons.
Windows 8.1 (in contrast to Windows 8) doesn't uphold the formation of a CD or DVD fix plate, in spite of the fact that you can utilize your Windows 8.1 dissemination media as a maintenance circle. With Windows 8.1, if your framework underpins booting from a USB drive, you ought to make a USB recuperation drive all things considered.
STOP (Blue Screen) Errors at Startup
In the event that you turn on your Windows PC and, rather than seeing the Windows login screen or work area, you see a screen like the one appeared in Figure 8.5, you have a STOP mistake, otherwise called a "Blue Screen" or BSOD ("blue screen of death) blunder. What was the deal?
Blue-screen mistakes can be brought about by numerous issues. At startup, they're normally brought about by issues with hard circle gadget drivers. On the off chance that a blue screen mistake shows up after you have booted to the Windows work area, it very well may be brought about by degenerate applications, degenerate gadget drivers, or memory issues.
At the point when you see a BSOD mistake, make certain to record the numbers recorded after the STOP message, for example, STOP: 0x0000001E, or 0x1E for short. On the off chance that the name of the mistake is shown, for example, KMODE_EXCEPTION_NOT_HANDLED, record it too. You would then be able to look into the blunder number and name on the Microsoft Support
Table 8.2 Common Windows STOP Errors and Solutions
|
STOP
Error Number |
STOP
Error Name |
Suggested
Solutions |
|
0xA |
IRQL_NOT_LESS_OR_EQUAL |
Check
device drivers or services used by backup or antivirus utilities. |
|
0xD1 |
DRIVER_IRQL_NOT_LESS_OR_EQUAL |
Check
device drivers or services used by backup or antivirus utilities. |
|
0x1E |
KMODE_EXCEPTION_NOT_HANDLED |
Illegal
or unknown instruction; check the driver referenced in the error message. |
|
0x24 |
NTFS_FILE
SYSTEM |
Test the
hard disk for errors. |
|
0x2E |
DATA_BUS
ERROR |
Test
memory modules; disable memory caching in system BIOS; check hardware
configuration. |
|
0x50 |
PAGE_FAULT_IN_NONPAGED
AREA |
Check
printer drivers. |
|
0x7B |
INACCESSIBLE_BOOT_DEVICE |
Incorrect
or missing hard disk device driver; see “Fixing 0x7B Errors,” this chapter,
for details. |
|
0x7F |
UNEXPECTED_KERNEL_MODE_TRAP |
Test
hardware and RAM; check SCSI configuration if in use; make sure CPU is not
overclocked. |
|
0x9F |
DRIVER_POWER_STATE_FAILURE |
Check
power management and CD-writing software; disable power management
temporarily; reinstall or upgrade CD-writing software. |
|
0xC21A |
STATUS_SYSTEM_PROCESS_TERMINATED |
Reinstall
third-party programs; use System File Checker with the Scannow option
(SFC/Scannow) to check system files. |
Shockingly, Windows is commonly arranged to restart the framework promptly when a STOP blunder is shown, so you can't understand it. To design Windows with the goal that a STOP blunder stays onscreen so you can figure out what it is and search for arrangements, see "Setting up a Windows-Based Computer or Tablet for Easier Troubleshooting," Chapter 1, p.37.
Fixing 0x7B Errors at Startup
Fixing 0x7B Errors at Startup
On the off chance that you are building a PC, have quite recently moved up to another hard circle, or have recently supplanted the motherboard battery that keeps up framework settings, it's conceivable that your PC has "failed to remember" the right hard plate setup settings.
Practically all hard plates are designed utilizing Auto as the hard circle type. Hence, if the arrangement data is lost, the default (ordinary) setting is Auto and the drive will be appropriately recognized.
Notwithstanding, the setting for the SATA interface utilized by your hard plate can be an issue. There are a few potential settings for the SATA interface (IDE, AHCI, and RAID), and if your framework is arranged utilizing one setting, however an alternate setting is utilized in the framework BIOS or UEFI firmware, your PC won't begin, showing a 0x7B STOP blunder (allude to Figure 8.5).
On the off chance that you know the right setting, follow these means:
1. Shut down the PC and restart it.
2. Start the BIOS or UEFI firmware arrangement program.
3. Change the SATA setting to the right worth.
4. Save settings and restart the PC.
5. Select Start Windows Normally whenever incited.
Changing to AHCI Mode in Windows 7 and Windows 8.x
In the event that your SATA drives are as of now set to run in IDE mode, yet you are wanting to introduce a SSD, remember that a SSD can't give you quicker execution except if you use AHCI mode. On the off chance that the framework crashes when you change SATA modes, how might you securely change from IDE to AHCI mode?
1. Search for and run msconfig.exe.
2. Click the Boot tab.
3. Click the unfilled Safe Boot box
1. Click OK.
2. Swipe from the privilege or move your mouse to the lower-right corner of the screen and snap or tap Settings.
3. Click or tap Change PC Settings.
4. Click or tap Update and Recovery.
5. Click or tap Recovery.
6. Click or tap Restart Now
7. Press the key or keys expected to enter the UEFI firmware arrangement program.
8. Change the SATA mode to AHC
1. Select the choice to save changes and restart your PC.
2. Search for and run msconfig.exe.
3. Click or tap the Boot tab.
4. Clear the Safe Boot check box.
5. Click or tap OK.
6. Open the Charms menu.
7. Click or tap Settings.
8. Click or tap Power.
9. Click or tap Restart.
Your PC will restart utilizing AHCI mode for full execution of your SATA gadgets.
Free Drive Data and Power Cables
The inside of a work area PC is a jumbled spot. Regardless of whether you had your framework opened up for a memory overhaul, segment substitution, or just to perceive what's "in the engine," you may have released or detached the force or information links going to the hard circle or the information link interfacing the hard plate to the motherboard. On the off chance that your framework (C:) drive has separated or free links, you will see No Operating System or other comparative mistake messages.
To take care of issues with free or disengaged links:
1. Shut down the PC.
2. Disconnect the force supply from AC power.
3. Open the framework.
4. Check the hard plate or SSD for free or detached cable(s).
5. Check the motherboard for free or separated SATA information links.
6. Securely fitting the cable(s) into place
1. Close the framework.
2. Reconnect the force supply to AC power.
3. Restart the PC.
Drive Failure
In the event that your hard plate is making a noisy or shaking commotion when it's running, it has most likely fizzled. In the event that the hard plate was dropped or smacked hard, a disappointment is likely.
Be that as it may, a hard plate may have fizzled on the off chance that it is totally quiet in any event, when you place your ear close to it or doesn't get warm after the framework has been on for a few minutes.
Prior to expecting a hard plate has fizzled, play out this disengagement test to decide if the issue is the hard circle, its capacity link, or its information link:
1. Shut down the PC.
2. Disconnect the force supply from AC power.
3. Open the framework.
4. Locate the force link running between the hard plate and the force supply.
5. Disconnect the force link from the force supply.
6. If the force link utilized a splitter or converter to give capacity to the drive, plug the crash straightforwardly into the force supply (if conceivable). On the off chance that that is beyond the realm of imagination, supplant the splitter or converter and ensure it is safely connected to the force supply lead and the drive.
7. Reconnect the force supply to AC power.
8. Restart the PC.
9. If the drive is as yet not working, rehash stages 1 and 2.
10. Reconnect the drive to the first force link (and splitter or converter).
11. Remove the information link from the hard plate drive and the PC.
12. Install a known-working substitution link.
13. Plug it into the SATA port on the motherboard and drive.
14. Repeat stages 7 and 8.
15. If the drive is as yet not working, the drive has fizzled. Supplant it.
|
|
||||||||