تمام يا هندسة الله يطمنك .. انا كنت محتاج رأى حد بيفهم علشان يقولى انها مشكلة سوفت وير
و جارى جربة الطريقة و ان شاء الله ابلغك بالنتيجة
يا اخ احمد معلش كنت محتاج مساعدتك فى موضوع كده ...
انا امبرح نزلت ملف البايوس BIOS من موقع HP الخاص بموديل اللاب بتاعى طبعا علشان احدث البايوسوحصلت حاجة غريبة
لما بدأ يحدث جه عند المرحلة erasing and writing و اللاب وقف و فضل كده بتاع ساعة لكن كانت مروحة اللاب شغالة سريعة جدا كأنى مشغل لعبة تقيلة مثلا ... و لكن الحمدلله لما فصلت عنه الكهربة و فتحته فتح تانى و طبعا بفيرجن البايوس القديم يعنى البايوس متحدثش ولا حاجة ... لكن انا مش عارف هو ليه مرضيش يحدث البايوس ؟ !!
لا ينصح بتحديث البيوس عند صدور أى أصدار جديد إلا إِذا كنت بالفعل تحتاجه ويجب تحديث البيوس فى بيئة الدوس.
مرسل من الهاتف.
حملت برنامجWhoCrashedوضغطت Analyze
ظهر دا
اضغط على ok وسيظهر لك التقرير قم بنسخه ثم ارفق ملفات ال dumb والبيانات المطلوبة الأخرى المطلوبة
مرسل من الهاتف.
بضغط OK بتفضل النافذة الخلفية كما هي ومش بيظهر تقرير
بعد الضغط على زر ok قم بالسحب ببكرة الفارة لأسفل لرؤية تقرير البرنامج، ويبدو أنك وقفت عند نقطة البداية ولم تتخطاها فيبدو أن مشكلتك حلها سيطول.................................
والله العظيم من غير حاجة اكيد نزلت بالماوس دي حاجة بديهيه ..
ومن قبل ماقول لحضرتك انها جاتلي النافذة دي لكن بردو مفيش غير صفحة بيضة بس
عامة شكرا لحضرتك واسف على الازعاج ...............
قم بتطبيق هذه الخطوات واذا ظهرت شاشة زرقاء جديدة ستظهر فى البرنامجالمشاركة الأصلية كتبت بواسطة Mohamed Omarr
https://www.arabhardware.net/forum/s....php?p=2026784
مرسل من الهاتف.
بسم الله الرحمن الرحيم
أولا ها هى البيانات من برنامج WhoCrashed
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 10/09/2013 04:38:56 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\091013-23088-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80075B1A20, 0xFFFFF80000B9C4D8, 0xFFFFFA8006E135C0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 10/09/2013 04:38:56 م GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80075B1A20, 0xFFFFF80000B9C4D8, 0xFFFFFA8006E135C0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Sat 07/09/2013 02:07:34 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\090713-34928-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A004B66000, 0x0, 0xFFFFF80003336079, 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 Sat 07/09/2013 02:06:10 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\090713-31325-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A003566000, 0x0, 0xFFFFF80003338079, 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 Sat 07/09/2013 02:04:34 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\090713-30981-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A013566000, 0x0, 0xFFFFF80003381079, 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 Fri 06/09/2013 10:10:51 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\090713-29250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00BFFE000, 0x0, 0xFFFFF80003384079, 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 Sat 31/08/2013 03:42:27 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\083113-34757-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800BAD0990, 0xFFFFFA800BAD0AB0, 0x4120001)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 that cannot be identified at this time.
Conclusion
7 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.
ثانيا ها هو رابط ملفات الـ Minidump
https://rapidshare.com/files/2554255525/Minidump.rar
ثالثا ها هى مواصفات الجهاز ونظام التشغيل:
1- نظام التشغيل ونوعه ( 32bit | 64bit )
Microsoft Windows 7 Ultimate 64-Bit (Not activated yet)
2- مضاد الفيروسات الذى تستخدمه و إصداره
AVG Antivirus Free 2013.0.3408
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة
G.Skill Ripjaws X 2*4GB (8GB Dual Channel Memory Kit)
4- موديل المازربورد و أسم الشركة المنتجة
Asus P8Z77-V Rev 3.0
وال Rev (ستجده مكتوب على الأستيكر الموجود على العلبة أو على الطرف السفلى الأيسر للمازربورد)
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة
Gainward GeForce GTX 580 "GOOD" Edition
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات
Cooler Master Extreme 2 725 (675W)
مع خالص الشكر والتقدير والمحبة أخى العزيز
أهلا بك أخى
قم أولا بفحص الرام بالطريقة المشروحة فى الموضوع لمدة كافية ويفضل فى الوقت الذى لا تستخدم جهازك فيه نهائيا فى وضع ال safe mode
وعند يصل الفحص إلى 300%بدون ظهور أى رسائل خطأ فأفحص الهارد وإذا كان الهارد سليم قم بتحميل التعريفات الأخيرة لجهازك من موقع الشركة المنتجة ثم قم بحذف التعريفات الحالية ونصب التعريفات الحديثة
وإذا لم تفلح كل الحلول السابقة حمل ويندوز ۔من أول وجديد.
مرسل من الهاتف.
ارجو المساعدة في مشكلة الشاشة الزرقاء والمعلومات كالتاليCrash Dump Analysis
ويندوز 7 بالحزمة الخدمية الاولى 32 بت غير معدلة
مضاد فيروسات microsoft security essential
اللوحة الام جيجابايت GA-945GCMX-S2 v6.6
كارت الشاشة مدمج باللوحة الام
الباور سبلاى من النوع العادي الذي ياتي مع الكيسة واذكر ان ثمنه لايتعدى 50 جنيه مصري
الرامات شريحتين كل شريحة 1 جيجا احدهما لا يظهر اسم الشركة المصنعة لها في برنامج cpu z و هي على سلوت 1 والاخرى كينجستون على سلوت 2 وكلتاهما 400mhz
وتقرير البرنامج هو:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 19/09/2013 06:40:03 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\091913-15771-01.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32+0x3F7BB)
Bugcheck code: 0x131 (0x3, 0xFFFFFFFF86619030, 0xFFFFFFFFFD29B030, 0x0)
Error: INVALID_EXTENDED_PROCESSOR_STATE
file path: C:\Windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: Invalid combination of parameters was detected while saving or restoring extended processor state.
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation INVALID_EXTENDED_PROCESSOR_STATE
On Thu 19/09/2013 02:56:56 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\091913-17659-01.dmp
This was probably caused by the following module: teviisall.sys (TeViiSAll+0x15AD0)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\teviisall.sys
product: TeViiSAll.sys
company: TeVii Technology Ltd.
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: teviisall.sys (TeVii Technology Ltd.).
Google query: TeVii Technology Ltd. UNEXPECTED_KERNEL_MODE_TRAP
On Wed 18/09/2013 01:17:02 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-17316-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x53126)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8595E000, 0xFFFFFFFF8A71397C, 0xFFFFFFFF8A713560)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 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
3 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:
igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
teviisall.sys (TeVii Technology Ltd.)
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.
https://www.4shared.com/rar/8uVMsZt6/New_folder.html
وملفات الدمب في الرابط اعلاه
ghobbosh @
يظهر مشاكل ب 3 تعريفات مختلفة فإما المشكلة من التعريفات أما مشكلة متعلقة بالرام أو الهارد فقم أولاً بتحديث التعريفات الموجودة بجهازك خصوصاً تعريف كارت الشاشة الداخلى وتعريف أى جهاز خارجى تستخدمه مثل كارت الستالايت أو TV Tuner وأى جهاز تقوم بتوصيله عن طريق ال USB - وقم بفحص الرام والهارد كما هو مشروح بأول الموضوع.
التعديل الأخير تم بواسطة Ahmed.Elsayed ; 20-09-2013 الساعة 14:00
ارجو المساعده اخي لاني عندي امتحان بعد 5 ايام ومحتاج اللاب واليو اس بي بيفصل لو شلته من اللاب مش يشتغل لازم ارستر وهوا راكب فى الجهاز
System Information (local)
computer name: WHITEHAT
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4240293888 total
VM: 2147352576, free: 1912758272
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are disabled for your computer.
On Thu 09/26/2013 09:20:04 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-60575-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0xC986)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA8003FF5B50, 0xFFFFF80000B9C3D0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Thu 09/26/2013 06:26:15 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-22370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA8003FFD660, 0xFFFFF800044BC3D0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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
2 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.
قال تعالى (وما اتيتم من العلم الا قليل) صدق الله العظيم
ما هو الجهاز الذى تقوم بتوصيله فى جهازك عن طريق ال usb
مرسل من الهاتف.
ضوابط المشاركة
رد مع اقتباس
المفضلات