A recent power outage choked Windows XP Home, running on a HP Pavillion.  After that, XP Blue Screens at startup with STOP ED Blue Screen Code.  Using The 'Net, it seems to point to a hard drive failure with a recommendation to boot from the XP install disk, do 'R' for repair, then perform 'CHKDSK /R' to try to repair disk.  

When I boot from the XP install disk, it eventually Blue Screens again with STOP 7B code, another hard disk issue. Apparently the install program is checking hardware integrity early in the process and dies when it encounters the damaged hard drive.

Any other recommendations at this point, or is it a lost cause?
Who is Participating?

plug your hard disk into another computer as a slave
do system and virus check,
Then plug it again in the laptop back and check
Format and Re-Load - Your HD may be damaged but not likely.  Your low-level format is corrupted.
Boot using a liveCD or UBCd to see whether anything can be determined on the status of the drive. IF you know the make of the HardDrive, you could use the Vendors boot disk to check the condition of the drive i.e. western digital data lifeguard tools
IBM/hitachi have their own bootable CD that can check the status of a disk.
I think similar tools exist for Seagate and other vendors.

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

buy you a new harddisk if you don't have hp care service. the data most probably could be read. pc shops would do that for little money.
Zak GunnellsIT Infrastructure ManagerCommented:
Another thing to check is if you bios has a SMART setting for the hard drive, and turn it on, on the reboot if it triggers the SMART error, then there is something wrong with the hard drive, if not, then try the format and reload of the OS.
Before you go out there spending money on anything, first, run some hardware diagnostics:
We need to know if the memory and/or the hard drive are bad.
You will need to run some memory tests.. go to download the memtest86+ free software and test your memory.
You will also need to download some hard drive tests.Here is a list of hard drive tests you can get depending on the manufacturer of your hard drive (these are usually very good):
IBM and Hitachi 
Western Digital 
Spinrite is not brand specific but it is also very good.... 
You could also download from the boot cd and run the hard drive and memory tests provided with knoppix there.
i suggest to download ubcd to run the disk diag (you may even run ram diags from it, and more ) :      

i assume the disk is seen in the bios ?
you can also post some specs, on motherboard or pc model..
syd_rabinAuthor Commented:
Was able to run chkfdk /t on it when I hooked it up to another computer--this let me fix the drive to the point to where I could then put it back in the original system and have it properly load XP--this WORKED!
You've got to be kidding me......? What does this have to do with a power outage? What does it have to do with a clean install that: " checking hardware integrity early in the process and dies when it encounters the damaged hard drive...."
The damaged hard drive is reasonable after a power outage or surge. The damaged system is something you expect..... But I would never expect that a dormant virus would "Wake UP" after a power surge.....
Well ... reflecting on the answer... I guess he was able to format it from the other system and NO more Conundrum.... some feedback would be helpful and appreciated...
syd_rabinAuthor Commented:
First off, there was NO FORMATTING done on the troublesome drive.  Most all the suggestions were good and noble efforts.  I tried to run a Samsung diagnostic on the HD as BitsandBytesandMore suggested, but had too much trouble getting the ISO file to convert into a disk file that ran properly at boot-up on the suspected machine.   At that point, the notion was presented to me to move the drive to another machine.  When I did, the OS recognized it and immediately went into CHKDSK /R for the bad drive.  It seemed to make a lot of repairs and corrections, after which I was able to read the drive from this second machine to which I had moved it.  At that juncture, I put the drive back to the original machine and voila, it booted right-up the first time I tried.  As a result, I felt that the recommendation to mount the drive on another machine was a good suggestion because it worked after that, so YES, the conundrum was solved.  The actual conundrum was that early suggestions were to run CHKDSK from the XP Install disc in Repair Mode from the Command Prompt.  When I tried to do this, it still kept BLUE SCREENING on me, even before I got to the Recovery screen, much to my surprise.  THAT was the connundrum...   I appreciate all the responses, but I gave the points to the first solution that worked for me.  You guys are great!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.