ciapus4 Opublikowano 3 Grudnia 2011 Zgłoś Udostępnij Opublikowano 3 Grudnia 2011 Witam, po reinstalacji systemu mam niebieski ekran, może ktoś pomóc. Oto minidump : Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\120311-13634-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e70 Debug session time: Sat Dec 3 21:21:13.018 2011 (GMT+1) System Uptime: 0 days 0:10:07.017 ********************************************************************* * 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 .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000B8, {fffffa8005af6b60, fffff880031dffc0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : nvlddmkm.sys ( nvlddmkm+1dba57 ) Followup: MachineOwner --------- Odnośnik do komentarza
3oo Opublikowano 3 Grudnia 2011 Zgłoś Udostępnij Opublikowano 3 Grudnia 2011 Probably caused by : nvlddmkm.sys ( nvlddmkm+1dba57 ) Jakiś problem ze sterownikiem nvidii. Masz aktualny? Właściwą wersję "bitową"? Co to za karta grafiki? Jak wyglądają temperatury? Pokaż screen z HWiNFO (zakładka Sensors) lub HWMonitor'a. Programy te możesz pobrać w wersji portable, wypakować, uruchomić... A swoją drogą jeśli to ten dysk o którym myślę, że w komentarzach do nich widziałem, że system na nim lubi sypać BSOD-ami - aktualizacja firmware'u nie rozwiązuje ponoć problemu. Ale, ci... sza... Odnośnik do komentarza
ciapus4 Opublikowano 3 Grudnia 2011 Autor Zgłoś Udostępnij Opublikowano 3 Grudnia 2011 Odnośnik do komentarza
3oo Opublikowano 4 Grudnia 2011 Zgłoś Udostępnij Opublikowano 4 Grudnia 2011 Zaktualizuj BIOS. Przeinstaluj stery grafy. Temperatury wydają się OK. Odnośnik do komentarza
ciapus4 Opublikowano 4 Grudnia 2011 Autor Zgłoś Udostępnij Opublikowano 4 Grudnia 2011 Witam, uruchomiłem rano komp i teraz mam takie cudo....Probably caused by : rdyboost.sys i takie Probably caused by : ntoskrnl.exe, co jest grane ? Odnośnik do komentarza
3oo Opublikowano 4 Grudnia 2011 Zgłoś Udostępnij Opublikowano 4 Grudnia 2011 (edytowane) Jako, że wygląda to na losowe BSOD-y przetestuj pamięć RAM. Memtest powinien trwać kilka godzin lub do pierwszego błędu. Znajdziesz go w zestawie parted magic (przy bootowaniu w Extras Menu), lub na stronce http://www.memtest.org/ Zrób to tym bardziej, jeśli w sygnaturce błędu jest MEMORY_MANAGEMENT. Wpinałeś nowy dysk, więc może coś się poluzowało. Warto sprawdzić podłączenia. Wypiąć RAM, przeczyścić styki i gniazda na płycie sprężonym powietrzem a najlepiej alkoholem izopropylowym (dostępny też w sprayu w sklepach z elektroniką). Zabrudzenia i/lub poluzowania mogą być jedną z przyczyn BSOD-ów. Edytowane 4 Grudnia 2011 przez 3oo Odnośnik do komentarza
ciapus4 Opublikowano 5 Grudnia 2011 Autor Zgłoś Udostępnij Opublikowano 5 Grudnia 2011 Witam, tak myślałem i miałem problem z sterami do czipsetu miałem znak - ? -w menadżerze i kombinowałem ze sterami, w związku z tym, że system był świeży po instalce, jeszcze raz format i system nie ma blue ekranów, także chyba stery coś mieszały. Odnośnik do komentarza
Rekomendowane odpowiedzi