yasminarose
27-01-2013, 18:09
السلام عليكم ورحمة الله وبركاتة
كنت قد طرحت سؤال حول مشكلة الشاشة الزرقاء وقراءت الموضوع المتعلق به و عملت زي ما هو مكتوب جربت البرامج بس برضوة ما في فايده و لمن يعمل ريستات وي رجع تظهر هذه الرسالة الي مكتوب فيها
(توقيع المشكلة: اسم الحدث الخاص بالمشكلة: BlueScreen
إصدار نظام التشغيل: 6.1.7601.2.1.0.256.1
معرف الإعدادات المحلية: 1033
معلومات إضافية حول المشكلة:
BCCode: d1
BCP1: 81D8AD3C
BCP2: 00000002
BCP3: 00000000
BCP4: 8FE70707
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
الملفات التي تساعد في وصف المشكلة:
C:\Windows\Minidump\010413-32640-01.dmp
C:\Users\pc.PC2013010404rwa\AppData\Local\Temp\WER-40687-0.sysdata.xml
اقرأ بيان الخصوصية على إنترنت:
https://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0401
إذا لم يكن بيان الخصوصية عبر إنترنت متوفراً, الرجاء قراءة بيان الخصوصية دون اتصال:
C:\Windows\system32\ar-SA\erofflps.txt)
اما بخصوص المعلومات المطلوبة من اجل تشخيص المشكلة فهي كالتالي:
- نظام التشغيل ونوعه 32 bit win 7 ultimate
2- مضاد الفيروسات الذى استخدمة و إصداره node 4 الاصدار الرابع
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة
(DDR2 - 1024 byet)
name company STAREX
4- موديل المازربورد و أسم الشركة المنتجة
وال Rev (ستجده مكتوب على الأستيكر الموجود على العلبة أو على الطرف السفلى الأيسر للمازربورد)
Rev = 2.1
اسم الشركة المصنعه لها :ITZR motherboerd
الموديل
Rev 945GCHA-478
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة
INTEL 82852/82855 GM/GME
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات
model ATX-400w p4
230v
50Hz
بالنسبة لقوة الباور انت طلبت انها تكون بالوات بس انا لمن شفت الباور ما لقيت اي رقم مكتوب جنبة وات وكتبت الارقام السابقة الا هي قيمة الدخل و الخرج
وهذة الرسالة التي ظهرت لمن جربت برنامج فحص الاخطاء
(Crash Dump Analysis--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/22/2013 5:30:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-30218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21A516)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A52516, 0xFFFFFFFF80DA1C2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 1/22/2013 1:57:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-68359-01.dmp
This was probably caused by the following module: hal.sys (hal+0x5BA9)
Bugcheck code: 0x50 (0xFFFFFFFFA4E1E000, 0x0, 0xFFFFFFFF8284AE13, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: hal.sys .
Google query: hal.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 1/22/2013 1:17:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-28921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x214880)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A31880, 0xFFFFFFFFA9C0394C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 2:51:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-32218-01.dmp
This was probably caused by the following module: hal.sys (hal+0x5BAA)
Bugcheck code: 0x50 (0xFFFFFFFFA9DE7BAD, 0x0, 0xFFFFFFFF82C17BAA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: hal.sys .
Google query: hal.sys PAGE_FAULT_IN_NONPAGED_AREA
On Mon 1/21/2013 2:34:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-25921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118C4E)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x5C, 0xFFFFFFFFB3C00010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 2:20:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-50593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38C5B)
Bugcheck code: 0xA (0xFFFFFFFF8393E73C, 0x2, 0x1, 0xFFFFFFFF8287403A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.
On Mon 1/21/2013 2:16:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-25281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED57)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF7, 0x0, 0xFFFFFFFF82A86B38, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® 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 that cannot be identified at this time.
On Mon 1/21/2013 1:55:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-67562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED52)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801C0000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 1:15:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-28296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118C4E)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x100, 0xFFFFFFFFAEBF9688)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 6:14:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-45843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x640C1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828670C1, 0xFFFFFFFFA4B6D7EC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/20/2013 8:12:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-34843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118F03)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82934F03, 0xFFFFFFFFA54E9B90, 0xFFFFFFFFA54E9770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/20/2013 8:04:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-35031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x24C604)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82AA0604, 0xFFFFFFFFA4FD1934, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/20/2013 7:59:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-28656-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15C7)
Bugcheck code: 0xD1 (0x1800090, 0x2, 0x1, 0xFFFFFFFF8FE215C7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: برنامج تشغيل منفذ USB 1.1 و 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.
On Sun 1/20/2013 7:54:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-31250-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC1ED4)
Bugcheck code: 0x7F (0x0, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: برنامج تشغيل Win32 متعدد المستخدمين
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 that cannot be identified at this time.
On Sun 1/20/2013 2:59:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-50359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x226897)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFA4EE9C04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
50 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has 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:
hal.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.
وشكر للاستجابة السريعة
كنت قد طرحت سؤال حول مشكلة الشاشة الزرقاء وقراءت الموضوع المتعلق به و عملت زي ما هو مكتوب جربت البرامج بس برضوة ما في فايده و لمن يعمل ريستات وي رجع تظهر هذه الرسالة الي مكتوب فيها
(توقيع المشكلة: اسم الحدث الخاص بالمشكلة: BlueScreen
إصدار نظام التشغيل: 6.1.7601.2.1.0.256.1
معرف الإعدادات المحلية: 1033
معلومات إضافية حول المشكلة:
BCCode: d1
BCP1: 81D8AD3C
BCP2: 00000002
BCP3: 00000000
BCP4: 8FE70707
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
الملفات التي تساعد في وصف المشكلة:
C:\Windows\Minidump\010413-32640-01.dmp
C:\Users\pc.PC2013010404rwa\AppData\Local\Temp\WER-40687-0.sysdata.xml
اقرأ بيان الخصوصية على إنترنت:
https://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0401
إذا لم يكن بيان الخصوصية عبر إنترنت متوفراً, الرجاء قراءة بيان الخصوصية دون اتصال:
C:\Windows\system32\ar-SA\erofflps.txt)
اما بخصوص المعلومات المطلوبة من اجل تشخيص المشكلة فهي كالتالي:
- نظام التشغيل ونوعه 32 bit win 7 ultimate
2- مضاد الفيروسات الذى استخدمة و إصداره node 4 الاصدار الرابع
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة
(DDR2 - 1024 byet)
name company STAREX
4- موديل المازربورد و أسم الشركة المنتجة
وال Rev (ستجده مكتوب على الأستيكر الموجود على العلبة أو على الطرف السفلى الأيسر للمازربورد)
Rev = 2.1
اسم الشركة المصنعه لها :ITZR motherboerd
الموديل
Rev 945GCHA-478
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة
INTEL 82852/82855 GM/GME
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات
model ATX-400w p4
230v
50Hz
بالنسبة لقوة الباور انت طلبت انها تكون بالوات بس انا لمن شفت الباور ما لقيت اي رقم مكتوب جنبة وات وكتبت الارقام السابقة الا هي قيمة الدخل و الخرج
وهذة الرسالة التي ظهرت لمن جربت برنامج فحص الاخطاء
(Crash Dump Analysis--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/22/2013 5:30:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-30218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21A516)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A52516, 0xFFFFFFFF80DA1C2C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 1/22/2013 1:57:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-68359-01.dmp
This was probably caused by the following module: hal.sys (hal+0x5BA9)
Bugcheck code: 0x50 (0xFFFFFFFFA4E1E000, 0x0, 0xFFFFFFFF8284AE13, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: hal.sys .
Google query: hal.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 1/22/2013 1:17:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-28921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x214880)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A31880, 0xFFFFFFFFA9C0394C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 2:51:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-32218-01.dmp
This was probably caused by the following module: hal.sys (hal+0x5BAA)
Bugcheck code: 0x50 (0xFFFFFFFFA9DE7BAD, 0x0, 0xFFFFFFFF82C17BAA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: hal.sys .
Google query: hal.sys PAGE_FAULT_IN_NONPAGED_AREA
On Mon 1/21/2013 2:34:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-25921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118C4E)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x5C, 0xFFFFFFFFB3C00010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 2:20:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-50593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38C5B)
Bugcheck code: 0xA (0xFFFFFFFF8393E73C, 0x2, 0x1, 0xFFFFFFFF8287403A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.
On Mon 1/21/2013 2:16:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-25281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED57)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF7, 0x0, 0xFFFFFFFF82A86B38, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® 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 that cannot be identified at this time.
On Mon 1/21/2013 1:55:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-67562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ED52)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801C0000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 1:15:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-28296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118C4E)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x100, 0xFFFFFFFFAEBF9688)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 1/21/2013 6:14:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-45843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x640C1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828670C1, 0xFFFFFFFFA4B6D7EC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/20/2013 8:12:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-34843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x118F03)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82934F03, 0xFFFFFFFFA54E9B90, 0xFFFFFFFFA54E9770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/20/2013 8:04:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-35031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x24C604)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82AA0604, 0xFFFFFFFFA4FD1934, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 1/20/2013 7:59:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-28656-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15C7)
Bugcheck code: 0xD1 (0x1800090, 0x2, 0x1, 0xFFFFFFFF8FE215C7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: برنامج تشغيل منفذ USB 1.1 و 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.
On Sun 1/20/2013 7:54:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-31250-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC1ED4)
Bugcheck code: 0x7F (0x0, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: برنامج تشغيل Win32 متعدد المستخدمين
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 that cannot be identified at this time.
On Sun 1/20/2013 2:59:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-50359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x226897)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFA4EE9C04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
50 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has 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:
hal.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.
وشكر للاستجابة السريعة