I have a windows 2003 member server with exchange 2003 that keeps rebooting.
I tried all bootup options
1 -All safe modes causes the server to reboot immediately
2 - Normal mode - reboot during applying computer settings
3 - Last known good bootup - a message “windows could not be started as
configured. a previous working configuration was used."
ntbtlog.txt shows that drivers loaded until "Did not load driver ACPI
Uniprocessor PC"

What are my options at this point? I need to preserve my exchange
installation.
Thanks,
Joe

Here's the content of the NTBTLOG.TXT file:

Service Pack 110 12 2009 10:01:00.500
Loaded driver \WINDOWS\system32\ntoskrnl.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver PCIIde.sys
Loaded driver \WINDOWS\System32\Drivers\PCIIDEX.SYS
Loaded driver intelide.sys
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver dmload.sys
Loaded driver dmio.sys
Loaded driver volsnap.sys
Loaded driver PartMgr.sys
Loaded driver atapi.sys
Loaded driver dpti2o.sys
Loaded driver \WINDOWS\system32\DRIVERS\SCSIPORT.SYS
Loaded driver disk.sys
Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
Loaded driver fltmgr.sys
Loaded driver Dfs.sys
Loaded driver KSecDD.sys
Loaded driver Ntfs.sys
Loaded driver NDIS.sys
Loaded driver timntr.sys
Loaded driver snapman.sys
Loaded driver Mup.sys
Loaded driver crcdisk.sys
Did not load driver ACPI Uniprocessor PC
etc.......

"Joe" wrote:

> I have a windows 2003 member server with exchange 2003 that keeps rebooting.
> I tried all bootup options
> 1 -All safe modes causes the server to reboot immediately
> 2 - Normal mode - reboot during applying computer settings
> 3 - Last known good bootup - a message “windows could not be started as
> configured. a previous working configuration was used."
> ntbtlog.txt shows that drivers loaded until "Did not load driver ACPI
> Uniprocessor PC"
>
> What are my options at this point? I need to preserve my exchange
> installation.
> Thanks,
> Joe
>

"Joe" <Joe@newsgroup> wrote in message
news:86C34FCB-C878-4F02-923A-68F7E1073361@newsgroup

> Here's the content of the NTBTLOG.TXT file:
>
> Service Pack 110 12 2009 10:01:00.500
> Loaded driver \WINDOWS\system32\ntoskrnl.exe
> Loaded driver \WINDOWS\system32\hal.dll
> Loaded driver \WINDOWS\system32\KDCOM.DLL
> Loaded driver \WINDOWS\system32\BOOTVID.dll
> Loaded driver ACPI.sys
> Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
> Loaded driver pci.sys
> Loaded driver isapnp.sys
> Loaded driver PCIIde.sys
> Loaded driver \WINDOWS\System32\Drivers\PCIIDEX.SYS
> Loaded driver intelide.sys
> Loaded driver MountMgr.sys
> Loaded driver ftdisk.sys
> Loaded driver dmload.sys
> Loaded driver dmio.sys
> Loaded driver volsnap.sys
> Loaded driver PartMgr.sys
> Loaded driver atapi.sys
> Loaded driver dpti2o.sys
> Loaded driver \WINDOWS\system32\DRIVERS\SCSIPORT.SYS
> Loaded driver disk.sys
> Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
> Loaded driver fltmgr.sys
> Loaded driver Dfs.sys
> Loaded driver KSecDD.sys
> Loaded driver Ntfs.sys
> Loaded driver NDIS.sys
> Loaded driver timntr.sys
> Loaded driver snapman.sys
> Loaded driver Mup.sys
> Loaded driver crcdisk.sys
> Did not load driver ACPI Uniprocessor PC
> etc.......
>
> "Joe" wrote:
>

>> I have a windows 2003 member server with exchange 2003 that keeps
>> rebooting.
>> I tried all bootup options
>> 1 -All safe modes causes the server to reboot immediately
>> 2 - Normal mode - reboot during applying computer settings
>> 3 - Last known good bootup - a message “windows could not be started as
>> configured. a previous working configuration was used."
>> ntbtlog.txt shows that drivers loaded until "Did not load driver ACPI
>> Uniprocessor PC"
>>
>> What are my options at this point? I need to preserve my exchange
>> installation.
>> Thanks,
>> Joe
>>

The first question I usually ask is what was changed, added, or removed
prior to this occuring? Were there any event log errors, such as possible
drive problems? Do you have a recent backup?

However, from what you're saying that it won't even boot in Safe Mode,
appears something is corrupted in the registry, or it has a bad drive. If
it's on a RAID, then I would say corrupted registry.

Seems the only options are (unless I'm forgetting something):
1. If you have a recent backup using a backup app that supports bare metal
restore, give that a shot.
2. Try running an upgrade/repair with the Windows 2003 CD. Boot with the CD,
opt to upgrade/repair. This will refresh the operating system, registry,
etc. You'll just have to re-run Windows updates afterwards, that is if it
boots.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP Windows 2008, MCTS Exchange 2007, MCSE & MCSA 2003 &
2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

You could also boot into the recovery console. Then copy the registry hives from
%systemroot%\repair
This should let you boot the system but unless you have been creating the ERD
recently it will be back to the initial install point for the OS. Still it may
let you recover your data or even trouble shoot the system. I have done this in
the past to get to a point where I can restore a recent backup.




the On Mon, 12 Oct 2009 22:42:49 -0400, "Ace Fekay [MCT]"
<aceman@newsgroup> wrote:

>"Joe" <Joe@newsgroup> wrote in message
>news:86C34FCB-C878-4F02-923A-68F7E1073361@newsgroup

>> Here's the content of the NTBTLOG.TXT file:
>>
>> Service Pack 110 12 2009 10:01:00.500
>> Loaded driver \WINDOWS\system32\ntoskrnl.exe
>> Loaded driver \WINDOWS\system32\hal.dll
>> Loaded driver \WINDOWS\system32\KDCOM.DLL
>> Loaded driver \WINDOWS\system32\BOOTVID.dll
>> Loaded driver ACPI.sys
>> Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
>> Loaded driver pci.sys
>> Loaded driver isapnp.sys
>> Loaded driver PCIIde.sys
>> Loaded driver \WINDOWS\System32\Drivers\PCIIDEX.SYS
>> Loaded driver intelide.sys
>> Loaded driver MountMgr.sys
>> Loaded driver ftdisk.sys
>> Loaded driver dmload.sys
>> Loaded driver dmio.sys
>> Loaded driver volsnap.sys
>> Loaded driver PartMgr.sys
>> Loaded driver atapi.sys
>> Loaded driver dpti2o.sys
>> Loaded driver \WINDOWS\system32\DRIVERS\SCSIPORT.SYS
>> Loaded driver disk.sys
>> Loaded driver \WINDOWS\system32\DRIVERS\CLASSPNP.SYS
>> Loaded driver fltmgr.sys
>> Loaded driver Dfs.sys
>> Loaded driver KSecDD.sys
>> Loaded driver Ntfs.sys
>> Loaded driver NDIS.sys
>> Loaded driver timntr.sys
>> Loaded driver snapman.sys
>> Loaded driver Mup.sys
>> Loaded driver crcdisk.sys
>> Did not load driver ACPI Uniprocessor PC
>> etc.......
>>
>> "Joe" wrote:
>>

>>> I have a windows 2003 member server with exchange 2003 that keeps
>>> rebooting.
>>> I tried all bootup options
>>> 1 -All safe modes causes the server to reboot immediately
>>> 2 - Normal mode - reboot during applying computer settings
>>> 3 - Last known good bootup - a message “windows could not be started as
>>> configured. a previous working configuration was used."
>>> ntbtlog.txt shows that drivers loaded until "Did not load driver ACPI
>>> Uniprocessor PC"
>>>
>>> What are my options at this point? I need to preserve my exchange
>>> installation.
>>> Thanks,
>>> Joe
>>>

>
>
>The first question I usually ask is what was changed, added, or removed
>prior to this occuring? Were there any event log errors, such as possible
>drive problems? Do you have a recent backup?
>
>However, from what you're saying that it won't even boot in Safe Mode,
>appears something is corrupted in the registry, or it has a bad drive. If
>it's on a RAID, then I would say corrupted registry.
>
>Seems the only options are (unless I'm forgetting something):
>1. If you have a recent backup using a backup app that supports bare metal
>restore, give that a shot.
>2. Try running an upgrade/repair with the Windows 2003 CD. Boot with the CD,
>opt to upgrade/repair. This will refresh the operating system, registry,
>etc. You'll just have to re-run Windows updates afterwards, that is if it
>boots.

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

"DaveMills" <DaveMills@newsgroup> wrote in message
news:tf08d5p5cejjqbjh188t5e89vbsfr0942b@newsgroup

> You could also boot into the recovery console. Then copy the registry
> hives from
> %systemroot%\repair
> This should let you boot the system but unless you have been creating the
> ERD
> recently it will be back to the initial install point for the OS. Still it
> may
> let you recover your data or even trouble shoot the system. I have done
> this in
> the past to get to a point where I can restore a recent backup.
>
>

I could imagine what you went through trying to recover that machine. Good
thing you had a backup. :-)

Ace