V
Vitor IS
Olá, estava a realizar a instalação de um programa e tive que cancelar por conta de um erro da instalação, desde então meu computador fica tendo esse erro do DPC WATCHDOG VIOLATION, pelo que conversei com o atendente da Microsoft pelo Answer Desk esse erro ocorre por causa de algum arquivo corrompido. Ele me passou uma lista de comandos e eu os fiz:
" Sfc /ScanNow
Dism / Online / Cleanup-image / ScanHealth
Dism /Online /Cleanup-image /CheckHealth
Dism /Online /Cleanup-image /RestoreHealth
Dism /Online /Cleanup-image /StartComponentCleanup
Execute a ferramenta CHKDSK.
Chkdsk.exe é a interface da linha de comando para um programa que verifica a integridade lógica de um sistema de arquivos no Windows. Quando o CHKDSK encontra inconsistências lógicas, executa ações para reparar os dados do sistema de arquivos, contanto que não estejam no modo somente leitura. Clique em Iniciar, na barra de pesquisa digite CMD clique com o botão direito do mouse sobre o aplicativo e selecione a opção Executar como administrador. Agora copie e cole o comando abaixo.
chkdsk /f /r /x /b
Observação você recebera uma mensagem informando que o “CHKDSK não pode ser executado porque o volume está em uso” pressione S para confirmar e pressione Enter e reinicie o computador. Antes de iniciar o sistema ele irá iniciar a verificação esse procedimento pode levar alguns minutos aguarde o procedimento ser finalizado. "
Ele também indicou que: " Caso os problemas de tela azul continuem, faça o reparo com a imagem do Windows 10 seguindo os passos do link abaixo:
Realizando um Inplace Upgrade no Windows 10 versão 1709."
Essa última indicação eu ainda não executei, o problema ocorre de "hora em hora" então eu baixei um programa chamado BlueScreenView e ele me apresentou os seguintes parâmetros
Drump File: 011118-31171-01.dmp
Crash Time: 11/01/2018 07:48:08
Bug Check code: 0x00000133
Parameters
1) 00000000`00000000
2) 00000000`00000501
3) 00000000`00000500
4) fffff801`63e14370
Caused by driver: hal.dll
Caused by Address: hal.dll+33c5
Descrição do arquivo: Hardware Abstraction Layer DLL
Nome do Produto: Microsoft® Windows® Operating System
Versão do Arquivo: 10.0.16299.192 (WinBuild.160101.0800)
Crash Address: ntoskrnl.exe+1756e0
Full patch: C:\WINDOWS\Minidump\011118-31171-01.dmp
Processors count: 4
major version: 15
minor: 16299
drump file size: 2.605.604
drump file time: 11/01/2018 07:58:18
Também usei o whoCrashed, vejam:
On Thu 11/01/2018 07:48:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011118-31171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80163E14370)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
CONCLUSÃO DO WHO CRASHED
2 (SÓ HOJE FORAM 2) crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
rfeco1.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Continue reading...
" Sfc /ScanNow
Dism / Online / Cleanup-image / ScanHealth
Dism /Online /Cleanup-image /CheckHealth
Dism /Online /Cleanup-image /RestoreHealth
Dism /Online /Cleanup-image /StartComponentCleanup
Execute a ferramenta CHKDSK.
Chkdsk.exe é a interface da linha de comando para um programa que verifica a integridade lógica de um sistema de arquivos no Windows. Quando o CHKDSK encontra inconsistências lógicas, executa ações para reparar os dados do sistema de arquivos, contanto que não estejam no modo somente leitura. Clique em Iniciar, na barra de pesquisa digite CMD clique com o botão direito do mouse sobre o aplicativo e selecione a opção Executar como administrador. Agora copie e cole o comando abaixo.
chkdsk /f /r /x /b
Observação você recebera uma mensagem informando que o “CHKDSK não pode ser executado porque o volume está em uso” pressione S para confirmar e pressione Enter e reinicie o computador. Antes de iniciar o sistema ele irá iniciar a verificação esse procedimento pode levar alguns minutos aguarde o procedimento ser finalizado. "
Ele também indicou que: " Caso os problemas de tela azul continuem, faça o reparo com a imagem do Windows 10 seguindo os passos do link abaixo:
Realizando um Inplace Upgrade no Windows 10 versão 1709."
Essa última indicação eu ainda não executei, o problema ocorre de "hora em hora" então eu baixei um programa chamado BlueScreenView e ele me apresentou os seguintes parâmetros
Drump File: 011118-31171-01.dmp
Crash Time: 11/01/2018 07:48:08
Bug Check code: 0x00000133
Parameters
1) 00000000`00000000
2) 00000000`00000501
3) 00000000`00000500
4) fffff801`63e14370
Caused by driver: hal.dll
Caused by Address: hal.dll+33c5
Descrição do arquivo: Hardware Abstraction Layer DLL
Nome do Produto: Microsoft® Windows® Operating System
Versão do Arquivo: 10.0.16299.192 (WinBuild.160101.0800)
Crash Address: ntoskrnl.exe+1756e0
Full patch: C:\WINDOWS\Minidump\011118-31171-01.dmp
Processors count: 4
major version: 15
minor: 16299
drump file size: 2.605.604
drump file time: 11/01/2018 07:58:18
Também usei o whoCrashed, vejam:
On Thu 11/01/2018 07:48:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011118-31171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1756E0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80163E14370)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
CONCLUSÃO DO WHO CRASHED
2 (SÓ HOJE FORAM 2) crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
rfeco1.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Continue reading...