BSOD during Install

Hi All,

I'm wondering (hoping/begging/praying) if anyone can shed any light on this,
as it's cost me a load of time already.

I'm trying to install Windows Server 2003 R2 x64 on a machine. I can get it
to boot from the CD, load files etc, but while still at the TEXT stage of
the installation, with the blue background and the white footer that shows
which files are being loaded, when it gets to the stage of "Starting
Windows" I get an instant BSOD.

The error is 0x0000007b - which means something along the lines of
"Inaccessible Boot Device". I believe what setup is saying is that it
cannot locate any hard drives (or their controllers) and therefore it
immediately crashes. I get exactly the same error if I unplug all the hard
drives.

However, if I try to install the 32bit version (which I did to test my
sanity) it recognises the hard drive and installs perfectly.

The machine has an Abit AB9 motherboard. The target install HDD is
connected to the first SATA port on the mainboard. The CD-ROM drive is
plugged into the IDE port. The machine is running the latest BIOS. I have
tried connecting the hard-drive into different SATA ports but to no avail.

I thought this may be due to Windows setup requiring 64bit AHCI/RAID drivers
in order to see the drives, so I copied these to a floppy and successfully
specified them at the very first stage of setup (i.e. the Press F6 to load
additional...etc stage), but this had no effect. These were downloaded from
the Abit website and are the latest versions available.

There is only one option regarding SATA in the BIOS, which allows a pair of
separate SATA ports (not the primary ports that the main drive is connected
to) to emulate IDE mode. I've tried setting this to IDE, RAID, and AHCI but
to no avail. I have tried connecting the drive into those ports with each
of those three settings, but again - nothing. Same BSOD with the 0x0000007b
error.

Frankly I'm stumped and I've run out of ideas, but this isn't the worst
part...

The really weird thing is, this machine *did* have Windows Server 2003 R2
x64 installed on it at one time (roughly 3 years ago) - this is actually a
reinstall on a new disc. The worst part? I'm the one who installed it the
first time around!

I cannot remember doing anything unusual during the setup phase, or even
having to specify extra drivers (that ole F6 option). It just seemed to
work. Perfectly.

Can anyone offer any advice, or perhaps even some psychiatric counselling,
to help me?

TIA,
Alex

 

Hello Alex,

Maybe you choose this NG:
microsoft.public.scripting.vbscript

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!

<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi All,
>
> I'm wondering (hoping/begging/praying) if anyone can shed any light on
> this, as it's cost me a load of time already.
>
> I'm trying to install Windows Server 2003 R2 x64 on a machine. I can
> get it to boot from the CD, load files etc, but while still at the
> TEXT stage of the installation, with the blue background and the white
> footer that shows which files are being loaded, when it gets to the
> stage of "Starting Windows" I get an instant BSOD.
>
> The error is 0x0000007b - which means something along the lines of
> "Inaccessible Boot Device". I believe what setup is saying is that it
> cannot locate any hard drives (or their controllers) and therefore it
> immediately crashes. I get exactly the same error if I unplug all the
> hard drives.
>
> However, if I try to install the 32bit version (which I did to test my
> sanity) it recognises the hard drive and installs perfectly.
>
> The machine has an Abit AB9 motherboard. The target install HDD is
> connected to the first SATA port on the mainboard. The CD-ROM drive
> is plugged into the IDE port. The machine is running the latest BIOS.
> I have tried connecting the hard-drive into different SATA ports but
> to no avail.
>
> I thought this may be due to Windows setup requiring 64bit AHCI/RAID
> drivers in order to see the drives, so I copied these to a floppy and
> successfully specified them at the very first stage of setup (i.e. the
> Press F6 to load additional...etc stage), but this had no effect.
> These were downloaded from the Abit website and are the latest
> versions available.
>
> There is only one option regarding SATA in the BIOS, which allows a
> pair of separate SATA ports (not the primary ports that the main drive
> is connected to) to emulate IDE mode. I've tried setting this to IDE,
> RAID, and AHCI but to no avail. I have tried connecting the drive
> into those ports with each of those three settings, but again -
> nothing. Same BSOD with the 0x0000007b error.
>
> Frankly I'm stumped and I've run out of ideas, but this isn't the
> worst part...
>
> The really weird thing is, this machine *did* have Windows Server 2003
> R2 x64 installed on it at one time (roughly 3 years ago) - this is
> actually a reinstall on a new disc. The worst part? I'm the one who
> installed it the first time around!
>
> I cannot remember doing anything unusual during the setup phase, or
> even having to specify extra drivers (that ole F6 option). It just
> seemed to work. Perfectly.
>
> Can anyone offer any advice, or perhaps even some psychiatric
> counselling, to help me?
>
> TIA,
> Alex<!--colorc--><!--/colorc-->

 

Alex Clark wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi All,
>
> I'm wondering (hoping/begging/praying) if anyone can shed any light on this,
> as it's cost me a load of time already.
>
> I'm trying to install Windows Server 2003 R2 x64 on a machine. I can get it
> to boot from the CD, load files etc, but while still at the TEXT stage of
> the installation, with the blue background and the white footer that shows
> which files are being loaded, when it gets to the stage of "Starting
> Windows" I get an instant BSOD.
>
> The error is 0x0000007b - which means something along the lines of
> "Inaccessible Boot Device". I believe what setup is saying is that it
> cannot locate any hard drives (or their controllers) and therefore it
> immediately crashes. I get exactly the same error if I unplug all the hard
> drives.
>
> However, if I try to install the 32bit version (which I did to test my
> sanity) it recognises the hard drive and installs perfectly.
>
> The machine has an Abit AB9 motherboard. The target install HDD is
> connected to the first SATA port on the mainboard. The CD-ROM drive is
> plugged into the IDE port. The machine is running the latest BIOS. I have
> tried connecting the hard-drive into different SATA ports but to no avail.
>
> I thought this may be due to Windows setup requiring 64bit AHCI/RAID drivers
> in order to see the drives, so I copied these to a floppy and successfully
> specified them at the very first stage of setup (i.e. the Press F6 to load
> additional...etc stage), but this had no effect. These were downloaded from
> the Abit website and are the latest versions available.
>
> There is only one option regarding SATA in the BIOS, which allows a pair of
> separate SATA ports (not the primary ports that the main drive is connected
> to) to emulate IDE mode. I've tried setting this to IDE, RAID, and AHCI but
> to no avail. I have tried connecting the drive into those ports with each
> of those three settings, but again - nothing. Same BSOD with the 0x0000007b
> error.
>
> Frankly I'm stumped and I've run out of ideas, but this isn't the worst
> part...
>
> The really weird thing is, this machine *did* have Windows Server 2003 R2
> x64 installed on it at one time (roughly 3 years ago) - this is actually a
> reinstall on a new disc. The worst part? I'm the one who installed it the
> first time around!
>
> I cannot remember doing anything unusual during the setup phase, or even
> having to specify extra drivers (that ole F6 option). It just seemed to
> work. Perfectly.
>
> Can anyone offer any advice, or perhaps even some psychiatric counselling,
> to help me?
>
> TIA,
> Alex
>
> <!--colorc--><!--/colorc-->

It sounds like during the F6 stage, you didn't specify, or it isn't
added automatically the IDE CDROM drivers that are required to be loaded
for windows TXT setup to go past the "Starting Windows" point.

When I was debugging an embedded NAS solution, a web post outlined very
clearly that you would need to specify both in order to get it to boot,
and install successfully.


I know in the older versions of windows setup, (I'm thinking NT), you
had to always tell it to load the CDROM drivers. I think the situation
still exists. Please retry with x64, F6 to load your SATA drive, and
during the part (if it presents to you) of specifying ADDITIONAL storage
devices, choose the IDE CDROM.



Good luck,
--Tim


--
This posting is provided for you, from a fellow community member. Use
at your own risk.

 

Hi Tim,

I did try adding those drivers during the F6 stage - the motherboard has 2
separate onboard SATA controller chipsets (one Intel, one JMicron) and I
loaded both drivers from diskette but it still BSOD'd me.

I think there is something quirky about the mainboard - the JMicron chipset
not only controls a pair of secondary SATA ports, it's also responsible for
the single IDE port on the mainboard (which the CD-ROM is connected to). I
have a suspicion that, after it loads its embedded drivers, the install may
actually lose the ability to communicate with the CD-ROM drive which is what
causes the BSOD, rather than it being unable to see the SATA drives.

But in any case, it's now irrelevant - as a last ditch attempt I decided to
try Windows Server 2008 Standard x64. I was expecting exactly the same
problems but instead it installed perfectly - no additional drivers needed -
and it took less than 45 minutes to go from a blank formatted SATA drive to
a login prompt. I'm well impressed!

Thanks for your help though - I think you had the most well reasoned idea
about what was going wrong. I'm still scratching my head as to how I
managed to get it installed 3 years ago, but maybe that will be one of
life's little mysteries.

Thanks,
Alex


"Tim Judd" <tjudd01@hotmail.com> wrote in message
news:eQ7GDL5FKHA.4608@TK2MSFTNGP02.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Alex Clark wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi All,
>>
>> I'm wondering (hoping/begging/praying) if anyone can shed any light on
>> this, as it's cost me a load of time already.
>>
>> I'm trying to install Windows Server 2003 R2 x64 on a machine. I can get
>> it to boot from the CD, load files etc, but while still at the TEXT stage
>> of the installation, with the blue background and the white footer that
>> shows which files are being loaded, when it gets to the stage of
>> "Starting Windows" I get an instant BSOD.
>>
>> The error is 0x0000007b - which means something along the lines of
>> "Inaccessible Boot Device". I believe what setup is saying is that it
>> cannot locate any hard drives (or their controllers) and therefore it
>> immediately crashes. I get exactly the same error if I unplug all the
>> hard drives.
>>
>> However, if I try to install the 32bit version (which I did to test my
>> sanity) it recognises the hard drive and installs perfectly.
>>
>> The machine has an Abit AB9 motherboard. The target install HDD is
>> connected to the first SATA port on the mainboard. The CD-ROM drive is
>> plugged into the IDE port. The machine is running the latest BIOS. I
>> have tried connecting the hard-drive into different SATA ports but to no
>> avail.
>>
>> I thought this may be due to Windows setup requiring 64bit AHCI/RAID
>> drivers in order to see the drives, so I copied these to a floppy and
>> successfully specified them at the very first stage of setup (i.e. the
>> Press F6 to load additional...etc stage), but this had no effect. These
>> were downloaded from the Abit website and are the latest versions
>> available.
>>
>> There is only one option regarding SATA in the BIOS, which allows a pair
>> of separate SATA ports (not the primary ports that the main drive is
>> connected to) to emulate IDE mode. I've tried setting this to IDE, RAID,
>> and AHCI but to no avail. I have tried connecting the drive into those
>> ports with each of those three settings, but again - nothing. Same BSOD
>> with the 0x0000007b error.
>>
>> Frankly I'm stumped and I've run out of ideas, but this isn't the worst
>> part...
>>
>> The really weird thing is, this machine *did* have Windows Server 2003 R2
>> x64 installed on it at one time (roughly 3 years ago) - this is actually
>> a reinstall on a new disc. The worst part? I'm the one who installed it
>> the first time around!
>>
>> I cannot remember doing anything unusual during the setup phase, or even
>> having to specify extra drivers (that ole F6 option). It just seemed to
>> work. Perfectly.
>>
>> Can anyone offer any advice, or perhaps even some psychiatric
>> counselling, to help me?
>>
>> TIA,
>> Alex
>>
>><!--colorc--><!--/colorc-->
>
> It sounds like during the F6 stage, you didn't specify, or it isn't added
> automatically the IDE CDROM drivers that are required to be loaded for
> windows TXT setup to go past the "Starting Windows" point.
>
> When I was debugging an embedded NAS solution, a web post outlined very
> clearly that you would need to specify both in order to get it to boot,
> and install successfully.
>
>
> I know in the older versions of windows setup, (I'm thinking NT), you had
> to always tell it to load the CDROM drivers. I think the situation still
> exists. Please retry with x64, F6 to load your SATA drive, and during the
> part (if it presents to you) of specifying ADDITIONAL storage devices,
> choose the IDE CDROM.
>
>
>
> Good luck,
> --Tim
>
>
> --
> This posting is provided for you, from a fellow community member. Use at
> your own risk. <!--colorc--><!--/colorc-->

 

Meinolf,

I'm not sure I understand? Why would I post a question about installing
Windows Server to a newsgroup about VBScript?

Thanks,
Alex



"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb662c8998cbe5741d7b233a@msnews.microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hello Alex,
>
> Maybe you choose this NG:
> microsoft.public.scripting.vbscript
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!
><!--coloro:green--><span style="color:green <!--/coloro-->
>> Hi All,
>>
>> I'm wondering (hoping/begging/praying) if anyone can shed any light on
>> this, as it's cost me a load of time already.
>>
>> I'm trying to install Windows Server 2003 R2 x64 on a machine. I can
>> get it to boot from the CD, load files etc, but while still at the
>> TEXT stage of the installation, with the blue background and the white
>> footer that shows which files are being loaded, when it gets to the
>> stage of "Starting Windows" I get an instant BSOD.
>>
>> The error is 0x0000007b - which means something along the lines of
>> "Inaccessible Boot Device". I believe what setup is saying is that it
>> cannot locate any hard drives (or their controllers) and therefore it
>> immediately crashes. I get exactly the same error if I unplug all the
>> hard drives.
>>
>> However, if I try to install the 32bit version (which I did to test my
>> sanity) it recognises the hard drive and installs perfectly.
>>
>> The machine has an Abit AB9 motherboard. The target install HDD is
>> connected to the first SATA port on the mainboard. The CD-ROM drive
>> is plugged into the IDE port. The machine is running the latest BIOS.
>> I have tried connecting the hard-drive into different SATA ports but
>> to no avail.
>>
>> I thought this may be due to Windows setup requiring 64bit AHCI/RAID
>> drivers in order to see the drives, so I copied these to a floppy and
>> successfully specified them at the very first stage of setup (i.e. the
>> Press F6 to load additional...etc stage), but this had no effect.
>> These were downloaded from the Abit website and are the latest
>> versions available.
>>
>> There is only one option regarding SATA in the BIOS, which allows a
>> pair of separate SATA ports (not the primary ports that the main drive
>> is connected to) to emulate IDE mode. I've tried setting this to IDE,
>> RAID, and AHCI but to no avail. I have tried connecting the drive
>> into those ports with each of those three settings, but again -
>> nothing. Same BSOD with the 0x0000007b error.
>>
>> Frankly I'm stumped and I've run out of ideas, but this isn't the
>> worst part...
>>
>> The really weird thing is, this machine *did* have Windows Server 2003
>> R2 x64 installed on it at one time (roughly 3 years ago) - this is
>> actually a reinstall on a new disc. The worst part? I'm the one who
>> installed it the first time around!
>>
>> I cannot remember doing anything unusual during the setup phase, or
>> even having to specify extra drivers (that ole F6 option). It just
>> seemed to work. Perfectly.
>>
>> Can anyone offer any advice, or perhaps even some psychiatric
>> counselling, to help me?
>>
>> TIA,
>> Alex<!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

See if anything helps here


--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Alex Clark" <quanta@noemail.noemail> wrote in message
news:Onfp4KGGKHA.1492@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Tim,
>
> I did try adding those drivers during the F6 stage - the motherboard has 2
> separate onboard SATA controller chipsets (one Intel, one JMicron) and I loaded
> both drivers from diskette but it still BSOD'd me.
>
> I think there is something quirky about the mainboard - the JMicron chipset not
> only controls a pair of secondary SATA ports, it's also responsible for the single
> IDE port on the mainboard (which the CD-ROM is connected to). I have a suspicion
> that, after it loads its embedded drivers, the install may actually lose the
> ability to communicate with the CD-ROM drive which is what causes the BSOD, rather
> than it being unable to see the SATA drives.
>
> But in any case, it's now irrelevant - as a last ditch attempt I decided to try
> Windows Server 2008 Standard x64. I was expecting exactly the same problems but
> instead it installed perfectly - no additional drivers needed - and it took less
> than 45 minutes to go from a blank formatted SATA drive to a login prompt. I'm
> well impressed!
>
> Thanks for your help though - I think you had the most well reasoned idea about
> what was going wrong. I'm still scratching my head as to how I managed to get it
> installed 3 years ago, but maybe that will be one of life's little mysteries.
>
> Thanks,
> Alex
>
>
> "Tim Judd" <tjudd01@hotmail.com> wrote in message
> news:eQ7GDL5FKHA.4608@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
>> Alex Clark wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi All,
>>>
>>> I'm wondering (hoping/begging/praying) if anyone can shed any light on this, as
>>> it's cost me a load of time already.
>>>
>>> I'm trying to install Windows Server 2003 R2 x64 on a machine. I can get it to
>>> boot from the CD, load files etc, but while still at the TEXT stage of the
>>> installation, with the blue background and the white footer that shows which
>>> files are being loaded, when it gets to the stage of "Starting Windows" I get an
>>> instant BSOD.
>>>
>>> The error is 0x0000007b - which means something along the lines of "Inaccessible
>>> Boot Device". I believe what setup is saying is that it cannot locate any hard
>>> drives (or their controllers) and therefore it immediately crashes. I get
>>> exactly the same error if I unplug all the hard drives.
>>>
>>> However, if I try to install the 32bit version (which I did to test my sanity)
>>> it recognises the hard drive and installs perfectly.
>>>
>>> The machine has an Abit AB9 motherboard. The target install HDD is connected to
>>> the first SATA port on the mainboard. The CD-ROM drive is plugged into the IDE
>>> port. The machine is running the latest BIOS. I have tried connecting the
>>> hard-drive into different SATA ports but to no avail.
>>>
>>> I thought this may be due to Windows setup requiring 64bit AHCI/RAID drivers in
>>> order to see the drives, so I copied these to a floppy and successfully
>>> specified them at the very first stage of setup (i.e. the Press F6 to load
>>> additional...etc stage), but this had no effect. These were downloaded from the
>>> Abit website and are the latest versions available.
>>>
>>> There is only one option regarding SATA in the BIOS, which allows a pair of
>>> separate SATA ports (not the primary ports that the main drive is connected to)
>>> to emulate IDE mode. I've tried setting this to IDE, RAID, and AHCI but to no
>>> avail. I have tried connecting the drive into those ports with each of those
>>> three settings, but again - nothing. Same BSOD with the 0x0000007b error.
>>>
>>> Frankly I'm stumped and I've run out of ideas, but this isn't the worst part...
>>>
>>> The really weird thing is, this machine *did* have Windows Server 2003 R2 x64
>>> installed on it at one time (roughly 3 years ago) - this is actually a reinstall
>>> on a new disc. The worst part? I'm the one who installed it the first time
>>> around!
>>>
>>> I cannot remember doing anything unusual during the setup phase, or even having
>>> to specify extra drivers (that ole F6 option). It just seemed to work.
>>> Perfectly.
>>>
>>> Can anyone offer any advice, or perhaps even some psychiatric counselling, to
>>> help me?
>>>
>>> TIA,
>>> Alex
>>>
>>><!--colorc--><!--/colorc-->
>>
>> It sounds like during the F6 stage, you didn't specify, or it isn't added
>> automatically the IDE CDROM drivers that are required to be loaded for windows
>> TXT setup to go past the "Starting Windows" point.
>>
>> When I was debugging an embedded NAS solution, a web post outlined very clearly
>> that you would need to specify both in order to get it to boot, and install
>> successfully.
>>
>>
>> I know in the older versions of windows setup, (I'm thinking NT), you had to
>> always tell it to load the CDROM drivers. I think the situation still exists.
>> Please retry with x64, F6 to load your SATA drive, and during the part (if it
>> presents to you) of specifying ADDITIONAL storage devices, choose the IDE CDROM.
>>
>>
>>
>> Good luck,
>> --Tim
>>
>>
>> --
>> This posting is provided for you, from a fellow community member. Use at your
>> own risk.<!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

Some days we're a half a click off.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]



"Alex Clark" wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Meinolf,
>
> I'm not sure I understand? Why would I post a question about installing
> Windows Server to a newsgroup about VBScript?
>
> Thanks,
> Alex<!--colorc--><!--/colorc-->

 

Hello Alex,

Sorry, mixed the NGs.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!

<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Meinolf,
>
> I'm not sure I understand? Why would I post a question about
> installing Windows Server to a newsgroup about VBScript?
>
> Thanks,
> Alex
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb662c8998cbe5741d7b233a@msnews.microsoft.com...
> <!--coloro:green--><span style="color:green <!--/coloro-->
>> Hello Alex,
>>
>> Maybe you choose this NG:
>> microsoft.public.scripting.vbscript
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> Hi All,
>>>
>>> I'm wondering (hoping/begging/praying) if anyone can shed any light
>>> on this, as it's cost me a load of time already.
>>>
>>> I'm trying to install Windows Server 2003 R2 x64 on a machine. I
>>> can get it to boot from the CD, load files etc, but while still at
>>> the TEXT stage of the installation, with the blue background and the
>>> white footer that shows which files are being loaded, when it gets
>>> to the stage of "Starting Windows" I get an instant BSOD.
>>>
>>> The error is 0x0000007b - which means something along the lines of
>>> "Inaccessible Boot Device". I believe what setup is saying is that
>>> it cannot locate any hard drives (or their controllers) and
>>> therefore it immediately crashes. I get exactly the same error if I
>>> unplug all the hard drives.
>>>
>>> However, if I try to install the 32bit version (which I did to test
>>> my sanity) it recognises the hard drive and installs perfectly.
>>>
>>> The machine has an Abit AB9 motherboard. The target install HDD is
>>> connected to the first SATA port on the mainboard. The CD-ROM drive
>>> is plugged into the IDE port. The machine is running the latest
>>> BIOS. I have tried connecting the hard-drive into different SATA
>>> ports but to no avail.
>>>
>>> I thought this may be due to Windows setup requiring 64bit AHCI/RAID
>>> drivers in order to see the drives, so I copied these to a floppy
>>> and successfully specified them at the very first stage of setup
>>> (i.e. the Press F6 to load additional...etc stage), but this had no
>>> effect. These were downloaded from the Abit website and are the
>>> latest versions available.
>>>
>>> There is only one option regarding SATA in the BIOS, which allows a
>>> pair of separate SATA ports (not the primary ports that the main
>>> drive is connected to) to emulate IDE mode. I've tried setting this
>>> to IDE, RAID, and AHCI but to no avail. I have tried connecting the
>>> drive into those ports with each of those three settings, but again
>>> - nothing. Same BSOD with the 0x0000007b error.
>>>
>>> Frankly I'm stumped and I've run out of ideas, but this isn't the
>>> worst part...
>>>
>>> The really weird thing is, this machine *did* have Windows Server
>>> 2003 R2 x64 installed on it at one time (roughly 3 years ago) - this
>>> is actually a reinstall on a new disc. The worst part? I'm the one
>>> who installed it the first time around!
>>>
>>> I cannot remember doing anything unusual during the setup phase, or
>>> even having to specify extra drivers (that ole F6 option). It just
>>> seemed to work. Perfectly.
>>>
>>> Can anyone offer any advice, or perhaps even some psychiatric
>>> counselling, to help me?
>>>
>>> TIA,
>>> Alex<!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Peter Foldes wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> See if anything helps here
>
> <!--colorc--><!--/colorc-->

Have you run the latest BIOS and device firmware updates ?
I've found those to be helpful on older machines and newer s/w.

 

Yep, BIOS was fully updated to the latest version.

And like I said in the OP, the crazy thing is I'd already somehow managed to
install Win2003 R2 x64 on it 3yrs ago!

Maybe some mysteries are meant to be left unsolved, though I'm still
scratching my head over it... At least I managed to get Win 2008 to install
okay.

Thanks,
Alex


"Adrian Marsh (NNTP)" <adrian.marsh@_removeme_ubiquisys.com> wrote in
message news:ulhcOdcGKHA.6056@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Peter Foldes wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
>> See if anything helps here
>>
>><!--colorc--><!--/colorc-->
>
> Have you run the latest BIOS and device firmware updates ?
> I've found those to be helpful on older machines and newer s/w. <!--colorc--><!--/colorc-->

 

Alex Clark wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Tim,
>
> I did try adding those drivers during the F6 stage - the motherboard has 2
> separate onboard SATA controller chipsets (one Intel, one JMicron) and I
> loaded both drivers from diskette but it still BSOD'd me.
>
> I think there is something quirky about the mainboard - the JMicron chipset
> not only controls a pair of secondary SATA ports, it's also responsible for
> the single IDE port on the mainboard (which the CD-ROM is connected to). I
> have a suspicion that, after it loads its embedded drivers, the install may
> actually lose the ability to communicate with the CD-ROM drive which is what
> causes the BSOD, rather than it being unable to see the SATA drives.
>
> But in any case, it's now irrelevant - as a last ditch attempt I decided to
> try Windows Server 2008 Standard x64. I was expecting exactly the same
> problems but instead it installed perfectly - no additional drivers needed -
> and it took less than 45 minutes to go from a blank formatted SATA drive to
> a login prompt. I'm well impressed!
>
> Thanks for your help though - I think you had the most well reasoned idea
> about what was going wrong. I'm still scratching my head as to how I
> managed to get it installed 3 years ago, but maybe that will be one of
> life's little mysteries.<!--colorc--><!--/colorc-->

I'd think on terms of Microsoft RIS or another likely product that
doesn't require CDROM support. That'd be my thought process.
<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> Thanks,
> Alex<!--colorc--><!--/colorc-->
<snip>


--
This posting is provided for you, from a fellow community member. Use
at your own risk.