Blue Screen Then Disk Read Error
Contents |
Fix for Windows XP, Vista, 7, 8 September 23, 2016 Get the fix for the error A disk read error occurred on Windows XP, Windows Vista and Windows 7. Contents1 About "A disk read error disk read error windows 7 occurred"1.1 Description and Symptoms1.2 Symptom 1: "A disk read error occurred" error screen
Disk Read Error Windows 10
on startup2 Causes of this Error2.1 Cause 1: Incorrect or invalid MBR configuration2.2 Cause 2: Misconfigured partition table3 Fixing “A disk read
A Disk Read Error Occurred Windows 10
error occurred” on Windows3.1 Fix #1: Use Easy Recovery Essentials3.2 Fix #2: Check RAM memory3.3 Fix #3: Check Hard Disk Cables3.4 Fix #4: Reset or Upgrade BIOS3.5 Fix #5: Run chkdsk3.6 Fix #6: Run http://www.tomshardware.com/forum/359273-31-disk-read-error-bsod bootrec4 More Information4.1 Linked Entries4.2 Support Links4.3 Applicable Systems About "A disk read error occurred" The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations. Description and Symptoms The error messages, alerts, warnings, and symptoms below are tied to this error. Symptom 1: "A disk read https://neosmart.net/wiki/a-disk-read-error-occured/ error occurred" error screen on startup The "A disk read error occurred error" appears on a black screen without an identifiable error code. Pressing the Ctrl, Alt and Del keys will only restart the computer and boot into the same error screen: A disk read error occurred Press Ctrl+Alt+Del to restart In most cases the error can appear for any of the following reasons: Incorrect or invalid MBR configuration Improperly configured partition table Faulty hard drive IDE cables failing Bad RAM memory Issues with your computer's BIOS version The most common cases of this error are attributable to an incorrectly-flashed MBR to the system startup disk or the absence of an active partition on the startup disk. In these situations, the recommendations below should resolve the problem readily. If the problem is with hardware, additional diagnosis and the possible replacement of system components may be needed. Causes of this Error This error has been known to occur as a result of one of the following causes: Cause 1: Incorrect or invalid MBR configuration The most common cause for this error is an incorrect MBR configuration. This is usually caused by disk write errors, virus attacks or power outages. Cause 2: Misconfigured parti
List Welcome Guide More BleepingComputer.com → Hardware → Internal Hardware Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable http://www.bleepingcomputer.com/forums/t/349000/a-disc-read-error-occurred-press-ctrl-alt-del-to-restart/ javascript to access full functionality. Register a free account to unlock http://www.sysopt.com/showthread.php?205794-W7-BSOD-followed-by-quot-a-disk-read-error-occurred-quot-at-boot additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can disk read not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this disk read error site. A disc read error occurred. Press Ctrl + Alt + Del to restart Started by LordBTY , Sep 22 2010 04:11 PM Page 1 of 3 1 2 3 Next Please log in to reply 40 replies to this topic #1 LordBTY LordBTY Members 23 posts OFFLINE Local time:06:22 PM Posted 22 September 2010 - 04:11 PM A while ago I got a RAM upgrade from Crucial memory. They have an online scanner that told me it was ok to install 7gb of RAM - it's not. This isn't a virus as far as I'm aware, so I've posted it here. After having received the blue screen a while back due to the fact it didn't like the hardware, I removed it. I now have 4gb installed, with the other 3gb gathering dust. My PC was working fine until just now when I was using the Digital Audio Workstation 'Cubase' with Propellerhead Reason. I eventually got the blue screen and my PC restarted with the message 'A disc read error occurred. Press CTRL+ALT+DEL to res
BSOD followed by "a disk read error occurred" at boot If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Page 1 of 2 1 2 Last Jump to page: Results 1 to 15 of 17 Thread: W7 BSOD followed by "a disk read error occurred" at boot Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 10-19-2010,09:59 AM #1 joah View Profile View Forum Posts Visit Homepage Member Join Date Aug 2002 Location Amsterdam Posts 233 W7 BSOD followed by "a disk read error occurred" at boot Hello everyone, First of all, thank you for your time. My computer dual boots to win7 pro / Xp pro SP3. Win 7 pro was recently added (about a month ago) and all was running fine. I was watching a media stream when i got a BSOD (couldnt see the error number, because the computer quickly rebooted). At boot it now gives me "a disk read error occurred - press CTRL-ALT-DEL to restart". The computer has two harddisks, an ATA WDC WD2500AAKS-0 and an ATA Maxtor 6B200M0. The WD disk is partitioned into two NTFS partitions, the Primary Bootable having the old WinXP pro on it and the other Primary having Win 7 on it. I used Rescue CD 1.1.6 to start Testdisk 6.10. In Testdisk i chose to repair the MFT by selecting "Fix MFT using its mirror". I did this to both partitions. My effort obviously did not help as i am still getting the error. I might as well have made things worse. Being weary about getting any deeper into trouble by doing something i should't, i came to ask your