BSOD dwm.exe

[XenLin]

Jako, że to mój pierwszy post tutaj to witam wszystkich bardzo serdecznie! Z drugiej strony z góry przepraszam, jeśli pomyliłem działy czy też taki sam problem się przewinął - widocznie za słabo szukałem (aczkolwiek wujek google nie dawał żadnych konkretów).

Przechodząc już do problemu - otóż zakupiłem sobie nowego laptopa MSI GP60 Leopard i zainstalowałem Win7 64bit. Po jakimś czasie zaczęły się pojawiać upierdliwe BSODy wyskakujące w różnych momentach.

Dzisiaj:

Kod: Zaznacz cały

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


Loading Dump File [C:\Windows\Minidump\122314-18985-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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0320c000 PsLoadedModuleList = 0xfffff800`03449e50
Debug session time: Tue Dec 23 17:56:15.284 2014 (GMT+1)
System Uptime: 0 days 5:18:27.689
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000666cf9, fffff880066bd0d0, 0}

Probably caused by : cdd.dll ( cdd!DrvAssociateSharedSurface+35 )

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

2: 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: fffff96000666cf9, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880066bd0d0, 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:
cdd!DrvAssociateSharedSurface+35
fffff960`00666cf9 44394e10        cmp     dword ptr [rsi+10h],r9d

CONTEXT:  fffff880066bd0d0 -- (.cxr 0xfffff880066bd0d0)
rax=fffff96000666cc4 rbx=0000000000000000 rcx=fffff900c28dbce8
rdx=0000000080007380 rsi=0000005b5a022e68 rdi=fffff900c2d35648
rip=fffff96000666cf9 rsp=fffff880066bdab0 rbp=fffff900c28dbce8
 r8=ffffffffa21215d4  r9=026a080000002e68 r10=0000000002ebf760
r11=fffff880066bdb08 r12=ffffffffa21215d4 r13=0000000080007380
r14=0000000004f30460 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
cdd!DrvAssociateSharedSurface+0x35:
fffff960`00666cf9 44394e10        cmp     dword ptr [rsi+10h],r9d ds:002b:0000005b`5a022e78=????????
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 fffff960001f77bd to fffff96000666cf9

STACK_TEXT: 
fffff880`066bdab0 fffff960`001f77bd : 00000000`00000000 fffff900`c2d355b0 00000000`02ebf800 026a0800`00002e68 : cdd!DrvAssociateSharedSurface+0x35
fffff880`066bdb10 fffff960`0021a969 : 00000000`00000001 fffff880`066bdc60 00000000`02ebf800 00000000`00007fac : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880`066bdb60 fffff800`0327d153 : fffffa80`0c252060 fffffa80`0df9fcd0 fffffa80`0dea0960 fffffa80`00000000 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`066bdbe0 000007fe`ff244efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02ebf738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff244efa


FOLLOWUP_IP:
cdd!DrvAssociateSharedSurface+35
fffff960`00666cf9 44394e10        cmp     dword ptr [rsi+10h],r9d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cdd!DrvAssociateSharedSurface+35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94

STACK_COMMAND:  .cxr 0xfffff880066bd0d0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_cdd!DrvAssociateSharedSurface+35

BUCKET_ID:  X64_0x3B_cdd!DrvAssociateSharedSurface+35

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


Dzisiaj 5h przed powyższym przypadkiem:

Kod: Zaznacz cały

Loading Dump File [C:\Windows\Minidump\122314-21840-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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0325f000 PsLoadedModuleList = 0xfffff800`0349ce50
Debug session time: Tue Dec 23 12:37:17.075 2014 (GMT+1)
System Uptime: 0 days 17:11:51.479
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001a4283, fffff88009021020, 0}

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

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

0: 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: fffff960001a4283, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009021020, 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`001a4283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff88009021020 -- (.cxr 0xfffff88009021020)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800e1d0b60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff960001a4283 rsp=fffff88009021a00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88009021a68 r12=0000000003031a00 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`001a4283 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 fffff9600035c6b0 to fffff960001a4283

STACK_TEXT: 
fffff880`09021a00 fffff960`0035c6b0 : fffff900`c2249a40 00000000`00000001 00000000`7012115b fffff900`c20ff4b0 : win32k!HmgLockEx+0xa3
fffff880`09021a70 fffff960`0035bbae : fffff900`c2249a40 00000000`00000000 0000115b`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`09021aa0 fffff960`0035cab3 : 00000000`00000000 00000000`7012115b fffff900`c2249a40 00000000`03031ae0 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`09021ae0 fffff960`002b95ff : 00000000`00000000 fffff900`c00c0010 fffff900`c2249a40 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`09021b20 fffff960`002da908 : 00000800`00000001 00000000`00000001 fffff880`09021c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`09021b60 fffff800`032d0153 : fffffa80`0e1d0b60 00000000`023cf9c0 000007fe`f979d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`09021be0 000007fe`fe5b4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`023cf418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe5b4efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`001a4283 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 0xfffff88009021020 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

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

0: 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: fffff960001a4283, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009021020, 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`001a4283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff88009021020 -- (.cxr 0xfffff88009021020)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800e1d0b60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff960001a4283 rsp=fffff88009021a00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88009021a68 r12=0000000003031a00 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`001a4283 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 fffff9600035c6b0 to fffff960001a4283

STACK_TEXT: 
fffff880`09021a00 fffff960`0035c6b0 : fffff900`c2249a40 00000000`00000001 00000000`7012115b fffff900`c20ff4b0 : win32k!HmgLockEx+0xa3
fffff880`09021a70 fffff960`0035bbae : fffff900`c2249a40 00000000`00000000 0000115b`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`09021aa0 fffff960`0035cab3 : 00000000`00000000 00000000`7012115b fffff900`c2249a40 00000000`03031ae0 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`09021ae0 fffff960`002b95ff : 00000000`00000000 fffff900`c00c0010 fffff900`c2249a40 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`09021b20 fffff960`002da908 : 00000800`00000001 00000000`00000001 fffff880`09021c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`09021b60 fffff800`032d0153 : fffffa80`0e1d0b60 00000000`023cf9c0 000007fe`f979d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`09021be0 000007fe`fe5b4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`023cf418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe5b4efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`001a4283 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 0xfffff88009021020 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

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

0: kd> lmvm win32k
start             end                 module name
fffff960`000e0000 fffff960`003ef000   win32k     (pdb symbols)          c:\symbols\win32k.pdb\A9F6403F14074E9D8A07D0AA6F0C1CFF2\win32k.pdb
    Loaded symbol image file: win32k.sys
    Mapped memory image file: c:\symbols\win32k.sys\4A5BC5E030f000\win32k.sys
    Image path: \SystemRoot\System32\win32k.sys
    Image name: win32k.sys
    Timestamp:        Tue Jul 14 01:40:16 2009 (4A5BC5E0)
    CheckSum:         002FE623
    ImageSize:        0030F000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    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:     win32k.sys
    OriginalFilename: win32k.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Multi-User Win32 Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.


I kolejny sprzed dwóch dni...

Kod: Zaznacz cały

Loading Dump File [C:\Windows\Minidump\122114-22011-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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`03494e50
Debug session time: Sun Dec 21 23:26:38.179 2014 (GMT+1)
System Uptime: 0 days 13:03:51.829
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001b4283, fffff880056bc020, 0}

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

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

2: 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: fffff960001b4283, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880056bc020, 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`001b4283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff880056bc020 -- (.cxr 0xfffff880056bc020)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800e0f9b60
rdx=fffff900c0200000 rsi=0000004400520000 rdi=fffff900c0200000
rip=fffff960001b4283 rsp=fffff880056bca00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff880056bca68 r12=000000000052cd00 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`001b4283 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 fffff9600036c6b0 to fffff960001b4283

STACK_TEXT: 
fffff880`056bca00 fffff960`0036c6b0 : fffff900`c2234b20 00000000`00000001 ffffffff`cf121079 fffff900`c1fa3870 : win32k!HmgLockEx+0xa3
fffff880`056bca70 fffff960`0036bbae : fffff900`c2234b20 00000000`00000000 00001079`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`056bcaa0 fffff960`0036cab3 : 00000000`00000000 ffffffff`cf121079 fffff900`c2234b20 00000000`0052cdb0 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`056bcae0 fffff960`002c95ff : 00000000`00000000 fffff900`c00c0010 fffff900`c2234b20 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`056bcb20 fffff960`002ea908 : 00000800`00000001 00000000`00000001 fffff880`056bcc60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`056bcb60 fffff800`032c8153 : fffffa80`0e0f9b60 00000000`02e4f960 000007fe`f933d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`056bcbe0 000007fe`fdc14efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02e4f3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdc14efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`001b4283 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 0xfffff880056bc020 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

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

Mam tego więcej - pojawiają się nieregularnie. Raz komputer chodzi cały dzień pod obciążeniem (gra + muzyka + Chrome z ~10 zakładkami), innym razem uruchomię go i po 5 sekundach łapię BSODa.
Generalnie z tego co udało mi się doczytać z tych dumpów to nawala w kółko:
- dwm.exe
- cdd.dll
- win32k.sys

Przeglądając forum (nim zdecydowałem się napisać) ktoś sugerował, iż problemy mogą być z RAM - przeskanowałem MemTestem, nic nie pokazał. HDD nie skanowałem (czasochłonne zadanie z racji 1TB pojemności).
Wujek google podawał także, żeby posprawdzać sterowniki - wszystkie obecnie mam aktualne (lub polecane jako najlepsze do podzespołów) za wyjątkiem GeForce'a aczkolwiek wątpię, żeby to on był tutaj problemem.

Pora na pytania:
1. Wszystkie 3 problemy dotyczą plików systemowych - instalacja nie poszła dobrze? Komputer był surowy, Win7 zainstalowałem z płytki. Zaznaczam, że na dysku obecnie mam pliki, które mocno są mi potrzebne na uczelnię i formatowanie dla mnie może być problematyczne - w ostateczności jeśli to rozwiąże problem to przeboleję bieganie za wykładowcami.
2. HDD - Toshiba MQ01ABD100. Dysku nie skanowałem - prosiłbym o polecenie jakiegoś dobrego programu do wykonania skanu i jeżeli program należy uruchomić podczas rozruchu sprzętu to w miarę możliwości przydałoby się, żeby szło program odpalić z pendrive.
Przy okazji - na laptopie mam nalepę "SSD mSata" - wie ktoś jak sprawdzić, czy faktycznie w tym pudle siedzi jakaś kość SSD (najwidoczniej ukryta partycja)? Jeżeli tak, to czy jest możliwość postawienia na tym systemu?
3. To już bardziej przy okazji ale... jako, że specem w tej dziedzinie nie jestem (aczkolwiek prosiłbym też o nie pisanie jak do totalnego nowicjusza), może BIOS? Nie zaglądałem tam jeszcze, może coś jest źle ustawione i są takie problemy? Bardzo prosiłbym o podpowiedzi - na co zwrócić uwagę i jakie wartości powinny być ustawione.

Z góry dziękuję za jakiekolwiek porady co zrobić z tym upierdliwym problemem.
Pozdrawiam!

[djkamil09061991]

Większośc raportów wskazuje na sterownik od grafiki tak więc przeinstaluj te od intela i nvdia:
intel:
Dostępne tylko dla zarejestrowanych użytkowników
nvidia:
Dostępne tylko dla zarejestrowanych użytkowników

[XenLin]

Przeinstalowałem sterowniki i nawet 30 minut nie musiałem czekać.

Kod: Zaznacz cały

Loading Dump File [C:\Windows\Minidump\122414-23275-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03200000 PsLoadedModuleList = 0xfffff800`0343de50
Debug session time: Wed Dec 24 02:06:55.509 2014 (GMT+1)
System Uptime: 0 days 0:37:12.914
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c28d6030, 0, fffff960002ec69d, 0}


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

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

0: 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: fffff900c28d6030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960002ec69d, 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 fffff800034a80e0
 fffff900c28d6030

FAULTING_IP:
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`002ec69d 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:  fffff8800d5f88e0 -- (.trap 0xfffff8800d5f88e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c1ecfa30
rdx=ffffffffe9120fe2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002ec69d rsp=fffff8800d5f8a70 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000002fa6
r11=fffff8800d5f8ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d:
fffff960`002ec69d 488b4f20        mov     rcx,qword ptr [rdi+20h] ds:fa30:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032f11e4 to fffff80003271f00

STACK_TEXT: 
fffff880`0d5f8778 fffff800`032f11e4 : 00000000`00000050 fffff900`c28d6030 00000000`00000000 fffff880`0d5f88e0 : nt!KeBugCheckEx
fffff880`0d5f8780 fffff800`0326ffee : 00000000`00000000 fffff900`c1ecfa30 00000000`00000800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`0d5f88e0 fffff960`002ec69d : 00000000`00000000 fffff900`c0217d30 fffff900`c0217d30 fffff900`c1ecfa30 : nt!KiPageFault+0x16e
fffff880`0d5f8a70 fffff960`002ebbae : fffff900`c1ecfa30 00000000`00000000 00000fe2`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d
fffff880`0d5f8aa0 fffff960`002ecab3 : 00000000`00000000 ffffffff`e9120fe2 fffff900`c1ecfa30 00000000`05001b50 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`0d5f8ae0 fffff960`002495ff : 00000000`00000000 fffff900`c00c2010 fffff900`c1ecfa30 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`0d5f8b20 fffff960`0026a908 : 00000800`00000001 00000000`00000001 fffff880`0d5f8c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`0d5f8b60 fffff800`03271153 : fffffa80`0e058060 00000000`0264fb20 000007fe`f4bad610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`0d5f8be0 000007fe`fdd04efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0264f578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdd04efa


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`002ec69d 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
---------



Jakieś nowe pomysły?
Wracając do poprzedniego posta - dysk skanuję właśnie HDTune aczkolwiek SMART nie pokazuje żadnych problemów (tak na wszelki wypadek). Odnośnie pytania o SSD - nieważne. Poszperałem odnośnie tego modelu i najwidoczniej fabrycznie była wydzielona partycja z sterownikami.

Nowe pytanie - czy MemTest może pokazać błędy pamięci dopiero po kilku cyklach skanowania?

[djkamil09061991]

Dalej niby coś z grafą a daj screena z programu HWMonitor tak aby było wszystko widac

[XenLin]

Kod: Zaznacz cały

Loading Dump File [C:\Windows\Minidump\122514-23587-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`0344ce50
Debug session time: Thu Dec 25 13:03:15.966 2014 (GMT+1)
System Uptime: 0 days 5:28:01.981
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000134283, fffff88008e7a020, 0}

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

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

2: 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: fffff96000134283, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008e7a020, 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`00134283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff88008e7a020 -- (.cxr 0xfffff88008e7a020)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800e367060
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000134283 rsp=fffff88008e7aa00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88008e7aa68 r12=0000000002196700 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`00134283 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 fffff960002ec6b0 to fffff96000134283

STACK_TEXT: 
fffff880`08e7aa00 fffff960`002ec6b0 : fffff900`c21a7570 00000000`00000001 ffffffff`e11211f5 fffff900`c1e3f010 : win32k!HmgLockEx+0xa3
fffff880`08e7aa70 fffff960`002ebbae : fffff900`c21a7570 00000000`00000000 000011f5`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`08e7aaa0 fffff960`002ecab3 : 00000000`00000000 ffffffff`e11211f5 fffff900`c21a7570 00000000`02196760 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`08e7aae0 fffff960`002495ff : 00000000`00000000 fffff900`c00c0010 fffff900`c21a7570 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`08e7ab20 fffff960`0026a908 : 00000800`00000001 00000000`00000001 fffff880`08e7ac60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`08e7ab60 fffff800`03280153 : fffffa80`0e367060 00000000`0279faf0 000007fe`f75cd610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`08e7abe0 000007fe`fda24efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0279f548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fda24efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00134283 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 0xfffff88008e7a020 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

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


Dzisiejsza porcja kłopotów

HWMonitor zwyczajnie wiesza się po uruchomieniu (program nie odpowiada). Jakaś alternatywa, która dostarczy tyle samo informacji?

Edit: W nocy zapuściłem HDTune i nic nie pokazał na dysku.

[cosik_ktosik]

Z HD Tune to daj zawartość okna Health. Co do alternatywy dla HW Monitor, w sumie to AIDA64 ma najlepszy odczyt czujników choć gorszy w prezentacji.

[XenLin]

Z tego co potrafię doczytać wspierając się wujkiem google - problemów nie ma. Martwi mnie jedynie G-sense error.

AIDA

[djkamil09061991]

Ten procek chyba za ciepły, jeśli te temperatury są w spoczynku to dobrze nie jest, max dla tego procka to 100 stopni.

[XenLin]

No tak - zapomniałem powiedzieć. Przy robieniu screena komp był pod sporym obciążeniem (wyjęty z kilku godzinnej hibernacji + odpalona gierka + Chrome + jeszcze jak na złość skan antywirusa). W każdym bądź razie Turbo Boost przetaktował procesor na max 3.4GHz.



Tak to się prezentuje przy odpalonej gierce + Chrome. Bez obciążenia trzyma temperatury 40-45 stopni.

-- 28 gru 2014, 18:00 --

Nie mogę edytować posta powyżej, więc wrzucam w nowym poście.

Kod: Zaznacz cały

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


Loading Dump File [C:\Windows\Minidump\122814-23119-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0324e000 PsLoadedModuleList = 0xfffff800`0348be50
Debug session time: Sun Dec 28 12:59:04.518 2014 (GMT+1)
System Uptime: 0 days 1:24:39.616
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c1e55770, 0, fffff96000736d15, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!DrvAssociateSharedSurface+51 )

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

1: 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: fffff900c1e55770, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000736d15, 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 fffff800034f60e0
 fffff900c1e55770

FAULTING_IP:
cdd!DrvAssociateSharedSurface+51
fffff960`00736d15 399f50070000    cmp     dword ptr [rdi+750h],ebx

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:  fffff88004b26920 -- (.trap 0xfffff88004b26920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff96000736cc4 rbx=0000000000000000 rcx=fffff900c24737d8
rdx=0000000040003140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000736d15 rsp=fffff88004b26ab0 rbp=fffff900c24737d8
 r8=ffffffff9b120dc8  r9=0000000000000040 r10=000000000219f3a0
r11=fffff88004b26b08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cdd!DrvAssociateSharedSurface+0x51:
fffff960`00736d15 399f50070000    cmp     dword ptr [rdi+750h],ebx ds:8020:00000000`00000750=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000333f1e4 to fffff800032bff00

STACK_TEXT: 
fffff880`04b267b8 fffff800`0333f1e4 : 00000000`00000050 fffff900`c1e55770 00000000`00000000 fffff880`04b26920 : nt!KeBugCheckEx
fffff880`04b267c0 fffff800`032bdfee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`04b26920 fffff960`00736d15 : 00000000`0000063c 00000000`00000000 ffffffff`9b120d12 00000000`00000020 : nt!KiPageFault+0x16e
fffff880`04b26ab0 fffff960`002b77bd : 00000000`00000000 fffff900`c2456630 00000000`0219f440 00000040`00000280 : cdd!DrvAssociateSharedSurface+0x51
fffff880`04b26b10 fffff960`002da969 : 00000000`00000001 fffff880`04b26c60 00000000`0219f440 00000000`00007ea6 : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880`04b26b60 fffff800`032bf153 : fffffa80`0e327a20 fffffa80`0e301560 fffffa80`00000000 fffffa80`0e301560 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`04b26be0 000007fe`fd9f4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0219f378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd9f4efa


STACK_COMMAND:  kb

FOLLOWUP_IP:
cdd!DrvAssociateSharedSurface+51
fffff960`00736d15 399f50070000    cmp     dword ptr [rdi+750h],ebx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cdd!DrvAssociateSharedSurface+51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94

FAILURE_BUCKET_ID:  X64_0x50_cdd!DrvAssociateSharedSurface+51

BUCKET_ID:  X64_0x50_cdd!DrvAssociateSharedSurface+51

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


Tym razem cdd.dll ześwirował.

[cosik_ktosik]

A daj zapisane dzienniki podglądu zdarzeń, może tam coś znajdziemy.

[XenLin]

Uhm... W Podglądzie zdarzeń jest masa rzeczy - co konkretnie podać?