Computer won't boot: "A problem has been detected...."

type /fastdetect /NoExecute=OptIn and press enter. Watch your spaces and be exact.

 

Both of you answered at the same time. Here's what's happened:

I hit Return ( "Enter" on my keyboard), and the result was:

[2]: F:\WINDOWS
Add installation to boot list? (Yes/No/All):

I typed N and that resulted in a C:WINDOWS prompt, and that's where I am now. Next?

 

That's all I have. Stick around for Bill's take on this and perhaps you can boot to see if your system files are still workable. I have serious doubts.

 

Bill must be busy elsewhere. While you're waiting, you can run chkdsk C: /r from the RC command line that you have there. It won't hurt to get another report. See if any lost files or bad sectors show up this time. You should get a full report when it finishes.

 

Ran chkdsk c: /r and quickly got a response that says in part:

The volume appears to contain one or more unrecoverable problems.
22531168 kilobytes total disk space.
8118536 kilobytes are available.
4096 bytes in each allocation unit.
5632790 total allocation units on disk.
2029634 allocation units available on disk.

And it ended with a C:\WINDOWS prompt.

Assuming that "the volume" refers to the C:\ drive, that 22.5 GB total disk space figure is about right. I recently checked the size of the HDD partitions and the C partition was reported to be 21.49 GB. I didn't record the available free space at the time, but 8.1 GB looks about right, too. The claim of 56 GB total allocation units in disk may raise a question. For a 80 GB HDD, a lot of allocation units seem to be missing. Is that from the disk damage and repairing we've been doing?

 

Ouch, that's not what we wanted to hear.

While resident in C:\windows, run the cd\ command to get the C:\ prompt and then run the attrib command. Lets see what's on the root of that C: drive. Report back what you see, especially if you see ntldr, ntdetect.com and boot.ini.

Then let's give that F: drive a look see also. What's with it having been detected as having Windows on it?? Anyway, run chkdsk F: (with no /switches) to see what it says.

It's not looking good for that HD although there's still an outside chance that some obscure software corruption is affecting these tests.

 

Running the attrib command from the C:\ prompt still gets the reply: "The parameter is not valid. Use /p if you want to check the volume anyway." The same thing happens if I enter "attrib c:\" (without the quotes). Should I try it with the /p parameter?

The scan found a Windows folder in F:\ because, as I explained in an earlier post, I use that partition as a holding place for numerous backup programs and files. When I can get a decent boot, I'd be able to copy files and folders from there to wherever I want. But that's the problem now, I haven't been able to get Windows to load for the past few days.

Running a chkdsk f:, it says in part:

The volume appears to be in good condition and was not checked.

Then there are some specs on disk space, allocated units, etc. And I'm now back to a C:\ prompt.

 

Forget the attrib command. It was just a weak shot anyway.

I don't think this HD is any good and I'm doubting that you got a definitive test with the Maxtor diagnostic CD. I recommend that you run it again. Stick with the non-destructive tests however unless you're not concerned about losing your personal data. If data is no consideration, you can go ahead and try to format the C: drive (partition) using the Maxtor CD and it will certainly tell the tale as to whether the drive is usable or not. Your choice - your data.

I'm not aware of any tool that can redeem a drive like this however you may try using the copy command to get any valued data over to the F: partition. That assumes that there is anything readable on the C: drive.

 

I'm not sure why, but the copy command is available now whereas when I tried to use it the other day it wasn't available. I believe I was working in the Recovery Console then. Am I not in it now?

Anyway, I'd rather not do a reformat of C:\ just yet. Hoping that somehow we'll still be able to work through this.

The only personal data I have on C:\ is my Netscape 7.1 data: e-mail, Address Book, Bookmarks, and Custom Dictionary. I'd like to not lose all that if possible. Toward that end I just finished trying to copy it with this command: "C:\copy C:\Documents and Settings to F:\ ", but the reply was: "The parameter is not valid." When I did a "copy /? ", a lot of explanatory text appeared that gives the impression I ought to be able to get the job done. Am I not doing it right? What's wrong with "the paramater "? I tried "c:\copy c:\documents and settings f:\documents and settings ", too, but that didn't work, either, giving me the identical response.

 

It is not reporting "56 GB" of allocation units:
4096 bytes in each allocation unit.
5632790 total allocation units on disk.
2029634 allocation units available on disk.


The numbers appear right to me.

The next two items in sequence I requested were not done:
fixmbr
fixboot

This was to recopy the XP boot files, and reset the MBR.

Do both steps, remove the XP CD, and type: exit

 

When I enter the fixmbr command, this appears:

** CAUTION **
This computer appears to have a non-standard or invalid master boot record.

FIXMBR may damage your partition tables if you proceed.

This could cause all the partitions on the current hard disk to become inaccessible.

If you are not having problems accessing your drive, do not continue.

Are you sure your want to write a new MBR?


Well, I am having trouble accessing my drive, so it would seem I should continue, but that part about all the partitions on the HDD becoming inaccessible makes me think twice. On one hand, if I don't go ahead, my HDD may remain inaccessible and in effect useless. But if I do go ahead, the "fix" could make what's on my HDD inaccessible and useless. A Catch-22 situation. But it does say it "may" damage the partition tables and "could" cause the partitions to become inaccessible, not "definitely will" cause those results.

So what I'm wondering now is whether the fix completely erases the current MBR and replaces it with a good one, or if it merely repairs the defects in the MBR and leaves most of it unchanged so the partition tables themselves won't be altered. Am I interpreting "partition tables" correctly? What's your take on the effect(s) this fixmbr step will have?

 

It is a good question with no good answer.

If you used any drive overlay software to work around BIOS limitations in acessing the full capacity of the drive, the answer must be no.

If you have used boot managers, for example, BootMagic that comes with Partition Magic, or have a Linux installation, for example, the answer must be no.

For the moment, answer no, I do not want to write a new MBR.

Please, however, do the fixboot c: command.

 

OK, did the fixboot c: command and the response was "The new bootsector was successfully written." I'm now back at a c:\ prompt.

BTW, I did use Partition Magic 7.0 to partition the HDD when it was new 4 years ago, if that affects any decisions to be made.

 

Remove the XP CD.
type: Exit

If XP does not start, power off. Count thirty Mississippi, and power on. Report your results.

 

Had to type Exit before I could get the CD drawer to open and remove the CD, did that, and then the boot options appeared. XP was a new option, at the top, then lower down was Microsoft Windows XP Home Edition. That's the one I chose. That brought up a screen with Start Windows Normally as an option. Chose that, and it resulted in that same old BSOD. Powered off, waited 45 seconds, powered on, this time selecting Safe Mode. BSOD again. Powered off.

Ideas?

 

What was the BSOD error number, and the error text.
What happens when you choose the other Windows option at boot?

 

Here's the BSOD message I've gotten every time:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical information:

*** STOP: 0x0000007B (0xF896D640, 0xC0000034, 0x00000000, 0x00000000)

That's the same BSOD I've gotten every time, every way I've tried so far. There may be other procedures to try, but I don't want to get too creative again by myself.

 

And what happens when you choose at boot the other shown Windows installation?

 

Do you mean the one in F:\?

I put the Dell Windows Reinstallation CD in so I could get to the Recovery Console, where it shows:

1: C:\WINDOWS
2. F:\WINDOWS

Which Windows intallation would you like to log onto

Should I select the F:\ prompt? Should I type a command there?

 

No, he means the one you described as Windows XP when you got the boot screen without the CD inserted in the drive. That's the installation we rebuilt, remember? I had you type Windows XP when it asked for the "Load Identifier. "

Exit the RC, remove the CD and boot to the option screen again. This time, highlight the Windows XP item (use up/down arrows as needed) and press enter.