Windows x64 Edition won't start after Avast Update
in [64 Bits Windows]
|
From: BillBled on 29 Oct 2007 06:28 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: Dominic Payer on 29 Oct 2007 08:09 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: John Barnes on 29 Oct 2007 08:30 The last listed item is the last one that successfully loaded, not the problem one. You could try installing a good system into your problem machine. That you say you cannot get to recovery console or boot the XP install cd has nothing to do with anything past the BIOS. The install cd goes past the license agreement (and recovery console) with no HD, as when you haven't installed necessary SATA drivers. You should therefore try to do your repairs from one of the other machines where you can access the boot files, fixmbr and fixboot. "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 29 Oct 2007 08:39 Hi Dominic, OK - I hear you. But....I can run the "damaged" disk on the good computer and I can see all of the data on the disk. It just won't boot the operating system on its own. But I will download and run the Seagate diagnostics when I get home tonight around 10pm (it's 8:37am EST here now). 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 29 Oct 2007 08:44 Hi John, Thanks for replying. I do have complete access to the drive when it is running on my other computer, which is also a x64 box. My limitation is that I'm trying to figure out (or be told) what utilitiies I can use within the x64 environment, since that is 100% what I am dealing with. I didn't think that all of the normal XP (32bit) tools would work in the x64 realm. I'm going to run the HD diagnostics from Seagate, but do you have any specific diagnostics that come to mind with respect to the x64 O/S? I ran chkdsk /f last night and it said it fixed some things - but still no boot when I tried the drive by itself. I realize I can just format the drive, and reload x64 and go from there, but that's not really the point. I'm trying to understand what went wrong and repair it. Thanks for everyone's help and ideas! -Bill "John Barnes" wrote: > The last listed item is the last one that successfully loaded, not the > problem one. You could try installing a good system into your problem > machine. That you say you cannot get to recovery console or boot the XP > install cd has nothing to do with anything past the BIOS. The install cd > goes past the license agreement (and recovery console) with no HD, as when > you haven't installed necessary SATA drivers. You should therefore try to do > your repairs from one of the other machines where you can access the boot > files, fixmbr and fixboot. > > > "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 > >> >> > >> >> > >> >> > >> > >> > >> > >
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Vista Shortcut Manager updated to v2.0 Next: chkdsk logs in Vista |