Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 20-Nov-12 1:58:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112012-15256-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009B3CB30, 0xFFFFFA8009B3CE10, 0xFFFFF800039E4460)
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 Tue 20-Nov-12 5:42:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112012-16551-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009C74060, 0xFFFFFA8009C74340, 0xFFFFF800039C7460)
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 Tue 20-Nov-12 5:40:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112012-16302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80071E4800, 0xFFFFFA80071E4AE0, 0xFFFFF800039D0460)
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.
النظام: Windows 7 Ultimate 64Bit SP1
مضاد الفايروس: Microsoft Security Essentials updated to the latest version
الرامات: Corsair XMS3 4GBx2
البورد: GIGABYTE GA-Z68P-DS3 Rev. 2.0
الكارت: Radeon MSI r6870 Twin Frozr II
الباور: Huntkey x7 900w
ارجو الأفادة و شكرا مقدما
maximum sam @
إذا كان المعالج مكسور سرعته فقم بأرجاعه للوضع الافتراضى وتأكد من أن درجات الحرارة معقولة أثناء الضغط عليه
وقم بفحص الرامات كما هو مشروح بأول الموضوع لمدة ساعة على الأقل
وقم بعمل الخطوات المذكورة بهذه المشاركة >>> https://arabhardware.net/forum/showt...07#post2072607
المشاركة الأصلية كتبت بواسطة Ahmed.Elsayed
نعم مكسور لأني رفعت الرامات الى 1600 يدويا .. لكن رجعت الرامات عادي و عملت ال XMP عال Profile1 هيك صار بشكل تلقائي مكسور السرعة
و ضغطت الرامات الحمد لله لا مشاكل
ذهبت المشكلة الحمد لله , الف شكر الك ..لكن معقول سببها كسر السرعة ؟؟
لو كسر السرعة غير مستقر طبيعى أن تظهر شاشات زرقاء معك.
السلام عليكم
عمل عظيم منك اخي بهذا الموضوع تستحق الشكر والثناء عليه ..
واجهتني مؤخرا مشكلة الشاشة الزرقا (كنت عامل ابجريد لويندوز 8 وثم رجعت اثبت 7 مرة ثانية واثناء التثبيت ظهرت لأول مرة واعدت تثبيت الويندوز من البداية وكل شي سار بشكل طيب لكن بعدها رجعت الشاشة الزرقا بالظهور بين كل فترة واخرى) عموما هذه تفاصيل المشكلة :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 11/23/2012 6:50:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112212-22651-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80035FF850, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 11/23/2012 6:50:42 AM 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: 0x1A (0x41790, 0xFFFFFA80035FF850, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/22/2012 2:49:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112212-22573-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFD900C1C8F840, 0x0, 0xFFFFF80003002B13, 0x7)
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 Thu 11/22/2012 11:02:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112212-10701-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880016B2D79)
Bugcheck code: 0x50 (0xFFFFD8A01110408C, 0x0, 0xFFFFF880016B2D79, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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 11/21/2012 6:12:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112112-22510-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x5005, 0xFFFFF70001080000, 0x9F7, 0x9F
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 11/21/2012 7:42:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112012-22604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80035FF850, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 11/13/2012 12:08:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111312-23103-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002E281EE)
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 Tue 11/13/2012 10:29:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111312-10093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80035FF850, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 11/13/2012 7:34:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111212-24024-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80035FF850, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 11/12/2012 11:35:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111212-25209-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80035FF820, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
1- نظام التشغيل ونوعه ( 32bit | 64bit )
64Bit ويندوز 7
2- مضاد الفيروسات الذى تستخدمه و إصداره
ما استخدم حاليا اي مضاد للفيروسات @@ بس قبل الفورمات االاخير كنت استخدم kingsoft وكانت الشاشة الزرقاء مستمرة بالظهور
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة
Corsair Vengeance 8 GB ( 2 x 4 GB )
4- موديل المازربورد و أسم الشركة المنتجة
ASUS P8Z77-V DELUXE
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة
EVGA GeForce GTX 680 2048MB
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات
Silent Pro Gold by cooler master
600W
ويعطيك العافية
ta9qi @
هذه المشكلة سببها أما الرام أو مشكلة فى التعريفات
فقم بالدخول فى وضع ال Safe Mode وأحذف التعريفات القديمة وقم بتحميل التعريفات الخاصة بويندوز 8 من الموقع الرسمى للشركة المنتجة لكل مكون بجهازك وتنصيبها على جهازك
وقم بفحص كل رامة على حدة كما هو مشروح بأول الموضوع لمدة ساعة على الأقل للتأكد من سلامتهم.
rash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 21/11/2012 1:59:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112112-29827-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDBC)
Bugcheck code: 0x7A (0xFFFFFFFFC0417EC8, 0xFFFFFFFFC0000185, 0x74B3F860, 0xFFFFFFFF82FD9874)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 21/11/2012 1:59:44 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0xDCDBC)
Bugcheck code: 0x7A (0xFFFFFFFFC0417EC8, 0xFFFFFFFFC0000185, 0x74B3F860, 0xFFFFFFFF82FD9874)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe KERNEL_DATA_INPAGE_ERROR
On Sun 18/11/2012 6:57:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111812-193051-01.dmp
This was probably caused by the following module: hdaudio.sys (HdAudio+0x2E7E6)
Bugcheck code: 0x7A (0xFFFFFFFFC0462170, 0xFFFFFFFFC0000185, 0x5248A860, 0xFFFFFFFF8C42E7E6)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\hdaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Function Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 17/11/2012 7:04:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-923775-01.dmp
This was probably caused by the following module: ci.dll (CI+0x77CC)
Bugcheck code: 0x7A (0xFFFFFFFFC0455B70, 0xFFFFFFFFC0000185, 0x35F4B8C0, 0xFFFFFFFF8AB6EE3
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Mon 12/11/2012 1:19:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111212-912637-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCDBC)
Bugcheck code: 0x7A (0xFFFFFFFFC058B018, 0xFFFFFFFFC0000185, 0x412CBBE0, 0xFFFFFFFFB1603000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 08/11/2012 6:36:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110812-896288-01.dmp
This was probably caused by the following module: pciidex.sys (PCIIDEX+0x784A)
Bugcheck code: 0x7A (0xFFFFFFFFC0442BC0, 0xFFFFFFFFC0000185, 0x41D0F860, 0xFFFFFFFF8857884A)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\pciidex.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: PCI IDE Bus Driver Extension
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 08/11/2012 2:49:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110812-888207-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x7A (0xFFFFFFFFC05540B8, 0xFFFFFFFFC0000185, 0x5D0D6BE0, 0xFFFFFFFFAA817000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 08/11/2012 2:03:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110812-878987-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x7A (0xFFFFFFFFC04539F8, 0xFFFFFFFFC0000185, 0x1F68BE0, 0xFFFFFFFF8A73F000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 07/11/2012 9:03:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110812-983477-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBB2E3)
Bugcheck code: 0x7A (0xFFFFFFFFC07D9608, 0xFFFFFFFFC0000185, 0x3CF788C0, 0xFFFFFFFFFB2C1000)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.
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 07/11/2012 1:39:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110712-114988-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8C92C)
Bugcheck code: 0x116 (0xFFFFFFFF84F78118, 0xFFFFFFFF8DA119B0, 0x0, 0xC)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
النظام : windows 7 (32 bit)
مضاد الفيروس : microsoft security essential
الرامات : 2 جيجا بيت
أتمنى ألاقي جواب لمشكلتي
علما انه بديت الاحظ انهيار جهازي لما نزل عندي طروادة وبديت افرمت الجهاز بس صار وضع تعيس ويعلق كتييييير وما يعمل بدء تشغيل على فيستا
بالنهاية نزلت ويندوز 7 مششي الحال نوعا ما بس في خطا 0x00000000
كان يظهر باستمرار !!! ولقيته بالريجستري ! ومن يومين حزفتهم كلهم وسار يتشغل الجهاز بدون مشاكل متل اول ؟!
HanHabil @
أستخدم برنامج مضاد فيروسات قوى مثل Avast أو AVG وقم بتحديثه وفحص جهازك بالكامل
وقم بفحص الهارد للكشف عن وجود قطاعات تالفة وتأكد من وجود مساحة فارغة كافية فى ال C
OS : Windows 8 Pro 64-bit
CPU : AMD FX8120 - 8 Cores - 16 MB Cash - 3.1 GHZ
RAM : Crossair - 8 GB - DDR3
Motherboard : Gigabyte 970A - D3
VGA : Nvidia GT 440 - 512 MB - DDR5
Antivirus : No Antivirus installed
Power Supply : HEC 350 W - with Gamma Case
الجهاز ده انا مجمعة من 3 ايام !!
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 11/24/2012 4:08:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112412-30451-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80079B4060, 0xFFFFF80286999760, 0xFFFFFA800A06FC10)
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 Sat 11/24/2012 4:08:38 PM 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, 0xFFFFFA80079B4060, 0xFFFFF80286999760, 0xFFFFFA800A06FC10)
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 Fri 11/23/2012 10:36:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112312-28782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80079A4060, 0xFFFFF801641B9760, 0xFFFFFA800A34C010)
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 Fri 11/23/2012 9:19:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112312-38438-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A740)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80049C4060, 0xFFFFF8028F679760, 0xFFFFFA8006695460)
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
4 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.
التعديل الأخير تم بواسطة mohameds102004 ; 24-11-2012 الساعة 18:50
mohameds102004 @
أولاً يجب أن تقوم بتنصيب برنامح حماية جيد وتقوم بتحديثه أول بأول
ثانياً قم بتحميل التعريفات الأخيرة الخاصة بويندوز 8 64 بت من موقع الشركة المنتجة للمارربورد وكارت الشاشة.
طيب هوه انا محتاج باور سبلاى اعلى من ده و ممكن يكون هوه المشكلة ولا ايه ؟ علشان مكتوب على علبة كارت الشاشة و علبة المازربورد انهم محتاجين باور سبلاى 550 فيما فوق مش اقل من كدة و انا مشغلهم على 350 ده هيأثر على ايه ؟ و شكراً جداً لمساعدة حضرتك
الكارت ما بيسحبش كتير من الباورسبلاى لكن المعالج بيسحب أكتر من الكارت وهتحتاج باورسبلاى أعلى فقولى أيه الميزانية اللى تقدر تخصصها لشراء باورسبلاى جديد وأنا أقولك أيه النوع الأفضل.
ممكن نقول حاجة فى حدود 500 جنية مثلاً
أحسن باورسبلاى 550 وات فى هذه الفئة السعرية هو XFX ProSeries 550W PSU 80 plus Bronze وسعره 450 جنية فى فى مول سوق العصر.
التعديل الأخير تم بواسطة Ahmed.Elsayed ; 25-11-2012 الساعة 17:48
ارجو المساعدة في مشكلة الشاشة الزرقاء والمعلومات كالتالي
ويندوز 7 بالحزمة الخدمية الاولى 32 بت غير معدلة
مضاد فيروسات افاست المجاني اصدار 7.0.1474
اللوحة الام جيجابايت GA-945GCMX-S2 v6.6
كارت الشاشة مدمج باللوحة الام
الباور سبلاى من النوع العادي الذي ياتي مع الكيسة واذكر ان ثمنه لايتعدى 50 جنيه مصري
الرامات شريحتين كل شريحة 1 جيجا احدهما لا يظهر اسم الشركة المصنعة لها في برنامج cpu z و هي على سلوت 1 والاخرى كينجستون على سلوت 2 وكلتاهما 400mhz
وتقرير البرنامج هو:System Information (local)
computer name: A_A-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 2138628096 total
VM: 2147352576, free: 1975226368
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 25/11/2012 07:41:21 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\112512-15459-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x9F (0x3, 0xFFFFFFFF8608C468, 0xFFFFFFFF82B77AE0, 0xFFFFFFFF86E746B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.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
One crash dump has 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.
ضوابط المشاركة
رد مع اقتباس
المفضلات