Witam otóż mam problem z wyskakującym bluescreenem spowodowanym przez tzw. afd.sys. Wiem że to podobno jest sterownik sieciowy ale jak naprawić problem nie mam pojęcia dlatego błagam admina i wszystkich o pomoc z góry dziekuje.
Tu log z debugging tolls for windows
icrosoft (R) Windows Debugger Version 6.2.8400.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16988.x86fre.win7_gdr.120401-1505
Machine Name:
Kernel base = 0x82a3d000 PsLoadedModuleList = 0x82b85810
Debug session time: Sun Jul 1 14:49:24.611 2012 (UTC + 2:00)
System Uptime: 0 days 0:42:02.079
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\drivers\afd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {df09dcd2, 2, 0, 8e39831c}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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 : afd.sys ( afd+2931c )
Followup: MachineOwner
---------
Nie wiedziałem jakie linijki dokładnie są potrzebne do rozwiązania tego problemu wiec wklejam wszystko błagam o szybką pomoc.
Przetestuj trochę dłużej, jak faktycznie wszystko będzie wskazywać że jest OK to włącz osłony na nowo - jak BSOD to jesteśmy pewni co go powoduje. Wyłączone osłony nie powinny mieć jakiegoś dramatycznego wpływu czy drastycznie obniżać poziom ochrony.