Firstly, a Packard Bell which is saying that it has an ‘Unmountable Boot Volume’. at start up; you are offered the chance to start in safe mode/safe mode with command prompt, last known good configuration etc., but even when selected the ‘Unmountable’ problem shows up. Additionally, it also has the letters/numbers ‘STOP 0X6 ED (0x8A5979E0) along with a whole lot more zeros. I’ve tried the usual Bios tricks – because it suggests knocking off ‘shadowing’ and ‘caching’ but I can’t find them! We don’t have the original installation disks so we’re at a loss.

Secondly, a Packard Bell which when it’s booting offers the Safe Mode options, along with start Windows normally. When it boots up in normal mode, it goes slow. In the icon section at the bottom right of the screen, an IDE device driver is installing and this, I think, is the problem. It doesn’t finish installing though.

Any suggestions to these problems would be greatly appreciated.

At the bootup set up I can see it detecting the disk but I run the first part of the installations its was fine but cant continue during examine disk.

this is the problem i had for my computer or hard disc

I remove the hard disc and slave it to other computer in the slave master but it restart the computer again repeatedly like my old computer.
I slave to recover my files but the same problem happen. it cannot be slave .

pls advice me how to solve my computer

thanks

Thanks for reading guys, let me know if you have any thoughts…

Thanks Joseph, As soon as I get back in town to my handicapped PC, I’ll let you know if anything works for it…

Did you recently install video drivers? Anything at all? I’ve heard of a bad install causing Windows to crash in semirandom DLL/SYS/EXE/etc. modules. Random but among a very small list (all of them loaded by kernel). If you only see NTFS.SYS then this might not be the problem. Did you add any new hardware? Is the power supply up to the job? Is the cable going to the drive loose/bad?

Here’s some info on fixing it if it’s the NTFS bug. Please tell us if it works. If it doesn’t then you may need recovery services.

I had the recovery console BSOD and had to use a trick like those to get around it. If you have a drive that works, it would be a good idea to just make an image using the program on this site. That way you can go back if you mess it up even worse with CHKDSK.
BTW If you have backups, you can just zero the drive out and start over. I’d still use a S.M.A.R.T. reading utility to see if the drive is likely to fail. I think this site has one.

Someone else had a problem like this that seems to be at least partially hardware related:
Link
That implies that you should try putting the drive in another board with different power supply and all, when trying to run the recovery console. It still may not work, but at least you’ll eliminate the hardware from immediate suspicion.

Here’s some stuff to run next time you build/rebuild a system.
1) Run the bootable memory checking CDs like Memtest86+.
2) Make sure that all cables and connectors look good. When I lived in the country I found a cable that a mouse had nibbled on! Someone left a small hole in the back and it got in. I’ve seen cables break when taken off of drives or sitting next to fans, etc. I’ve seen pins on the drives get bent or even pushed in. A little visual inspection can’t hurt and only takes a few minutes while wondering what the problem is could take days!
3) Check that the system doesn’t get too hot. Cleaning fans and vents often solves thermal problems on older machines. Most BIOS setup screens have a “System health” menu or the like. If not, just check using a program like Everest in Windows.
4) If Windows doesn’t want to install even to a new drive, try a boot CD like Kubuntu. If it fails to boot then at least you know that it’s not your Windows CD! Added bonus is that the memory testing program is on that CD so you only need to burn one.
5) Enable S.M.A.R.T. warnings in your BIOS setup screen if available. If your BIOS doesn’t have an option to warn you when booting with a bad drive in the system, then get a Windows program that does the same.
6) Backup, backup, backup! LOL I imagine that DTI will repeat that sentiment if you don’t.

Mine is not quite the same screen as the one displayed above.

It tells me first to disable any anti virus programs and run a chkdsk /F on the drive. I did run the scandisk and everything checked out fine. This is what the tech info looked like:

*** STOP: 0×00000024 (0x001902FA, 0xF96DF814, 0xF96DF514, 0xF8E84BBA)

*** ntfs.sys – Address F8E84BBA base at F8E78000, DateStamp 3d6e5c1

When I tried to run the recovery console, as soon as I type in “r” to start the process the screen reappears again. Every type of way to boot up leads to the same screen… any ideas?? At least if I can’t ever boot up, are there ways to get info from the disk still?

Thanks

David

1. You could try taking this drive out of the laptop and slaving it in to a desktop with XP PRO on it and then try the steps in this walkthru. I would think that the permissions from the XP Professional load would over take the permission on the salve drive since those would not be loaded. You could then log into the recovery console as the admin of that machine and do what is needed.

2. The assumption I am making is that you have the Windows XP Home Cd? If this is the case you could theoretically try re installing windows over the top of itself. I am not a fan of this method because something could go very go awry. So I would try the first method if at all possible.

I just recently experienced a BSOD with a stop code: 0x0000007B on a Dell Dimension 2400 machine running XP SP2 Home. When I ran across your fix procedure here I fired it back up and attempted it. The response to the very first command> C:\Windows CD C:\System~1\_Restor~1; provoked this repsonse on enter: Access is denied.

I suspect that there may not be a way to get around this “access denied” issue on XP Home, but perhaps you could suggest what I might now try to do.

Thank you for any camaraderie on this.

Mike