Como desabilitar hibernação ou Habilitar - Solução - hibernação não desabilitar
O Windows utiliza um
arquivo oculto "Hiberfil.sys" que fica na raiz da pasta onde o
sistema operacional está instalado (C:\), o "Windows Kernel Power
Manager" utiliza esse arquivo para salvar as informações do estado do seu
computador quando entra no modo de hibernação.
O tamanho desse
arquivo é aproximadamente igual a quantidade de memória ram instalada no
computador. Se por algum motivo, esse arquivo for corrompido, o Windows não
consegue desabilitar e nem reabilitar a hibernação na máquina.
Se você estiver com
problema para desabilitar ou habilitar a hibernação na sua máquina, vide a solução
abaixo:
Desabilitar hibernação:
1. Clicar em "Iniciar" e
digitar "cmd";
2. Clicar com o botão direito do mouse
em Prompt de Comando e em seguida "Executar como Administrador";
3.
No prompt de comando, digite powercfg.exe /hibernate off e
pressione ENTER;
4. Ok, agora é só fechar e testar.
Habilitar hibernação:
1. Clicar em "Iniciar" e digitar "cmd";
2. Clicar com o botão direito do mouse em Prompt de Comando e em seguida "Executar como Administrador";
3. No prompt de comando, digite powercfg.exe /hibernate on e pressione ENTER;
4. Ok, agora é só fechar e testar.
Nenhum comentário:
Marcadores:
Soluções,
Windows,
Windows 7
How to display the blogger image youtube video on facebook
To put thumbnails youtube videos to appear on Facebook is very importate to the success of your post , a picture illustrating your link on Facebook is essential to attract the interest of readers .These photos in thumbnails are called " thumbnails " . To put pictures on blogger of youtube videos and then share on Facebook reaping the step below:
1 . Copy the code below and paste your post in " HTML " tab
<iframe allowfullscreen="" frameborder="0" height="315" src="//www.youtube.com/embed/********" width="420"><img src="http://img.youtube.com/vi/********/hqdefault.jpg" alt=""/></iframe>
2 . Where has the ******** you must replace the ID of the video you want to post.
See an example below:
To share this post, you 'll see that the video loads a thumbnail.
If your image does not appear , do not worry , this happens when Facebook does not correctly read your blog or your post is new . You solve this by going to the Facebook page of Debugger and then insert / paste the link in your post and press the " Debug " button. This is done you will see a thumbnail just below the video.
PS . Images must be your size greater than 200 x 200 and avoid placing too large images. Nenhum comentário:
Marcadores:
Good tip
Como exibir no blogger imagem de vídeo do youtube no facebook
Para aumentar o impacto da sua postagem no Facebook, é essencial incluir miniaturas de vídeos do YouTube. Uma imagem ilustrativa do link no Facebook é fundamental para despertar o interesse dos leitores.
Essas imagens em miniatura são conhecidas como "thumbnails". Para adicionar as miniaturas aos vídeos do YouTube no seu blog e, em seguida, compartilhá-las no Facebook, siga as etapas abaixo:
1. Copie o código abaixo e cole-o na seção "HTML" do seu post:
<iframe allowfullscreen="" frameborder="0" height="315" src="//www.youtube.com/embed/ID_DO_VÍDEO" width="420"><img src="http://img.youtube.com/vi/ID_DO_VÍDEO/hqdefault.jpg" alt=""/></iframe>
2. No código acima, substitua "ID_DO_VÍDEO" pelo ID do vídeo que você deseja postar.
Veja um exemplo:
Ao compartilhar essa postagem, você verá que o vídeo será exibido com uma miniatura, chamando a atenção dos usuários.
Caso a imagem não apareça, não se preocupe, isso pode ocorrer quando o Facebook não consegue ler corretamente o seu blog ou quando o post é novo. Para resolver esse problema, siga os passos abaixo:
- Acesse a página de Debugger do Facebook.
- Cole o link do seu post na caixa fornecida.
- Clique no botão "Debug".
- Após a depuração, você verá uma miniatura do vídeo logo abaixo.
Observações:
Certifique-se de que as imagens tenham tamanho superior a 200 x 200 pixels.
Evite usar imagens muito grandes, pois podem levar mais tempo para carregar e afetar a experiência dos usuários.
Marcadores:
Dica,
Facebook
Probably caused by : Ntfs.sys ( Ntfs+992e )
O Windows 7 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 Ntfs.sys.
Vide abaixo como resolver esse problema:
1. Iniciar a máquina com a mídia de instalação do Windows;
2. Entrar no console de recuperação;
3. Abrir o CMD;
4. Navegar até a pasta %windir%\system32\drivers e renomear o arquivo ntfs.sys para ntfs.sys_old
5. Navegar até a pasta %windir%\winsxs e escreva no prompt: dir ntfs.sys /s localizar o arquivo Ntfs.sys;
6. Copiar o arquivo para a pasta %windir%\system32\drivers
Exe: copy ntfs.sys %windir%\system32\drivers
7. Reiniciar o sistema;
8. Ok
Caso você não consiga realizado os passo mencionados logo acima, vide outra solução:
- Iniciar a máquina com a mídia de instalação do Windows;
- Entrar no console de recuperação;
- Abrir o prompt de comando;
- Digite o seguinte comando: dism.exe /image:C:\ /cleanup-image /revertpendingactions
Lembrando que a unidade C: representa o local de instalação do SO
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 [c$\Windows\Minidump\052314-21918-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
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22436.amd64fre.win7sp1_ldr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e636d0
Debug session time: Fri May 23 13:53:09.664 2014 (UTC - 3:00)
System Uptime: 0 days 0:11:22.805
*********************************************************************
* 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
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {3a0000, 0, 0, fffff8a00bfd86b0}
***** 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 : Ntfs.sys ( Ntfs+992e )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000003a0000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8a00bfd86b0
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.
MODULE_NAME: Ntfs
FAULTING_MODULE: fffff80002c1f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52e1bf1c
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x24
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8800143f92e to fffff80002c93540
STACK_TEXT:
fffff880`07659ef8 fffff880`0143f92e : 00000000`00000024 00000000`003a0000 00000000`00000000 00000000`00000000 : nt+0x74540
fffff880`07659f00 00000000`00000024 : 00000000`003a0000 00000000`00000000 00000000`00000000 fffff8a0`0bfd86b0 : Ntfs+0x992e
fffff880`07659f08 00000000`003a0000 : 00000000`00000000 00000000`00000000 fffff8a0`0bfd86b0 fffff880`07659fd0 : 0x24
fffff880`07659f10 00000000`00000000 : 00000000`00000000 fffff8a0`0bfd86b0 fffff880`07659fd0 fffff8a0`0bfd86b0 : 0x3a0000
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs+992e
fffff880`0143f92e ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs+992e
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Ntfs.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Marcadores:
Soluções,
Solutions,
Windows 7