"A disk read error occured" is displayed when the active partitions boot sector cannot read ntldr.
It can also be displayed if extended int13 calls are disabled in bios, ntldr is on a bad sector, FRS segment can't be loaded or any NTFS metadata is corrupt.
It's unlikely extended int13s are disabled. resetting bios to default would eliminate this.
The chain of events that leads you here follows. The last step is the one that fails, I'll let you troubleshoot from here.
1. Bios picks what disk to read based on the settings you give.
2. Bios reads and executes code in MBR at sector 0.
3. MBR checks partition table for which partition is active.
4. MBR loads the boot code at the active partition.
5. The boot code reads ntldr.
Step 5 is where the error is.
If ntldr were actually missing in step 5 you would get a missing ntldr message.
Step 2 & 4 must be working properly or we couldn't reach this point.
Check the settings for step 1 & 3 and you'll find your answer.
If they are both correct then you are back to the corruption I mentioned earlier. Chkdsk /R ftw.
Good Luck!
by c'g the above problem in my life now, here my problem is when i connect hdd and on bios is not opening , when i remove my hdd and on pc then my bios is opening , where d problem is ,
actually my hdd is also not opening
when i start pc and press del key,
1.auto detecting cd-rom,
2.auto detecting hdd(segate).....
3.autodetecting usb ...
BIOS
4me it is stoping at step 2 only , in my pc , if i keep my hdd in some other pc it is show'g ntldr is missing disk read error
what 2 do now plz reply me!
self-promotion facebook link removed
Last edited by a moderator:
Facebook
Twitter