Prev: Vista Shortcut Manager updated to v2.0
Next: chkdsk logs in Vista
From: Dominic Payer on 31 Oct 2007 03:45
SeaTools for DOS is the one you want.
http://www.seagate.com/www/en-us/support/downloads/seatools/



"BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
news:89E3FF5E-BE95-4AEF-874F-DE705BFC3974(a)microsoft.com...
> Hi Dominic,
> Your suggestion is a good idea, but I can't find an edition of Seagate's
> SeaTools that runs on x64. Do you know of one?
> Thanks,
> Bill
>
> "Dominic Payer" wrote:
>
>> This sounds like a disk hardware failure that coincided with the Avast
>> update.
>>
>> Download and run the disk manufacturer's test utility. That will tell you
>> what is wrong with the disk.
>>
>>
>>
>>
>> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
>> news:FEE6D0B5-C0CD-4685-BF43-A638F52F8677(a)microsoft.com...
>> > Tony,
>> > Yes, flashing the BIOS was after the Avast upgrade and part of my
>> > attempt
>> > to
>> > repair. Also, I have another identical machine (I've actually built 3
>> > of
>> > these the exact same way) and I have removed the hard drive out of the
>> > problem machine and put it in the other one, which boots fine with its
>> > own
>> > normal hard drive. When I install the problem HD into it, it acts the
>> > exact
>> > same way - no boot. So I am pretty sure that something has happened to
>> > the
>> > hard drive itself. It's not a problem on the motherboard or with SATA
>> > cables
>> > or CMOS batteries or resets. If it was, then when I moved the HD to the
>> > other
>> > machine, the behaviour would be different. It isn't. It's identical. No
>> > boot,
>> > and when I do actually get into Safe Mode, it stops at the same place
>> > (biosinfo.inf).
>> >
>> > And speaking on that, I thought that the file biosinfo.inf might be a
>> > problem. So I copied it from the twin machine back to the damaged one.
>> > Still
>> > no difference. Exact same result - no boot, etc.
>> >
>> > I really think something is wrong in the boot files that was corrupted
>> > when
>> > the Avast update was done. I do not believe it is any sort of hardware
>> > issue,
>> > since when I move the HD to the twin machine (which runs fine) I get
>> > the
>> > same
>> > results.
>> > Thanks,
>> > --Bill
>> >
>> > "Tony Sperling mail.dk>" wrote:
>> >
>> >> Well, this is close to what I am having. In addition to the BIOS
>> >> thing, I
>> >> want to draw attention to the SATA cables as one possible weak point.
>> >> They
>> >> are rather stiff and routing them around the case could result in them
>> >> having tension that wants to pull them out of their sockets. They
>> >> aren't
>> >> snapping on very tightly in their sockets anyway and I had to apply a
>> >> half-turn sideway twist before looping them around between the HD and
>> >> the
>> >> MB. This is hard to explain in graphical language, but I think you'll
>> >> probably see what I'm driving at.
>> >>
>> >> While you are inside, you might as well reseat everything else too,
>> >> just
>> >> unfasten and give everything a gentle 'wiggle' and fasten it again.
>> >> Then
>> >> let's see how it behaves. You should at least be able to boot from a
>> >> CD/DVD.
>> >> Hopefully!
>> >>
>> >> Oh - and flashing the BIOS, was that after the Avast upgrade?
>> >>
>> >>
>> >> Tony. . .
>> >>
>> >>
>> >>
>> >> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
>> >> news:2F343F93-2C7B-4649-9D78-A44760AE8ADE(a)microsoft.com...
>> >> > Hi Tony,
>> >> > Thanks for taking the time to reply.
>> >> > To answer your questions:
>> >> > 1- The system was built in June 2006.
>> >> > 2- It is not a dual boot box. Only boots to x64 Windows.
>> >> > 3- Avast was installed from the beginning.
>> >> > 4- One HD. Seagate, 320GB, SATAII - no RAID
>> >> > 5- I have flashed the BIOS to the latest one. No difference.
>> >> > Flashing
>> >> > resets
>> >> > the BIOS just like removing the battery (I think). At any rate, it
>> >> > didn't
>> >> > help.
>> >> >
>> >> > Motherboard is ASUS A8N32-SLI Deluxe, BIOS 1303
>> >> > Processor is AMD Athlon 64 x2 at 4200+ Dual Core (socket 939)
>> >> > RAM is 2GB Corsair XMS RAM
>> >> > HD is Seagate ST3320620AS
>> >> > Video card is Matrox Quad card, QID-E128-LPAF
>> >> > Power supply is Antec 550w TruePower 2.0
>> >> >
>> >> > This system has been rock solid from the time it was built until the
>> >> > Avast
>> >> > update Thursday night.
>> >> > Thanks again for your responise.
>> >> > --Bill
>> >> >
>> >> >
>> >> > "Tony Sperling mail.dk>" wrote:
>> >> >
>> >> >> Hi Bill,
>> >> >>
>> >> >> I have been running Avast myself for more than two years now, I
>> >> >> think.
>> >> >> My
>> >> >> machines are updating automatically, sometimes several times a day,
>> >> >> never
>> >> >> had a problem. Something can easily have been corrupted in that
>> >> >> update,
>> >> >> but
>> >> >> I am positive it is not Avast that did it. Anything you download
>> >> >> may
>> >> >> be
>> >> >> corrupted along the 'line' at any time and these updates are not
>> >> >> trivial,
>> >> >> in
>> >> >> a running system.
>> >> >>
>> >> >> On the other hand, it doesn't sound to me as something that HAS to
>> >> >> be
>> >> >> software related - how old is the system you've built? How long
>> >> >> since
>> >> >> Avast
>> >> >> was installed? Are you 'Dual-Booting'? How many HD's? IDE, SCSI,
>> >> >> RAID
>> >> >> or
>> >> >> SATA?
>> >> >>
>> >> >> If nobody else here objects, I would probably first try and remove
>> >> >> the
>> >> >> CMOS
>> >> >> battery for a few minutes (maybe ten?) - this will reset the BIOS
>> >> >> and
>> >> >> [should] be harmless.
>> >> >>
>> >> >>
>> >> >> Tony. . .
>> >> >>
>> >> >>
>> >> >> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
>> >> >> news:3DE47E52-F482-48B3-A242-C9DB3FA8E75E(a)microsoft.com...
>> >> >> > Hi,
>> >> >> > I have a computer that I built that won't boot after the latest
>> >> >> > Avast
>> >> >> > update. I updated Avast late Thurs (10/25/07) night and when it
>> >> >> > said
>> >> >> > that
>> >> >> > I
>> >> >> > needed to restart the computer, I pushed OK for it to restart and
>> >> >> > went
>> >> >> > to
>> >> >> > bed. I got up Friday morning and it was on a solid blue (not
>> >> >> > BSOD)
>> >> >> > screen.
>> >> >> > Now, it won't boot at all. I get thru the POST, and when it gets
>> >> >> > to
>> >> >> > launching
>> >> >> > the Windows x64 logo, it freezes on a black screen. No text.
>> >> >> >
>> >> >> > I also:
>> >> >> > - cannot get into any of the safe mode options, with one
>> >> >> > exception -
>> >> >> > when
>> >> >> > I
>> >> >> > launch into "Safe Mode" - I can see the lines "multidisk, rdisk,
>> >> >> > etc
>> >> >> > etc"
>> >> >> > coming across the screen and it stops on a line that ends in
>> >> >> > \windows\inf\biosinfo.inf - so it appears that this is where it
>> >> >> > freezes.
>> >> >> > - cannot boot to my original XP CDrom.
>> >> >> > - cannot get into the recovery console.
>> >> >> >
>> >> >> > Everything freezes to a black screen before I can get to any
>> >> >> > options
>> >> >> > that
>> >> >> > may allow me to work on this drive.
>> >> >> >
>> >> >> > I have slaved the drive to another x64 computer. I have full
>> >> >> > access
>> >> >> > to
>> >> >> > all
>> >> >> > of the data and files. Nothing is lost.
>> >> >> >
>> >> >> > So I'm thinking that when Avast did it's update on Thursday
>> >> >> > night,
>> >> >> > it
>> >> >> > corrupted one of the Windows boot files.
>> >> >> > Does anyone have any ideas?
>> >> >> > Do you need more information?
>> >> >> > Thanks in advance for any help you can offer.
>> >> >> > --Bill
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>

From: BillBled on 31 Oct 2007 21:46
AN UPDATE - as of 31Oct07 at 9:30pm EST:
I have now run these tests / procedures on the problem drive. Nothing has
helped. Data is still there, but cannot get the drive to boot x64:

chkdsk /f and /r
fixboot
fixmbr
SeaTools (both short and long tests passed)
BIOS on the computer is updated

Does anyone have any more suggestions?
Thanks much,
Bill




"Tony Sperling mail.dk>" wrote:

> Well, yes. I do know that the regular updates are database stuff and
> definitions, but the program itself updates this way too once in a while -
> and requires re-booting. I have tried doing the forced update, but I don't
> see anything that isn't in the auto-update facility. I simply think the
> menu-item is a service for users on dial-up?
>
> Anyway - the problem is the same and I still think we should adapt to the
> notion that downloads can be harmfull when they decide to be.
>
>
> Tony. . .
>
>
>
> "Carlos" <Carlos(a)discussions.microsoft.com> wrote in message
> news:9F0D5582-B65F-45B2-967C-D5F4DD95FF97(a)microsoft.com...
> > Tony:
> > The Avast update mentioned by the OP was a Program (i.e.: kernel) update
> > of
> > the Antivirus, rather than the regular daily definition update.
> > Those program updates are not automatic and you can force them by
> > right-clicking on the Avast icon (systray), then Update, then Program
> > Upate.
> > That will force you a reboot.
> > Current kernel version is 4.7.1074 (right-click, About Avast, etc.)
> > Carlos
> >
> > "Tony Sperling mail.dk>" wrote:
> >
> >> Hi Bill,
> >>
> >> I have been running Avast myself for more than two years now, I think. My
> >> machines are updating automatically, sometimes several times a day, never
> >> had a problem. Something can easily have been corrupted in that update,
> >> but
> >> I am positive it is not Avast that did it. Anything you download may be
> >> corrupted along the 'line' at any time and these updates are not trivial,
> >> in
> >> a running system.
> >>
> >> On the other hand, it doesn't sound to me as something that HAS to be
> >> software related - how old is the system you've built? How long since
> >> Avast
> >> was installed? Are you 'Dual-Booting'? How many HD's? IDE, SCSI, RAID or
> >> SATA?
> >>
> >> If nobody else here objects, I would probably first try and remove the
> >> CMOS
> >> battery for a few minutes (maybe ten?) - this will reset the BIOS and
> >> [should] be harmless.
> >>
> >>
> >> Tony. . .
> >>
> >>
> >> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
> >> news:3DE47E52-F482-48B3-A242-C9DB3FA8E75E(a)microsoft.com...
> >> > Hi,
> >> > I have a computer that I built that won't boot after the latest Avast
> >> > update. I updated Avast late Thurs (10/25/07) night and when it said
> >> > that
> >> > I
> >> > needed to restart the computer, I pushed OK for it to restart and went
> >> > to
> >> > bed. I got up Friday morning and it was on a solid blue (not BSOD)
> >> > screen.
> >> > Now, it won't boot at all. I get thru the POST, and when it gets to
> >> > launching
> >> > the Windows x64 logo, it freezes on a black screen. No text.
> >> >
> >> > I also:
> >> > - cannot get into any of the safe mode options, with one exception -
> >> > when
> >> > I
> >> > launch into "Safe Mode" - I can see the lines "multidisk, rdisk, etc
> >> > etc"
> >> > coming across the screen and it stops on a line that ends in
> >> > \windows\inf\biosinfo.inf - so it appears that this is where it
> >> > freezes.
> >> > - cannot boot to my original XP CDrom.
> >> > - cannot get into the recovery console.
> >> >
> >> > Everything freezes to a black screen before I can get to any options
> >> > that
> >> > may allow me to work on this drive.
> >> >
> >> > I have slaved the drive to another x64 computer. I have full access to
> >> > all
> >> > of the data and files. Nothing is lost.
> >> >
> >> > So I'm thinking that when Avast did it's update on Thursday night, it
> >> > corrupted one of the Windows boot files.
> >> > Does anyone have any ideas?
> >> > Do you need more information?
> >> > Thanks in advance for any help you can offer.
> >> > --Bill
> >>
> >>
> >>
>
>
>
From: Dominic Payer on 1 Nov 2007 03:29
Test the memory on the system with e.g. memtest http://www.memtest.org/

As the disk tests as good and, from your original post, it seems you cannot
boot to the x64 CD to do a repair install this is the last hope.



"BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
news:1D6B3AE3-83EB-40C3-98D7-3A3A31126713(a)microsoft.com...
> AN UPDATE - as of 31Oct07 at 9:30pm EST:
> I have now run these tests / procedures on the problem drive. Nothing has
> helped. Data is still there, but cannot get the drive to boot x64:
>
> chkdsk /f and /r
> fixboot
> fixmbr
> SeaTools (both short and long tests passed)
> BIOS on the computer is updated
>
> Does anyone have any more suggestions?
> Thanks much,
> Bill
>
>
>
>
> "Tony Sperling mail.dk>" wrote:
>
>> Well, yes. I do know that the regular updates are database stuff and
>> definitions, but the program itself updates this way too once in a
>> while -
>> and requires re-booting. I have tried doing the forced update, but I
>> don't
>> see anything that isn't in the auto-update facility. I simply think the
>> menu-item is a service for users on dial-up?
>>
>> Anyway - the problem is the same and I still think we should adapt to the
>> notion that downloads can be harmfull when they decide to be.
>>
>>
>> Tony. . .
>>
>>
>>
>> "Carlos" <Carlos(a)discussions.microsoft.com> wrote in message
>> news:9F0D5582-B65F-45B2-967C-D5F4DD95FF97(a)microsoft.com...
>> > Tony:
>> > The Avast update mentioned by the OP was a Program (i.e.: kernel)
>> > update
>> > of
>> > the Antivirus, rather than the regular daily definition update.
>> > Those program updates are not automatic and you can force them by
>> > right-clicking on the Avast icon (systray), then Update, then Program
>> > Upate.
>> > That will force you a reboot.
>> > Current kernel version is 4.7.1074 (right-click, About Avast, etc.)
>> > Carlos
>> >
>> > "Tony Sperling mail.dk>" wrote:
>> >
>> >> Hi Bill,
>> >>
>> >> I have been running Avast myself for more than two years now, I think.
>> >> My
>> >> machines are updating automatically, sometimes several times a day,
>> >> never
>> >> had a problem. Something can easily have been corrupted in that
>> >> update,
>> >> but
>> >> I am positive it is not Avast that did it. Anything you download may
>> >> be
>> >> corrupted along the 'line' at any time and these updates are not
>> >> trivial,
>> >> in
>> >> a running system.
>> >>
>> >> On the other hand, it doesn't sound to me as something that HAS to be
>> >> software related - how old is the system you've built? How long since
>> >> Avast
>> >> was installed? Are you 'Dual-Booting'? How many HD's? IDE, SCSI, RAID
>> >> or
>> >> SATA?
>> >>
>> >> If nobody else here objects, I would probably first try and remove the
>> >> CMOS
>> >> battery for a few minutes (maybe ten?) - this will reset the BIOS and
>> >> [should] be harmless.
>> >>
>> >>
>> >> Tony. . .
>> >>
>> >>
>> >> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
>> >> news:3DE47E52-F482-48B3-A242-C9DB3FA8E75E(a)microsoft.com...
>> >> > Hi,
>> >> > I have a computer that I built that won't boot after the latest
>> >> > Avast
>> >> > update. I updated Avast late Thurs (10/25/07) night and when it said
>> >> > that
>> >> > I
>> >> > needed to restart the computer, I pushed OK for it to restart and
>> >> > went
>> >> > to
>> >> > bed. I got up Friday morning and it was on a solid blue (not BSOD)
>> >> > screen.
>> >> > Now, it won't boot at all. I get thru the POST, and when it gets to
>> >> > launching
>> >> > the Windows x64 logo, it freezes on a black screen. No text.
>> >> >
>> >> > I also:
>> >> > - cannot get into any of the safe mode options, with one exception -
>> >> > when
>> >> > I
>> >> > launch into "Safe Mode" - I can see the lines "multidisk, rdisk, etc
>> >> > etc"
>> >> > coming across the screen and it stops on a line that ends in
>> >> > \windows\inf\biosinfo.inf - so it appears that this is where it
>> >> > freezes.
>> >> > - cannot boot to my original XP CDrom.
>> >> > - cannot get into the recovery console.
>> >> >
>> >> > Everything freezes to a black screen before I can get to any options
>> >> > that
>> >> > may allow me to work on this drive.
>> >> >
>> >> > I have slaved the drive to another x64 computer. I have full access
>> >> > to
>> >> > all
>> >> > of the data and files. Nothing is lost.
>> >> >
>> >> > So I'm thinking that when Avast did it's update on Thursday night,
>> >> > it
>> >> > corrupted one of the Windows boot files.
>> >> > Does anyone have any ideas?
>> >> > Do you need more information?
>> >> > Thanks in advance for any help you can offer.
>> >> > --Bill
>> >>
>> >>
>> >>
>>
>>
>>

From: "Tony Sperling" tony.sperling on 1 Nov 2007 05:10
Bill,

are you still on the second machine, and this is where you've been running
all tests and procedures?

Can you put a new HD on the original failure machine and install a new OS
there - just for the time being? (You'll most liky need it anyway!)

You must home in on something that will work, in order to (at best) isolate
the real problem. Since the problem HD can be accessed from outside your
data is not the prime concern - it is important that you don't restore it
all to something that still carries the error. . .whatever that might be.

I've tried googling for a solution but everything is just stabs in darkness,
as far as I can tell.

Did you ever try and remove that battery?


Tony. . .


"BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
news:1D6B3AE3-83EB-40C3-98D7-3A3A31126713(a)microsoft.com...
> AN UPDATE - as of 31Oct07 at 9:30pm EST:
> I have now run these tests / procedures on the problem drive. Nothing has
> helped. Data is still there, but cannot get the drive to boot x64:
>
> chkdsk /f and /r
> fixboot
> fixmbr
> SeaTools (both short and long tests passed)
> BIOS on the computer is updated
>
> Does anyone have any more suggestions?
> Thanks much,
> Bill
>
>
>
>
> "Tony Sperling mail.dk>" wrote:
>
>> Well, yes. I do know that the regular updates are database stuff and
>> definitions, but the program itself updates this way too once in a
>> while -
>> and requires re-booting. I have tried doing the forced update, but I
>> don't
>> see anything that isn't in the auto-update facility. I simply think the
>> menu-item is a service for users on dial-up?
>>
>> Anyway - the problem is the same and I still think we should adapt to the
>> notion that downloads can be harmfull when they decide to be.
>>
>>
>> Tony. . .
>>
>>
>>
>> "Carlos" <Carlos(a)discussions.microsoft.com> wrote in message
>> news:9F0D5582-B65F-45B2-967C-D5F4DD95FF97(a)microsoft.com...
>> > Tony:
>> > The Avast update mentioned by the OP was a Program (i.e.: kernel)
>> > update
>> > of
>> > the Antivirus, rather than the regular daily definition update.
>> > Those program updates are not automatic and you can force them by
>> > right-clicking on the Avast icon (systray), then Update, then Program
>> > Upate.
>> > That will force you a reboot.
>> > Current kernel version is 4.7.1074 (right-click, About Avast, etc.)
>> > Carlos
>> >
>> > "Tony Sperling mail.dk>" wrote:
>> >
>> >> Hi Bill,
>> >>
>> >> I have been running Avast myself for more than two years now, I think.
>> >> My
>> >> machines are updating automatically, sometimes several times a day,
>> >> never
>> >> had a problem. Something can easily have been corrupted in that
>> >> update,
>> >> but
>> >> I am positive it is not Avast that did it. Anything you download may
>> >> be
>> >> corrupted along the 'line' at any time and these updates are not
>> >> trivial,
>> >> in
>> >> a running system.
>> >>
>> >> On the other hand, it doesn't sound to me as something that HAS to be
>> >> software related - how old is the system you've built? How long since
>> >> Avast
>> >> was installed? Are you 'Dual-Booting'? How many HD's? IDE, SCSI, RAID
>> >> or
>> >> SATA?
>> >>
>> >> If nobody else here objects, I would probably first try and remove the
>> >> CMOS
>> >> battery for a few minutes (maybe ten?) - this will reset the BIOS and
>> >> [should] be harmless.
>> >>
>> >>
>> >> Tony. . .
>> >>
>> >>
>> >> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
>> >> news:3DE47E52-F482-48B3-A242-C9DB3FA8E75E(a)microsoft.com...
>> >> > Hi,
>> >> > I have a computer that I built that won't boot after the latest
>> >> > Avast
>> >> > update. I updated Avast late Thurs (10/25/07) night and when it said
>> >> > that
>> >> > I
>> >> > needed to restart the computer, I pushed OK for it to restart and
>> >> > went
>> >> > to
>> >> > bed. I got up Friday morning and it was on a solid blue (not BSOD)
>> >> > screen.
>> >> > Now, it won't boot at all. I get thru the POST, and when it gets to
>> >> > launching
>> >> > the Windows x64 logo, it freezes on a black screen. No text.
>> >> >
>> >> > I also:
>> >> > - cannot get into any of the safe mode options, with one exception -
>> >> > when
>> >> > I
>> >> > launch into "Safe Mode" - I can see the lines "multidisk, rdisk, etc
>> >> > etc"
>> >> > coming across the screen and it stops on a line that ends in
>> >> > \windows\inf\biosinfo.inf - so it appears that this is where it
>> >> > freezes.
>> >> > - cannot boot to my original XP CDrom.
>> >> > - cannot get into the recovery console.
>> >> >
>> >> > Everything freezes to a black screen before I can get to any options
>> >> > that
>> >> > may allow me to work on this drive.
>> >> >
>> >> > I have slaved the drive to another x64 computer. I have full access
>> >> > to
>> >> > all
>> >> > of the data and files. Nothing is lost.
>> >> >
>> >> > So I'm thinking that when Avast did it's update on Thursday night,
>> >> > it
>> >> > corrupted one of the Windows boot files.
>> >> > Does anyone have any ideas?
>> >> > Do you need more information?
>> >> > Thanks in advance for any help you can offer.
>> >> > --Bill
>> >>
>> >>
>> >>
>>
>>
>>



From: John Barnes on 1 Nov 2007 08:07
One last try would be to swap a different and known good cd player into the
problem machine. Unplug all your hd's. If you still don't get the install
cd to boot, you have a problem with the motherboard. You did say you had
flashed the BIOS, so the only remaining variable is the MOBO itself

"BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
news:1D6B3AE3-83EB-40C3-98D7-3A3A31126713(a)microsoft.com...
> AN UPDATE - as of 31Oct07 at 9:30pm EST:
> I have now run these tests / procedures on the problem drive. Nothing has
> helped. Data is still there, but cannot get the drive to boot x64:
>
> chkdsk /f and /r
> fixboot
> fixmbr
> SeaTools (both short and long tests passed)
> BIOS on the computer is updated
>
> Does anyone have any more suggestions?
> Thanks much,
> Bill
>
>
>
>
> "Tony Sperling mail.dk>" wrote:
>
>> Well, yes. I do know that the regular updates are database stuff and
>> definitions, but the program itself updates this way too once in a
>> while -
>> and requires re-booting. I have tried doing the forced update, but I
>> don't
>> see anything that isn't in the auto-update facility. I simply think the
>> menu-item is a service for users on dial-up?
>>
>> Anyway - the problem is the same and I still think we should adapt to the
>> notion that downloads can be harmfull when they decide to be.
>>
>>
>> Tony. . .
>>
>>
>>
>> "Carlos" <Carlos(a)discussions.microsoft.com> wrote in message
>> news:9F0D5582-B65F-45B2-967C-D5F4DD95FF97(a)microsoft.com...
>> > Tony:
>> > The Avast update mentioned by the OP was a Program (i.e.: kernel)
>> > update
>> > of
>> > the Antivirus, rather than the regular daily definition update.
>> > Those program updates are not automatic and you can force them by
>> > right-clicking on the Avast icon (systray), then Update, then Program
>> > Upate.
>> > That will force you a reboot.
>> > Current kernel version is 4.7.1074 (right-click, About Avast, etc.)
>> > Carlos
>> >
>> > "Tony Sperling mail.dk>" wrote:
>> >
>> >> Hi Bill,
>> >>
>> >> I have been running Avast myself for more than two years now, I think.
>> >> My
>> >> machines are updating automatically, sometimes several times a day,
>> >> never
>> >> had a problem. Something can easily have been corrupted in that
>> >> update,
>> >> but
>> >> I am positive it is not Avast that did it. Anything you download may
>> >> be
>> >> corrupted along the 'line' at any time and these updates are not
>> >> trivial,
>> >> in
>> >> a running system.
>> >>
>> >> On the other hand, it doesn't sound to me as something that HAS to be
>> >> software related - how old is the system you've built? How long since
>> >> Avast
>> >> was installed? Are you 'Dual-Booting'? How many HD's? IDE, SCSI, RAID
>> >> or
>> >> SATA?
>> >>
>> >> If nobody else here objects, I would probably first try and remove the
>> >> CMOS
>> >> battery for a few minutes (maybe ten?) - this will reset the BIOS and
>> >> [should] be harmless.
>> >>
>> >>
>> >> Tony. . .
>> >>
>> >>
>> >> "BillBled" <BillBled(a)discussions.microsoft.com> wrote in message
>> >> news:3DE47E52-F482-48B3-A242-C9DB3FA8E75E(a)microsoft.com...
>> >> > Hi,
>> >> > I have a computer that I built that won't boot after the latest
>> >> > Avast
>> >> > update. I updated Avast late Thurs (10/25/07) night and when it said
>> >> > that
>> >> > I
>> >> > needed to restart the computer, I pushed OK for it to restart and
>> >> > went
>> >> > to
>> >> > bed. I got up Friday morning and it was on a solid blue (not BSOD)
>> >> > screen.
>> >> > Now, it won't boot at all. I get thru the POST, and when it gets to
>> >> > launching
>> >> > the Windows x64 logo, it freezes on a black screen. No text.
>> >> >
>> >> > I also:
>> >> > - cannot get into any of the safe mode options, with one exception -
>> >> > when
>> >> > I
>> >> > launch into "Safe Mode" - I can see the lines "multidisk, rdisk, etc
>> >> > etc"
>> >> > coming across the screen and it stops on a line that ends in
>> >> > \windows\inf\biosinfo.inf - so it appears that this is where it
>> >> > freezes.
>> >> > - cannot boot to my original XP CDrom.
>> >> > - cannot get into the recovery console.
>> >> >
>> >> > Everything freezes to a black screen before I can get to any options
>> >> > that
>> >> > may allow me to work on this drive.
>> >> >
>> >> > I have slaved the drive to another x64 computer. I have full access
>> >> > to
>> >> > all
>> >> > of the data and files. Nothing is lost.
>> >> >
>> >> > So I'm thinking that when Avast did it's update on Thursday night,
>> >> > it
>> >> > corrupted one of the Windows boot files.
>> >> > Does anyone have any ideas?
>> >> > Do you need more information?
>> >> > Thanks in advance for any help you can offer.
>> >> > --Bill
>> >>
>> >>
>> >>
>>
>>
>>

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Vista Shortcut Manager updated to v2.0
Next: chkdsk logs in Vista