corrupted files

  • Thread starter Thread starter Jon
  • Start date Start date
J

Jon

Guest
I downloaded the 120 day trial version:

WS03SP1_RTM_1830_PX6_EN.iso

Having created a 30G partition, burnt a bootable image on a CD (using Ultra
ISO 8) and proceeded to install, booting from the CD:

attempt 1. During the installation wmsvbvm60.dll could not be copied,
although it was on the cd in the \i386 folder.

attempt 2. During bootup the following error (with a blue background) is
displayed:

STOP C0000221 Unknown Hard Error
\SystemRoot\System32\ntdll.dll

After another reboot an error message was prompted while the boot cd was
loading that NTLDR is corrupt.

Any ideas, please?
 
Re: corrupted files

Did you verify the download as well as the burn? Have you cleaned the drive?
Did you install to a dedicated partition?

30Gig, should be just about enough, I think - but it certainly isn't a whole
lot! Check the assigned boot-order in the BIOS, and check that you are not
installing to a SATA drive while having an IDE HD attached!!!


Tony. . .




"Jon" <Jon@discussions.microsoft.com> wrote in message
news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>I downloaded the 120 day trial version:
>
> WS03SP1_RTM_1830_PX6_EN.iso
>
> Having created a 30G partition, burnt a bootable image on a CD (using
> Ultra
> ISO 8) and proceeded to install, booting from the CD:
>
> attempt 1. During the installation wmsvbvm60.dll could not be copied,
> although it was on the cd in the \i386 folder.
>
> attempt 2. During bootup the following error (with a blue background) is
> displayed:
>
> STOP C0000221 Unknown Hard Error
> \SystemRoot\System32\ntdll.dll
>
> After another reboot an error message was prompted while the boot cd was
> loading that NTLDR is corrupt.
>
> Any ideas, please?
 
Re: corrupted files

I had almost identical problems, specifically the "Unknown Hard Error", and
the ntldr is corrupt problem. I suspected a bad burn of the CD, as burning
another CD seemed to fix the problem. I also had similar problems installing
XP32 on another partition, so I could not blame any of this on XP64 itself.

I have also noticed that if I boot with any usb flash drives (zip drives,
thumb drives, etc) plugged, I sometimes get various boot errors, including
corrupt ntldr, but interesting enough they are not consistent. Removing the
usb drive or just unplugging my usb hubs always fixes it and lets XP boot.



"Jon" <Jon@discussions.microsoft.com> wrote in message
news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>I downloaded the 120 day trial version:
>
> WS03SP1_RTM_1830_PX6_EN.iso
>
> Having created a 30G partition, burnt a bootable image on a CD (using
> Ultra
> ISO 8) and proceeded to install, booting from the CD:
>
> attempt 1. During the installation wmsvbvm60.dll could not be copied,
> although it was on the cd in the \i386 folder.
>
> attempt 2. During bootup the following error (with a blue background) is
> displayed:
>
> STOP C0000221 Unknown Hard Error
> \SystemRoot\System32\ntdll.dll
>
> After another reboot an error message was prompted while the boot cd was
> loading that NTLDR is corrupt.
>
> Any ideas, please?
 
Re: corrupted files

Corrupted burn or corrupted download. It's easier to re-burn, so start
there.

Reduce the burn speed to no more than 1/2 maximum speed. And turn on Verify.
(if your burn product doesn't support a verify pass, I recommend getting one
that does. )

If that doesn't resolve it, time for a new download.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Jon" <Jon@discussions.microsoft.com> wrote in message
news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>I downloaded the 120 day trial version:
>
> WS03SP1_RTM_1830_PX6_EN.iso
>
> Having created a 30G partition, burnt a bootable image on a CD (using
> Ultra
> ISO 8) and proceeded to install, booting from the CD:
>
> attempt 1. During the installation wmsvbvm60.dll could not be copied,
> although it was on the cd in the \i386 folder.
>
> attempt 2. During bootup the following error (with a blue background) is
> displayed:
>
> STOP C0000221 Unknown Hard Error
> \SystemRoot\System32\ntdll.dll
>
> After another reboot an error message was prompted while the boot cd was
> loading that NTLDR is corrupt.
>
> Any ideas, please?
 
Re: corrupted files

Perhaps the result of a pending write that didn't get done.

"Zootal" <Don't send me any freaking spam at zootal dot com remove the don't
send me any freaking spam> wrote in message
news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>I had almost identical problems, specifically the "Unknown Hard Error", and
>the ntldr is corrupt problem. I suspected a bad burn of the CD, as burning
>another CD seemed to fix the problem. I also had similar problems
>installing XP32 on another partition, so I could not blame any of this on
>XP64 itself.
>
> I have also noticed that if I boot with any usb flash drives (zip drives,
> thumb drives, etc) plugged, I sometimes get various boot errors, including
> corrupt ntldr, but interesting enough they are not consistent. Removing
> the usb drive or just unplugging my usb hubs always fixes it and lets XP
> boot.
>
>
>
> "Jon" <Jon@discussions.microsoft.com> wrote in message
> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>I downloaded the 120 day trial version:
>>
>> WS03SP1_RTM_1830_PX6_EN.iso
>>
>> Having created a 30G partition, burnt a bootable image on a CD (using
>> Ultra
>> ISO 8) and proceeded to install, booting from the CD:
>>
>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>> although it was on the cd in the \i386 folder.
>>
>> attempt 2. During bootup the following error (with a blue background) is
>> displayed:
>>
>> STOP C0000221 Unknown Hard Error
>> \SystemRoot\System32\ntdll.dll
>>
>> After another reboot an error message was prompted while the boot cd was
>> loading that NTLDR is corrupt.
>>
>> Any ideas, please?
>
>
 
Re: corrupted files

Have you checked if your driveletters move around when you insert external
drives? And specifically, when there is trouble booting? Remember that in
the early phase of booting, SATA is ATA but enumerated after the IDE
sockets, inserting additional IDE drives should be expected to be enumerated
before any bootable SATA drive - perhaps!


Tony. . .


"Zootal" <Don't send me any freaking spam at zootal dot com remove the don't
send me any freaking spam> wrote in message
news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>I had almost identical problems, specifically the "Unknown Hard Error", and
>the ntldr is corrupt problem. I suspected a bad burn of the CD, as burning
>another CD seemed to fix the problem. I also had similar problems
>installing XP32 on another partition, so I could not blame any of this on
>XP64 itself.
>
> I have also noticed that if I boot with any usb flash drives (zip drives,
> thumb drives, etc) plugged, I sometimes get various boot errors, including
> corrupt ntldr, but interesting enough they are not consistent. Removing
> the usb drive or just unplugging my usb hubs always fixes it and lets XP
> boot.
>
>
>
> "Jon" <Jon@discussions.microsoft.com> wrote in message
> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>I downloaded the 120 day trial version:
>>
>> WS03SP1_RTM_1830_PX6_EN.iso
>>
>> Having created a 30G partition, burnt a bootable image on a CD (using
>> Ultra
>> ISO 8) and proceeded to install, booting from the CD:
>>
>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>> although it was on the cd in the \i386 folder.
>>
>> attempt 2. During bootup the following error (with a blue background) is
>> displayed:
>>
>> STOP C0000221 Unknown Hard Error
>> \SystemRoot\System32\ntdll.dll
>>
>> After another reboot an error message was prompted while the boot cd was
>> loading that NTLDR is corrupt.
>>
>> Any ideas, please?
>
>
 
Re: corrupted files

or possibly the BIOS is set to boot from a removable device first.

"Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
news:B194371C-5F9C-4086-BDA0-7A0D2DABC253@microsoft.com...
> Perhaps the result of a pending write that didn't get done.
>
> "Zootal" <Don't send me any freaking spam at zootal dot com remove the
> don't send me any freaking spam> wrote in message
> news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>>I had almost identical problems, specifically the "Unknown Hard Error",
>>and the ntldr is corrupt problem. I suspected a bad burn of the CD, as
>>burning another CD seemed to fix the problem. I also had similar problems
>>installing XP32 on another partition, so I could not blame any of this on
>>XP64 itself.
>>
>> I have also noticed that if I boot with any usb flash drives (zip drives,
>> thumb drives, etc) plugged, I sometimes get various boot errors,
>> including corrupt ntldr, but interesting enough they are not consistent.
>> Removing the usb drive or just unplugging my usb hubs always fixes it and
>> lets XP boot.
>>
>>
>>
>> "Jon" <Jon@discussions.microsoft.com> wrote in message
>> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>>I downloaded the 120 day trial version:
>>>
>>> WS03SP1_RTM_1830_PX6_EN.iso
>>>
>>> Having created a 30G partition, burnt a bootable image on a CD (using
>>> Ultra
>>> ISO 8) and proceeded to install, booting from the CD:
>>>
>>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>>> although it was on the cd in the \i386 folder.
>>>
>>> attempt 2. During bootup the following error (with a blue background) is
>>> displayed:
>>>
>>> STOP C0000221 Unknown Hard Error
>>> \SystemRoot\System32\ntdll.dll
>>>
>>> After another reboot an error message was prompted while the boot cd was
>>> loading that NTLDR is corrupt.
>>>
>>> Any ideas, please?
>>
>>
>
 
Re: corrupted files

No, I checked that. What it sometimes done is start to load XP64, and then
stop before the desktop gets displayed. I get a black screen with a mouse
pointer, and a locked up computer. Removing all the usb drives always fixes
this. I boot, plug them back in, and we're good to go until next week when
it does it again. I also get other intermittent hard locks immediatly after
booting. I usually let it sit for 5 minutes before I do anything. If it runs
that long, it never locks up. The first few minutes after boot - not very
reliable. I thought of a heating issue, where something warms up, and as it
expands breaks a connection somewhere causing failure. <shrug>.

"John Barnes" <jbarnes@email.net> wrote in message
news:%23FRmPNVVIHA.4140@TK2MSFTNGP04.phx.gbl...
> or possibly the BIOS is set to boot from a removable device first.
>
> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
> news:B194371C-5F9C-4086-BDA0-7A0D2DABC253@microsoft.com...
>> Perhaps the result of a pending write that didn't get done.
>>
>> "Zootal" <Don't send me any freaking spam at zootal dot com remove the
>> don't send me any freaking spam> wrote in message
>> news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>I had almost identical problems, specifically the "Unknown Hard Error",
>>>and the ntldr is corrupt problem. I suspected a bad burn of the CD, as
>>>burning another CD seemed to fix the problem. I also had similar problems
>>>installing XP32 on another partition, so I could not blame any of this on
>>>XP64 itself.
>>>
>>> I have also noticed that if I boot with any usb flash drives (zip
>>> drives, thumb drives, etc) plugged, I sometimes get various boot errors,
>>> including corrupt ntldr, but interesting enough they are not consistent.
>>> Removing the usb drive or just unplugging my usb hubs always fixes it
>>> and lets XP boot.
>>>
>>>
>>>
>>> "Jon" <Jon@discussions.microsoft.com> wrote in message
>>> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>>>I downloaded the 120 day trial version:
>>>>
>>>> WS03SP1_RTM_1830_PX6_EN.iso
>>>>
>>>> Having created a 30G partition, burnt a bootable image on a CD (using
>>>> Ultra
>>>> ISO 8) and proceeded to install, booting from the CD:
>>>>
>>>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>>>> although it was on the cd in the \i386 folder.
>>>>
>>>> attempt 2. During bootup the following error (with a blue background)
>>>> is
>>>> displayed:
>>>>
>>>> STOP C0000221 Unknown Hard Error
>>>> \SystemRoot\System32\ntdll.dll
>>>>
>>>> After another reboot an error message was prompted while the boot cd
>>>> was
>>>> loading that NTLDR is corrupt.
>>>>
>>>> Any ideas, please?
>>>
>>>
>>
>
 
Re: corrupted files

Have you looked at http://support.microsoft.com/?kbid=941600 on the chance
that the rollup may address this issue?

"Zootal" <msnews@zootal.nospam.com> wrote in message
news:uoO6DlVVIHA.4768@TK2MSFTNGP02.phx.gbl...
> No, I checked that. What it sometimes done is start to load XP64, and then
> stop before the desktop gets displayed. I get a black screen with a mouse
> pointer, and a locked up computer. Removing all the usb drives always
> fixes this. I boot, plug them back in, and we're good to go until next
> week when it does it again. I also get other intermittent hard locks
> immediatly after booting. I usually let it sit for 5 minutes before I do
> anything. If it runs that long, it never locks up. The first few minutes
> after boot - not very reliable. I thought of a heating issue, where
> something warms up, and as it expands breaks a connection somewhere
> causing failure. <shrug>.
>
> "John Barnes" <jbarnes@email.net> wrote in message
> news:%23FRmPNVVIHA.4140@TK2MSFTNGP04.phx.gbl...
>> or possibly the BIOS is set to boot from a removable device first.
>>
>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>> news:B194371C-5F9C-4086-BDA0-7A0D2DABC253@microsoft.com...
>>> Perhaps the result of a pending write that didn't get done.
>>>
>>> "Zootal" <Don't send me any freaking spam at zootal dot com remove the
>>> don't send me any freaking spam> wrote in message
>>> news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>>I had almost identical problems, specifically the "Unknown Hard Error",
>>>>and the ntldr is corrupt problem. I suspected a bad burn of the CD, as
>>>>burning another CD seemed to fix the problem. I also had similar
>>>>problems installing XP32 on another partition, so I could not blame any
>>>>of this on XP64 itself.
>>>>
>>>> I have also noticed that if I boot with any usb flash drives (zip
>>>> drives, thumb drives, etc) plugged, I sometimes get various boot
>>>> errors, including corrupt ntldr, but interesting enough they are not
>>>> consistent. Removing the usb drive or just unplugging my usb hubs
>>>> always fixes it and lets XP boot.
>>>>
>>>>
>>>>
>>>> "Jon" <Jon@discussions.microsoft.com> wrote in message
>>>> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>>>>I downloaded the 120 day trial version:
>>>>>
>>>>> WS03SP1_RTM_1830_PX6_EN.iso
>>>>>
>>>>> Having created a 30G partition, burnt a bootable image on a CD (using
>>>>> Ultra
>>>>> ISO 8) and proceeded to install, booting from the CD:
>>>>>
>>>>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>>>>> although it was on the cd in the \i386 folder.
>>>>>
>>>>> attempt 2. During bootup the following error (with a blue background)
>>>>> is
>>>>> displayed:
>>>>>
>>>>> STOP C0000221 Unknown Hard Error
>>>>> \SystemRoot\System32\ntdll.dll
>>>>>
>>>>> After another reboot an error message was prompted while the boot cd
>>>>> was
>>>>> loading that NTLDR is corrupt.
>>>>>
>>>>> Any ideas, please?
>>>>
>>>>
>>>
>>
>
>
 
Re: corrupted files

That looks like Vista only, but I wonder how much of also applies to XP? I
notice that one of the issues is a long time to resume from a suspend state.
I wonder what they mean by "a long time"? I've long since given up trying to
get my machines to reliably suspend/hibernate, and then resume. 20% do it
fine, the reset never resume. Maybe I should try it again, but be sure to
wait "a long time"?

"Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
news:61C0A28E-D0FD-459D-B819-913DB7382AF9@microsoft.com...
> Have you looked at http://support.microsoft.com/?kbid=941600 on the chance
> that the rollup may address this issue?
>
> "Zootal" <msnews@zootal.nospam.com> wrote in message
> news:uoO6DlVVIHA.4768@TK2MSFTNGP02.phx.gbl...
>> No, I checked that. What it sometimes done is start to load XP64, and
>> then stop before the desktop gets displayed. I get a black screen with a
>> mouse pointer, and a locked up computer. Removing all the usb drives
>> always fixes this. I boot, plug them back in, and we're good to go until
>> next week when it does it again. I also get other intermittent hard locks
>> immediatly after booting. I usually let it sit for 5 minutes before I do
>> anything. If it runs that long, it never locks up. The first few minutes
>> after boot - not very reliable. I thought of a heating issue, where
>> something warms up, and as it expands breaks a connection somewhere
>> causing failure. <shrug>.
>>
>> "John Barnes" <jbarnes@email.net> wrote in message
>> news:%23FRmPNVVIHA.4140@TK2MSFTNGP04.phx.gbl...
>>> or possibly the BIOS is set to boot from a removable device first.
>>>
>>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>> news:B194371C-5F9C-4086-BDA0-7A0D2DABC253@microsoft.com...
>>>> Perhaps the result of a pending write that didn't get done.
>>>>
>>>> "Zootal" <Don't send me any freaking spam at zootal dot com remove the
>>>> don't send me any freaking spam> wrote in message
>>>> news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>>>I had almost identical problems, specifically the "Unknown Hard Error",
>>>>>and the ntldr is corrupt problem. I suspected a bad burn of the CD, as
>>>>>burning another CD seemed to fix the problem. I also had similar
>>>>>problems installing XP32 on another partition, so I could not blame any
>>>>>of this on XP64 itself.
>>>>>
>>>>> I have also noticed that if I boot with any usb flash drives (zip
>>>>> drives, thumb drives, etc) plugged, I sometimes get various boot
>>>>> errors, including corrupt ntldr, but interesting enough they are not
>>>>> consistent. Removing the usb drive or just unplugging my usb hubs
>>>>> always fixes it and lets XP boot.
>>>>>
>>>>>
>>>>>
>>>>> "Jon" <Jon@discussions.microsoft.com> wrote in message
>>>>> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>>>>>I downloaded the 120 day trial version:
>>>>>>
>>>>>> WS03SP1_RTM_1830_PX6_EN.iso
>>>>>>
>>>>>> Having created a 30G partition, burnt a bootable image on a CD
>>>>>> (using Ultra
>>>>>> ISO 8) and proceeded to install, booting from the CD:
>>>>>>
>>>>>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>>>>>> although it was on the cd in the \i386 folder.
>>>>>>
>>>>>> attempt 2. During bootup the following error (with a blue background)
>>>>>> is
>>>>>> displayed:
>>>>>>
>>>>>> STOP C0000221 Unknown Hard Error
>>>>>> \SystemRoot\System32\ntdll.dll
>>>>>>
>>>>>> After another reboot an error message was prompted while the boot cd
>>>>>> was
>>>>>> loading that NTLDR is corrupt.
>>>>>>
>>>>>> Any ideas, please?
>>>>>
>>>>>
>>>>
>>>
>>
>>
>
 
Re: corrupted files

Yeah, I caught my mistake right after I posted and tried to cancel the
message before it downloaded to anybody. Sorry about that.

"Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
news:61C0A28E-D0FD-459D-B819-913DB7382AF9@microsoft.com...
> Have you looked at http://support.microsoft.com/?kbid=941600 on the chance
> that the rollup may address this issue?
>
> "Zootal" <msnews@zootal.nospam.com> wrote in message
> news:uoO6DlVVIHA.4768@TK2MSFTNGP02.phx.gbl...
>> No, I checked that. What it sometimes done is start to load XP64, and
>> then stop before the desktop gets displayed. I get a black screen with a
>> mouse pointer, and a locked up computer. Removing all the usb drives
>> always fixes this. I boot, plug them back in, and we're good to go until
>> next week when it does it again. I also get other intermittent hard locks
>> immediatly after booting. I usually let it sit for 5 minutes before I do
>> anything. If it runs that long, it never locks up. The first few minutes
>> after boot - not very reliable. I thought of a heating issue, where
>> something warms up, and as it expands breaks a connection somewhere
>> causing failure. <shrug>.
>>
>> "John Barnes" <jbarnes@email.net> wrote in message
>> news:%23FRmPNVVIHA.4140@TK2MSFTNGP04.phx.gbl...
>>> or possibly the BIOS is set to boot from a removable device first.
>>>
>>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>> news:B194371C-5F9C-4086-BDA0-7A0D2DABC253@microsoft.com...
>>>> Perhaps the result of a pending write that didn't get done.
>>>>
>>>> "Zootal" <Don't send me any freaking spam at zootal dot com remove the
>>>> don't send me any freaking spam> wrote in message
>>>> news:uBMS2MvUIHA.3556@TK2MSFTNGP02.phx.gbl...
>>>>>I had almost identical problems, specifically the "Unknown Hard Error",
>>>>>and the ntldr is corrupt problem. I suspected a bad burn of the CD, as
>>>>>burning another CD seemed to fix the problem. I also had similar
>>>>>problems installing XP32 on another partition, so I could not blame any
>>>>>of this on XP64 itself.
>>>>>
>>>>> I have also noticed that if I boot with any usb flash drives (zip
>>>>> drives, thumb drives, etc) plugged, I sometimes get various boot
>>>>> errors, including corrupt ntldr, but interesting enough they are not
>>>>> consistent. Removing the usb drive or just unplugging my usb hubs
>>>>> always fixes it and lets XP boot.
>>>>>
>>>>>
>>>>>
>>>>> "Jon" <Jon@discussions.microsoft.com> wrote in message
>>>>> news:1FB6E994-DBE0-4A52-82F0-EFE0D61E3727@microsoft.com...
>>>>>>I downloaded the 120 day trial version:
>>>>>>
>>>>>> WS03SP1_RTM_1830_PX6_EN.iso
>>>>>>
>>>>>> Having created a 30G partition, burnt a bootable image on a CD
>>>>>> (using Ultra
>>>>>> ISO 8) and proceeded to install, booting from the CD:
>>>>>>
>>>>>> attempt 1. During the installation wmsvbvm60.dll could not be copied,
>>>>>> although it was on the cd in the \i386 folder.
>>>>>>
>>>>>> attempt 2. During bootup the following error (with a blue background)
>>>>>> is
>>>>>> displayed:
>>>>>>
>>>>>> STOP C0000221 Unknown Hard Error
>>>>>> \SystemRoot\System32\ntdll.dll
>>>>>>
>>>>>> After another reboot an error message was prompted while the boot cd
>>>>>> was
>>>>>> loading that NTLDR is corrupt.
>>>>>>
>>>>>> Any ideas, please?
>>>>>
>>>>>
>>>>
>>>
>>
>>
>
 
Back
Top