السلام عليكم
المشكلة اللي عندي هي انو عندما اريد ان اثبت الوينداوز و في مرحلة ما تظهر رسالة تقول أن الهارد ديسك غيرموجود ويجب التحقق منه ومن الأسفل F3: exit , بعد محاولتين أو ثلاث ظهرت الشاشة الزرقاء مع هذا الكود 000007B*0
تطلب التحقق من الفيروسات وبلابلابلا رغم ان عند الخول الى البيوس تجد انو يطلع حجم نوع وبعض المعلومات عن الهارد ديسك.لمن عنده علم نرجو الإفادة
بارك الله فيكم
هل تستخدم هارد ساتا أم هارد قديم داتا ؟المشاركة الأصلية كتبت بواسطة noufal
السلام عليكم و رحمة الله و بركاته
اولا شكرا على هذا الموضوع الطيب .. و الذي يساعد الكثير منا على حل مشكلاتهم المماثلة ..
على كل حال ..
واجهتني مشكلة الشاشة الزرقاء اضافة الى مشاكل اخرى ..
ساذكر اولا المعلومات المطلوبة بالنسبة لمشكلة الشاشة الزرقاء .. و من ثم سأذكر المشاكل التي صادفتها و هل للاثنين صلة ببعض ..
1- نظام التشغيل ونوعه:
(32) Microsoft Windows XP Professional / X86-based PC
2- مضاد الفيروسات الذى تستخدمه و إصداره :
Norton Antivirus Online الإصدار: 19.8.0.14
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة :
1024 ميجا / لا تظهر اسم الشركة
4- موديل المازربورد و أسم الشركة المنتجة :
Intel - D945GCNL
وال Rev : لم اجده او انني لم استدل عليه .. و لكن من خلال البرنامج CPU-Z تبين لي التالي:
Chipset : A2
SouthBridge: A1
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة:
NVIDIA GeForce 8600 GT
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات:
Mercury - 500 w
بالنسبة للريستارت التلقائي ، فانني لا اواجه هذه المشكلة حاليا ..
و بالنسبة لنتيجة برنامج Who Crashed هي:
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.
1- التاكد من درجة الحرارة ، و تبين لي ان درجة حرارة كرت الشاشة عالية .. لا اعلم اذا كانت صحيحة ام لا
2- فحص الرامات .. و تبين ان هناك مشكلة واحدة .. علما بأنني تركت عملية البحث لمدة تقارب الساعة و قد تجاوزت الـ 300%
3- فحص القرص الصلب ..
اضافة لما سبق ..
اواجه مشكلة البطئ ، فخلال هذه الايام القليلة .. اجد ان متصفح IE بطيء و يتوقف فجأة لبعض الوقت و من ثم يعمل .. و احيانا قد لا يعمل ابدا مما يؤدي ايضا الى توقف الجهاز على حالته دون التمكن من عمل اي شيء .. فلا اجد الا ان اقوم باعادة تشغيل الجهاز ..
و مشكلة اضافية اكتشفتها ..
ان صفحة الـ Device Manager لا تظهر كما في الصور التالية ..
أرجوا منكم المساعدة في حل المشكلة ..
فقد حاولت جاهدا البحث عن طريقة مناسبة ... و لكن دون جدوى .. كما ان الجهاز محدث الى أحدث اصدار لكل شيء حسب علمي لانني لم اجد اي تحديثات موجودة ..
و ان كان الامر يتطلب ايضا لفتح موضوع مستقل ، فالرجاء اعلامي بذلك لاقوم باللازم ..
تحية طيبة
التعديل الأخير تم بواسطة dxline ; 07-09-2012 الساعة 19:40
السلام عليكم
1- نظام التشغيل ونوعهWindows 7, Xp ( 32bit ) المشكلة تحدث في النظامين ولكن المعلومات من 7
2- مضاد الفيروسات الذى تستخدمه و إصداره : ESET Smart Security 5.2.9.1
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة: 2 ×2جيجا Micron Technology (DDR3)
4- موديل المازربورد و أسم الشركة المنتجة Gigabyte G41MT-S2PT
وال Rev (ستجده مكتوب على الأستيكر الموجود على العلبة أو على الطرف السفلى الأيسر للمازربورد) Rev.2.1
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة AMD Radeon HD 6670 ATI
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات SKY ROAD P4 , Model:SR-800W , REV: H01
----------------------------------------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 9/19/2012 10:21:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-13338-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
Bugcheck code: 0x4E (0x99, 0x5809B, 0x3, 0x48945)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 9/18/2012 7:38:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-11980-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xA (0x6777E828, 0x2, 0x1, 0xFFFFFFFF82EB0E24)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 9/17/2012 10:54:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-11544-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xA (0x151083EF, 0x2, 0x1, 0xFFFFFFFF82EC6F4C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 9/17/2012 9:39:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-13728-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xA (0xBD030AD, 0x2, 0x1, 0xFFFFFFFF82EB4E24)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 9/17/2012 5:18:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-17955-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBDC93)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x67E8, 0xB3AF24)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
انا استخدمت البرنامج والنتيجة دى
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 02/10/2012 12:29:29 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\100212-38579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A003D66000, 0x0, 0xFFFFF80002F85079, 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 which cannot be identified at this time.
اما بالنسبة للمعلومات
1- نظام التشغيل ونوعه ( widnows 7 profisional | 64bit )
2- مضاد الفيروسات الذى تستخدمه و إصداره : avg 2013
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة
4- موديل المازربورد و أسم الشركة المنتجة : asus p5g411t-mlx
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة : gainward ggorce 450 gts 1 gb ddr5
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات : hec gamma 450w
مشكلة بسبب ظهور الشاشة ويندوز 7 ؟تظهر مشكلة الشاشة الزرقاء بصقة مستمرة ...
علما بأن ,
نظام التشغيل > Windows 7 professional 64-bit
المازر بورد > G41- Gigabyte كارت الشاشة داخلى مرفق مع البوردة 1Gb
رامات > 4gb .. Kingston
برنامج حماية >Norton Internet Security 2012
عملت Test للرامات و مفيش فيها اى مشكلة .. و عملت فرمات للهارد و قسمتة من الاول برضو الشاشة الزرقاء بتظهر
دى صورة للشاشة الزرقاء و بعض الصور لامكانيات الجهاز ارجو الافادة
https://www.4shared.com/rar/ZGtFPZxp/Z_online.html?
https://rapidshare.com/#!download|11...|Z.rar|671|0|0
مع العلم ان انا استعمل نت Tedata عن طريق Usb modem Speed Touch 330 وجدت صعوبة فى تنصيب التعريف للمودم على ويندوز 7 .. واشك انه السبب لان لما بشيل ال usb الشاشة الزرقاء تقريبا مش بتظهر
لو المشكلة فى تعريف المودم ارجوا الافادة .. وهل المودم ده تعريفه على ال 7 غير ال XP ?!
Usb modem Speed Touch 330
وانا عندي نفس المشكله والرامات 6 جيجا كنجستون والجهاز لا يعمل 10 دقائق متواصله ويفصل اللوحه الام
اسوس 88 يو اس بي 3
والمعالج اي ام دي 555
وعملت كل حاجه في الاقتباس اعلاه ولم يفلح ولكن لما نزلت ويندوز 8 تظهر لي رياله بان هناك مشكله في الهاروير
فهل من اقتراحات؟!!
جزاكم الله خيرا
فى البداية بشكرك على الموضوع الرائع دة
الشاشة الزرقاء بقت بتحصل معايا فى الفترة الاخيرة باستمرار
ولماتكون بتحمل ملف حجمة كبيير شوية من الدونلود مانجر
التحميل لمابيوصل 99 % ويبتدى يجمع اجزاء الملف
الجهاز بيجيب شاشة زرقا ويرستر
وبيحصل تقطيع ساعات والجهاز يتجمد ويجيب شاشة زرقا ويرستر
دة رابط
لامكانيات المازر والرام
لان الرام الشركة المنتجة مش مكتوب
وكمان مرفق بعض الصور للشاشة الزرقاء من جهازى
+ الملفات المطلوبة من ال c
https://www.mediafire.com/?vial6k4xdzc1rfd
النظام ويندوز اكس بى معدل ( elmoders(
نظام 32 bit
الباور u-max
model -atx- 650 w
بس هوة اصلا عادى ابو 45 جنية دة تقريبا
برنامج الفيروس - افاست انترنت سيكورتى اخر اصدار
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 25/02/2013 01:40:24 م GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022513-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x69693)
Bugcheck code: 0xD1 (0xA130040, 0x2, 0x0, 0xFFFFFFFFBA710AF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 25/02/2013 01:40:24 م GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: atapi.sys (atapi+0x5AF2)
Bugcheck code: 0xD1 (0xA130040, 0x2, 0x0, 0xFFFFFFFFBA710AF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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 24/02/2013 11:31:07 م GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022513-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1862B)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89B3D1D0, 0xFFFFFFFF89B3D344, 0xFFFFFFFF805C8CBA)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
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. This problem might be caused by a thermal issue.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software CRITICAL_OBJECT_TERMINATION
Conclusion
3 crash dumps have been found and analyzed. 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:
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
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.
منتظر ردك وان شاء الله تفدنى بحل
لانى تعبت جدا
وناوى ان شاء الله اغير المازر والبروسوسر والرام
لما ربنا يسهل
علشان زهقت من المشكلة دى
رد: الموضوع الموحد لمشاكل الشاشات الزرقاء
السلام عليكم
================================================== =========
عندى مشكلة شاشة الموت الزرقاء
:mad::mad:
================================================== =========
(1)
WhoCrashed
صور :
و معلومات :
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 4.01
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: x-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Celeron(R) D CPU 3.06GHz Intel586, level: 15
1 logical processors, active mask: 1
RAM: 2136465408 total
VM: 2147352576, free: 1990688768
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 12/03/2013 11:32:41 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\031213-13244-01.dmp
This was probably caused by the following module: partmgr.sys (partmgr+0x12BA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82834D86, 0xFFFFFFFF8078AC7C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\partmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Partition Management 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 that cannot be identified at this time.
On Tue 12/03/2013 11:32:41 ص GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeRaiseIrqlToSynchLevel+0x8F)
Bugcheck code: 0x8E (0xFFFFFFFFC000001D, 0xFFFFFFFF82834D86, 0xFFFFFFFF8078AC7C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Tue 12/03/2013 09:03:11 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\031213-18751-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x70C70)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF92BD0C70, 0xFFFFFFFFA9273A38, 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 that cannot be identified at this time.
On Tue 12/03/2013 07:13:56 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\031213-18704-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x9276)
Bugcheck code: 0xD1 (0x3EC, 0x2, 0x1, 0xFFFFFFFF8D526276)
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 Port Driver
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. 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.
و تحميل معلومات txt :
https://www.gulfup.com/?89Ugig
================================================== =========
(2)
C:\Windows\Minidump
صور :
تحميل ملفات dmp
https://www.gulfup.com/?tJhuBx
================================================== =========
(3)
1- نظام التشغيل ونوعه ( 32bit | 64bit )
32bit - windows 7 ultimate
https://im32.gulfup.com/LL3r1.jpg
2- مضاد الفيروسات الذى تستخدمه و إصداره
avast! Internet Security v8.0.1482
https://im32.gulfup.com/R7gB4.jpg
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة
موجود صور كامل في CPUZ
4- موديل المازربورد و أسم الشركة المنتجة
وال Rev (ستجده مكتوب على الأستيكر الموجود على العلبة أو على الطرف السفلى الأيسر للمازربورد)
موجود صور كامل في CPUZ
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة
موجود صور كامل في CPUZ
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات
موجود صور كامل في CPUZ
CPUZ
صور كامل:
================================================== =========
(5)
صور :
================================================== =========
(6)
MemTest
نتيجة فحص الرام
================================================== =========
(7)
HD Tune
نتيجة فحص الهاردسك
صور :
1
2
================================================== =========
(
HWmonitor
نتيجة فحص حرارة الجهاز
صور :
================================================== =========
ممكن حل مشكلة
شاشة الموت الزرقاء
Ahmed Egy @
برجاء إعادة رفع ملفات ال minidumb على أى موقع اَخر للرفع لأن الملفات ترفض التحميل.
السلام عليكم أخى الكريم أحمد السيد
أرجو المساعدة
1- windows 7 ulimate 64 bit.
2-Avast pro Antivirus 6.0.1456
3-MB Asus P5Q P45 Ver 1.03G.
4-Ram 2*2 Giga DDR2 OCZ Gold
Edition bus 1066 Kit.
5- Geforce 9800GT oc - Gigabyte.
6- PSU GOUGAR 700 Watt.
بالنسبة للملف ال Zip مش عرف ارفعه والرابيد شير مش بيرفع معايا هوا والفايل فكتورى.
Crash dump directory: C:\Windows
\Minidump
Crash dumps are enabled on your
computer.
On Tue 4/2/2013 12:07:26 AM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\040213-20529-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004CBD028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Tue 4/2/2013 12:07:26 AM GMT
your computer crashed
crash dump file: C:\Windows
\memory.dmp
This was probably caused by the
following module: hal.dll (hal!
HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004CBD028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Sat 3/23/2013 11:21:39 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\032413-20529-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004D55028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Fri 1/25/2013 11:31:58 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\012613-15631-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004C84028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Fri 12/14/2012 12:37:14 AM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\121412-18813-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt
+0x7EFC0)
Bugcheck code: 0xF4 (0x3,
0xFFFFFA8005B11B30,
0xFFFFFA8005B11E10,
0xFFFFF800031C7460)
Error: CRITICAL_OBJECT_TERMINATION
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 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. 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 Sat 11/10/2012 10:35:26 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\111112-16504-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004C62028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 10/7/2012 7:44:44 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\100712-15693-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004C5B028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Wed 9/26/2012 11:29:12 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\092712-19453-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004A6C028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Wed 9/26/2012 6:39:53 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\092612-17191-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004C52028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Sat 9/22/2012 8:54:07 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\092212-15912-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004CB7028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Sat 9/22/2012 8:21:21 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\092212-29125-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004C11028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Fri 9/21/2012 7:24:02 PM GMT
your computer crashed
crash dump file: C:\Windows
\Minidump\092112-23805-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004C7B028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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 Wed 8/1/2012 2:44:14 AM GMT your
computer crashed
crash dump file: C:\Windows
\Minidump\080112-17612-01.dmp
This was probably caused by the
following module: hal.dll (hal
+0x12A3B)
Bugcheck code: 0x124 (0x0,
0xFFFFFA8004CB4028, 0xB2000040,
0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows
\system32\hal.dll
product: Microsoft® Windows®
Operating System
company: Microsoft Corporation
description: Hardware Abstraction
Layer DLL
Bug check description: This bug
check indicates that a fatal
hardware error has occurred. This
bug check uses the error data that
is provided by the Windows Hardware
Error Architecture (WHEA).
This is likely to be caused by a
hardware problem problem. This
problem might be caused by a
thermal issue.
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.
-----------------------------------
-----------------------------------
----------
Conclusion
-----------------------------------
-----------------------------------
----------
13 crash dumps have been found and
analyzed. No offending third party
drivers have been found. Consider
configuring your system to produce
a full memory dump for better
analysis.
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.
التعديل الأخير تم بواسطة Devastated Soul ; 04-04-2013 الساعة 02:07
حملت برنامجWhoCrashedوضغطت Analyze
ظهر دا
والله العظيم من غير حاجة اكيد نزلت بالماوس دي حاجة بديهيه ..
ومن قبل ماقول لحضرتك انها جاتلي النافذة دي لكن بردو مفيش غير صفحة بيضة بس
عامة شكرا لحضرتك واسف على الازعاج ...............
قم بتطبيق هذه الخطوات واذا ظهرت شاشة زرقاء جديدة ستظهر فى البرنامج
https://www.arabhardware.net/forum/s....php?p=2026784
مرسل من الهاتف.
السلام عليكم ورحمة الله وبركاته
لو سمحت أنا عندي مشكلة بعاني منها جدااااااا ومش لاقيلها أي حل
دايما بتظهرلي رسالة : has stopped working
وكل لما أقفل المسج تطلع تاني لدرجة إنها ممكن تطلع 100 مرة في الدقيقة
وبتخليني مش عارف أشتغل
ياريت لو تعرف تفيدني في الموضوع ده أكون شاكر ليك جدااااااا
التعديل الأخير تم بواسطة Ahmed.Elsayed ; 25-10-2013 الساعة 22:09 سبب آخر: تم تصغير حجم الخط.
ضوابط المشاركة
رد مع اقتباس
المفضلات