صفحة 53 من 82 الأولىالأولى ... 3 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 ... الأخيرةالأخيرة
النتائج 781 إلى 795 من 1218

الموضوع: الموضوع الموحد لمشاكل الشاشات الزرقاء

  1. #781
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    ghobbosh @

    الظاهر فى التقرير بأن الشاشة الزرقاء حدثت معك مرة واحدة فإذا ظهرت معك بشكل متكرر فأحتمال كبير أن تكون بسبب الباورسبلاى

    ودائماً أنصح بأستخدام باورسبلاى أحترافى والبعد عن الأنواع التجارية لأن الباورسبلاى هو صمام الأمان لجهاز الكمبيوتر ككل.

  2. #782
    عضو
    تاريخ التسجيل
    Mar 2011
    المشاركات
    251
    الدولة: Egypt
    معدل تقييم المستوى
    0

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    ارجو المساعدة في مشكلة الشاشة الزرقاء والمعلومات كالتالي
    ويندوز 7 بالحزمة الخدمية الاولى 32 بت غير معدلة
    مضاد فيروسات افاست المجاني اصدار 7.0.1474
    اللوحة الام جيجابايت hp
    كارت الشاشة مدمج باللوحة الام
    الباور سبلاى اوريجناللان الكيسه اوريجنال hp
    الرامات شريحتين كل شريحة 2 جيجاddr3
    hp

    .................................................. .........
    Crash Dump Analysis

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Thu 06/12/2012 09:13:59 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120712-13868-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0xACCF6)
    Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88045590, 0xFFFFFFFF88045EF8, 0x92D002A)
    Error: BAD_POOL_HEADER
    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 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 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 06/12/2012 09:13:59 م GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0xACCF6)
    Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88045590, 0xFFFFFFFF88045EF8, 0x92D002A)
    Error: BAD_POOL_HEADER
    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 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 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 06/12/2012 06:59:18 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120612-14024-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF85562280, 0xFFFFFFFF91A4C9B0, 0x0, 0xD)
    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.



    On Wed 05/12/2012 03:20:00 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120512-14788-01.dmp
    This was probably caused by the following module: srs_premiumsound_i386.sys (srs_PremiumSound_i386+0x33E9)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9190C3E9, 0xFFFFFFFF8FDABA00, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\srs_premiumsound_i386. sys
    product: SRS Premium Sound for Windows
    description: SRS Premium Sound 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.
    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: srs_premiumsound_i386.sys (SRS Premium Sound driver, ).
    Google query: srs_premiumsound_i386.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Mon 03/12/2012 11:22:31 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120412-29328-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x79AC2)
    Bugcheck code: 0x19 (0x20, 0xFFFFFFFF85640FB0, 0xFFFFFFFF85641800, 0x90A002A)
    Error: BAD_POOL_HEADER
    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 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 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


    5 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:

    srs_premiumsound_i386.sys (SRS Premium Sound driver, )

    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.




  3. #783
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    kemo840 @

    قم بفحص الرام والهارد كما هو مشروح بأول الموضوع وحمل تعريفات جهازك من موقع الشركة المنتجة HP

  4. #784
    عضو
    تاريخ التسجيل
    Mar 2011
    المشاركات
    251
    الدولة: Egypt
    معدل تقييم المستوى
    0

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء


    Crash Dump Analysis


    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 16/12/2012 07:54:11 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121612-20077-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xF761D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002AFA61D, 0xFFFFF8800331D888, 0xFFFFF8800331D0E0)
    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 16/12/2012 07:54:11 ص 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002AFA61D, 0xFFFFF8800331D888, 0xFFFFF8800331D0E0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
    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 15/12/2012 07:01:05 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121512-22183-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7F140)
    Bugcheck code: 0x1A (0x41287, 0x2078746341, 0x0, 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.




    Conclusion


    3 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.




    بص بقى يا جماعة الشاشة الزرقاء دى مش بتجى غير لم اشغل كارت الدش نوع كارت الدش تونهان اللى هو usp

  5. #785
    عضو
    تاريخ التسجيل
    Mar 2011
    المشاركات
    251
    الدولة: Egypt
    معدل تقييم المستوى
    0

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    وطبعا انا بحثت وراه كارت الشاة وعملت كل حاجه فى الجهاز بس للاسف برضو نفس المشكله
    المشكله الاكبر انى لم اسطب نسخة جديدة اول يوم او يومين يشتغل الجهاز زى الفل مع كل حاجه كارت الدش واللعاب وكل حاجه بس بعد اليومين دول يرجع يعمل نفس الفلم تانى شاشة زرقاء كل ما اشغل كارت الدش

  6. #786
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    kemo840 @

    حضرتك فيه بيانات المفروض بتعرضها فى الأول زى مواصفات جهازك على العموم أذكر أسم الشركة المصنعة لكارت الدش والموديل بالكامل.

  7. #787
    عضو
    تاريخ التسجيل
    Mar 2011
    المشاركات
    251
    الدولة: Egypt
    معدل تقييم المستوى
    0

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    تونهان ده اسم الشركة المصنعة لكرت الدش
    الموديل:azurewave(ad-sb200) usb

  8. #788
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    اقتباس المشاركة الأصلية كتبت بواسطة kemo840 مشاهدة المشاركة
    تونهان ده اسم الشركة المصنعة لكرت الدش
    الموديل:azurewave(ad-sb200) usb
    جرب هذا التعريف >>> https://www.azurewave.com/driver/Dig...1.4_RTM_CD.rar

  9. #789
    عضو
    تاريخ التسجيل
    Mar 2011
    المشاركات
    251
    الدولة: Egypt
    معدل تقييم المستوى
    0

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    نفس الكلام يا باشا بس
    بقى يطول شويه يعنى كان ممكن الاول يفضل شغال نصف ساعة دلوقتى بقى يشتغل ساعة ساعة ونصف

  10. #790
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    اقتباس المشاركة الأصلية كتبت بواسطة kemo840 مشاهدة المشاركة
    نفس الكلام يا باشا بس
    بقى يطول شويه يعنى كان ممكن الاول يفضل شغال نصف ساعة دلوقتى بقى يشتغل ساعة ساعة ونصف
    أنت شغال على نظام تشغيل أيه ؟ و نظام 32 بت ولا 64 بت ؟

  11. #791
    عضو برونزي الصورة الرمزية mawedahmed
    تاريخ التسجيل
    Jul 2012
    المشاركات
    413
    الدولة: Egypt
    معدل تقييم المستوى
    16

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    ارجو الحل وها هى الرسالة
    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Tue 25/12/2012 01:50:09 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122512-19515-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009A7BA60, 0xFFFFFA8009A7BD40, 0xFFFFF80002DC8D50)
    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 25/12/2012 01:50:09 ص 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: 0xF4 (0x3, 0xFFFFFA8009A7BA60, 0xFFFFFA8009A7BD40, 0xFFFFF80002DC8D50)
    Error: CRITICAL_OBJECT_TERMINATION
    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.




    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.
    اسم الرامة kingston 8 gb 1600
    اسم الماذر gigabyte z77x d3h rev1.0
    اسم الكارت ati5450
    اسم الوندوز 7 64bit
    اسم الحماية trend micro titanium internet security
    التعديل الأخير تم بواسطة mawedahmed ; 25-12-2012 الساعة 04:17

  12. #792
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    mawedahmed @

    تأكد من درجات حرارة مكونات جهازك كما هو موضح بأول الموضوع.

  13. #793
    عضو الصورة الرمزية zezo22
    تاريخ التسجيل
    Nov 2009
    المشاركات
    292
    الدولة: Egypt
    معدل تقييم المستوى
    15

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء


    الوندوز 7 بيتا 32
    الرامات 2جيجا ديدى ار 2
    البرسوسورpentium(R) Dual-core CPU Es700 @ 3.00ghz 3.00Ghz
    كرت الشاشة اى تى اى سيريس 5400



    Crash Dump Analysis



    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Wed 19/12/2012 07:34:04 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121912-13946-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8AF075C4, 0xFFFFFFFF8AF071A0, 0xFFFFFFFF88E2F36E)
    Error: NTFS_FILE_SYSTEM
    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 a problem occurred in the NTFS file system.
    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 19/12/2012 07:34:04 م GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8AF075C4, 0xFFFFFFFF8AF071A0, 0xFFFFFFFF88E2F36E)
    Error: NTFS_FILE_SYSTEM
    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 a problem occurred in the NTFS file system.
    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 19/12/2012 03:27:17 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121912-16520-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xE063E)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F3187B, 0xFFFFFFFF9ED7FAFC, 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 Sun 16/12/2012 07:25:44 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121612-19078-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xD341
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82F2D87B, 0xFFFFFFFF9AEF3484, 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 Sun 16/12/2012 01:11:18 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121612-34117-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF9C63B464, 0xFFFFFFFF9C63B040, 0xFFFFFFFF88C2736E)
    Error: NTFS_FILE_SYSTEM
    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 a problem occurred in the NTFS file system.
    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 13/12/2012 02:27:57 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121312-14913-01.dmp
    This was probably caused by the following module: Unknown (0x00000000)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8665D3D4, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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.
    A third party driver was identified as the probable root cause of this system error.
    Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Wed 12/12/2012 01:39:25 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121212-13322-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8AD0F644, 0xFFFFFFFF8AD0F220, 0xFFFFFFFF88C4136E)
    Error: NTFS_FILE_SYSTEM
    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 a problem occurred in the NTFS file system.
    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 04/12/2012 09:27:53 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120412-12589-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8AD0B644, 0xFFFFFFFF8AD0B220, 0xFFFFFFFF88C1836E)
    Error: NTFS_FILE_SYSTEM
    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 a problem occurred in the NTFS file system.
    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 02/12/2012 06:58:04 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120212-13306-01.dmp
    This was probably caused by the following module: Unknown (0x00000000)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8664AC14, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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.
    A third party driver was identified as the probable root cause of this system error.
    Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Sat 01/12/2012 11:39:01 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120112-13462-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12044)
    Bugcheck code: 0x19 (0x20, 0xFFFFFFFF9E2CE228, 0xFFFFFFFF9E2CE260, 0xA070605)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    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 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 30/11/2012 09:55:40 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\113012-14944-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xB0CD3)
    Bugcheck code: 0x50 (0xFFFFFFFFFE492000, 0x0, 0xFFFFFFFF94D60CD3, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 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 Fri 30/11/2012 05:23:16 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\113012-13509-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x238366)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E71366, 0xFFFFFFFF8A7FBBAC, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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 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 25/11/2012 06:14:13 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112512-13353-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9
    Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF865E4030, 0xFFFFFFFF865E419C, 0xFFFFFFFF82E6DE10)
    Error: CRITICAL_OBJECT_TERMINATION
    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 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 24/11/2012 08:20:29 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112412-14960-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x238366)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E71366, 0xFFFFFFFF8C8F6BAC, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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 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 Sat 24/11/2012 08:19:05 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112412-14695-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF9B5E9394, 0xFFFFFFFF9B5E8F70, 0xFFFFFFFF88C2B36E)
    Error: NTFS_FILE_SYSTEM
    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 a problem occurred in the NTFS file system.
    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


    42 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:

    udst7000bda.sys (AzureWave USB, AzureWave Provide)
    atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
    eamon.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.



    هناك عضويات على مواقع تورنت رائعة للبيع و عضويات جديدة
    لمن يرغب فل يراسلنى على الخاص و من يرغب فى عروض و اشياء للعبة كونكر اون :ah2:لاين ايضا وشكرا:ah40:

  14. #794
    إداري سابق الصورة الرمزية Ahmed.Elsayed
    تاريخ التسجيل
    Apr 2011
    المشاركات
    8,156
    الدولة: Egypt
    معدل تقييم المستوى
    210

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    zezo22 @

    قم بفحص الهارد والرام كما هو مشروح بأول الموضوع.

  15. #795
    عضو
    تاريخ التسجيل
    Oct 2009
    المشاركات
    135
    معدل تقييم المستوى
    0

    رد: الموضوع الموحد لمشاكل الشاشات الزرقاء

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Thu 12/27/2012 2:30:08 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\Mini122712-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6A3C4)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805413C4, 0xFFFFFFFFB5272CF0, 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 Wed 12/26/2012 5:08:56 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\Mini122612-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6A3C4)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805413C4, 0xFFFFFFFFB5D8CCF0, 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


    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.




    نظام التشغيل 32 بت واول مرة تحصل المشكلة على هذا نظام ولكنى قومت بتغيير الرامات قريبا

    مضاد الفيروسات : لا يوجد حالياُ

    حجم الرام : 2*2 كينج ستون هايبر أكس باص 1600 cl9 ولكنها تعمل على البوردة بتردد 1333

    موديل المازر بورد : gigabyte ep43T-ud3l

    كارت الشاشة: خارجى nvidia ge force 8400 gs

    الباور سبلاى مش ماركة ولكنه جيد الى حد ما ولا يوجد به اى مشاكل

صفحة 53 من 82 الأولىالأولى ... 3 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 ... الأخيرةالأخيرة

المواضيع المتشابهه

  1. الموضوع الموحد عن كسر E5300
    بواسطة snow leopard في المنتدى الأرشيف
    مشاركات: 11
    آخر مشاركة: 15-07-2011, 22:50
  2. الموضوع الموحد لتغطيه معرض E3
    بواسطة coolhero في المنتدى الأرشيف
    مشاركات: 58
    آخر مشاركة: 18-06-2011, 22:00
  3. الموضوع الموحد لمراجعات الاعضاء
    بواسطة coolhero في المنتدى الأرشيف
    مشاركات: 0
    آخر مشاركة: 08-06-2011, 04:20

المفضلات

ضوابط المشاركة

  • لا تستطيع إضافة مواضيع جديدة
  • لا تستطيع الرد على المواضيع
  • لا تستطيع إرفاق ملفات
  • لا تستطيع تعديل مشاركاتك
  •