Tela azul indicando erro no arquivo wdf01000.sys

[Muguetsu]

A primeira vez que deu tela azul foi quando eu tava jogando Skyrim. Depois começou a dar enquanto eu jogava nos emuladores de Playstation 2 e Game Cube.

Estranho que com o Skyrim o problema parou depois dele crashar umas três vezes. Fiquei mais de 3 horas seguidas jogando ontem sem nenhum problema. Testei com o BF3 também. Fiquei um bom tempo jogando, e nada. Mas os emuladores ainda tão dando problema, com menos de uma hora de jogo

O BlueScreen Viewer fornece isso:

Quando eu coloco no WinDbg, log que aparece é esse:

Microsoft ® Windows Debugger Version 6.12.0002.633 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Tiago\Desktop\030413-14898-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\WINDOWS\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

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 (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431

Machine Name:

Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e48670

Debug session time: Sun Mar 3 21:37:50.623 2013 (UTC - 3:00)

System Uptime: 0 days 2:53:43.513

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

.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

..............................................................

................................................................

...........................

Loading User Symbols

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88005bc6638, 2, 8, fffff88005bc6638}

Unable to load image \SystemRoot\system32\DRIVERS\MijXfilt.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for MijXfilt.sys

*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.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 ***

*** ***

*************************************************************************

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

Unable to open image file: c:\WINDOWS\symbols\ntoskrnl.exe\50E799355e7000\ntoskrnl.exe

O sistema não pode encontrar o arquivo especificado.

*************************************************************************

*** ***

*** ***

*** 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 : MijXfilt.sys ( MijXfilt+1b638 )

Followup: MachineOwner

---------

Não sei se tá faltando alguma coisa nesse log do WinDbg. Eu adicionei o caminho dos símbolos antes de fazer o debug, mas ele continuou acusando ausência de símbolos.

Enfim, quem puder ajudar, agradeço desde já

[Muguetsu]

Consegui resolver aqui. O problema começou com um arquivo de uma atualização do Motion in Joy. O nome do arquivo é MijXfilt.sys. Foi só deletar (apesr de que precisa liberar as permissões do system32, o que já deu um trabalhinho por si só).

Se fosse possível editar o título, eu colocaria o nome do arquivo lá pra facilitar a pesquisa de alguém que porventura tenha o mesmo problema. Podem marcar o tópco como resolvido