Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety •

Pełna wersja: Problem z plikiem ntoskrnl.exe i blue screen
Aktualnie przeglądasz uproszczoną wersję forum. Kliknij tutaj, by zobaczyć wersję z pełnym formatowaniem.
Otóż mam problem wyskoczył mi już chyba setny raz blue screen więc zbadałem przyczynę tego programem Debugger Windows .
Ten program wskazał plik który jest powodem tego całego zamieszania . ( ntoskrnl.exe )
Mój system to Win 7 professional 64 bit
Bardzo proszę o udzielenie jakieś pomocy, gdzie szukać problemu, co zrobić wielkie dzięki

Kod:
Microsoft (R) Windows Debugger  Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\111113-32479-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 2
*** WARNING:  Unable to verify timestamp for ntoskrnl.exe
*** ERROR:  Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS Personal
Built by:  7601.18247.amd64fre.win7sp1_gdr.130828-1532
Kernel base = 0xfffff800`04209000 PsLoadedModuleList = 0xfffff800`0444c6d0
Debug session time:  Mon Nov 11 10: 10: 50.826 2013 (GMT+1)
System Uptime:  0 days 0: 36: 17.685
*********************************************************************
* 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 2
*** 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
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff880017306fd}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 2
*** WARNING:  Unable to verify timestamp for NETIO.SYS
*** ERROR:  Module load completed but symbols could not be loaded for NETIO.SYS
*** WARNING:  Unable to verify timestamp for mssmbios.sys
*** ERROR:  Module load completed but symbols could not be loaded for mssmbios.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 load image \SystemRoot\system32\drivers\mfefirek.sys, Win32 error 2
*** WARNING:  Unable to verify timestamp for mfefirek.sys
*** ERROR:  Module load completed but symbols could not be loaded for mfefirek.sys
*** WARNING:  Unable to verify timestamp for hal.dll
*** ERROR:  Module load completed but symbols could not be loaded for hal.dll
Unable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 2
*** WARNING:  Unable to verify timestamp for mfehidk.sys
*** ERROR:  Module load completed but symbols could not be loaded for mfehidk.sys
Probably caused by :  NETIO.SYS ( NETIO+106fd )

Followup:  MachineOwner
---------
Jak nie potrafisz analizować i nie masz w pełni kompletnego debuggera (brak symboli), to wrzuć pliki dmp. Poza tym gdzie masz wpisane, że spowodowane jest to plikiem, który przechwytuje zdarzenie? Jakoś widać, że
Cytat:Probably caused by : NETIO.SYS ( NETIO+106fd )
więc wpisz w Google "bccode D1 netio.sys" i uzyskasz potrzebne informacje
A tak przy okazji wszelkie dane wyjściowe z komend wkłada się do znaczników code aby nie rozjeżdżały wątku
Przekierowanie