Re: UNMOUNTABLE_BOOT_VOLUME
- From: "Brian Burgess" <bburgess66@xxxxxxxxxxx>
- Date: Fri, 22 May 2009 11:19:16 +0800
Hi Gerry,
Thx. No beep codes tho. It gets all the way to the WinXP start screen ..
for about 1/2 sec before the BSOD shows. I cant even find a boot log.
Thx again
-BB
"Gerry" <gerry@xxxxxxxxxx> wrote in message
news:ee7OMBj2JHA.240@xxxxxxxxxxxxxxxxxxxxxxx
Brian
What is the BIOS -I am wondering whether beep codes might help?
You might try checking the Boot progress against the information in
these links to see if you can identify how far it gets
http://www.pcguide.com/ref/mbsys/bios/bootSequence-c.html
http://dotnetjunkies.com/WebLog/unknownreference/articles/12284.aspx
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Brian Burgess wrote:
Sorry Gerry,
I forgot to give you the stop code:
(0x83331530, 0xC0000102, 0x0, 0x0)
thx
-BB
"Gerry" <gerry@xxxxxxxxxx> wrote in message
news:uNJumbT2JHA.5896@xxxxxxxxxxxxxxxxxxxxxxx
Brian
The solution you have tried is only one of a number. There are a
number of differing problems that can cause the Stop Error bug code
you are seeing. It would help if you posted a copy of the Stop
Error report. Disable automatic restart on system failure. This should
help by
allowing time to write down the STOP code properly. Keep pressing
the F8 key during Start-Up and select option - Disable automatic
restart on system failure. Do not re-enable automatic restart on
system failure. How did you create the dual boot? Did you use any third
party boot
manager? Do you have a particular reason for dual booting? Do you
have access to a second computer? Do you have important data files
you need to recover?
Unmountable Boot Volume
http://support.microsoft.com/kb/555302
Background information on Stop error code
http://msdn2.microsoft.com/en-us/library/ms797142.aspx
0x000000ED: UNMOUNTABLE_BOOT_VOLUME
The kernel mode I/O subsystem attempted to mount the boot volume and
it failed. This error also might occur during an upgrade to Win XP on
systems that use higher throughput ATA disks or controllers with
incorrect cabling. In some cases, your system might appear to work
normally after you restart.
Source: http://aumha.org/a/stop.htm
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Brian Burgess wrote:
Hi all,
I've been 'googling' this subject for the past two weeks. All
posts seem to suggest following the same set of procedures shown
below:
***************************************************************************
1) Boot up your computer from your Windows XP installation CD.
Insert the XP CD into your CD-ROM drive and turn on your computer.
2) Set your BIOS to boot from CD. Your system's BIOS settings can be
opened by hitting the F2, F8, F8 or Delete key on your keyboard as
the computer boots up. The specific key differs depending on your
computer's manufacturer. When you see the message "Press any key to
boot from CD," tap any key on your keyboard and wait until you see
the "Welcome to Setup" screen.
3) Hit "R" to use your Recovery Console to repair the installation.
If you have a dual-boot computer, you need to select the particular
Windows installation you would like to access.
4) Type in your administrative password when the computer prompts
you to. If you have no password, simply press Enter. This will
bring you to the command prompt.
5) Type in "CHKDSK/R" and press Enter. CHKDSK will now scan and
repair your hard drive. Type Exit when this process is complete
6) Press Enter to restart the computer. Your computer should now
boot properly, without that annoying error.
***************************************************************************
All of this I have followed without success. I do have a special
circumstance also:
This is a dual boot system with Win2K on the primary (FAT32)
partition, and WinXP on the extended (NTFS) partition. Both fail
with same error.
This all started occurring after a power failure. The power
failure ended up being a physical defect with the plug into the
wall socket. Plug replaced, power restored, boot problem occurs....
My question in the end of course is 'how to fix'. But I'm also
wondering if (because both windows wont start) is: Could a
controller failure cause this? The motherboard is about 4yrs old.
Has two IDE (UDMA133) controllers built in. Is it possible that a
marginal controller can cause this???
PLZ help
many thx in advance
-BB
.
- Follow-Ups:
- Re: UNMOUNTABLE_BOOT_VOLUME
- From: Gerry
- Re: UNMOUNTABLE_BOOT_VOLUME
- References:
- UNMOUNTABLE_BOOT_VOLUME
- From: Brian Burgess
- Re: UNMOUNTABLE_BOOT_VOLUME
- From: Gerry
- Re: UNMOUNTABLE_BOOT_VOLUME
- From: Brian Burgess
- Re: UNMOUNTABLE_BOOT_VOLUME
- From: Gerry
- UNMOUNTABLE_BOOT_VOLUME
- Prev by Date: Re: explorer.exe will not start
- Next by Date: Re: Coooo21a-rectify without inst disc?
- Previous by thread: Re: UNMOUNTABLE_BOOT_VOLUME
- Next by thread: Re: UNMOUNTABLE_BOOT_VOLUME
- Index(es):
Relevant Pages
|