Здравейте. Става дума за син екран и грешката, както се подразбира от заглавието на темата. Бях оставил компютъра включен и като се прибирам...ме посреща син екран. ОS Windows 7\64bit SP1. Не съм инсталирал скоро нови програми, не ползвам програми оптимизатори и чистачи на регистри. Заради това съм и малко объркан, как от нищото изниква този син екран. На какво може да се дължи? Виждам win32k.sys, но това нищо не ми говори, както и инфото на което попадам в нета, конкретно за тази грешка. Изтеглих програмата WhoCrashed и това е инфото от дъмп файла:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU E8400 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4293382144 total
VM: 2147352576, free: 1865183232
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 2/6/2012 21:09:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-13618-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x280AD7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002A0AD7, 0xFFFFF88009B40FE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
Conclusion
1 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU E8400 @ 3.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4293382144 total
VM: 2147352576, free: 1865183232
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 2/6/2012 21:09:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-13618-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x280AD7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002A0AD7, 0xFFFFF88009B40FE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
Conclusion
1 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.