- Thread Starter
- #21
Crashing-what's causing it
I have had a crash with the BSOD. The screen was on so briefly, I couldn't read what the error.
I ran the software WhoCrashed. I copied and pasted the following
I haven't changed or added any software in months.
Any ideas?
On Mon 4/30/2012 6:41:05 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043012-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x603E8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8603E8, 0xFFFFFFFFA8610B48, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
I have had a crash with the BSOD. The screen was on so briefly, I couldn't read what the error.
I ran the software WhoCrashed. I copied and pasted the following
I haven't changed or added any software in months.
Any ideas?
On Mon 4/30/2012 6:41:05 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini043012-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x603E8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8603E8, 0xFFFFFFFFA8610B48, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.