A disk error occurred now i'ts on the bios and won't boot program

A disk read error is very common; it usually occurs as soon as your computer boots up from SSD, HDD or another hard drive and has affected a large number of users of Windows 10/8/7/XP.
This error has the message "A disk read error occurred. Press Ctrl+Alt+Del to restart" on the screen like the picture below:
This message indicates that your hard drive has a problem when the operating system attempts to read the disk. That is, the disk is preventing the computer from entering into its operating systems.
Simply put, a disk error could be caused by several reasons such as incorrect boot order, BIOS issue, IDE cables failure, incorrect MBR configuration, faulty hard drive, etc.
When meeting such an issue, no matter how many times you restart your computer by pressing "Ctrl+Alt+Del" keys, this error still exists.
In the presence of this issue, it will still exist regardless of how many times you restart your computer by pressing "Ctrl+Alt+Del". In fact, a disk read error is not a problem that can be solved by a simple restart. But don't worry, this post will tell you top seven useful solutions to a disk read error occurred SSD.
How to Fix Disk Read Error Windows XP/7/8/10

Solution 1: Boot OS from Hard Drive

If a disk error occurred, the first thing to do is to check whether the boot order is correct in BIOS.
There are different ways to get into BIOS in different computer models and operating systems. When turning on the computer, the first boot screen will usually show you what key to press to go into the BIOS.
You can refer to this guidance How to Enter The BIOS On Your Computer. Once you are in BIOS, find the boot order section. In the boot order section, check to make sure the correct hard drive is placed as the first boot priority before any others in the listing.
Changing this setting might be enough to help your computer boot normally. If it is still unbootable, try the next solution to fix disk error occurred.

Solution 2: Reset or Upgrade BIOS

Resetting your computer BIOS to default or upgrading to the latest version might be able to solve "A disk read error occurred" in Windows XP/7/8/10.
Here is the step-by-step guide to reset BIOS:

1. Press a specific key (F2, F8, F12, Esc or Del) according to your computer model and OS to enter into BIOS.
2. Find the option to reset BIOS to default.

Tip: The option name is different depending on different computer manufacturers and BIOS versions, which can be "Load BIOS Defaults", "Load Default Settings", "Load Fail-Safe Defaults", "Load Setup Default" or "Get Default Values". Choose one according to the real case, then save this change.
If the disk read error on boot up persists, try the following solution.

Solution 3: Repair Master Boot Record and Boot Sector

A corrupted or damaged Master Boot Record or boot sector could cause disk errors. Therefore, repairing the MBR or boot sector might be able to fix the issue"A disk read error occurred" with USB boot.
You can use a professional and reliable partition and disk management tool - MiniTool Partition Wizard - to repair your MBR in Windows XP/7/8/10.
As a dedicated partition manager, MiniTool Partition Wizard could be used for many operations such as resize/move/extend/copy/wipe partition, rebuild MBR, migrate OS to SSD/HD, copy disk, recover lost partition, perform data recovery, and so on.
Here we strongly recommend MiniTool Partition Wizard Professional Ultimate Edition. This edition has a feature called "Bootable Media" based on Win-PE; it is designed to manage disks and partitions when the operating system fails to boot or when there is no operating system.

First - re-seat the hard disk and reboot the computer. If the computer does not boot up then reboot and go into the BIOS configuration to see if the BIOS detects the hard drive. If it doesn't detect the hard drive then it could be faulty.
Then the hard drive needs to be replaced in the computer/laptop, Windows installed and the computer or laptop's device drivers plus your programs etc. to get a functioning computer/laptop again.

First - re-seat the hard disk and reboot the computer. If the computer does not boot up then reboot and go into the BIOS configuration to see if the BIOS detects the hard drive. If it doesn't detect the hard drive then it could be faulty.
Then the hard drive needs to be replaced in the computer/laptop, Windows installed and the computer or laptop's device drivers plus your programs etc. to get a functioning computer/laptop again.

Hard drives do not like being dropped even inside a notebook. It is a sure way of destroying a hard disk.
First - re-seat the harddisk and reboot the computer. If the computer does not boot up then reboot andgo into the BIOS configuration to see if the BIOS detects the hard drive. If itdoesn't detect the hard drive then it could be faulty.
Then the hard drive needsto be replaced in the computer/laptop, Windows installed and the computer orlaptop's device drivers plus your programs etc. to get a functioningcomputer/laptop again.

First - re-seat the harddisk and reboot the computer. If the computer does not boot up then reboot andgo into the BIOS configuration to see if the BIOS detects the hard drive. If itdoesn't detect the hard drive then it could be faulty.
Then the hard drive needsto be replaced in the computer/laptop, Windows installed and the computer orlaptop's device drivers plus your programs etc. to get a functioningcomputer/laptop again.

When the Date and time error message comes up during booting up the computer, it means the BIOS requires configuration.
If this occurs every time you boot up your computer after changing the Date and Time then, this is caused by a flat BIOS battery.
The BIOS battery is ususlly a 20mm dia. 3 volt lithium battery type CR2030
Replace the BIOS battery and then configure the Date and Time and you won't get this error again.

This error occurs when the notebook cannot boot up from the hard disk. The hard disk may be faulty.
Try re-seating the hard disk to make sure it makes proper connection to the motherboard.
Next go into the BIOS configuration and check to see if the BIOS detects the hard disk, if it is not detected the the hard disk is probably faulty.
To get your notebook operating again, replace the faulty hard disk, install Windows on the new hard disk, plus the notebook's device drivers and your programs.

Error code 0101340000, may be due to hardware issues

1. Faulty hard drive or defective memory
2. Damaged recovery media(CD) or faulty CD ROM

OR

Boot system corrupted,
This issue may occur if one or more of the following conditions are true:
The basic input/output system (BIOS) does not detect the hard disk.
The hard disk is damaged.
Sector 0 of the physical hard disk drive has an incorrect or malformed master boot record (MBR).
Note Some third-party programs or disk corruption can damage an MBR.
An incompatible partition is marked as Active.
A partition that contains the MBR is no longer active.

Hope it helps.

Please check that the hard disk is connected properly. If you know that the hard disk is working, check whether it is detected or not. If it's not detected, you'll need to recheck it again with the power supply. If possible, try it to another Laptop so that you can make sure that Hdd isn't the culprit. In case it's detected and the problem still persists, repair the operating system installation, this will definitely solve your problem. Good luck.

Non-System Disk or Disk Error results when the Basic Input/Output System (BIOS) cannot find the boot sector or the master boot record is missing or damaged; i.e. the device does not have bootable media. The BIOS searches drives in the order usually specified in the CMOS Setup. This order is often, but not always, A: (floppy drive), C: (first partition on the hard disk)… The error will occur during startup if the CMOS is set so the BIOS seeks the floppy drive first and a non-bootable (or blank) floppy is in (was left in) the floppy drive. Other causes include:

No bootable partition on a hard disk drive

A defective hard disk drive

The CMOS drive settings (parameters) are not correct for the boot device

Defective floppy

Defective floppy drive

A virus