Vista won't Boot - Problem Event Name:Startup repairV2

Have Vista running on Dell Inspiron 1720. All of a sudden I can't star
Windows. Startup Repair can't fix the problem and System restore can'
seem to solve the problem either. Am starting to panic

Startup Repair listed the following as the problem details but i
leaves me clueless

Problem Event Name:Startup repairV

Problem Signature 01: AutoFailur

Prob Sig 02: 6.0.6001.18000.6.0.6001.1800

Prob Sig 03:

Prob Sig 04: 78644

Prob Sig 05: Corruptvolum

Prob Sig 06: NoRootCaus

Prob Sig 07:

Prob Sig 08:

Prob Sig 09: WrpRepai

Prob Sig 10: 8

OS Version: 6.0.6001.2.1.0.256.
Local ID: 100

Have used Dell pre-boot checks and all physical systems seem fine s
must be software. Can anyone help

Thank

--
Buzbyb6

>Startup repairV2

>Startup Repair can't fix the problem and System restore can't
> seem to solve the problem either.


From what you posted it everything seems to point to the Hard Drive

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Buzbyb6" <> wrote in message
news:...
>
> Have Vista running on Dell Inspiron 1720. All of a sudden I can't start
> Windows. Startup Repair can't fix the problem and System restore can't
> seem to solve the problem either. Am starting to panic.
>
> Startup Repair listed the following as the problem details but it
> leaves me clueless.
>
> Problem Event Name:Startup repairV2
>
> Problem Signature 01: AutoFailure
>
> Prob Sig 02: 6.0.6001.18000.6.0.6001.18000
>
> Prob Sig 03: 6
>
> Prob Sig 04: 786444
>
> Prob Sig 05: Corruptvolume
>
> Prob Sig 06: NoRootCause
>
> Prob Sig 07: 0
>
> Prob Sig 08: 2
>
> Prob Sig 09: WrpRepair
>
> Prob Sig 10: 87
>
> OS Version: 6.0.6001.2.1.0.256.1
> Local ID: 1003
>
> Have used Dell pre-boot checks and all physical systems seem fine so
> must be software. Can anyone help?
>
> Thanks
>
>
> --
> Buzbyb6

I have done a Dell system check on the hard drive as well as a chkdsk /
/f... which did find some mis-allocations which were fixed but no othe
abnormalities. When I run System Restore I get the error message: syste
cannot find the file specified (0x80070002

Any further thoughts or advice

--
Buzbyb6

Buzbyb6;977028 Wrote:
> I have done a Dell system check on the hard drive as well as a chkdsk /
> /f... which did find some mis-allocations which were fixed but no othe
> abnormalities. When I run System Restore I get the error message: syste
> cannot find the file specified (0x80070002
>
> Any further thoughts or advice

Further Info..

Having done a bootlog, everything goes phlooey after the driver
crcdisk.sys gets loaded... Does this help

Buzbyb

--
Buzbyb6

Buzbyb6 wrote:

>
> I have done a Dell system check on the hard drive as well as a chkdsk /r
> /f... which did find some mis-allocations which were fixed but no other
> abnormalities. When I run System Restore I get the error message: system
> cannot find the file specified (0x80070002)

My experience with the Dell diagnostics is that they aren't particularly
accurate. Test your hard drive with a diagnostic utility downloaded from
the drive mftr. (or use Seagate's SeaTools For DOS). You will create a
bootable CD with the file you download. You will need third-party burning
software to do this such as Roxio, Nero, or the free CDBurnerXP Pro. Burn
as an image, not as data.

http://www.cdburnerxp.se/

Boot with the CD you made and do a thorough test of the drive. If it fails
any physical tests, replace it.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Malke;977096 Wrote:
> Buzbyb6 wrote:
> > > >
> > >
> > > I have done a Dell system check on the hard drive as well as a chkdsk
> > /r
> > > /f... which did find some mis-allocations which were fixed but no
> > other
> > > abnormalities. When I run System Restore I get the error message:
> > system
> > > cannot find the file specified (0x80070002) > > My experience with the Dell diagnostics is that they aren't
> particularly
> accurate. Test your hard drive with a diagnostic utility downloaded
> from
> the drive mftr. (or use Seagate's SeaTools For DOS). You will create
> a
> bootable CD with the file you download. You will need third-party
> burning
> software to do this such as Roxio, Nero, or the free CDBurnerXP Pro.
> Burn
> as an image, not as data.
>
> 'CDBurnerXP: Introduction and News' (http://www.cdburnerxp.se/)
>
> Boot with the CD you made and do a thorough test of the drive. If it
> fails
> any physical tests, replace it.
>
> Malke
> --
> MS-MVP
> Elephant Boy Computers - Don't Panic!
> 'index' (http://www.elephantboycomputers.com/#FAQ)

Will do.... I created a bootlog and all goes fine until after
crcdisk.sys driver is loaded.. Is this some kind of hard drive checking
system? Everyone seems to have had troubles after this driver is loaded.
Some people have suggested editing the bios, others deleting driver
files.... Yikes?! can you shed any light on this point?

Sorry real newbie in all of this...


--
Buzbyb6

Buzbyb6 wrote:

> Will do.... I created a bootlog and all goes fine until after
> crcdisk.sys driver is loaded.. Is this some kind of hard drive checking
> system? Everyone seems to have had troubles after this driver is loaded.
> Some people have suggested editing the bios, others deleting driver
> files.... Yikes?! can you shed any light on this point?
>
> Sorry real newbie in all of this...

I've re-read your thread and noticed that you said this happened "all of a
sudden". Are you sure you didn't change anything? Add any virtual drive
software (like Daemon Tools)? That error message can refer to a driver,
which would be a software problem, but I've also seen it on machines where
the hard drive was dying.

Since you can't get into Safe Mode, Regular Mode, or Last Known Good
Configuration, can't do Startup Repair or System Restore - you're really
stuck. I would:

1. Retrieve any data that you forgot to back up. Do this by booting with a
rescue CD such as Knoppix (Linux) and copying the files to an external hard
drive or USB thumb drive with enough capacity. Doing this satisfies two
goals - to get your data and to see how the computer behaves when booted
into Linux. If the machine behaves perfectly, then you know that hardware
isn't the issue and Windows is hosed (software). Conversely, if the machine
won't boot to Linux or freezes during use, etc. then you know it's hardware
(probably the hard drive).

2. Let's say the machine is fine under Linux and you've now gotten your data
off. I would still do the long test with a hard drive diagnostic utility
because it won't hurt and it's nice to have that extra reassurance the
drive is healthy. Then if the drive passes, I'd restore to factory
condition using whatever method Dell gave you for that laptop.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ