From: JB on
Are you supposed to get this error WHENEVER you start in safe mode?

Thank you


From: PA Bear [MS MVP] on
No.

You're welcome.


JB wrote:
> Are you supposed to get this error WHENEVER you start in safe mode?
>
> Thank you
From: JB on
Well, I do. What does that mean?

I assumed that it was normal as, indeed, in safe mode many drivers are not
loaded. What 7026 says, apparently, is that those drivers are missing.

Any ideas?

Thank you

JB




"PA Bear [MS MVP]" <PABearMVP(a)gmail.com> escreveu na mensagem
news:%23Xdwp2ZuKHA.5008(a)TK2MSFTNGP05.phx.gbl...
> No.
>
> You're welcome.
>
>
> JB wrote:
>> Are you supposed to get this error WHENEVER you start in safe mode?
>>
>> Thank you


From: Jose on
On Mar 2, 3:59 am, "JB" <o...(a)closed.com> wrote:
> Well, I do.  What does that mean?
>
> I assumed that it was normal as, indeed, in safe mode many drivers are not
> loaded.  What 7026 says, apparently, is that those drivers are missing.
>
> Any ideas?
>
> Thank you
>
> JB
>
> "PA Bear [MS MVP]" <PABear...(a)gmail.com> escreveu na mensagemnews:%23Xdwp2ZuKHA.5008(a)TK2MSFTNGP05.phx.gbl...
>
>
>
> > No.
>
> > You're welcome.
>
> > JB wrote:
> >> Are you supposed to get this error WHENEVER you start in safe mode?
>
> >> Thank you

More information is necessary to help understand and resolve your
issue.

We need some system information and the actual contents of the Event
Log message.

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
back here.

There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete from the pasted
information.

Here is a method to post the specific information about individual
events.

To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box
enter:

%SystemRoot%\system32\eventvwr.msc /s

Click OK to launch the Event Viewer.

The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty.
Not every event is a problem, some are informational messages that
things are working okay and some are warnings.
No event should defy reasonable explanation.

Each event is sorted by Date and Time. Errors will have red Xs,
Warnings will have yellow !s.
Information messages have white is. Not every Error or Warning event
means there is a serious issue.
Some are excusable at startup time when Windows is booting. Try to
find just the events at the date
and time around your problem.

If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.

When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.

To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.
From: JB on
Thank you, so much, Jose

Here are the logs of the usual error when I go into Safe Mode


Nome do SO Microsoft Windows XP Professional
Vers�o 5.1.2600 Service Pack 3 Compila��o 2600
Fabricante do SO Microsoft Corporation
Nome do sistema TOSHIBA
Fabricante do sistema TOSHIBA
Modelo do sistema Satellite P100
Tipo do sistema X86-based PC
Processador x86 Family 6 Model 14 Stepping 8 GenuineIntel ~1666 Mhz
Data/vers�o de BIOS TOSHIBA V1.70, 16/03/2006
Vers�o SMBIOS 2.4
Direct�rio do Windows C:\WINDOWS
Direct�rio do sistema C:\WINDOWS\system32
Dispositivo de arranque \Device\HarddiskVolume1
Localiza��o Reino Unido
Camada de abstrac��o de hardware (HAL) Vers�o = "5.1.2600.5512
(xpsp.080413-2111)"
Nome de utilizador TOSHIBA\Qimi
Fuso hor�rio GMT Standard Time
Mem�ria f�sica total 1,024.00 MB
Mem�ria f�sica dispon�vel 343.97 MB
Mem�ria virtual total 2.00 GB
Mem�ria virtual dispon�vel 1.96 GB
Espa�o de ficheiro de p�gina 2.40 GB
Ficheiro de pagina��o C:\pagefile.sys


Tipo de evento: Erro
Origem do evento: Service Control Manager
Categoria do evento: Nenhum
ID do evento: 7026
Data: 28/02/2010
Hora: 15:03:25
Utilizador: N/D
Computador: TOSHIBA
Descri��o:
Falhou o carregamento dos seguintes controladores de in�cio de arranque ou
de in�cio do sistema:
Aavmker4
AFD
aswSP
aswTdi
cmdGuard
cmdHlp
Fips
intelppm
IPSec
MRxSmb
NetBIOS
NetBT
RasAcd
Rdbss
Tcpip
Tcpip6

Para mais informa��es, consulte o 'Centro de ajuda e suporte' em
http://go.microsoft.com/fwlink/events.asp.


Tipo de evento: Erro
Origem do evento: Service Control Manager
Categoria do evento: Nenhum
ID do evento: 7001
Data: 28/02/2010
Hora: 15:03:25
Utilizador: N/D
Computador: TOSHIBA
Descri��o:
O servi�o IPSEC Services depende do servi�o IPSEC driver o qual falhou o
arranque devido ao seguinte erro:
Um dispositivo ligado ao sistema n�o est� a funcionar.

Para mais informa��es, consulte o 'Centro de ajuda e suporte' em
http://go.microsoft.com/fwlink/events.asp.


Tipo de evento: Erro
Origem do evento: Service Control Manager
Categoria do evento: Nenhum
ID do evento: 7001
Data: 28/02/2010
Hora: 15:03:25
Utilizador: N/D
Computador: TOSHIBA
Descri��o:
O servi�o IPv6 Helper Service depende do servi�o Microsoft IPv6 Protocol
Driver o qual falhou o arranque devido ao seguinte erro:
Um dispositivo ligado ao sistema n�o est� a funcionar.

Para mais informa��es, consulte o 'Centro de ajuda e suporte' em
http://go.microsoft.com/fwlink/events.asp.


Tipo de evento: Erro
Origem do evento: Service Control Manager
Categoria do evento: Nenhum
ID do evento: 7001
Data: 28/02/2010
Hora: 15:03:25
Utilizador: N/D
Computador: TOSHIBA
Descri��o:
O servi�o TCP/IP NetBIOS Helper depende do servi�o AFD o qual falhou o
arranque devido ao seguinte erro:
Um dispositivo ligado ao sistema n�o est� a funcionar.

Para mais informa��es, consulte o 'Centro de ajuda e suporte' em
http://go.microsoft.com/fwlink/events.asp.


Tipo de evento: Erro
Origem do evento: Service Control Manager
Categoria do evento: Nenhum
ID do evento: 7001
Data: 28/02/2010
Hora: 15:03:25
Utilizador: N/D
Computador: TOSHIBA
Descri��o:
O servi�o DHCP Client depende do servi�o NetBios over Tcpip o qual falhou o
arranque devido ao seguinte erro:
Um dispositivo ligado ao sistema n�o est� a funcionar.

Para mais informa��es, consulte o 'Centro de ajuda e suporte' em
http://go.microsoft.com/fwlink/events.asp.


Tipo de evento: Erro
Origem do evento: DCOM
Categoria do evento: Nenhum
ID do evento: 10005
Data: 28/02/2010
Hora: 15:03:08
Utilizador: NT AUTHORITY\SYSTEM
Computador: TOSHIBA
Descri��o:
O DCOM obteve o erro "N�o � poss�vel iniciar este servi�o em modo de
seguran�a " ao tentar iniciar o servi�o EventSystem com os argumentos "" de
forma a executar o servidor:
{1BE1F766-5536-11D1-B726-00C04FB926AF}

Para mais informa��es, consulte o 'Centro de ajuda e suporte' em
http://go.microsoft.com/fwlink/events.asp.






























"Jose" <jose_ease(a)yahoo.com> escreveu na mensagem
news:431992cc-3efb-445d-9495-993b3cbcfe75(a)f35g2000yqd.googlegroups.com...
On Mar 2, 3:59 am, "JB" <o...(a)closed.com> wrote:
> Well, I do. What does that mean?
>
> I assumed that it was normal as, indeed, in safe mode many drivers are not
> loaded. What 7026 says, apparently, is that those drivers are missing.
>
> Any ideas?
>
> Thank you
>
> JB
>
> "PA Bear [MS MVP]" <PABear...(a)gmail.com> escreveu na
> mensagemnews:%23Xdwp2ZuKHA.5008(a)TK2MSFTNGP05.phx.gbl...
>
>
>
> > No.
>
> > You're welcome.
>
> > JB wrote:
> >> Are you supposed to get this error WHENEVER you start in safe mode?
>
> >> Thank you

More information is necessary to help understand and resolve your
issue.

We need some system information and the actual contents of the Event
Log message.

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
back here.

There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete from the pasted
information.

Here is a method to post the specific information about individual
events.

To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box
enter:

%SystemRoot%\system32\eventvwr.msc /s

Click OK to launch the Event Viewer.

The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty.
Not every event is a problem, some are informational messages that
things are working okay and some are warnings.
No event should defy reasonable explanation.

Each event is sorted by Date and Time. Errors will have red Xs,
Warnings will have yellow !s.
Information messages have white is. Not every Error or Warning event
means there is a serious issue.
Some are excusable at startup time when Windows is booting. Try to
find just the events at the date
and time around your problem.

If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.

When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.

To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.


 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Screen does not look right
Next: FLV Format Playes