Prev: Upgrade from 2000 to 2003
Next: ntbackup schedule not working
From: Jason on 13 Apr 2007 16:30
I have a computer that has never finished fully starting up. This is a fresh
installation of windows server 2003, and is the first os ever loaded on to
this machine. When started in safe mode, the last driver loaded is
acpitabl.dat. My question is: does that indicate that the problem is with
acpitabl.dat, or with the next driver that would be loaded? I have seen
different people say different things.

Thanks in advance,
Jason
From: Dave Patrick on 13 Apr 2007 23:43
Probably the next assuming drivers are the issue.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Jason" wrote:
>I have a computer that has never finished fully starting up. This is a
>fresh
> installation of windows server 2003, and is the first os ever loaded on to
> this machine. When started in safe mode, the last driver loaded is
> acpitabl.dat. My question is: does that indicate that the problem is with
> acpitabl.dat, or with the next driver that would be loaded? I have seen
> different people say different things.
>
> Thanks in advance,
> Jason

From: Hayman Ezzeldin on 14 Apr 2007 06:28
Dear Jason,
To make sure of that, all you have to do is to start your machine in "Enable
Boot Logging" mode instead of "Safe Mode"
This will create a text file "Ntbtlog.txt" in the "Windows" folder.
In this file, you will find the name and path of each file that runs during
startup. The log marks each file as successful (Loaded driver) or
unsuccessful (Did not load driver). Boot logging appends entries to
Ntbtlog.txt when you start your system in safe mode. Comparing normal mode
and safe mode entries enables you to determine which services run in normal
mode only.

for example:
Loaded driver \SystemRoot\System32\DRIVERS\flpydisk.sys
Did not load driver \SystemRoot\System32\DRIVERS\flpydisk.SYS

And becasue you can't load the windows, so you can restart your windows in
"Recovery Console" from your windows CD.

Please let me know if more info is required
Best regards.

"Jason" <Jason(a)discussions.microsoft.com> wrote in message
news:857705EE-E8BE-482B-B9E3-063AA60F1A2E(a)microsoft.com...
>I have a computer that has never finished fully starting up. This is a
>fresh
> installation of windows server 2003, and is the first os ever loaded on to
> this machine. When started in safe mode, the last driver loaded is
> acpitabl.dat. My question is: does that indicate that the problem is with
> acpitabl.dat, or with the next driver that would be loaded? I have seen
> different people say different things.
>
> Thanks in advance,
> Jason


From: Jason on 15 Apr 2007 00:00
Some of the times that I restarted with boot logging enabled, no ntbtlog.txt
was created, however the windows splash screen never came up. But I
restarted one time with boot logging enabled, and suprisingly, I was able to
get into windows and opened the ntbtlog.txt file. Everytime I tried booting
in safe mode, the last driver that was listed was acpitabl.dat. So, trying
to find the next driver (that would have been causing the problem), I
searched ntbtlog.txt for acpitabl.dat. However, it did not exist in the
file. I was able to get two boot logs, from two successful startups, and
neither file contained acpitabl.dat.

Now I am curious as to why this driver never showed up in either boot log.
Any ideas?

Thanks,
Jason

"Hayman Ezzeldin" wrote:

> Dear Jason,
> To make sure of that, all you have to do is to start your machine in "Enable
> Boot Logging" mode instead of "Safe Mode"
> This will create a text file "Ntbtlog.txt" in the "Windows" folder.
> In this file, you will find the name and path of each file that runs during
> startup. The log marks each file as successful (Loaded driver) or
> unsuccessful (Did not load driver). Boot logging appends entries to
> Ntbtlog.txt when you start your system in safe mode. Comparing normal mode
> and safe mode entries enables you to determine which services run in normal
> mode only.
>
> for example:
> Loaded driver \SystemRoot\System32\DRIVERS\flpydisk.sys
> Did not load driver \SystemRoot\System32\DRIVERS\flpydisk.SYS
>
> And becasue you can't load the windows, so you can restart your windows in
> "Recovery Console" from your windows CD.
>
> Please let me know if more info is required
> Best regards.
>
> "Jason" <Jason(a)discussions.microsoft.com> wrote in message
> news:857705EE-E8BE-482B-B9E3-063AA60F1A2E(a)microsoft.com...
> >I have a computer that has never finished fully starting up. This is a
> >fresh
> > installation of windows server 2003, and is the first os ever loaded on to
> > this machine. When started in safe mode, the last driver loaded is
> > acpitabl.dat. My question is: does that indicate that the problem is with
> > acpitabl.dat, or with the next driver that would be loaded? I have seen
> > different people say different things.
> >
> > Thanks in advance,
> > Jason
>
>
>
 | 
Pages: 1
Prev: Upgrade from 2000 to 2003
Next: ntbackup schedule not working