kaplan8 utworzono 21 marca 2010 utworzono 21 marca 2010 Witam!!! Wczoraj zrobiłem formata dysku C i teraz co jakiś czas jak np. przeglądam strony internetowe albo coś innego robię wyskakuje mi komunikat na niebieskim tle ,,Pojawił sie problem i system windows zostanie zamkniety aby zapobiec uszkodzeniu komputera. IRQL_NOT_LESS_OR-EQUAL itd. później są informacje techniczne ***STOP: (0x7FFD7000,0x00000002 ,0x00000001,0x805AFA2B) POCZYM PISZE ROZPOCZYNANIE ZRZUCANIA FIZYCZNEJ PAMIECI ITD. Bardzo prosze o pomoc co mam zrobic.. pozdrawiam Patryk
raazor90 komentarz 21 marca 2010 komentarz 21 marca 2010 Wykonaj czynności związane z BSOD-em: http://www.forumpc.pl/index.php?showtopic=16074
kaplan8 komentarz 21 marca 2010 Autor komentarz 21 marca 2010 ok zaraz spróbuje mam nadzieje ze pomoże bo przed chwilą znowu miałem niebiesko.. hmm no niestety .. ale chyba cos mi nie wychodzi tzn wszystko robie wg wskazówek ale nie wchodzi CTRL+d.. i ponad to mam Mini032110-01.dmp Mini032110-02.dmp Mini032110-03.dmp Mini032110-04.dmp Mini032110-05.dmp Mini032110-06.dmp i nie wiem od którego mam zacząc..
raazor90 komentarz 21 marca 2010 komentarz 21 marca 2010 Otwórz najnowszy minidump i wklej jego treść na forum. Być może akcja z CTRL+d nie będzie konieczna.
kaplan8 komentarz 21 marca 2010 Autor komentarz 21 marca 2010 (edytowane) po czym poznać który jest najnowszy ??
asmodeuszz komentarz 21 marca 2010 komentarz 21 marca 2010 Po dacie utworzenia pliku Możesz wybrać taką kolumnę w oknie, lub posprawdzać we właściwościach każdego z plików
raazor90 komentarz 21 marca 2010 komentarz 21 marca 2010 Właściwie wszystkie zostały utworzone dzisiaj więc nie ma większej różnicy który.
kaplan8 komentarz 21 marca 2010 Autor komentarz 21 marca 2010 (edytowane) [log]Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini032110-07.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 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 XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Sun Mar 21 21:39:20.031 2010 (GMT+1) System Uptime: 0 days 0:13:20.620 ********************************************************************* * 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 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 100000D1, {18a005, 2, 1, 7c91a2d8} ***** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for nv4_mini.sys *** ERROR: Module load completed but symbols could not be loaded for nv4_mini.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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 : nv4_mini.sys ( nv4_mini+54b01 ) Followup: MachineOwner --------- WARNING: Inaccessible path: 'Probably caused by : nv4_disp.dll ( nv4_disp+fc6e5 )'[/log]
Psycholandia komentarz 21 marca 2010 komentarz 21 marca 2010 [quote]Probably caused by : nv4_mini.sys ( nv4_mini+54b01 )[/quote] Odinstaluj sterowniki od karty graficzne programem Drive Cleaner 3 i zainstaluj najnowsze ze strony producenta.
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.