Aster utworzono 23 grudnia 2013 utworzono 23 grudnia 2013 Witam czy może mi ktoś wskazać co jest powodem blue screena? Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\122313-15397-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.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`0304fe50 Debug session time: Mon Dec 23 03:02:16.919 2013 (GMT-8) System Uptime: 0 days 14:35:10.230 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960000d4283, fffff88004619060, 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: fffff960000d4283, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88004619060, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: win32k!HmgLockEx+a3 fffff960`000d4283 0fb7430c movzx eax,word ptr [rbx+0Ch] CONTEXT: fffff88004619060 -- (.cxr 0xfffff88004619060) rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8008f72060 rdx=fffff900c0200000 rsi=0000ffffffff0000 rdi=fffff900c0200000 rip=fffff960000d4283 rsp=fffff88004619a40 rbp=0000000000000000 r8=0000000000000001 r9=0000000000000000 r10=0000000000000000 r11=fffff88004619aa8 r12=000000000767ce00 r13=0000000000000000 r14=0000000000000001 r15=0000000000000001 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`000d4283 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 fffff9600028c6b0 to fffff960000d4283 STACK_TEXT: fffff880`04619a40 fffff960`0028c6b0 : fffff900`c2b8f440 00000000`00000001 00000000`0a121633 fffff900`c23be010 : win32k!HmgLockEx+0xa3 fffff880`04619ab0 fffff960`0028bbae : fffff900`c2b8f440 00000000`00000000 00001633`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40 fffff880`04619ae0 fffff960`0028cab3 : 00000000`00000000 00000000`0a121633 fffff900`c2b8f440 00000000`0767ce4c : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e fffff880`04619b20 fffff960`001e95ff : 00000000`00000000 fffff900`c010a010 fffff900`c2b8f440 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b fffff880`04619b60 fffff960`0020a908 : 00000000`00000001 00000000`00000001 fffff880`04619ca0 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f fffff880`04619ba0 fffff800`02e83153 : fffffa80`08f72060 fffff880`04619ca0 00000000`000000bc fffffa80`08f64610 : win32k!NtGdiHLSurfSetInformation+0x1a8 fffff880`04619c20 000007fe`ff164efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`01e2f808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff164efa FOLLOWUP_IP: win32k!HmgLockEx+a3 fffff960`000d4283 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 0xfffff88004619060 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3 BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3 Followup: MachineOwner
Youki komentarz 23 grudnia 2013 komentarz 23 grudnia 2013 Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 ) To powoduje problem odpowiadając na pytanie.
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.