صفحة 74 من 82 الأولىالأولى ... 24 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 الأخيرةالأخيرة
النتائج 1,096 إلى 1,110 من 1218

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

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

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

    جرب فحص الرام لفترة أطول لأنى لا أثق فى أى رامات تجارية وقم بأختبار درجات الحرارة فى الخمول وأثناء الضغط على المعالج ببرنامج Prime95

    وقم بتحديث البيوس والتعريفات الخاصة بالمازربورد من موقع الشركة المنتجة >>> https://www.gigabyte.com/products/pr...px?pid=2866#dl

  2. #1097
    عضو
    تاريخ التسجيل
    Jun 2003
    المشاركات
    11
    الدولة: Bahrain
    معدل تقييم المستوى
    0

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

    اقتباس المشاركة الأصلية كتبت بواسطة Ahmed.Elsayed مشاهدة المشاركة
    جرب فحص الرام لفترة أطول لأنى لا أثق فى أى رامات تجارية وقم بأختبار درجات الحرارة فى الخمول وأثناء الضغط على المعالج ببرنامج Prime95

    وقم بتحديث البيوس والتعريفات الخاصة بالمازربورد من موقع الشركة المنتجة >>> https://www.gigabyte.com/products/pr...px?pid=2866#dl
    مرحبا اخي
    آسف على التأخير بسبب بعض المشاغل
    لقد قمت بجميع الخطوات
    [IMG]memtestpic.png[/IMG]

    [IMG]small-fft.png[/IMG]
    [IMG]large-fft.png[/IMG]


    لقد قمت بتحديث درايفر الماذربورد ولكن البيوس لم يقبل التركيب

    و لا زالت الشاشة الزرقاء مستمرة بالظهور

    Crash Dump Analysis

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 12/15/2013 12:44:20 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-29640-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D89406A52E, 0xB3B7465EE684E254, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 12:44:20 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D89406A52E, 0xB3B7465EE684E254, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 11:57:42 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-34601-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D8976BF822, 0xB3B7465EE9EA3558, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 11:13:15 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-27612-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D89654B505, 0xB3B7465EE8D2F23B, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 10:30:01 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-25833-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D8976935F5, 0xB3B7465EE9E7731B, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 9:46:36 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-29608-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D8976EC540, 0xB3B7465EE9ED0266, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 9:03:20 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-28891-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D893BDE53C, 0xB3B7465EE63C2262, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 8:48:07 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-29562-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D893C4B667, 0xB3B7465EE642F38D, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 8:32:22 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-31590-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D893DBD76E, 0xB3B7465EE65A1494, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 8:17:06 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-57080-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D896D6699D, 0xB3B7465EE954A6C3, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 7:33:51 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-61136-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D896C82657, 0xB3B7465EE946638D, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 6:50:35 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-67610-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D8936538AA, 0xB3B7465EE5E375E0, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sun 12/15/2013 6:21:19 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-147904-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D896DD7537, 0xB3B7465EE95BB25D, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sat 12/14/2013 10:19:11 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-89341-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D893A1853B, 0xB3B7465EE61FC261, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION



    On Sat 12/14/2013 9:34:09 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-107016-01.dmp
    This was probably caused by the following module: nt_fffff80000b95000.sys (0xFFFFF80000B96BB0)
    Bugcheck code: 0x109 (0xA3A039D893DD84F8, 0xB3B7465EE65BC22E, 0xFFFFF80000B96BB0, 0x6)
    Error: CRITICAL_STRUCTURE_CORRUPTION
    Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
    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.
    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: nt_fffff80000b95000.sys .
    Google query: nt_fffff80000b95000.sys CRITICAL_STRUCTURE_CORRUPTION




    Conclusion


    51 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

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




  3. #1098
    عضوية جديدة
    تاريخ التسجيل
    Sep 2009
    المشاركات
    1
    الدولة: Egypt
    معدل تقييم المستوى
    0

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

    انا مشكلتى تحدث عندما اقوم بعمل Shut down >> تظهر شاشة زرقاء لمدة ثوانى ثم يعمل ريستارت وليس غلق .. حملت البرنامج الى قلت عليه ونسخت بعد الخطوة الاول وهو :

    Welcome to WhoCrashed (HOME EDITION) v 5.00


    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 allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

    Click here for more information on the professional edition.
    Click here to buy the the professional edition of WhoCrashed.


    System Information (local)


    computer name: USER-PC
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    Hardware: G41T-M13, ECS
    CPU: GenuineIntel Pentium(R) Dual-Core CPU E5700 @ 3.00GHz Intel586, level: 6
    2 logical processors, active mask: 3
    RAM: 2077483008 total
    VM: 2147352576, free: 1950580736




    Crash Dump Analysis


    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 15/12/2013 01:26:29 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121713-14648-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF868D19C8, 0xFFFFFFFF868D1B34, 0xFFFFFFFF82E09FE0)
    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 Sun 15/12/2013 01:26:29 م GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x1E)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF868D19C8, 0xFFFFFFFF868D1B34, 0xFFFFFFFF82E09FE0)
    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.



    On Sun 15/12/2013 01:24:25 م GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-16270-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF86F50808, 0xFFFFFFFF86F50974, 0xFFFFFFFF82E38FE0)
    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 Sun 15/12/2013 11:52:53 ص GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121513-16333-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF86B7E728, 0xFFFFFFFF86B7E894, 0xFFFFFFFF82A2AFE0)
    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.




    Conclusion


    4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    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.




  4. #1099
    إداري الصورة الرمزية MaHmOuD ZeRo
    تاريخ التسجيل
    Sep 2002
    المشاركات
    11,697
    الدولة: Egypt
    معدل تقييم المستوى
    239

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

    شكرآ لك اخى الفاضل
    رافق كل من أراد الخروج من حياتك إلى الباب ...
    وودعه بابتسامة .. وتأكد من أنك أغلقت الباب جيدا




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

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

    بنك دور @

    قم بفك الرام والتنظيف مكانها بأى فرشة ونظف جهازك بالكامل إذا أمكن بجهاز بلاور ثم قم بتنظيف أسنان الرام بأى أستيكة ثم قم بتركيب الرام مرة أخرى

    وإذا لم يفلح الحل السابق فقم بإعادة تحميل الويندوز والتعريفات مرة أخرى وإذا حدثت نفس المشكلة فقم بشراء رامة جديدة لكن من ماركة تجارية معروفة مثل : kingstone أو G-Skill أو Corsair أو A-Data

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

    رد: الحل النهائى لظهور شاشات التوقف الزرقاء

    nsrina @

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

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

    رد: الحل النهائى لظهور شاشات التوقف الزرقاء

    ali yahia @

    ​قم بفحص الرام كما هو مشروح بأول الموضوع وأخبرنى بالنتيجة.

  8. #1103
    عضو
    تاريخ التسجيل
    Jun 2003
    المشاركات
    11
    الدولة: Bahrain
    معدل تقييم المستوى
    0

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

    اقتباس المشاركة الأصلية كتبت بواسطة Ahmed.Elsayed مشاهدة المشاركة
    بنك دور @

    قم بفك الرام والتنظيف مكانها بأى فرشة ونظف جهازك بالكامل إذا أمكن بجهاز بلاور ثم قم بتنظيف أسنان الرام بأى أستيكة ثم قم بتركيب الرام مرة أخرى

    وإذا لم يفلح الحل السابق فقم بإعادة تحميل الويندوز والتعريفات مرة أخرى وإذا حدثت نفس المشكلة فقم بشراء رامة جديدة لكن من ماركة تجارية معروفة مثل : kingstone أو G-Skill أو Corsair أو A-Data

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

  9. #1104
    مخالف للقوانين
    تاريخ التسجيل
    May 2013
    المشاركات
    189
    الدولة: Egypt
    معدل تقييم المستوى
    0

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

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 12/28/2013 5:58:09 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122813-20280-01.dmp
    This was probably caused by the following module: avnetflt.sys (avnetflt+0x2257)
    Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF88D14646)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\avnetflt.sys
    product: Avira Product Family
    company: Avira Operations GmbH & Co. KG
    description: Avira WFP Network 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.
    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: avnetflt.sys (Avira WFP Network Driver, Avira Operations GmbH & Co. KG).
    Google query: Avira Operations GmbH & Co. KG DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Sat 12/28/2013 6:53:27 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122813-17206-01.dmp
    This was probably caused by the following module: xantiarp.sys (xAntiArp+0x1C85)
    Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF88D1E646)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\xantiarp.sys
    product: Windows (R) 2000 DDK driver
    company: Windows (R) 2000 DDK provider
    description: Sample NDIS 4.0 Intermediate Miniport 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.
    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: xantiarp.sys (Sample NDIS 4.0 Intermediate Miniport Driver, Windows (R) 2000 DDK provider).
    Google query: Windows (R) 2000 DDK provider DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Sat 12/28/2013 6:47:05 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122813-17331-01.dmp
    This was probably caused by the following module: xantiarp.sys (xAntiArp+0x1C85)
    Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFFFFF88CFB646)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\xantiarp.sys
    product: Windows (R) 2000 DDK driver
    company: Windows (R) 2000 DDK provider
    description: Sample NDIS 4.0 Intermediate Miniport 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.
    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: xantiarp.sys (Sample NDIS 4.0 Intermediate Miniport Driver, Windows (R) 2000 DDK provider).
    Google query: Windows (R) 2000

  10. #1105
    مخالف للقوانين
    تاريخ التسجيل
    May 2013
    المشاركات
    189
    الدولة: Egypt
    معدل تقييم المستوى
    0

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

    ثم قم بالدخول على المجلد C:\Windows\Minidump وقم بالتعليم على كل الملفات الموجود فى هذا المجلد وقم بضغطهم كما هو موضح

    https://www.4shared.com/get/8PLmBlx3...sMinidump.html

    نظام التشغيل Windows 7 32bit
    Avira Ultimate Protection Suite 2014
    الرامات Kingston2G
    التعديل الأخير تم بواسطة ahmedelbehery ; 28-12-2013 الساعة 21:05

  11. #1106
    عضو خبير بالمعاملات التجاريه
    Trusted Seller
    الصورة الرمزية arrow92
    تاريخ التسجيل
    Dec 2013
    المشاركات
    6,850
    الدولة: Egypt
    معدل تقييم المستوى
    132

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

    انا ظهرت معايا مره شاشه زرقا وعمل ريستارت ومش ظهرت تانى
    لحد دلوقتى مش عارف المشكله كانت منين

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

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

    اقتباس المشاركة الأصلية كتبت بواسطة ahmedelbehery مشاهدة المشاركة
    ثم قم بالدخول على المجلد C:\Windows\Minidump وقم بالتعليم على كل الملفات الموجود فى هذا المجلد وقم بضغطهم كما هو موضح

    https://www.4shared.com/get/8PLmBlx3...sMinidump.html

    نظام التشغيل Windows 7 32bit
    Avira Ultimate Protection Suite 2014
    الرامات Kingston2G
    برنامج ال.AntiARP متعارض مع برنامج ال Avira فأمسح أى منهم أو حمل نسخة مختلفة.

    مرسل عن طريق الهاتف.

  13. #1108
    مخالف للقوانين
    تاريخ التسجيل
    May 2013
    المشاركات
    189
    الدولة: Egypt
    معدل تقييم المستوى
    0

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

    اقتباس المشاركة الأصلية كتبت بواسطة Ahmed.Elsayed مشاهدة المشاركة
    برنامج ال.AntiARP متعارض مع برنامج ال Avira فأمسح أى منهم أو حمل نسخة مختلفة.

    مرسل عن طريق الهاتف.

    حذفت AntiARP و تكررت المشكلة مرتين اليوم ( شاشة زرقاء و بعدها restart )

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

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

    اقتباس المشاركة الأصلية كتبت بواسطة arrow92 مشاهدة المشاركة
    انا ظهرت معايا مره شاشه زرقا وعمل ريستارت ومش ظهرت تانى
    لحد دلوقتى مش عارف المشكله كانت منين
    أعطنى البيانات المطلوبة بأول الموضوع + تقرير برنامج WhoCrashed

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

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

    اقتباس المشاركة الأصلية كتبت بواسطة ahmedelbehery مشاهدة المشاركة
    حذفت AntiARP و تكررت المشكلة مرتين اليوم ( شاشة زرقاء و بعدها restart )
    أعطنى آخر تقرير لبرنامج WhoCrashed لأطلع عليه.

صفحة 74 من 82 الأولىالأولى ... 24 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 الأخيرةالأخيرة

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

  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

المفضلات

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

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