Windows 7 bị BSOD, có liên quan file win32k.sys ?

Mình dùng windows 7 Ultimate 64-bit

Trước đây, đã có xảy ra trường hợp BSOD, máy tự restart lại, mình scannow thử nhưng không phát hiện thiếu file.

Sau đó, mình cài Windows Debug, thiết lập lưu mini dump và khoảng 1 thời gian kha khá, tới hôm nay nó lại bị BSOD.

Anh em vui lòng giúp mình trường hợp này với ạ!

Từ file dump, mình trích ra đc thông tin như sau:

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

Loading Dump File [C:WindowsMinidump80710-25053-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:websymbols*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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
Debug session time: Sat Aug 7 13:32:26.774 2010 (UTC + 7:00)
System Uptime: 0 days 3:03:28.241
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001543c7, fffff88009511030, 0}

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

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

1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: fffff960001543c7, Address of the instruction which caused the bugcheck
Arg3: fffff88009511030, 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`001543c7 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff88009511030 -- (.cxr 0xfffff88009511030)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8006e07720
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff960001543c7 rsp=fffff88009511a00 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff88009511a68 r12=0000000003b53a00 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`001543c7 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 fffff9600030c750 to fffff960001543c7

STACK_TEXT:
fffff880`09511a00 fffff960`0030c750 : fffff900`c4b352a0 00000000`00000001 00000000`6b120a1b fffff900`c09b9690 : win32k!HmgLockEx+0xa3
fffff880`09511a70 fffff960`0030bc4e : fffff900`c4b352a0 00000000`00000000 00000a1b`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`09511aa0 fffff960`0030cb53 : 00000000`00000000 00000000`6b120a1b fffff900`c4b352a0 00000000`03b53a60 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`09511ae0 fffff960`00269667 : 00000000`00000000 fffff900`c00bf010 fffff900`c4b352a0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`09511b20 fffff960`0028a940 : 00000800`00000001 00000000`00000001 fffff880`09511c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`09511b60 fffff800`02c80853 : fffffa80`06e07720 00000000`039af6d0 000007fe`f6e0d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`09511be0 000007fe`fd804efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`039af128 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd804efa

FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`001543c7 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: 4bdc4376

STACK_COMMAND: .cxr 0xfffff88009511030 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

Followup: MachineOwner
thuy linh
thuy linh
Trả lời 14 năm trước
File win32k.sys không gây ra BSOD. Theo thông tin debug thì dwm.exe mới là tiến trình gây ra BSOD. Nguyên nhân chủ yếu do phần cứng. Theo mình thì do lỗi card màn hình hoặc lỗi bộ nhớ. Nếu bạn có VGA onboard thì tạm thời xài nó thử. Nếu có 2 thanh RAM chạy kênh đôi thì lần lượt tháo bớt 1 thanh để tìm ra thanh nào bị lỗi.