BlackSkill utworzono 26 sierpnia 2014 utworzono 26 sierpnia 2014 (edytowane) Cześć. Wgrałem sobie czysty system windows 8.1. Oryginalny prosto z dremasparka. Wszystko było ok. Zainstalowałem pakiet językowy wszystkie aktualizacje. Kilka niezbędnych programów. Battlefielda 3. Oraz watch dogs. Podczas grania w watch dogs nagle dostałem error że aplikacja zostanie zamknięta. Chciałem włączyć chrome chrome zostało zamknięte. I tak ze wszystkimi aplikacjami. I nagle bsod(irql_not_less_or_equal) Dobra. Restart kompa wchodzę na pulpit włączam chrome. Aplikacja została zamknięta... włączam explorer- aplikacja została zamknięta i nagle kolejny bsod o tej samej nazwie. Restart kompa wchodzę na pulpit i miga sobie tapeta z kolorem szarym. -kolejny bsod (Memory_Management) (irql_not_less_or_equal). I tak kilka restartów Wstawiam też minidumpy w zipie 1 zrzut : [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Rafał\Desktop\1.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 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035 Machine Name: Kernel base = 0xfffff800`39c1e000 PsLoadedModuleList = 0xfffff800`39ee82d0 Debug session time: Tue Aug 26 17:26:58.950 2014 (GMT+2) System Uptime: 0 days 0:03:03.680 ********************************************************************* * 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 1A, {41793, fffff68000023000, 1, 0} ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : ntoskrnl.exe ( nt+153fa0 ) Followup: MachineOwner --------- [/spoiler] Drugi zrzut:[spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Rafał\Desktop\2.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 9600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035 Machine Name: Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`036d72d0 Debug session time: Tue Aug 26 16:46:23.587 2014 (GMT+2) System Uptime: 0 days 1:10:36.320 ********************************************************************* * 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 A, {c8, 2, 1, fffff800034b2baf} ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : ntoskrnl.exe ( nt+a5baf ) Followup: MachineOwner --------- [/spoiler] @edit W powyższych logach nie miałem symboli. Tutaj nowe: [spoiler] ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41793, fffff68000023000, 1, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1abcc ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041793, The subtype of the bugcheck. Arg2: fffff68000023000 Arg3: 0000000000000001 Arg4: 0000000000000000 Debugging Details: ------------------ OVERLAPPED_MODULE: Address regions for 'RTCore64' and 'WUDFRd.sys' overlap BUGCHECK_STR: 0x1a_41793 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80039d9d07c to fffff80039d71fa0 STACK_TEXT: ffffd000`e0b91988 fffff800`39d9d07c : 00000000`0000001a 00000000`00041793 fffff680`00023000 00000000`00000001 : nt!KeBugCheckEx ffffd000`e0b91990 fffff800`39c8e6d4 : 00000000`0000001e 00000000`1912d18a 00000000`80000000 7f18ca4c`99be7983 : nt! ?? ::FNODOBFM::`string'+0x1abcc ffffd000`e0b91c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x244 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+1abcc fffff800`39d9d07c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1abcc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53388e13 FAILURE_BUCKET_ID: X64_0x1a_41793_nt!_??_::FNODOBFM::_string_+1abcc BUCKET_ID: X64_0x1a_41793_nt!_??_::FNODOBFM::_string_+1abcc Followup: MachineOwner --------- [/spoiler] [spoiler] ****************************************************************************** * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {c8, 2, 1, fffff800034b2baf} Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+2f ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000000000000c8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800034b2baf, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: fffff800036c4ce0: Unable to get special pool info fffff800036c4ce0: Unable to get special pool info unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 00000000000000c8 CURRENT_IRQL: 2 FAULTING_IP: nt!KeAcquireInStackQueuedSpinLock+2f fffff800`034b2baf 488711 xchg rdx,qword ptr [rcx] DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: watch_dogs.exe LAST_CONTROL_TRANSFER: from fffff8000356cae9 to fffff80003560fa0 STACK_TEXT: ffffd001`e74313e8 fffff800`0356cae9 : 00000000`0000000a 00000000`000000c8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx ffffd001`e74313f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!KeAcquireInStackQueuedSpinLock+2f fffff800`034b2baf 488711 xchg rdx,qword ptr [rcx] SYMBOL_NAME: nt!KeAcquireInStackQueuedSpinLock+2f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53388e13 FAILURE_BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+2f BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+2f Followup: MachineOwner --------- [/spoiler]
Youki komentarz 26 sierpnia 2014 komentarz 26 sierpnia 2014 Przetestuj pamięci RAM za pomocą programu memtest86+
BlackSkill komentarz 26 sierpnia 2014 Autor komentarz 26 sierpnia 2014 Spoczko. Ale tak nagle by pamięci padły ? Teraz już nie występuje ten problem.
Youki komentarz 26 sierpnia 2014 komentarz 26 sierpnia 2014 Teraz już nie występuje ten problem. A coś zrobił ?
BlackSkill komentarz 26 sierpnia 2014 Autor komentarz 26 sierpnia 2014 No właśnie nic ;/. Ale boje sie gierki odpalać xd
BlackSkill komentarz 27 sierpnia 2014 Autor komentarz 27 sierpnia 2014 Grałem Dobre 2 i pół godzinki w watch dogs. I wszystko ok. Gra wymagająca. Użycie procka 80%. Phenom II x4 955 3.2 ghz aktualnie 3.7ghz możliwe 4ghz ale oszczędzam ;)
BlackSkill komentarz 31 sierpnia 2014 Autor komentarz 31 sierpnia 2014 Siema. Grałem w watch dogs i znowu blue screen :) Tym razem podczas gry nagle. Z tym że był tylko niebieski ekran bez napisów żadnych. Minidumpa też ni ma :/ ?
Youki komentarz 31 sierpnia 2014 komentarz 31 sierpnia 2014 Jakoś nie doczytałem, specyfikacja PC wraz z marką i mocą zasilacza ?
BlackSkill komentarz 31 sierpnia 2014 Autor komentarz 31 sierpnia 2014 (edytowane) Płytka: Gigabyte Ga-ma770t-ud3p Karta graf: Amd Radeon Hd 7850 Procek: Amd Phenom II x4 955BE 3.2ghz podkręcony do 3.7ghz 4ghz też jest stabilnie. Temperatury ok. 59-60c Testowane prime 95. Zasilacz: Chieftec Gpa-500S8 500w Ram: (Według cpu-z.) 2gb Patriot 2gb Nanya Technology Na windows 7 wszystko było okej..... Artefaktów w grze też nie mam. Nic. Tylko nagle jeb.
BlackSkill komentarz 31 sierpnia 2014 Autor komentarz 31 sierpnia 2014 (edytowane) Niee.... Zaraz odpalę... @edit ile razy robić test memtestem jednej kości ? @edit Test zrobiony. Zero błędów. @edit Po włączeniu kompa i przeglądarki bluescreen/ Minidump: [spoiler] ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7A, {fffff6e800eba960, ffffffffc00000c0, 11febbbe0, ffffd001d752c000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ecfd ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: fffff6e800eba960, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc00000c0, error status (normally i/o status code) Arg3: 000000011febbbe0, current process (virtual address for lock type 3, or PTE) Arg4: ffffd001d752c000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc00000c0 - To urz BUGCHECK_STR: 0x7a_c00000c0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff803b8e0d1ad to fffff803b8dddfa0 STACK_TEXT: ffffd001`d728d818 fffff803`b8e0d1ad : 00000000`0000007a fffff6e8`00eba960 ffffffff`c00000c0 00000001`1febbbe0 : nt!KeBugCheckEx ffffd001`d728d820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ecfd STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+1ecfd fffff803`b8e0d1ad cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1ecfd FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53388e13 FAILURE_BUCKET_ID: X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+1ecfd BUCKET_ID: X64_0x7a_c00000c0_nt!_??_::FNODOBFM::_string_+1ecfd Followup: MachineOwner --------- [/spoiler]
Youki komentarz 31 sierpnia 2014 komentarz 31 sierpnia 2014 Profilaktycznie zaaktualizuj BIOS. Pokaż screena z zakładki Health z programu HD Tune. Przeskanuj system za pomocą programu MalwareBytes AntiMalware.
Que komentarz 1 września 2014 komentarz 1 września 2014 Ogólnie procesory AMD są zupełnie nie gamingowe. Ile razy testowałeś pamięci? Przetestuj przynajmniej 5-6 razy lecz niektórzy zalecają nawet 10+ :) Zanim wyciągniesz jedną kość to dotknij np, grzejnika żeby uniknąć uszkodzenia pamięci.
BlackSkill komentarz 1 września 2014 Autor komentarz 1 września 2014 Wiem wiem o elektro statyczności . Pamięci testowałem 3 razy. Problem robił sterownik do karty dźwiękowej. (Zainstalowałem stary) + Komp był/jest niestabilny przez padającą płytę. Płyta wczoraj odmówiła posłuszeństwa , nie ładowała w ogóle biosu. Byłem u kumpla wygrzaliśmy obydwa mostki nic to nie dało płyta dalej martwa w ogóle nie startowała. Ale złożyłem kompa. i jakimś cudem ruszyła. Chodzi pewnie do czasu :) Jaką płytę polecicie do oc Amd Phenom II x4 955BE ???
Que komentarz 1 września 2014 komentarz 1 września 2014 (edytowane) Ile chcesz wydać na owy motherboard? Od siebie moge Ci powiedzieć, że jeśli masz zamiar kręcić do 3.7 -3.8GHz to weź jakiegoś asrocka 870 extreme3 jeśli nawet do 4GHz, to polecam Asusa i jeśli nie masz to jakieś porządnie chłodzenie, dam Ci niżej link do strony producenta żebyś sobie co nieco o niej poczytał. http://www.asus.com/pl/Motherboards/M4A89GTD_PRO/
BlackSkill komentarz 1 września 2014 Autor komentarz 1 września 2014 (edytowane) Chłodzenie na procka mam. Na 4ghz 60c więc tak wystarczająco. Mogło być chłodniej ale ok. Na płytę 300zł http://allegro.pl/asus-m4a89gtd-pro-am3-ddr3-fv-hdmi-dvi-ios-i4562352847.html Co myślisz o tej aukcji ? Co jest w wersji box ? Dodatkowo ?
Que komentarz 1 września 2014 komentarz 1 września 2014 za 300zł bodajże jest ten asrock lub coś koło sumy 300zł :)
BlackSkill komentarz 1 września 2014 Autor komentarz 1 września 2014 (edytowane) http://www.morele.net/plyta-glowna-asrock-970-pro3-r2-0-572933/ A to ? @edit To nie extreme.... @edit... To co brać bo zamawiam. http://allegro.pl/asus-m4a89gtd-pro-am3-ddr3-fv-hdmi-dvi-ios-i4562352847.html Wersja OEM bez kabli niczego ? http://allegro.pl/nowy-asrock-970-extreme3-box-i4565950544.html Wersja Box.
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.