Forrmat utworzono 3 września 2011 utworzono 3 września 2011 (edytowane) Witam Od miesiąca walczę z bsod. Nie będę się zagłębiał w moje rozdrażnienie na ten temat, po prostu podam wszystkie dane. Wysypuje się przy oglądaniu filmów, YouTube, przeglądarce. Nieregularnie. Bez zasady. Czasem dzień przerwy, czasem 3 razy dziennie. Wyłączałem Nivide, reinstalowałem sterowniki do grafiki, włączałem i wyłączałem turbo33 ( aplikacja asus do podkręcenia procka). Bez reguły. Laptop ASUS UL80JT procesor i3 ( nie podkręcony ) 4Gb Ramu Windows 7 Home Premium ( zainstalowany jeszcze z salonu - laptop ma 3 miesiące) Karta graficzna - Nvidia Optimus czyli dwie karty na pokładzie: a) Intel HD Graphics b) Nvidia GeForce 310M Dysk twardy - ST9500325AS Minidump: [quote] Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [D:\Programy\Debug\083011-20748-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*D:\Programy\Debug\Raporty *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03015000 PsLoadedModuleList = 0xfffff800`0325a670 Debug session time: Tue Aug 30 23:19:55.281 2011 (UTC + 2:00) System Uptime: 0 days 2:23:44.826 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa802aced008, 2, 1, fffff80003148fe6} Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 ) Followup: MachineOwner --------- 0: 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: fffffa802aced008, 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: fffff80003148fe6, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c4100 fffffa802aced008 CURRENT_IRQL: 2 FAULTING_IP: nt!MiReleaseConfirmedPageFileSpace+86 fffff800`03148fe6 480fb328 btr qword ptr [rax],rbp CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe TRAP_FRAME: fffff8800d552420 -- (.trap 0xfffff8800d552420) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa800aced010 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003148fe6 rsp=fffff8800d5525b0 rbp=00000000ffffffff r8=fffff8800d5525e0 r9=fffffa800bb679f0 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MiReleaseConfirmedPageFileSpace+0x86: fffff800`03148fe6 480fb328 btr qword ptr [rax],rbp ds:a110:fffffa80`0aced010=ffffffffffffffff Resetting default scope LAST_CONTROL_TRANSFER: from fffff800030911e9 to fffff80003091c40 STACK_TEXT: fffff880`0d5522d8 fffff800`030911e9 : 00000000`0000000a fffffa80`2aced008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0d5522e0 fffff800`0308fe60 : fffffa80`06b7cb40 fffffa80`06b7d880 fffffa80`06b7d880 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0d552420 fffff800`03148fe6 : fffff880`0d552ca0 00000000`00000000 fffffa80`07b7f920 fffffa80`049541b8 : nt!KiPageFault+0x260 fffff880`0d5525b0 fffff800`03100fea : 00000000`000000a0 00000000`00000290 00000000`02800000 fffffa80`071ac8b0 : nt!MiReleaseConfirmedPageFileSpace+0x86 fffff880`0d552630 fffff800`0307f0ff : fffffa80`00000000 00000000`0283ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35eb6 fffff880`0d5527f0 fffff800`03090ed3 : ffffffff`ffffffff fffff880`0d552ac8 fffff880`0d552ad8 fffff8a0`00008000 : nt!NtFreeVirtualMemory+0x61f fffff880`0d5528f0 fffff800`0308d470 : fffff800`03367b6a fffffa80`03f54b60 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0d552a88 fffff800`03367b6a : fffffa80`03f54b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage fffff880`0d552a90 fffff800`03367eed : 00000000`00000000 fffff800`03389500 000007ff`fff8a000 00000000`00000000 : nt!PspExitThread+0x5ba fffff880`0d552b90 fffff800`03367ff5 : fffffa80`03f54b60 00000000`00000000 fffffa80`03f54b60 00000000`003b3300 : nt!PspTerminateThreadByPointer+0x4d fffff880`0d552be0 fffff800`03090ed3 : fffffa80`03f54b60 fffff880`0d552ca0 00000000`77d445c0 00000000`0198f910 : nt!NtTerminateThread+0x45 fffff880`0d552c20 00000000`77c9184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0283fba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c9184a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiReleaseConfirmedPageFileSpace+86 fffff800`03148fe6 480fb328 btr qword ptr [rax],rbp SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+86 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86 BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86 Followup: MachineOwner --------- [/quote] [b]Nie mogę sobie przypomnieć żeby blue screen wyskoczył w momencie jak pracuję na zasilaczu... Nie wiem czy ma to jakieś znaczenie.[/b] [b]Błąd wskazuje na kartę graficzną prawda?[/b] Kolejny BSOD z dzisiaj: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Programy\Debug\090311-21294-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*D:\Programy\Debug\Raporty *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`03295670 Debug session time: Sat Sep 3 10:18:21.959 2011 (UTC + 2:00) System Uptime: 0 days 2:32:47.114 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff800030cf539, 0, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+d9 ) Followup: MachineOwner --------- 0: 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: fffff800030cf539, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo FAULTING_IP: nt!KiSwapContext+d9 fffff800`030cf539 c3 ret EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ff100 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80003118588 to fffff800030ccc40 STACK_TEXT: fffff880`05e4f0c8 fffff800`03118588 : 00000000`0000001e ffffffff`c0000005 fffff800`030cf539 00000000`00000000 : nt!KeBugCheckEx fffff880`05e4f0d0 fffff800`030cc2c2 : fffff880`05e4f8a8 fffffa80`045324f0 fffff880`05e4f950 fffffa80`045325b0 : nt! ?? ::FNODOBFM::`string'+0x4977d fffff880`05e4f770 fffff800`030cabca : 00000000`00000000 fffffa80`0bae6bb8 00000000`00000000 fffff800`030cf8a4 : nt!KiExceptionDispatch+0xc2 fffff880`05e4f950 fffff800`030cf539 : 80808080`80808080 00000003`80808080 fffffa80`045324f0 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a fffff880`05e4fae8 80808080`80808080 : 00000003`80808080 fffffa80`045324f0 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0xd9 fffff880`05e4faf0 00000003`80808080 : fffffa80`045324f0 00000000`00000000 00000000`00000000 00000000`00000000 : 0x80808080`80808080 fffff880`05e4faf8 fffffa80`045324f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3`80808080 fffff880`05e4fb00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`045324f0 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiSwapContext+d9 fffff800`030cf539 c3 ret SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!KiSwapContext+d9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiSwapContext+d9 BUCKET_ID: X64_0x1E_c0000005_nt!KiSwapContext+d9 Followup: MachineOwner ---------I kolejny : [quote] Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Programy\Debug\090411-22354-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*D:\Programy\Debug\Raporty *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`03255670 Debug session time: Sun Sep 4 00:25:10.355 2011 (UTC + 2:00) System Uptime: 0 days 4:58:25.900 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa802acdb008, 2, 1, fffff80003143fe6} Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 ) Followup: MachineOwner --------- 0: 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: fffffa802acdb008, 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: fffff80003143fe6, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bf100 fffffa802acdb008 CURRENT_IRQL: 2 FAULTING_IP: nt!MiReleaseConfirmedPageFileSpace+86 fffff800`03143fe6 480fb328 btr qword ptr [rax],rbp CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: uTorrent.exe TRAP_FRAME: fffff8800a9033f0 -- (.trap 0xfffff8800a9033f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa800acdb010 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003143fe6 rsp=fffff8800a903580 rbp=00000000ffffffff r8=fffff8800a9035b0 r9=fffffa80042e8830 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MiReleaseConfirmedPageFileSpace+0x86: fffff800`03143fe6 480fb328 btr qword ptr [rax],rbp ds:fffffa80`0acdb010=91ffff9e7fffffff Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000308c1e9 to fffff8000308cc40 STACK_TEXT: fffff880`0a9032a8 fffff800`0308c1e9 : 00000000`0000000a fffffa80`2acdb008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0a9032b0 fffff800`0308ae60 : 00000000`00000019 0000002b`00000001 00000000`073ffd24 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0a9033f0 fffff800`03143fe6 : fffffa80`047ed8e0 00000000`00000000 fffffa80`07af5e80 fffffa80`0aff7000 : nt!KiPageFault+0x260 fffff880`0a903580 fffff800`030fbfea : 00000000`000001c8 fffff800`03202e80 00000000`07200000 00000000`00000000 : nt!MiReleaseConfirmedPageFileSpace+0x86 fffff880`0a903600 fffff800`0307a0ff : fffffa80`00000000 00000000`073fffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35eb6 fffff880`0a9037c0 fffff800`0308bed3 : ffffffff`ffffffff fffff880`0a903a90 fffff880`0a903a98 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f fffff880`0a9038c0 fffff800`03088470 : fffff800`033099af 00000000`00000010 00000000`00000086 fffff880`0a903a88 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0a903a58 fffff800`033099af : 00000000`00000010 00000000`00000086 fffff880`0a903a88 00000000`00000000 : nt!KiServiceLinkage fffff880`0a903a60 fffff800`03362b8d : 00000000`07120000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlFreeUserStack+0x27 fffff880`0a903a90 fffff800`03362eed : fffff880`00000000 fffff800`03384500 00000000`7ef89000 00000000`00000000 : nt!PspExitThread+0x5dd fffff880`0a903b90 fffff800`03362ff5 : fffffa80`06efd060 00000000`00000000 fffffa80`06efd060 00000000`0370f100 : nt!PspTerminateThreadByPointer+0x4d fffff880`0a903be0 fffff800`0308bed3 : fffffa80`06efd060 fffff880`0a903ca0 00000000`7ef89000 fffffa80`04326070 : nt!NtTerminateThread+0x45 fffff880`0a903c20 00000000`7739184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0370e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7739184a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiReleaseConfirmedPageFileSpace+86 fffff800`03143fe6 480fb328 btr qword ptr [rax],rbp SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+86 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86 BUCKET_ID: X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86 Followup: MachineOwner --------- [/quote]
Gość komentarz 4 września 2011 komentarz 4 września 2011 [php]Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa802acdb008, 2, 1, fffff80003143fe6} Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )[/php] Wykonaj test Ramu programem Memtest. Robisz go kilka godzin lub do pierwszych błędów.
Forrmat komentarz 5 września 2011 Autor komentarz 5 września 2011 (edytowane) Memtest: [url="http://tinypic.pl/oxkg6id3u2kp"][img]http://tinypic.pl/i/00120/oxkg6id3u2kp_t.jpg[/img][/url] HdTune na baterii: [img]http://i54.tinypic.com/no6e5l.jpg[/img] Hdtune na zasilaczu: [img]http://i56.tinypic.com/4h2t1j.jpg[/img] [b]LOG z SeaTools:[/b] a)Smart test --> pass b)Short DST ---> pass b)Long Generic Test --------------- SeaTools for Windows v1.2.0.5 --------------- 2011-09-04 22:10:20 Model: ST9500325AS Serial Number: 6VE663X3 Firmware Revision: 0002SDM1 Long Generic - Started 2011-09-04 22:10:20 Long Generic - Pass 2011-09-05 00:52:20 Kolejny BSOD: [url="http://wklej.org/id/589955/"]Minidump[/url]
tomtom komentarz 11 września 2011 komentarz 11 września 2011 dysk ma mala predkosc maksymalna oraz wysoka temperature. zamontuj wentylator kolo dysku. przetestuj dysk na bad sektory ( zakladka error scan, nie quick a zwykle wolne skanowanie ) i zrob zdjecie zakladki health.
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.