Bluescreen od 3 dni

Wszelkie problemy komputerowe, których nie można jednoznacznie sklasyfikować do wybranego działu
vermanek

Użytkownik
Posty: 5
Rejestracja: 17 paź 2014, 10:54

Bluescreen od 3 dni

Post17 paź 2014, 10:56

Witam! Od trzech dni po wyłączeniu gry (Counter-Strike:GO), lub komputera wywala mi bluescreena. Dodatkowo dodam, że nie zawsze, ale od 3 dni miałem już 5 bluescreenów.

Odczyt ostatniego pliku minidump:

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101714-15615-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Fri Oct 17 02:03:15.304 2014 (GMT+2)
System Uptime: 0 days 7:31:39.599
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c23fd030, 0, fffff9600029c69d, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff900c23fd030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600029c69d, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f080e0
 fffff900c23fd030

FAULTING_IP:
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`0029c69d 488b4f20        mov     rcx,qword ptr [rdi+20h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005b0f8e0 -- (.trap 0xfffff88005b0f8e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c2b81250
rdx=00000000021221ad rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600029c69d rsp=fffff88005b0fa70 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000410 r10=fffff80002c60000
r11=000000000000001f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d:
fffff960`0029c69d 488b4f20        mov     rcx,qword ptr [rdi+20h] ds:1250:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d51024 to fffff80002cd0700

STACK_TEXT: 
fffff880`05b0f778 fffff800`02d51024 : 00000000`00000050 fffff900`c23fd030 00000000`00000000 fffff880`05b0f8e0 : nt!KeBugCheckEx
fffff880`05b0f780 fffff800`02cce7ee : 00000000`00000000 fffff900`c2b81250 fffffa80`35616c00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x427f7
fffff880`05b0f8e0 fffff960`0029c69d : 00000000`00000000 00000000`021221ad 00000000`021221ad 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`05b0fa70 fffff960`0029bbae : fffff900`c2b81250 00000000`00000000 000021ad`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d
fffff880`05b0faa0 fffff960`0029cab3 : 00000000`00000000 00000000`021221ad fffff900`c2b81250 00000000`06c001a8 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`05b0fae0 fffff960`001f95ff : 00000000`00000000 fffff900`c00c1010 fffff900`c2b81250 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`05b0fb20 fffff960`0021a908 : 00000000`00000001 00000000`00000001 fffff880`05b0fc60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`05b0fb60 fffff800`02ccf953 : fffffa80`085ae060 fffff880`05b0fc60 00000000`000000e0 00000000`06c001a8 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`05b0fbe0 000007fe`fdbc4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`024bf688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdbc4efa


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`0029c69d 488b4f20        mov     rcx,qword ptr [rdi+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

FAILURE_BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

Followup: MachineOwner
---------


Proszę o pomoc!

Awatar użytkownika
djkamil09061991

Globalny Moderator
Posty: 8250
Rejestracja: 18 lut 2009, 11:54
Lokalizacja: Wrocław
Kontaktowanie:

Bluescreen od 3 dni

Post17 paź 2014, 11:03

Problemem niby jest sterownik od karty graficznej, tak więc przeinstaluj go na inną wersje, nowszą lub starszą.

vermanek

Użytkownik
Posty: 5
Rejestracja: 17 paź 2014, 10:54

Bluescreen od 3 dni

Post17 paź 2014, 18:13

Właśnie ostatnio aktualizowałem sterownik do wersji: Catalyst Software Suite V14.9
Przeinstaluje, a jak nie pomoże to wgram starszą wersję.

-- 17 paź 2014, 18:13 --

UPDATE: Niestety 5 minut temu kolejny bluescreen.

LOGI:

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101714-20467-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Fri Oct 17 18:07:21.971 2014 (GMT+2)
System Uptime: 0 days 6:32:20.251
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000144283, fffff88006bbb030, 0}

Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000144283, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006bbb030, 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:
win32k!HmgLockEx+a3
fffff960`00144283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff88006bbb030 -- (.cxr 0xfffff88006bbb030)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8008609060
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000144283 rsp=fffff88006bbba00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88006bbba68 r12=0000000003a87600 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`00144283 0fb7430c        movzx   eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff960002fc6b0 to fffff96000144283

STACK_TEXT: 
fffff880`06bbba00 fffff960`002fc6b0 : fffff900`c548ab20 00000000`00000001 ffffffff`e4122319 fffff900`c4fdb010 : win32k!HmgLockEx+0xa3
fffff880`06bbba70 fffff960`002fbbae : fffff900`c548ab20 00000000`00000000 00002319`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`06bbbaa0 fffff960`002fcab3 : 00000000`00000000 ffffffff`e4122319 fffff900`c548ab20 00000000`03a876e0 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`06bbbae0 fffff960`002595ff : 00000000`00000000 fffff900`c00c1010 fffff900`c548ab20 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`06bbbb20 fffff960`0027a908 : 00000800`00000001 00000000`00000001 fffff880`06bbbc60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`06bbbb60 fffff800`02ccb953 : fffffa80`08609060 00000000`0218f570 000007fe`fa95d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`06bbbbe0 000007fe`fdce4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0218efc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdce4efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00144283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!HmgLockEx+a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

STACK_COMMAND:  .cxr 0xfffff88006bbb030 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

Followup: MachineOwner
---------


Awatar użytkownika
XMan

Globalny Moderator
Posty: 13385
Rejestracja: 30 lis 2008, 00:40

Bluescreen od 3 dni

Post17 paź 2014, 18:29

Kto pyta - nie błądzi, kto szuka - znajduje.
Obrazek
Dostępne tylko dla zarejestrowanych użytkowników

Awatar użytkownika
djkamil09061991

Globalny Moderator
Posty: 8250
Rejestracja: 18 lut 2009, 11:54
Lokalizacja: Wrocław
Kontaktowanie:

Bluescreen od 3 dni

Post17 paź 2014, 19:27

Dalej coś czepia się do grafy.
Podaj temperatury z programu HWMonitor.
Chodź według mnie to chyba przez dysk bo w innym temacie wyszło chyba że do wymiany.

vermanek

Użytkownik
Posty: 5
Rejestracja: 17 paź 2014, 10:54

Bluescreen od 3 dni

Post17 paź 2014, 22:47

Temat z dyskiem: sprzet-komputerowy/problem-z-dyskiem-t31733.html

Jutro postaram się sprawdzić pamięć.



  • Reklama

Wróć do „Problemy”



Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 2 gości