On Wed 2011/7/20 下午 12:21:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072011-15646-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x236BCC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000316BCC, 0xFFFFF88003CEC170, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: 多使用者 Win32 驅動程式
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 2011/7/20 下午 12:21:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!XLATEOBJ_cGetPalette+0x4194C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000316BCC, 0xFFFFF88003CEC170, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: 多使用者 Win32 驅動程式
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 2011/7/19 上午 08:43:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071911-16567-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF900CA61D370, 0x0, 0xFFFFF9600026FB54, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 2011/7/18 上午 06:40:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071811-15178-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x56684)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F6684, 0xFFFFF880074B1450, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: 多使用者 Win32 驅動程式
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 2011/7/17 上午 08:00:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-15475-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF900C86ABCA8, 0x0, 0xFFFFF960001BB676, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 2011/7/17 上午 03:01:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-15022-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF900C87285F0, 0x0, 0xFFFFF960000D885F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 2011/7/14 下午 04:46:59 GMT your computer crashed crash dump file: C:\Windows\Minidump\071511-16785-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x766EC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001266EC, 0xFFFFF880076223F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: 多使用者 Win32 驅動程式
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Mon 2011/7/4 下午 06:00:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070511-19203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF8800936A290, 0x0, 0xFFFFF96000112E2F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 2011/7/3 上午 02:06:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070311-20982-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x94BE0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000104BE0, 0xFFFFF8800884AD00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: 多使用者 Win32 驅動程式
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 2011/7/2 下午 02:29:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-29718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80061B3B30, 0xFFFFFA80061B3E10, 0xFFFFF800047DCF40)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.