Re: Can no longer boot up after vista update.
(cross-post added to Vista Perf & Maint)
"typhoon763" <email@example.com> wrote in message news:171223AB-F2B7-4EE1-9CAC-1C32CAF8D0BA@microsoft.com...
> My PC has been running vista ultimate for about 8 months now without much of
> an issue. Tuesday night I had the pleasure of that changing.
> An automatic update kicked in and when I awoke in the morning my pc was in a
> reboot cycle.
> I have tried all the safe modes, (it reboots right after the "loading
> crcdisk.sys "appears)
> I have tried the last known good config same results.
> I have booted with the install dvd and chosen repair. This fails too a
> message that it cannot correct the issue. It shows the following
> Problem signature:
> Problem Event Name: StartupRepairV2
> Problem Signature 01: ExternalMedia
> Problem Signature 02: 6.0.6000.163184.108.40.20600.16386
> Problem Signature 03: 6
> Problem Signature 04: 2752554
> Problem Signature 05: NoBootFailure
> Problem Signature 06: BadDriver
> Problem Signature 07: 0
> Problem Signature 08: 3
> Problem Signature 09: WrpRepair
> Problem Signature 10: 10
> OS Version: 6.0.6000.2.0.0.256.1
> Locale ID: 1033
> (As an aside, would it have been too much trouble to have added one more
> line to this with something like "Oh by the way, the bad driver is the xxxx
> driver". If I knew what driver I know I could correct this problem.)
Wouldn't that crcdisk.sys be a good guess? ; )
BTW does Vista have the /SOS boot option?
That might give you more information...
BTW although you may perceive WU as being the cause of your problem
symptoms, I think you are more likely to find a repair solution in a newsgroup
which specializes in your OS. (FWIW I don't use Vista.) Cross-posting for
> I have tried booting up with F8 and selecting the enable logging, but it
> fails to create a log.
> I thought maybe it was my nvidia raid driver, but the disks check out with
> the onboard tests as well as opening a command window when in the repair
> bootup and running chkdsk and the nvidia drivers appear to be the same ones
> as prior to this issue.
> Does anyone have an idea where I can look to see what driver is failing?