lukaszek19831 0 Napisano 11 Kwietnia 2012 Udostępnij Napisano 11 Kwietnia 2012 Witam proszę was o pomoc gdyż nie mam pojęcia co mam robic podczas działania komputera ciągle co jakis czas wywala mi blue screan . System windows 7 ultimate 64bit Procek AMD 955BE Grafika Gigabyte ATI 6950 RAm Kingston HyperX 8gb DZwiękowa ASUS Xonar HDAV 1.3 Zasilacz OCZ ZX 650 Zmieniłem system i dalej to samo na nowym wyskoczyły mi już 3 po zainstalowani programiku blu screan viev za każdym razem inny . Bug check String ATTEMPTED_WRITE_TO_READONLY_MEMORY Bug check Code 0x000000be Caused by driver afd.sys Caused by adress afd.sys+155d0 Crash Address ntoskrnl.exe+7cd40 To 2 Bug check SYSTEM_SERVICE_EXCEPTION Bug check 0x0000003b Caused by driver atikmdag.sys Caused by adress atikmdag.sys+40f720 Crash Address ntoskrnl.exe+7cd40 A to 3 dzisiejszy Bug check PAGE_FAULT_IN_NONPAGED_AREA Bug check 0x00000050 Caused by driver ntoskrnl.exe Caused by adress ntoskrnl.exe+7cd40 Crash Address ntoskrnl.exe+7cd40 Po prostu nie wiem co już mam robic sprawdziłem pamięc i wszystko jest ok . Cytuj Link to post Share on other sites
sebki1 596 Napisano 11 Kwietnia 2012 Udostępnij Napisano 11 Kwietnia 2012 Sproboj sprawdzic bledy na dysku twardym z opcja naprawy plikow. Cytuj Link to post Share on other sites
Biafra 16739 Napisano 11 Kwietnia 2012 Udostępnij Napisano 11 Kwietnia 2012 Masz SSD? Cytuj Link to post Share on other sites
lukaszek19831 0 Napisano 11 Kwietnia 2012 Autor Udostępnij Napisano 11 Kwietnia 2012 Mam samsung 830 128gb. Ale z tego co pamiętam na normalnym też miałem bsod. Sprawdziłem dysk i wszystko jest ok .Ale coś mi sie wydaje że to sprzetowe jest strzelam że albo zasilacz albo dzwięk albo grafa . Ramy sprawdziłeł jest ok zasilacza nie jestem w stanie . Cytuj Link to post Share on other sites
Lukaszbass 116 Napisano 11 Kwietnia 2012 Udostępnij Napisano 11 Kwietnia 2012 Sprawdz pamięć komputera w memtescie. Cytuj Link to post Share on other sites
philips 78 Napisano 12 Kwietnia 2012 Udostępnij Napisano 12 Kwietnia 2012 Tutaj znajduje się kompletna instrukcja jak należy odczytać co pc'owi dolega. (zalecam również wykonanie pkt 1a, raport wtedy jest czytelniejszy i łatwo można się w nim odnaleźć - na win7 pewnie będzie podobnie). Cytuj Link to post Share on other sites
lukaszek19831 0 Napisano 12 Kwietnia 2012 Autor Udostępnij Napisano 12 Kwietnia 2012 Mem Test nic nie wykazał . Zamieszczam jeszcze takie dane 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 (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c90650 Debug session time: Wed Apr 11 20:23:48.632 2012 (GMT+2) System Uptime: 0 days 3:53:50.146 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff87ff94aff89, 8, fffff87ff94aff89, 5} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43d41 ) Followup: MachineOwner to 2 Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041012-8470-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available 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 (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c48650 Debug session time: Tue Apr 10 20:12:40.808 2012 (GMT+2) System Uptime: 0 days 0:39:51.932 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88004e73720, fffff8800c2ce1f0, 0} Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : atikmdag.sys ( atikmdag+40f720 ) Followup: MachineOwner a to 3 Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\040412-8112-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available 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 (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c93650 Debug session time: Wed Apr 4 18:23:36.470 2012 (GMT+2) System Uptime: 0 days 7:10:10.984 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {fffff880040b95d0, 8000000220ab9121, fffff8800318b700, a} Probably caused by : afd.sys ( afd!AfdReturnBuffer+7f ) Followup: MachineOwner --------- --------- to jeszcze do 3 ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff880040b95d0, Virtual address for the attempted write. Arg2: 8000000220ab9121, PTE contents. Arg3: fffff8800318b700, (reserved) Arg4: 000000000000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: System CURRENT_IRQL: 2 TRAP_FRAME: fffff8800318b700 -- (.trap 0xfffff8800318b700) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000001a rbx=0000000000000000 rcx=fffffa80079f7d70 rdx=fffffa800a31b7e0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880040e508f rsp=fffff8800318b890 rbp=000000000000001c r8=0000000000000000 r9=0000000000000000 r10=fffffa800a414dd0 r11=fffffa800a31b1b8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe cy afd!AfdReturnBuffer+0x7f: fffff880`040e508f ff153b45fdff call qword ptr [afd!_imp_ExpInterlockedPushEntrySList (fffff880`040b95d0)] ds:b040:fffff880`040b95d0={nt!RtlpInterlockedPushEntrySList (fffff800`02ac3cc0)} Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a767b7 to fffff80002acbd40 STACK_TEXT: fffff880`0318b598 fffff800`02a767b7 : 00000000`000000be fffff880`040b95d0 80000002`20ab9121 fffff880`0318b700 : nt!KeBugCheckEx fffff880`0318b5a0 fffff800`02ac9e6e : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`079f7d70 : nt! ?? ::FNODOBFM::`string'+0x4387b fffff880`0318b700 fffff880`040e508f : fffff880`0318ba38 00000000`00000000 00000000`00000000 fffffa80`0a414cb0 : nt!KiPageFault+0x16e fffff880`0318b890 fffff880`040ea053 : 00000000`00000074 fffffa80`08729d30 00000000`00000000 fffffa80`09cd8c90 : afd!AfdReturnBuffer+0x7f fffff880`0318b8d0 fffff880`01956bb4 : 00000000`00000000 fffffa80`09726e00 00000000`00000000 fffff880`055513bc : afd!AfdTLBufferedSendComplete+0xc3 fffff880`0318b970 fffff880`0195567a : fffffa80`07a26490 fffff880`0194db00 fffffa80`074eaa01 00000000`00000000 : tcpip!TcpTcbReceive+0x4f4 fffff880`0318bb20 fffff880`019572ab : fffff880`06d6dfe2 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpMatchReceive+0x1fa fffff880`0318bc70 fffff880`0194e1c7 : fffffa80`07a26490 fffffa80`07a263a0 fffffa80`0000f3d7 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x36b fffff880`0318bd40 fffff880`0194dd3a : 00000000`00000000 fffff880`01a6d9a0 fffff880`0318bf00 00000000`00000001 : tcpip!IppDeliverListToProtocol+0x97 fffff880`0318be00 fffff880`0194d339 : fffff880`0318bec0 fffffa80`09cd8d48 fffffa80`09cd8bc0 fffff880`0318bef0 : tcpip!IppProcessDeliverList+0x5a fffff880`0318bea0 fffff880`0194b0af : fffffa80`07d091a0 fffffa80`07a19000 fffff880`01a6d9a0 00000000`07dc3301 : tcpip!IppReceiveHeaderBatch+0x23a fffff880`0318bf80 fffff880`0194a6a2 : fffffa80`06a52010 00000000`00000000 fffffa80`07dc3301 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x64f fffff880`0318c180 fffff880`01949b3a : fffffa80`07dc3330 fffff880`0318c2b0 fffffa80`07dc3330 fffffa80`08850000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`0318c260 fffff800`02ad7a88 : fffffa80`0824c030 00000000`00004800 fffff880`0316efc0 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`0318c2b0 fffff880`0194a202 : fffff880`01949a60 fffffa80`088521b0 fffffa80`0839f102 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8 fffff880`0318c390 fffff880`017a50eb : fffffa80`07fd5010 00000000`00000000 fffffa80`07ce31a0 fffffa80`07ce31a0 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`0318c400 fffff880`0176ead6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`0318c470 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 STACK_COMMAND: kb FOLLOWUP_IP: afd!AfdReturnBuffer+7f fffff880`040e508f ff153b45fdff call qword ptr [afd!_imp_ExpInterlockedPushEntrySList (fffff880`040b95d0)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: afd!AfdReturnBuffer+7f FOLLOWUP_NAME: MachineOwner MODULE_NAME: afd IMAGE_NAME: afd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4efa9418 FAILURE_BUCKET_ID: X64_0xBE_afd!AfdReturnBuffer+7f BUCKET_ID: X64_0xBE_afd!AfdReturnBuffer+7f Followup: MachineOwner --------- to do 2 SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff88004e73720, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800c2ce1f0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo FAULTING_IP: atikmdag+40f720 fffff880`04e73720 488b81b0020000 mov rax,qword ptr [rcx+2B0h] CONTEXT: fffff8800c2ce1f0 -- (.cxr 0xfffff8800c2ce1f0) rax=fffff880051af098 rbx=000000000000a191 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88004e73720 rsp=fffff8800c2cebd8 rbp=0000000000000000 r8=0000000000000003 r9=0000000000000000 r10=fffff8a0043f9e50 r11=fffff8a0043f9e50 r12=fffffa8006c7b000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282 atikmdag+0x40f720: fffff880`04e73720 488b81b0020000 mov rax,qword ptr [rcx+2B0h] ds:002b:00000000`000002b0=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff88004e9e6f0 to fffff88004e73720 STACK_TEXT: fffff880`0c2cebd8 fffff880`04e9e6f0 : fffffa80`07c08c20 00000024`f80f560e 00000002`00000000 00000000`00000000 : atikmdag+0x40f720 fffff880`0c2cebe0 fffffa80`07c08c20 : 00000024`f80f560e 00000002`00000000 00000000`00000000 fffffa80`086a5528 : atikmdag+0x43a6f0 fffff880`0c2cebe8 00000024`f80f560e : 00000002`00000000 00000000`00000000 fffffa80`086a5528 fffff880`04ebff77 : 0xfffffa80`07c08c20 fffff880`0c2cebf0 00000002`00000000 : 00000000`00000000 fffffa80`086a5528 fffff880`04ebff77 00000000`00000000 : 0x24`f80f560e fffff880`0c2cebf8 00000000`00000000 : fffffa80`086a5528 fffff880`04ebff77 00000000`00000000 00000000`00000000 : 0x2`00000000 FOLLOWUP_IP: atikmdag+40f720 fffff880`04e73720 488b81b0020000 mov rax,qword ptr [rcx+2B0h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+40f720 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f598161 STACK_COMMAND: .cxr 0xfffff8800c2ce1f0 ; kb FAILURE_BUCKET_ID: X64_0x3B_atikmdag+40f720 BUCKET_ID: X64_0x3B_atikmdag+40f720 Followup: MachineOwner --------- A to do 1 PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff87ff94aff89, memory referenced. Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. Arg3: fffff87ff94aff89, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfa100 fffff87ff94aff89 FAULTING_IP: +0 fffff87f`f94aff89 ?? ??? MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: moh.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800a32ae90 -- (.trap 0xfffff8800a32ae90) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000fffe rbx=0000000000000000 rcx=0000000000002c20 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff87ff94aff89 rsp=fffff8800a32b020 rbp=fffffa8007654010 r8=0000000000000000 r9=0000000000010000 r10=fffff8a000326000 r11=fffffa8007cb9180 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po cy fffff87f`f94aff89 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a73c1f to fffff80002ac8d40 STACK_TEXT: fffff880`0a32ad28 fffff800`02a73c1f : 00000000`00000050 fffff87f`f94aff89 00000000`00000008 fffff880`0a32ae90 : nt!KeBugCheckEx fffff880`0a32ad30 fffff800`02ac6e6e : 00000000`00000008 fffff87f`f94aff89 fffff980`1d940000 fffff8a0`00afc620 : nt! ?? ::FNODOBFM::`string'+0x43d41 fffff880`0a32ae90 fffff87f`f94aff89 : fffff880`746c6644 fffff880`00000000 00000200`02eab740 00000000`00000001 : nt!KiPageFault+0x16e fffff880`0a32b020 fffff880`746c6644 : fffff880`00000000 00000200`02eab740 00000000`00000001 00000000`000003d0 : 0xfffff87f`f94aff89 fffff880`0a32b028 fffff880`00000000 : 00000200`02eab740 00000000`00000001 00000000`000003d0 00000000`00000000 : 0xfffff880`746c6644 fffff880`0a32b030 00000200`02eab740 : 00000000`00000001 00000000`000003d0 00000000`00000000 fffffa80`07654010 : 0xfffff880`00000000 fffff880`0a32b038 00000000`00000001 : 00000000`000003d0 00000000`00000000 fffffa80`07654010 ffffffff`80000c20 : 0x200`02eab740 fffff880`0a32b040 00000000`000003d0 : 00000000`00000000 fffffa80`07654010 ffffffff`80000c20 00000000`006c0000 : 0x1 fffff880`0a32b048 00000000`00000000 : fffffa80`07654010 ffffffff`80000c20 00000000`006c0000 00000001`00000000 : 0x3d0 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+43d41 fffff800`02a73c1f cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+43d41 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+43d41 BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+43d41 Followup: MachineOwner --------- A to dziś najnowszy nie wiem juz co mam robpi szajby można dostac ciągle cos innego Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\041212-9048-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available 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 (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`02a63000 PsLoadedModuleList = 0xfffff800`02ca7650 Debug session time: Thu Apr 12 16:52:35.786 2012 (GMT+2) System Uptime: 0 days 2:22:56.910 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8800435fca1, fffff88007150868, fffff880071500c0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800435fca1, The address that the exception occurred at Arg3: fffff88007150868, Exception Record Address Arg4: fffff880071500c0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo FAULTING_IP: dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 fffff880`0435fca1 41c7450004000000 mov dword ptr [r13],4 EXCEPTION_RECORD: fffff88007150868 -- (.exr 0xfffff88007150868) ExceptionAddress: fffff8800435fca1 (dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x0000000000000029) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880071500c0 -- (.cxr 0xfffff880071500c0) rax=fffff8a009864200 rbx=fffffa8008525000 rcx=fffffa8008534690 rdx=fffff8a00a611980 rsi=fffffa8006dc69a0 rdi=fffff8a00a611980 rip=fffff8800435fca1 rsp=fffff88007150aa0 rbp=fffffa800852edb0 r8=0000000000000000 r9=0000000000000000 r10=fffff8a00a611980 r11=fffff8a0093542a0 r12=0000000000000000 r13=f7fff8a00a22c620 r14=0000000000000000 r15=fffff88007150ca0 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x29: fffff880`0435fca1 41c7450004000000 mov dword ptr [r13],4 ds:002b:f7fff8a0`0a22c620=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d11100 ffffffffffffffff FOLLOWUP_IP: dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 fffff880`0435fca1 41c7450004000000 mov dword ptr [r13],4 BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff8800434f5e1 to fffff8800435fca1 STACK_TEXT: fffff880`07150aa0 fffff880`0434f5e1 : fffffa80`08525000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x29 fffff880`07150b00 fffff880`0434de13 : fffff8a0`0a611980 fffffa80`08525000 fffffa80`06dc69a0 fffffa80`08525000 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x59 fffff880`07150b30 fffff880`04349358 : fffffa80`08c60f80 fffffa80`07249220 00000000`00000000 fffff880`07150ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x523 fffff880`07150c50 fffff880`0436716d : fffffa80`00000000 fffffa80`08371010 00000000`00000000 00000000`00000080 : dxgmms1!VidMmiProcessTerminationCommand+0x4c fffff880`07150ca0 fffff880`043663f8 : fffff800`00b96080 fffffa80`06fee010 00000000`00000000 fffffa80`08371010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`07150cd0 fffff880`04365e96 : 00000000`00000000 fffffa80`07249220 00000000`00000080 fffffa80`08371010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`07150d00 fffff800`02d79fda : 00000000`0205c213 fffffa80`08368a10 fffffa80`06a0f740 fffffa80`08368a10 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`07150d40 fffff800`02ad09c6 : fffff800`02c54e80 fffffa80`08368a10 fffff800`02c62cc0 fffff880`033a7730 : nt!PspSystemThreadStartup+0x5a fffff880`07150d80 00000000`00000000 : fffff880`07151000 fffff880`0714b000 fffff880`07150680 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 STACK_COMMAND: .cxr 0xfffff880071500c0 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+29 Followup: MachineOwner --------- 3: kd> lmvm dxgmms1 start end module name fffff880`0432e000 fffff880`04374000 dxgmms1 (pdb symbols) c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb Loaded symbol image file: dxgmms1.sys Mapped memory image file: c:\symbols\dxgmms1.sys\4CE799C146000\dxgmms1.sys Image path: \SystemRoot\System32\drivers\dxgmms1.sys Image name: dxgmms1.sys Timestamp: Sat Nov 20 10:49:53 2010 (4CE799C1) CheckSum: 00047A89 ImageSize: 00046000 File version: 6.1.7601.17514 Product version: 6.1.7601.17514 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: dxgmms1.sys OriginalFilename: dxgmms1.sys ProductVersion: 6.1.7601.17514 FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850) FileDescription: DirectX Graphics MMS LegalCopyright: © Microsoft Corporation. All rights reserved. Nikt nie potrafi mi pomóc???? Cytuj Link to post Share on other sites
Biafra 16739 Napisano 12 Kwietnia 2012 Udostępnij Napisano 12 Kwietnia 2012 No ciężko Cię niestety po tym zdiagnozować... Trzeba przekładać części i sprawdzać szukając winowajcy. BSODY wyglądają na dosyć losowe. Na wstępie update biosa i firmware do SSD (choć ten samsung na bank nie powoduje tej zawieruchy). Cytuj Link to post Share on other sites
Recommended Posts
Dołącz do dyskusji
Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.