Home > Blue Screen > Hard Drive Dead After BSOD? (but Still Readible Through CMD)

Hard Drive Dead After BSOD? (but Still Readible Through CMD)


RSS ALL ARTICLES FEATURES ONLY TRIVIA Search The How-To Geek Forums Have Migrated to Discourse How-To Geek Forums / Windows Vista (Solved) - No Bootable Device, now hard drive is trouble_28Feb 16, 2010, 12:39 AM I regularly image drives using another pc. Well here’s one way to fix it. My situation is not quite the same. have a peek at this web-site

When I press the F11 key, down in the corner it says "system recovery." The only thing is that when I put the drive in the computer as opposed to the I hope the information I have provided is helpful in some way when they encounter the "A Disk Read Error..." and nothing works. Perhaps it got tired of running the show. Not sure if Vista or Windows 7 have this problem?

Blue Screen Of Death Windows 7 Fix

Get your motherboard drivers downloaded from the manufacturer’s website. Perhaps it got tired of running the show. sub mesaFeb 21, 2010, 5:48 PM Fix the bad sector, of course.

Now when I load up, if I have the drive in an external case, I can load to the "System Recovery Options" dialog box, but if I have the drive in Changing the BIOS drive settings from auto to user-specified, ensuring that LBA is selected may fix it.9. I removed the flash drive as it was rebooting and.... Chkdsk Blue Screen Windows 7 I installed Linux to rule out the issue being Windows related but instead is now evidence the issue is related to Windows (in combination with the hardware).

When I restarted, I got that message about disk reading. How To Fix Blue Screen With Command Prompt This one uses F11 on booting to access the restore wizard http://h10025.www1.hp.com/ewfr.....=c01895783 When you get your system running make an O/S image following the instructions in that link Reports: · Posted Why else would only ONE program cause this error. This is where that other thread came in handy, to an extent.

On my system I can duplicate the error by copying the "windows" directory from a backup I made off of the drive before I re-imaged it. Windows 7 Blue Screen On Startup No Safe Mode schmappelFeb 23, 2011, 5:27 PM Another "me too". i can see and copy all the files from it. Follow screen prompts.

How To Fix Blue Screen With Command Prompt

Always with Comodo Time Machine. click for more info I am going to install Linux Mint 9 on the laptop and if the problem goes away, then indeed, it is a "Windows" related issue that needs to be addressed my Blue Screen Of Death Windows 7 Fix After they’ve finished downloading, you need to extract them to a folder. Unmountable Boot Volume Windows 7 Post back on what it shows.

Choaking myself in the process! http://gbcmedina.com/blue-screen/games-closing-while-playing-with-bsod-and-without-bsod.php I have been advised to use FDISK. You can do this by right clicking and selecting 7-Zip -> Extract to : Copy the extracted folder to a CD, thumb drive, or external USB drive. Could it be that the program file is corrupted in some way that only this ONE tower cannot deal with? Windows 7 Blue Screen On Startup Loop

Reports: · Posted 6 years ago Top germ-x Posts: 5310 This post has been reported. Also the drive has an 8 MB cache and maybe the machine powers down two quickly before the disk has had enough time to write the cache to disk? Having recently dealt with this again, I thought I'd post my thoughts in the hopes that it helps someone else out there.So you receive the dreaded "a disk read error occurred. Source Thanks for any help.

Here's my experience:* HP compac NC6400* put new sata 250 G drive in enclosure + clone existing 80 G drive to new drive using cloning utility.* put new drive in laptop. Blue Screen Of Death Windows 7 Memory Dump Get the answer madunitDec 21, 2009, 5:29 PM Hi, I am receiving this message and unable to do any of the options you suggest.I recently purchased a Dell Netbook Inspiron Mini THEREFORE, narrowing the issue (at least in this case) down to a file contained in the Windows directory that perhaps is not corrupt but telling Windows to look for something in

I was convinced to be the only one with this particular problem of the error happening only after a reboot when the disk seems to work fine initially.If i find anything,

No USB booting utilities helped. I did find something interesting, perhaps the problem itself but not how to fix. Reports: · Posted 6 years ago Top germ-x Posts: 5310 This post has been reported. 0x000000ea Windows 10 Could be a coincidence, but I, like, got a feeling that it's not.

I tried turning off the write cache in windows and system became painfully slow so I enabled it again. But my laptop will not boot from it. I reseated the drive and found some new screws. have a peek here SR does not always work, CTM always does.

Change your BIOS making your optical device the first boot order. Win7 Starter is worse than everything I had to face so far so I was trying everything to replace the 7 to the XP. Then I typed in DISKPART and detail disk. solved Disk read error occurred while formatting and reinstalling windows.

Maybe F: – check it out. mbokone davlakAug 3, 2010, 7:13 PM in my experience "A disk read error occurred" has nothing to do with the health of HD or damaged file system, but is a comunication rtrgSep 29, 2010, 11:59 PM PBARNY--- Since you seem to know more than I, I will pick your brains for help. The problem typically evades all forms of detection.Here's what I've learned: this error message likely has more to do with a hardware interaction between the drive and your system than any

faithfulnathanSep 7, 2010, 11:24 AM Hi all,I fixed mine by going to the BIOS, BOOT settings, HARD DISK DRIVES, and switching the order of the drives around - ie. Nobody seems to know why. That got me to the HP Windows Vista Recovery Manager or something, and I was able to re-install Windows Vista. Sometimes the fix is simple, sometimes it's a complete pain.

They ALL have the same issue with CTM. Read up on it, there is plenty of documentation out there.To simply clean a drive and repartition, do the following:1 - boot to the wiindows dvd and choose Repair.2 - Cancel I am guessing it is the registry because it is being written to and for some reason the process does not complete. I then re-imaged the unbootable drive and once again ended up with a working XP pro system.