Crash Dump Analysis
--------------------------------------------------------------------------------Crash dump directory: C:\WINDOWS\MinidumpCrash dumps are enabled on your computer.
On Thu 06/09/2012 09:44:15 م GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini090712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1568C
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF9568C8, 0xFFFFFFFFAF83DC00, 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.
On Tue 07/08/2012 01:36:03 م GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1568D5)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF9568D5, 0xFFFFFFFFB3414C00, 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.
On Sun 11/12/2011 10:23:11 ص GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini121111-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x155332)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF955332, 0xFFFFFFFFA5DCAC00, 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.
On Fri 21/10/2011 08:59:09 ص GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102111-01.dmp
This was probably caused by the following module: kl1.sys (kl1+0x44E87)
Bugcheck code: 0xC2 (0x7, 0xCD4, 0x0, 0xFFFFFFFF88B05E0
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: kl1.sys .
Google query: kl1.sys BAD_POOL_CALLER
On Sun 24/10/2010 07:35:54 م GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102410-01.dmp
This was probably caused by the following module: klif.sys (klif+0x2C6C3)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFE8, 0x1, 0xFFFFFFFF805266CA, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klif.sys .
Google query: klif.sys CUSTOM_ERROR --------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------5 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: kl1.sys klif.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.
كما و قمت بعمل الاجراءات الاخرى و هي موضحة بالصور التالية :
المفضلات