XP Pro Recovery Errors

[bw]

Ok,

long error - all of a sudden PC got BSOD error 0xc0000034 (0x00000000
0x00000000) or something. Thought it was no big deal until I tried to reboot
- nothing at all. I resorted to recovery installation via XP setup Cd.

When it recognized that there was already an install on the machine, it
asked me to try and recover. I tried, but received the following errors:
Windows cannot install file:
Winipsec.dll
Stdole2.tlb
Mswdat10.dll
Msyuv.dll
Shmedia.dll
Sys_srv.chm
Vgasysr.fon
Winlogon.exe
Webclnt.dll
Wmp.ocx
Mswebdvd.dll
Msxm12.dll
Sti.dll
Sti_ci.dll
Wmpcd.dll
Tabletoc.dll
Medctroc.dll
Spra0412.dll
Msmsgs.inf

Cannot boot into Windows; cannot recover. What could have caused this, and
why "all of a sudden"? There was no virus, at least none that AVG could
find...however, could not run appwiz.cpl or task manager either...

Please help!

BW

[bw]

Nevermind...decided to use Ubuntu Live CD to recover files from HD and
reinstalled XP...what a crock.

"BW" wrote:

> Ok,
>
> long error - all of a sudden PC got BSOD error 0xc0000034 (0x00000000
> 0x00000000) or something. Thought it was no big deal until I tried to reboot
> - nothing at all. I resorted to recovery installation via XP setup Cd.
>
> When it recognized that there was already an install on the machine, it
> asked me to try and recover. I tried, but received the following errors:
> Windows cannot install file:
> Winipsec.dll
> Stdole2.tlb
> Mswdat10.dll
> Msyuv.dll
> Shmedia.dll
> Sys_srv.chm
> Vgasysr.fon
> Winlogon.exe
> Webclnt.dll
> Wmp.ocx
> Mswebdvd.dll
> Msxm12.dll
> Sti.dll
> Sti_ci.dll
> Wmpcd.dll
> Tabletoc.dll
> Medctroc.dll
> Spra0412.dll
> Msmsgs.inf
>
> Cannot boot into Windows; cannot recover. What could have caused this, and
> why "all of a sudden"? There was no virus, at least none that AVG could
> find...however, could not run appwiz.cpl or task manager either...
>
> Please help!
>
> BW

[Paul]

BW wrote:
> Nevermind...decided to use Ubuntu Live CD to recover files from HD and
> reinstalled XP...what a crock.

Have you tested the disk at all ?

Perhaps you should do a surface scan, to see if there are any bad blocks.

Or, you might consider running the disk manufacturer's non-destructive
diagnostic. For example, I have one from Seagate, which fits on a floppy,
and is self booting. It tests my Seagate drive, checks the SMART status
and the like. You can download these tools for free, for the manufacturers
that care enough to provide them.

I can find a 0xc0000034 mentioned here, but it is part of a
STOP: 0x0000007B Inaccessible Boot Device error. Was
that the error ?

http://support.microsoft.com/?kbid=811408

One thing to note about SATA drives, something I've noticed. If
the drive controller board goes "insane" while the system is
running, it will not be reset when the reset button is pressed
on the front of the computer. You have to power off the system,
if you expect the SATA drive to fully recover its senses. I
noticed this on one of my SATA drives. It stopped responding, and
I couldn't reach it, until I power cycled. IDE drives seem to be
better behaved - at least I've never had those symptoms on IDE.

Paul

>
> "BW" wrote:
>
>> Ok,
>>
>> long error - all of a sudden PC got BSOD error 0xc0000034 (0x00000000
>> 0x00000000) or something. Thought it was no big deal until I tried to reboot
>> - nothing at all. I resorted to recovery installation via XP setup Cd.
>>
>> When it recognized that there was already an install on the machine, it
>> asked me to try and recover. I tried, but received the following errors:
>> Windows cannot install file:
>> Winipsec.dll
>> Stdole2.tlb
>> Mswdat10.dll
>> Msyuv.dll
>> Shmedia.dll
>> Sys_srv.chm
>> Vgasysr.fon
>> Winlogon.exe
>> Webclnt.dll
>> Wmp.ocx
>> Mswebdvd.dll
>> Msxm12.dll
>> Sti.dll
>> Sti_ci.dll
>> Wmpcd.dll
>> Tabletoc.dll
>> Medctroc.dll
>> Spra0412.dll
>> Msmsgs.inf
>>
>> Cannot boot into Windows; cannot recover. What could have caused this, and
>> why "all of a sudden"? There was no virus, at least none that AVG could
>> find...however, could not run appwiz.cpl or task manager either...
>>
>> Please help!
>>
>> BW

[bw]

"Paul" wrote:
Paul,

I have not tried testing the drive. I let the reformat (Full) run
overnight, but the weird thing was that I had an error about some driver not
being recognized when I woke this morning. I then loaded Sea Tool, which is
probably the utility you are talking about, to do a complete wipe. I was
able to recover my data, so I am not all that concerned with the fresh
install, but was rather frustrated last night!!!

I am 100% positive that I have a backup from a while back, but I think it
may have resided on the same HDD as the OS (one would think not, but I have
done more foolish things!). I will also have to look at this when I get
home.

Anyway, Win7 pro has been pre-ordered for both my home PC and my desktop, so
I will have fun in about two months!

Thank you for your help,

BW
> BW wrote:
> > Nevermind...decided to use Ubuntu Live CD to recover files from HD and
> > reinstalled XP...what a crock.
>
> Have you tested the disk at all ?
>
> Perhaps you should do a surface scan, to see if there are any bad blocks.
>
> Or, you might consider running the disk manufacturer's non-destructive
> diagnostic. For example, I have one from Seagate, which fits on a floppy,
> and is self booting. It tests my Seagate drive, checks the SMART status
> and the like. You can download these tools for free, for the manufacturers
> that care enough to provide them.
>
> I can find a 0xc0000034 mentioned here, but it is part of a
> STOP: 0x0000007B Inaccessible Boot Device error. Was
> that the error ?
>
> http://support.microsoft.com/?kbid=811408
>
> One thing to note about SATA drives, something I've noticed. If
> the drive controller board goes "insane" while the system is
> running, it will not be reset when the reset button is pressed
> on the front of the computer. You have to power off the system,
> if you expect the SATA drive to fully recover its senses. I
> noticed this on one of my SATA drives. It stopped responding, and
> I couldn't reach it, until I power cycled. IDE drives seem to be
> better behaved - at least I've never had those symptoms on IDE.
>
> Paul
>
> >
> > "BW" wrote:
> >
> >> Ok,
> >>
> >> long error - all of a sudden PC got BSOD error 0xc0000034 (0x00000000
> >> 0x00000000) or something. Thought it was no big deal until I tried to reboot
> >> - nothing at all. I resorted to recovery installation via XP setup Cd.
> >>
> >> When it recognized that there was already an install on the machine, it
> >> asked me to try and recover. I tried, but received the following errors:
> >> Windows cannot install file:
> >> Winipsec.dll
> >> Stdole2.tlb
> >> Mswdat10.dll
> >> Msyuv.dll
> >> Shmedia.dll
> >> Sys_srv.chm
> >> Vgasysr.fon
> >> Winlogon.exe
> >> Webclnt.dll
> >> Wmp.ocx
> >> Mswebdvd.dll
> >> Msxm12.dll
> >> Sti.dll
> >> Sti_ci.dll
> >> Wmpcd.dll
> >> Tabletoc.dll
> >> Medctroc.dll
> >> Spra0412.dll
> >> Msmsgs.inf
> >>
> >> Cannot boot into Windows; cannot recover. What could have caused this, and
> >> why "all of a sudden"? There was no virus, at least none that AVG could
> >> find...however, could not run appwiz.cpl or task manager either...
> >>
> >> Please help!
> >>
> >> BW
>

[bw]

Paul,

it turns out that the boot sector, sector 0, of my HDD failed to "read,
write, or remove write-protection." I am assuming that the drive, well, to
be PC, failed. I have reinstalled XP Pro SP3 with a slipstreamed version I
created some time ago - boy, was that slick! No waiting for SP2 and SP3 to
download.

Is there anything I can do to fix the HDD? I have recovered my data as
described in the previous post, but I would like to have the HDD around for
backup purposes.

Thank you again,

BW


> BW wrote:
> > Nevermind...decided to use Ubuntu Live CD to recover files from HD and
> > reinstalled XP...what a crock.

> "Paul" wrote:

> Have you tested the disk at all ?
>
> Perhaps you should do a surface scan, to see if there are any bad blocks.
>
> Or, you might consider running the disk manufacturer's non-destructive
> diagnostic. For example, I have one from Seagate, which fits on a floppy,
> and is self booting. It tests my Seagate drive, checks the SMART status
> and the like. You can download these tools for free, for the manufacturers
> that care enough to provide them.
>
> I can find a 0xc0000034 mentioned here, but it is part of a
> STOP: 0x0000007B Inaccessible Boot Device error. Was
> that the error ?
>
> http://support.microsoft.com/?kbid=811408
>
> One thing to note about SATA drives, something I've noticed. If
> the drive controller board goes "insane" while the system is
> running, it will not be reset when the reset button is pressed
> on the front of the computer. You have to power off the system,
> if you expect the SATA drive to fully recover its senses. I
> noticed this on one of my SATA drives. It stopped responding, and
> I couldn't reach it, until I power cycled. IDE drives seem to be
> better behaved - at least I've never had those symptoms on IDE.
>
> Paul
>
> >
> > "BW" wrote:
> >
> >> Ok,
> >>
> >> long error - all of a sudden PC got BSOD error 0xc0000034 (0x00000000
> >> 0x00000000) or something. Thought it was no big deal until I tried to reboot
> >> - nothing at all. I resorted to recovery installation via XP setup Cd.
> >>
> >> When it recognized that there was already an install on the machine, it
> >> asked me to try and recover. I tried, but received the following errors:
> >> Windows cannot install file:
> >> Winipsec.dll
> >> Stdole2.tlb
> >> Mswdat10.dll
> >> Msyuv.dll
> >> Shmedia.dll
> >> Sys_srv.chm
> >> Vgasysr.fon
> >> Winlogon.exe
> >> Webclnt.dll
> >> Wmp.ocx
> >> Mswebdvd.dll
> >> Msxm12.dll
> >> Sti.dll
> >> Sti_ci.dll
> >> Wmpcd.dll
> >> Tabletoc.dll
> >> Medctroc.dll
> >> Spra0412.dll
> >> Msmsgs.inf
> >>
> >> Cannot boot into Windows; cannot recover. What could have caused this, and
> >> why "all of a sudden"? There was no virus, at least none that AVG could
> >> find...however, could not run appwiz.cpl or task manager either...
> >>
> >> Please help!
> >>
> >> BW
>

[Paul]

BW wrote:
> Paul,
>
> it turns out that the boot sector, sector 0, of my HDD failed to "read,
> write, or remove write-protection." I am assuming that the drive, well, to
> be PC, failed. I have reinstalled XP Pro SP3 with a slipstreamed version I
> created some time ago - boy, was that slick! No waiting for SP2 and SP3 to
> download.
>
> Is there anything I can do to fix the HDD? I have recovered my data as
> described in the previous post, but I would like to have the HDD around for
> backup purposes.
>
> Thank you again,
>
> BW
>

So is the message you quote above, coming from the diagnostic test ?

Hard drives, when they have a problem with a sector, mark it as "pending".
An attempt to write the sector later, is when the drive will try to
resolve the problem. If there are spare sectors left, the drive will
use a spare sector, to take the place of the broken sector. That would be,
if sector 0 could no longer be read without error, and had been
marked as "pending" substitution.

So if you do something to write to the disk, and write sector zero,
at that point you'd know whether it could be solved or not. For example,
perhaps using Recovery Console and FixMBR, might have written a new
sector 0. Since the hard drive isn't healthy, you might use the Recovery
Console from the WinXP install CD. FixMBR takes a disk argument,
implying you can write sector 0 on more than one disk.

http://en.wikipedia.org/wiki/Fixmbr

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcons_fixmbr.mspx?mfr=true

I use a Linux LiveCD for various kinds of disk maintenance, and if I wanted
to experiment, there are ways there as well for screwing around with the
disk. For example, rather than learning how to use the Recovery Console,
I've used "dd" to copy the sector 0 MBR from one drive, to another. I've
had three occasions now, where it needed to be repaired.

Modern hard drives don't "low level format" like they used to. If you
want to "freshen up" a drive now, what you need is a process that writes
to each sector. If any sectors are pending, the substitution process
will take place during the write. I would use whatever I could get as
a disk eraser program, as a means to write to all the sectors.

*******

These are some examples of ways to erase all the sectors on a disk.

1) This is a port of Unix "dd", to the Windows environment.

http://www.chrysocome.net/dd (DOS program, use command window)

dd if=/dev/zero of=\\?\Device\Harddisk0\Partition0

That would use sectors filled with zeros, to erase the entire Harddisk0.
You must be *very* careful to ensure you have the correct disk address.
For example, you could overwrite the current WinXP boot partition, if
you get the name of the disk wrong. The "dd --list" command, gives
the names of the disks and partitions. If each of your disks has a
different number of partitions on it, that helps tell you which disk
is which. "Partition0" means the whole disk, while "Partition1" is
only the first partition on the disk (not the whole disk). So in my
example, the entire disk will be erased. Since no "block size" or
"count" parameter is being used, the command runs until the output
file specification is exhausted for space (i.e. hit the end of the
disk).

2) The CMRR SecureErase program, uses an erasing feature inside the disk drive.
You need to read all the documentation on this page, before using it.
(The reason you need to read the documentation, is because the erase
feature is protected by things like passwords, which complicate the
ability of the user to successfully access the command.)

And as in (1), be absolutely sure you have the right disk. Since this
one boots from its own CD (they offer an ISO9660 file, to prepare a CD),
you can physically disconnect all but the disk to be erased.

http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml

3) DBAN from dban.org, can erase all hard drives on the computer. For
safety, have only the disk you want to erase, connected up. Use
the Quick Erase option. It isn't really that Quick, but if you start
it running before you go to bed, it should be ready the next day.
DBAN can run from a floppy, so you don't need your working WinXP
disk connected, to make it work.

Once the disk is erased, connect the erased disk and your regular
WinXP boot disk to the computer. Boot WinXP. Then, you can use
HDTune 2.55 free version, from hdtune.com , and do a surface scan
of the disk, to check for bad sectors. If the entire surface of the
disk is "green", you can use it again. What that doesn't tell you,
is how many spare sectors are left. If some of the blocks aren't
green, then chances are you have broken sectors which can no longer
be substituted. Toss the disk in that case, as it isn't worth
the aggravation. You can get new disks at prices from $40 to
$100, and at some point, it no longer makes sense to use
a disk that is on its last legs.

If the disk is connected directly to the motherboard, the SMART
statistics also give you some idea of the health of the
disk. HDTune has a tab which will display the SMART stats.
If SMART is not accessible (due to the interface type being
used), the SMART tab will not display any data.

If erasing the disk and scanning it looks clean, you can
use Disk Management to put a partition on it, and begin
to use it again. Keep an eye on the SMART, and listen
for odd noises, if you expect to catch the disk before
it dies completely.

HTH,
Paul