Solução - Tela Azul ao clicar com botão direito do mouse em quaisquer ícones na Área de Trabalho - nvlddmkm.sys
Análise do problemaNo momento que o cliente individual clicava com botão direito do mouse em quaisquer ícones na "Área de Trabalho", o computador apresentava tela azul e em seguida reinicializava.
Utilizado a ferramenta WinDbg (Windows Debugging), analisamos o despejo de memória na máquina para descobrirmos o que estava causado a tela azul. Verificamos que o problema estava sendo causado por uma falha do arquivo nvlddmkm.sys para Windows Vista. Esse arquivo é utilizado pelo drive da placa de vídeo Nvidia FX5500, renomeamos o nvlddmkm.sys para nvlddmkm.old e testamos o clique do mouse com o lado direito, funcionou normalmente. Porem, as opções de resolução e propriedades do vídeo foram afetadas; já que o arquivo nvlddmkm.sys tinha sido renomeado.
O problema foi resolvido atualizado o drive da placa de vídeo.
Ante de proseguir com o passos abaixo, faça o download do drive no site do fabricante do seu dispositivo. No meu caso foi o nvidia,
Obs. O mesmo driver pode servir para vários modelos.
Solução
1. Abrir o "Gerenciador de Dispositivos" pressionado as teclas "bandeira do windows + R" escrever: devmgmt.msc;
2. No gerenciador de dispositivos, vá para "Adaptadores de Vídeo";
3. Selecionar o dispositivo e clicar com o lado direto do mouse e "Atualizar Driver";
4. Clicar em "Procurar software de driver no computador";
5. Apontar para a pasta onde você fez o download do drive;
6. Aguardar o final da instalação e em seguida realizar a máquina;
7. Realizar os testar e ok.
Vide o Arquivo DUMP¹ convertido em txt que foi analisado:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\052214-24039-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22436.amd64fre.win7sp1_ldr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e446d0
Debug session time: Thu May 22 10:49:56.762 2014 (UTC - 3:00)
System Uptime: 0 days 0:16:59.717
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff880078c3e26, fffff88004a8cab0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+ae26 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880078c3e26, Address of the instruction which caused the bugcheck
Arg3: fffff88004a8cab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80002c00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru o no 0x%08lx fez refer ncia mem ria no 0x%08lx. A mem ria n o p de ser %s.
FAULTING_IP:
nvlddmkm+ae26
fffff880`078c3e26 418b4008 mov eax,dword ptr [r8+8]
CONTEXT: fffff88004a8cab0 -- (.cxr 0xfffff88004a8cab0)
rax=00000000c1d00071 rbx=0000000000000001 rcx=fffff88004a8d4b0
rdx=0000000000000001 rsi=fffff8800832f640 rdi=fffff88004a8d810
rip=fffff880078c3e26 rsp=fffff88004a8d490 rbp=00000000070000a6
r8=0000000000000000 r9=fffff8800832fe50 r10=0000000000000001
r11=00000000aa000001 r12=0000000000000038 r13=0000000000000001
r14=fffffa802b3f7000 r15=000000000016a838
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0xae26:
fffff880`078c3e26 418b4008 mov eax,dword ptr [r8+8] ds:002b:00000000`00000008=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880078c3e26
STACK_TEXT:
fffff880`04a8d490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xae26
FOLLOWUP_IP:
nvlddmkm+ae26
fffff880`078c3e26 418b4008 mov eax,dword ptr [r8+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+ae26
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88004a8cab0 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
¹ DUMP, Despejo de memória - memory dump, é um arquivo gerado automaticamente pelo SO com uma cópia parcial da memória no momento do erro. Nenhum comentário:
Marcadores:
Driver,
Microsoft,
Soluções,
Solutions,
Windows,
Windows 10,
Windows 10 Enterprise,
Windows 11,
Windows 7
Como compartilhar a internet do smartphone
Realizamos testes de
compartilhamento da conexão de dados no Smartphone Motorola RAZ/RD1 nas funções
“Tethering - Vinculo USB / Wi-Fi portátil”. Verificamos que é possível compartilhar
a internet do seu smartphone de três maneiras:
Cabo USB – Utilizado o
cabo que acompanha seu Smartphone, conecte o seu celular ao computador e em
seguida toque na opção, “Vínculo USB”;
Wi-Fi portátil – É um ponto de
acesso muito parecido com os padrões encontrados nos roteadores wireless. Nesse
modo é possível configurar uma rede SSID e compartilhar com outros dispositivos
próximo de você. (SSID, Service Set IDentifier) esse é o nome que será dado para identificar o seu ponto
de acesso Wi-Fi),
Na função Wi-Fi, ainda
é possível contar com algumas opções de segurança e serviço de DHCP,
criptografia e senha segura utilizado o protocolo WPA2.
Bluetooth – Esse método não é
muito utilizado devido a suas limitações. Você pode ativar o ponto de
acesso usando Bluetooth, marcando a opção correspondente dentro da
opção Tethering e Roteador.
É recomendado
utilizar este serviço no modo “Vinculo USB” (Com o cabo conectado ao computador)
com isso, o smartphone continuará com sua carga. Em teste de laboratório, no modo
Wi-Fi portátil, o smartphone “Motorola Moto G XT1032” passou 16h conectado
direto.
Tempo da bateria:
Smartphone: Motorola
Moto G XT1032
No modo “Wi-Fi portátil”: 16h
No modo “Vinculo USB”: Não
descarrega
Smartphone: BlackBerry
9360
No modo “Wi-Fi portátil”: 5:30h
No modo “Vinculo USB”: Não
descarrega
Configurando um
ponto de acesso Wi-Fi portátil direto
do Smartphone Android
1.
Toque em “Configurar/Ajuste”
2.
Dentro das
Configurações, procure pela opção “Tethering
e Roteador”. Dependendo da versão do Android, esta opção pode
estar em um submenu "mais",
que guarda outras opções.
3.
Em “Tethering e Roteador” toque na
opção desejada
Nesse exemplo, vamos
criar um ponto de acesso Wi-Fi
4.
Toque na opção “Wi-Fi
portátil”.
5.
Configurações
necessárias para o ponto “Wi-Fi portátil”:
SSID da rede - Aceite o nome que será sugerindo ou entre com um novo nome;
Cana preferido – Deixar como “Automático”;
Endereço de início (DHCP)
do cliente – Não precisa alterar;
Segurança – deve utilizar o protocolo WPA2
PSK;
Senha – A senha deverá ser criada pelo Cliente individual e deve ter no mínimo 8
caracteres.
6.
Ok, agora é só testar
a conexão.
Nenhum comentário:
Marcadores:
3G Modem,
Android,
Dica,
Smartphone
Calculadoras on-line IP - cálculos de rede de sub-rede
Vide abaixo uma lista de calculadoras on-line que permite realizar cálculos de sub-redes usando a classe de rede, endereço IP, máscara de sub-rede, bits de sub-rede, bits da máscara e IP de sub-redes...
Nenhum comentário:
| Site | Descrição | Imagem da Calc |
 jodies.de / ipcalc | Simples Perl calculadora IP baseado com características básicas |  |
| subnet-calculator.com | Poderosa Java ferramenta para cálculos de IP / sub-rede |  |
 subnetmask.info | Detalhada JavaScript calculadora IP para gerar uma lista de sub-redes |  |
 faqintosh.com | Simples JavaScript calculadora IP |  |
| subnetonline.com | Profissional e muito detalhada |  |
 t1shopper.com | Poderosa ferramenta definida para calcular máscaras de sub-rede, endereços IP, número de hosts e etc |  |
Marcadores:
Boa Dica