CZAKO utworzono 5 sierpnia 2011 utworzono 5 sierpnia 2011 Oto odczyt mojego pliku powstalego przy blue screenie. Prosze o zapoznanie sie i pomoc co zrobic aby uniknac kolejnych tego typu sytuacji Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Mateusz.000\Desktop\$RWEBRJO.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 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0309d650 Debug session time: Fri Aug 5 18:02:38.487 2011 (UTC + 2:00) System Uptime: 0 days 2:39:38.548 ********************************************************************* * 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, {ffff9a8007fba570, 2, 0, fffff80002ec0648} ***** 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 *** *** *** ************************************************************************* Probably caused by : ntoskrnl.exe ( nt+68648 ) Followup: MachineOwner ---------
Gość komentarz 6 sierpnia 2011 komentarz 6 sierpnia 2011 [code]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[/code] Nie załadowały sie symbole. Nic nie mówi taka analiza błedu, poza faktem że jest jakiś problem sprzetowy.
kabi95 komentarz 6 sierpnia 2011 komentarz 6 sierpnia 2011 Podaj więcej informacji, na forum nie ma wróżek. Przetestuj pamięci np. memtestem.
CZAKO komentarz 7 sierpnia 2011 Autor komentarz 7 sierpnia 2011 Zrobilem zgodnie z intrsukcja z poradnika i wyglada to teraz tak : Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\080711-11965-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03057650 Debug session time: Sun Aug 7 14:54:18.573 2011 (UTC + 2:00) System Uptime: 1 days 20:50:47.635 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff800031dcdfb, 0, 31} Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+42c20 ) Followup: MachineOwner --------- po analizie przez debuggera wyszlo to: 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff800031dcdfb, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000031, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt! ?? ::NNGAKEGL::`string'+42c20 fffff800`031dcdfb 488b4f30 mov rcx,qword ptr [rdi+30h] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000031 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c1100 0000000000000031 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88007334a20 -- (.trap 0xfffff88007334a20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000c000005f rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8009437b60 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800031dcdfb rsp=fffff88007334bb8 rbp=fffff88007334ca0 r8=0000000000000000 r9=0000000000000000 r10=000000000289f760 r11=fffffa8009437b60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt! ?? ::NNGAKEGL::`string'+0x42c20: fffff800`031dcdfb 488b4f30 mov rcx,qword ptr [rdi+30h] ds:0001:00000000`00000030=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002edd5d8 to fffff80002e91d00 STACK_TEXT: fffff880`07334198 fffff800`02edd5d8 : 00000000`0000001e ffffffff`c0000005 fffff800`031dcdfb 00000000`00000000 : nt!KeBugCheckEx fffff880`073341a0 fffff800`02e91382 : fffff880`07334978 00000000`0289f7b8 fffff880`07334a20 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d fffff880`07334840 fffff800`02e8fefa : 00000000`00000000 00000000`00000031 00000000`00000000 00000000`0289f7b8 : nt!KiExceptionDispatch+0xc2 fffff880`07334a20 fffff800`031dcdfb : 00000000`0289f7b8 fffff880`07334ca0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a fffff880`07334bb8 00000000`00000002 : 000007ff`fffd7000 00000000`44eba000 00000000`00000000 00000000`c20c0020 : nt! ?? ::NNGAKEGL::`string'+0x42c20 fffff880`07334c88 000007ff`fffd7000 : 00000000`44eba000 00000000`00000000 00000000`c20c0020 00000000`00000000 : 0x2 fffff880`07334c90 00000000`44eba000 : 00000000`00000000 00000000`c20c0020 00000000`00000000 00000000`44870000 : 0x7ff`fffd7000 fffff880`07334c98 00000000`00000000 : 00000000`c20c0020 00000000`00000000 00000000`44870000 00000000`00000000 : 0x44eba000 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::NNGAKEGL::`string'+42c20 fffff800`031dcdfb 488b4f30 mov rcx,qword ptr [rdi+30h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+42c20 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::NNGAKEGL::_string_+42c20 BUCKET_ID: X64_0x1E_c0000005_nt!_??_::NNGAKEGL::_string_+42c20 Followup: MachineOwner --------- Ktos mnie pokieruje co mam zrobic zeby nie wystepowal ten błąd ?
Gość komentarz 8 sierpnia 2011 komentarz 8 sierpnia 2011 Nie ma jednoznacznej odpowiedzi co powoduje bład, poza faktem, że sterowniki. Zaktualizuj [b]chipset i grafike[/b]. Nie podajesz żadnych okolicznosci, kiedy pojawia się BSOD. Co robisz na kompie? Czy podkręcałeś sprzęt?
CZAKO komentarz 8 sierpnia 2011 Autor komentarz 8 sierpnia 2011 [quote name='squonk' timestamp='1312815397' post='1317359'] Nie ma jednoznacznej odpowiedzi co powoduje bład, poza faktem, że sterowniki. Zaktualizuj [b]chipset i grafike[/b]. Nie podajesz żadnych okolicznosci, kiedy pojawia się BSOD. Co robisz na kompie? Czy podkręcałeś sprzęt? [/quote] Nie podkrecalem bo to dell. Do chipsetu mam najnowsze sterowniki od producenta i do karty graficznej tez. Kiedy przegladam internet w explorerze to sie pojawia.
Emus1994 komentarz 8 sierpnia 2011 komentarz 8 sierpnia 2011 A co sie stanie jak przejdziesz na Mozille/Opere ?? Moze to wina sterownikow IE .... tylko i wylacznie pojawia sie BSOD jak przeglądasz internet na IE ?
Gość komentarz 8 sierpnia 2011 komentarz 8 sierpnia 2011 [quote]Nie podkrecalem bo to dell. [/quote] M powinieneś od razu podać co za komp. Tu jest wątek post nr7 dotyczy DELLA, ponoć rozwiazaniem jest aktualizacja BIOSU i sterowników grafiki[b] [url="http://forums.pcper.com/showthread.php?t=447852"]KLIK[/url][/b] [quote]Kiedy przegladam internet w explorerze to sie pojawia. [/quote] Jak wersja IE? Czy masz zainstalowane najnowszą jave i flasha?
CZAKO komentarz 9 sierpnia 2011 Autor komentarz 9 sierpnia 2011 Sterowniki od karty graficznej i chipsetu sa aktualne. Mam tez najnowsza wersję BIOSu. Wersja IE9, własnie zainstalowalem najnowsza jave i flash playera, zobaczymy czy sie bedzie powtarzal blad. I co do sterowników mam karte quadro i sterowniki wlasnie do niej. Tylko jedne sam windows znalazl a drugie, przeznaczone do kart quadro ja zainstalowalem z jakims calym control panelem itd itp.(Zupelnie inna numeracja wersje sterownika) - ze strony della po service tagu.
Gość komentarz 9 sierpnia 2011 komentarz 9 sierpnia 2011 [quote]I co do sterowników mam karte quadro i sterowniki wlasnie do niej. Tylko jedne sam windows znalazl a drugie, przeznaczone do kart quadro ja zainstalowalem z jakims calym control panelem itd itp.(Zupelnie inna numeracja wersje sterownika) - ze strony della po service tagu. [/quote] I tu może być problem. czy usuwałeś poprzednia wersje sterowników zanim zainstalowałeś te Quadro? Poza tym jak podajesz marke lapka to od razu podaj model.
CZAKO komentarz 9 sierpnia 2011 Autor komentarz 9 sierpnia 2011 [quote name='squonk' timestamp='1312883911' post='1317939'] I tu może być problem. czy usuwałeś poprzednia wersje sterowników zanim zainstalowałeś te Quadro? Poza tym jak podajesz marke lapka to od razu podaj model. [/quote] To nie lapek to dell precision T1500, taka mala WS. Wlasnie nie usówałem, zaraz postaram sie to naprawic, usune wszystko zwiazane z grafika i zainstaluje nowe. Pytanie czy sa jakies programy dodatkowe do czyszczenia pozostalosci po sterownikach ?
Gość komentarz 9 sierpnia 2011 komentarz 9 sierpnia 2011 [quote]Pytanie czy sa jakies programy dodatkowe do czyszczenia pozostalosci po sterownikach ? [/quote] [color="#0000FF"][b][url="http://www.guru3d.com/category/driversweeper/"]KLIK[/url][/b][/color]
CZAKO komentarz 9 sierpnia 2011 Autor komentarz 9 sierpnia 2011 Dzieki wielkie. Juz zainstalowalem nowe. Zobaczymy czy znow cos wyskoczy. Okazalo sie ze spora aktualizacja jest w stosunku do strony della. (192 a 275) numer poczatkowy sterownika. Jakby wyskakiwaly mi kolejne bledy to bede tutaj pisal.
Gość komentarz 9 sierpnia 2011 komentarz 9 sierpnia 2011 (edytowane) [quote]Okazalo sie ze spora aktualizacja jest w stosunku do strony della. (192 a 275) numer poczatkowy sterownika. [/quote] Sterowniki zawsze są nowsze na stronie producenta danego podzespołu. Daj link do nich. Obawiam się ze i chipset można uaktualnić. Wybierasz swój system i ściągasz [b]Inf Update Utility Zip[/b] wersja 9.2.010.10 z 4 kwietnia 2011 [b][url="http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Chipsets&ProductLine=Desktop+Chipsets&ProductProduct=Intel%C2%AE+5+Series+Chipset"]KLIK[/url][/b]
CZAKO komentarz 9 sierpnia 2011 Autor komentarz 9 sierpnia 2011 [quote name='squonk' timestamp='1312888361' post='1317997'] Sterowniki zawsze są nowsze na stronie producenta danego podzespołu. Daj link do nich. Obawiam się ze i chipset można uaktualnić. Wybierasz swój system i ściągasz [b]Inf Update Utility Zip[/b] wersja 9.2.010.10 z 4 kwietnia 2011 [b][url="http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Chipsets&ProductLine=Desktop+Chipsets&ProductProduct=Intel%C2%AE+5+Series+Chipset"]KLIK[/url][/b] [/quote] ten link podeslales dla procesora i5 a ja mam i7 860 - juz stary z 2009 zakup
Gość komentarz 10 sierpnia 2011 komentarz 10 sierpnia 2011 [quote]ten link podeslales dla procesora i5 a ja mam i7 860 - juz stary z 2009 zakup [/quote] Ten link dotyczy chipsetu, a nie procesora. Na tym chipie masz płyte głowną . Chipset obsługuje i7. Takie dane miałem po wejściu na stronę Della. Intel[sup]®[/sup] H57 chipset [color="#0000FF"][b][url="http://www.dell.com/us/business/p/precision-t1500/pd"]KLIK[/url][/b][/color] Żeby nie było nieporozumień pobierz program [b]CPU-Z[/b] i daj obrazek z zakładki [b]Mainboard[/b]. Tam bedzie nazwa chipsetu
CZAKO komentarz 12 sierpnia 2011 Autor komentarz 12 sierpnia 2011 [quote name='squonk' timestamp='1312988074' post='1318892'] Ten link dotyczy chipsetu, a nie procesora. Na tym chipie masz płyte głowną . Chipset obsługuje i7. Takie dane miałem po wejściu na stronę Della. Intel[sup]®[/sup] H57 chipset [color="#0000FF"][b][url="http://www.dell.com/us/business/p/precision-t1500/pd"]KLIK[/url][/b][/color] Żeby nie było nieporozumień pobierz program [b]CPU-Z[/b] i daj obrazek z zakładki [b]Mainboard[/b]. Tam bedzie nazwa chipsetu [/quote] Było 2 dni dobrze i znow blue screen sie pojawił. Oto odczyt i analiza: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\081111-11169-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Machine Name: Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`0305c650 Debug session time: Thu Aug 11 00:39:22.997 2011 (UTC + 2:00) System Uptime: 1 days 11:44:05.058 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, 4972001, 0, fffff70001080000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041284, A PTE or the working set list is corrupt. Arg2: 0000000004972001 Arg3: 0000000000000000 Arg4: fffff70001080000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41284 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: uTorrent.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002eee5d7 to fffff80002e96d00 STACK_TEXT: fffff880`06a1e208 fffff800`02eee5d7 : 00000000`0000001a 00000000`00041284 00000000`04972001 00000000`00000000 : nt!KeBugCheckEx fffff880`06a1e210 fffff800`02eb0db9 : fffffa80`05bfbec8 ffffffff`ffffffff fffff8a0`00000006 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x4ac3 fffff880`06a1e250 fffff800`02e8c75b : faf00001`6d1f8867 fffff680`00024b90 ffffffff`ffffffff 000fffff`ffffffff : nt!MiTerminateWsle+0x29 fffff880`06a1e290 fffff800`02e83ee2 : 00000000`7efd5000 00000000`00000000 fffffa80`05bfbb30 fffffa80`05bfbec8 : nt!MiDecommitPages+0x20b fffff880`06a1eb20 fffff800`02e95f93 : ffffffff`ffffffff 00000000`0215e810 00000000`0215e808 00000000`00004000 : nt!NtFreeVirtualMemory+0x382 fffff880`06a1ec20 00000000`777014fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0215e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777014fa STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4ac3 fffff800`02eee5d7 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ac3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3 BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3 Followup: MachineOwner ---------
Gość komentarz 12 sierpnia 2011 komentarz 12 sierpnia 2011 [quote]PROCESS_NAME: uTorrent.exe [/quote] to już wiesz co
CZAKO komentarz 12 sierpnia 2011 Autor komentarz 12 sierpnia 2011 [quote name='squonk' timestamp='1313158250' post='1320278'] to już wiesz co [/quote] no ok, a to ze dalej bylo tez ntkrnlmp.exe - co to jest wogole od czego zalezne ?
Gość komentarz 12 sierpnia 2011 komentarz 12 sierpnia 2011 Zrób test RAM, programem Memtest. Test ma trwac kilka godzin lub do pierwszych błedów.
CZAKO komentarz 12 sierpnia 2011 Autor komentarz 12 sierpnia 2011 [quote name='squonk' timestamp='1313159997' post='1320285'] Zrób test RAM, programem Memtest. Test ma trwac kilka godzin lub do pierwszych błedów. [/quote] Robilem i nie ma błędówoto nowy blue screen z przed chwili: tym razem wina iexplorer.exe ale czy to znaczy ze bedzie wina zawsze tego co akurat jest odpalone ? Moze ktoś coś doradzić ? Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\081211-11606-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`0304f670 Debug session time: Fri Aug 12 17:32:46.121 2011 (UTC + 2:00) System Uptime: 1 days 14:14:18.183 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ....................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5002, fffff70001080000, b3ca, 4400d481fffffffe} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a7fa ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005002, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 000000000000b3ca Arg4: 4400d481fffffffe Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5002 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ef20e7 to fffff80002e86c40 STACK_TEXT: fffff880`09e4d248 fffff800`02ef20e7 : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`0000b3ca : nt!KeBugCheckEx fffff880`09e4d250 fffff800`02e9419e : 00000000`00000001 00000000`0da5c000 fffff880`09e4d4a0 fffff680`0006d2e0 : nt! ?? ::FNODOBFM::`string'+0x2a7fa fffff880`09e4d340 fffff800`02e84d6e : 00000000`00000001 00000000`0da5c000 00000000`00299e01 00000000`13d98bb0 : nt!MmAccessFault+0x5de fffff880`09e4d4a0 000007fe`ee9c1ffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0320a5a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ee9c1ffa STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+2a7fa fffff800`02ef20e7 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2a7fa FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2a7fa BUCKET_ID: X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2a7fa Followup: MachineOwner ---------
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.