صفحة 3 من 4 الأولىالأولى 1 2 3 4 الأخيرةالأخيرة
النتائج 31 إلى 45 من 51

الموضوع: صوت بالجهاز عند تشغيله

  1. #31
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    حملت ولازالت المشكله قائمه ..

    يمكن من الجهاز ايش الحل ..

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

    رد: صوت بالجهاز عند تشغيله

    حمل هذا البرنامج >>> https://www.4shared.com/file/19378020...bhardware.html

    ثم شغل البرنامج و أدخل على التبويب Health و أنتظر لمدة دقيقة ثم أرفع صورة لنتيجة الفحص

  3. #33
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

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

    أدخل على هذا الموضوع >>> https://arabhardware.net/forum/showthread.php?t=256987

    وطبق الخطوات الموجودة به ثم أكتب البيانات المطلوبة و ألصق التقرير بداخله و سأرد عليك بحل مشكلتك بأذن الله
    Crash Dump Analysis



    Crash dump
    directory: C:\windows\Minidump


    Crash
    dumps are enabled on your computer.


    On Sun 12/4/2011 7:59:19 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\120411-29718-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x4E
    (0x99, 0x87264, 0x2, 0x794DA)
    Error: PFN_LIST_CORRUPT
    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 the page frame number (PFN)
    list is corrupted.
    This appears to be a typical software driver bug and is
    not likely to be caused by a hardware problem. This might be a case of memory
    corruption. More often memory corruption happens because of software errors in
    buggy drivers, not because of faulty RAM modules.
    The crash took place in
    the Windows kernel. Possibly this problem is caused by another driver which
    cannot be identified at this time.


    On Sun 12/4/2011 7:59:19 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:
    0x4E (0x99, 0x87264, 0x2, 0x794DA)
    Error: PFN_LIST_CORRUPT
    Bug check description: This
    indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem
    is caused by another driver which cannot be identified at this time.

    نوع الجهاز لابتوب موديل satellite c655-s9532d من توشيبا

    نظام التشغيل ويندوز 7 , 64 بت

    مضاد الفايروسات norton 2012 الاصدار 19.2.0.10

    وهذي صور للمعلومات المطلوبه











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

    رد: صوت بالجهاز عند تشغيله

    أخى إذا قرأت المشاركات السابقة ستجد نصائح كثيرة أخبرناك بها لم تقوم بعمل أى شئ منها

    أولاً قم بعمل الخطوات الموجودة بهذه المشاركة >>> https://arabhardware.net/forum/showt...07#post2072607

    ثانياً قم بعمل فحص للهارد و الرام و الشرح موجود بداخل هذا الموضوع >>> https://arabhardware.net/forum/showthread.php?t=256987

    وأريد منك صورتين واحدة لنتيجة فحص الرام وواحدة لنتيجة فحص الهارد

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

  5. #35
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    صور فحص الهارد





    والحين اسوي فحص للرام أول مايخلص بنزل النتائج

  6. #36
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    فحصت الرام وماطلع فيه أي مشكله

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

    رد: صوت بالجهاز عند تشغيله

    قم بتطبيق جميع الخطوات الموجودة فى هذه المشاركة >>> https://arabhardware.net/forum/showt...07#post2072607

    ثم قم بتنصيب التعريفات الموجودة فى هذه المشاركة >>> https://arabhardware.net/forum/showt...04#post2065104

  8. #38
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    راح اجرب واشوف

  9. #39
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    اخوي تيربو ظهرت لي شاشة زرقاء جديده

    والكود تبعها هو : stop:01000001A

    طبعاً الكود مو مكتوب مضبوط بس هذا الي قدرت اشوفه من الشاشة الزرقاء الي طلعت لي ..

    يآليت حل ..

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

    رد: صوت بالجهاز عند تشغيله

    هل قمت بتنصيب التعريفات التى أعطيتها لك سابقاً ؟

    هل تقوم بتحديث الويندوز دورياً ؟

    وما هو نوع الباورسبلاى الذى تستخدمه و قدرته بالوات ؟

    --------------------------------------------------------------------------

    الكود الذى ذكرته خاطئ أريد منك فى كل ظهور للشاشة الزرقاء أن تدخل على برنامج WhoCrashed وتقوم بعمل Analyze ثم تقوم بنسخ التقرير ولصقه بداخل الموضوع

  11. #41
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    شاشة زرقاء ظهرت لي

    الكود الخاص بها

    0x0000007E

    التقرير

    Crash dump directory:
    C:\windows\Minidump

    Crash
    dumps are enabled on your computer.


    On Tue 12/13/2011 1:02:16 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\121311-30139-01.dmp
    This
    was probably caused by the following module: igdkmd64.sys (igdkmd64+0xC916E)
    Bugcheck code:
    0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880050E616E, 0xFFFFF88006335138,
    0xFFFFF88006334990)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path:
    C:\windows\system32\drivers\igdkmd64.sys
    product: Intel Graphics Accelerator Drivers for Windows
    XP(R)

    company: Intel
    Corporation

    description: Intel Graphics Kernel Mode Driver
    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.
    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: igdkmd64.sys
    (Intel Graphics Kernel Mode Driver, Intel Corporation).
    Google query: igdkmd64.sys Intel Corporation
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M





    On Tue 12/13/2011 1:02:16 PM GMT
    your computer crashed

    crash dump file: C:\windows\memory.dmp
    This was
    probably caused by the following module: igdkmd64.sys (igdkmd64!hybDriverEntry+0xC803E)

    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880050E616E,
    0xFFFFF88006335138, 0xFFFFF88006334990)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    file path:
    C:\windows\system32\drivers\igdkmd64.sys
    product: Intel Graphics Accelerator Drivers for Windows
    XP(R)

    company: Intel
    Corporation

    description: Intel Graphics Kernel Mode Driver
    Bug
    check description: This bug check indicates that a system thread generated an
    exception that the error handler did not catch.
    A third party driver was
    identified as the probable root cause of this system error. It is suggested you
    look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel
    Mode Driver, Intel Corporation).
    Google query: igdkmd64.sys Intel Corporation
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED





    On Sat 12/10/2011 7:09:44 PM GMT
    your computer crashed

    crash dump file:
    C:\windows\Minidump\121011-29577-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A
    (0x8886, 0xFFFFFA800385AF10, 0xFFFFFA800385B840, 0x305)
    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 which cannot be identified at this
    time.


    On Fri 12/9/2011 10:49:31 AM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\120911-38438-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50
    (0x28EC000, 0x1, 0x7537A05B, 0x
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.

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

    رد: صوت بالجهاز عند تشغيله

    تابع حل مشكلتك فى هذا الموضوع >>> https://arabhardware.net/forum/showthread.php?t=264583&page=2

    ولا تكرر موضوعك أكثر من مرة

  13. #43
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    يآليت نتابع حل المشكله هنا .. وخلاص تعريف الشاشة ضبط معي ..

    وهذي آخر شاشات زرقاء ظهرت لي ..

    Crash dump directory:
    C:\windows\Minidump

    Crash
    dumps are enabled on your computer.


    On Fri 12/16/2011 3:42:48 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\121611-29530-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50
    (0xFFFFFFFFFFFFFFA0, 0x0, 0xFFFFF8800421D2E8, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.


    On Fri 12/16/2011 3:42:48 PM GMT your computer
    crashed

    crash dump file: C:\windows\memory.dmp
    This was probably
    caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0xBA2

    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFA0, 0x0, 0xFFFFF8800421D2E8,
    0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 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 which cannot be
    identified at this time.


    On Wed 12/14/2011 2:02:27 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\121411-25786-01.dmp
    This
    was probably caused by the following module: iastor.sys (iaStor+0x72046)
    Bugcheck code: 0xD1
    (0xF, 0x2, 0x1, 0xFFFFF880010B3046)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\windows\system32\drivers\iastor.sys
    product: Intel Rapid Storage Technology
    company: Intel
    Corporation

    description: Intel Rapid Storage Technology -
    x64
    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: iastor.sys (Intel Rapid Storage Technology - x64, Intel Corporation).

    Google query: iastor.sys Intel Corporation
    DRIVER_IRQL_NOT_LESS_OR_EQUAL





    On Tue 12/13/2011 1:02:16 PM GMT
    your computer crashed

    crash dump file:
    C:\windows\Minidump\121311-30139-01.dmp
    This was probably caused by the
    following module: igdkmd64.sys (igdkmd64+0xC916E)
    Bugcheck code:
    0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880050E616E, 0xFFFFF88006335138,
    0xFFFFF88006334990)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path:
    C:\windows\system32\drivers\igdkmd64.sys
    product: Intel Graphics Accelerator Drivers for Windows
    7(R)

    company: Intel
    Corporation

    description: Intel Graphics Kernel Mode Driver
    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.
    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: igdkmd64.sys
    (Intel Graphics Kernel Mode Driver, Intel Corporation).
    Google query: igdkmd64.sys Intel Corporation
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M





    On Sat 12/10/2011 7:09:44 PM GMT
    your computer crashed

    crash dump file:
    C:\windows\Minidump\121011-29577-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A
    (0x8886, 0xFFFFFA800385AF10, 0xFFFFFA800385B840, 0x305)
    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 which cannot be identified at this
    time.


    On Fri 12/9/2011 10:49:31 AM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\120911-38438-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50
    (0x28EC000, 0x1, 0x7537A05B, 0x
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.

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

    رد: صوت بالجهاز عند تشغيله

    أخى لقد أخبرتك فى الموضوع الاَخر أن تقوم بالرجوع إلى التحديث القديم لأن اَخر تحديث يوجد به مشاكل كثيرة مع كثير من الأجهزة و شركة أنتل لم تجد له حل حتى الاَن

    أختار موضوع لكى نكمل به

  15. #45
    عضوية جديدة
    تاريخ التسجيل
    Nov 2011
    المشاركات
    57
    معدل تقييم المستوى
    16

    رد: صوت بالجهاز عند تشغيله

    السلام عليكم ورحمة الله وبركاته ..

    أخوي تيربو .. الصوت سجلته ومن هنا تحميل الصوت

    https://www.mediafire.com/?675ctz7mp4j17ne

    طبعاً الصوت يبدأ من الثانيه 4 .. ياليت ترفع الصوت عشان يكون أوضح ..

    وصراحه في ناس يقولو لي ممكن هذا عطل مصنعي .. واغلب الشاشات الزرقاء منه ..

    ياليت تفيدني بخبرتك وايش اقدر اسوي في هالحاله ..

    وعندك هذا أخر شاشات زرقاء ظهرت لي ..

    Crash dump directory:
    C:\windows\Minidump

    Crash
    dumps are enabled on your computer.


    On Sat 12/31/2011 5:45:13 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\123111-19500-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x7F (0x8,
    0x80050033, 0x6F8, 0xFFFFF80002A8BC10)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    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 Intel CPU
    generated a trap and the kernel failed to catch this trap.
    The crash took
    place in the Windows kernel. Possibly this problem is caused by another driver
    which cannot be identified at this time.


    On Sat 12/31/2011 5:45:13 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:
    0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80002A8BC10)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    Bug check description:
    This bug check indicates that the Intel CPU generated a trap and the kernel
    failed to catch this trap.
    The crash took place in the Windows kernel.
    Possibly this problem is caused by another driver which cannot be identified at
    this time.


    On Sat 12/31/2011 3:37:01 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\123111-18907-01.dmp
    This
    was probably caused by the following module: iastor.sys (iaStor+0x72046)
    Bugcheck code: 0xD1
    (0xF, 0x2, 0x1, 0xFFFFF8800115B046)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\windows\system32\drivers\iastor.sys
    product: Intel Rapid Storage Technology
    company: Intel
    Corporation

    description: Intel Rapid Storage Technology -
    x64
    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: iastor.sys (Intel Rapid Storage Technology - x64, Intel Corporation).

    Google query: iastor.sys Intel Corporation
    DRIVER_IRQL_NOT_LESS_OR_EQUAL





    On Thu 12/29/2011 8:14:42 PM GMT
    your computer crashed

    crash dump file:
    C:\windows\Minidump\122911-27487-01.dmp
    This was probably caused by the
    following module: watchdog.sys (watchdog+0x122F)
    Bugcheck code: 0x10E
    (0x1F, 0xFFFFF8A009C05670, 0x0, 0x745D5F)
    Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
    file path:
    C:\windows\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog
    Driver
    Bug check description: This indicates that the video memory manager
    has encountered a condition that it is unable to recover from.
    The crash
    took place in a standard Microsoft module. Your system configuration may be
    incorrect. Possibly this problem is caused by another driver on your system
    which cannot be identified at this time.


    On Mon 12/26/2011 6:55:34 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\122611-23821-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A
    (0x403, 0xFFFFF68000281040, 0x9F900000485EC86F, 0xFFFFF6800028E34
    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 which cannot be identified at this
    time.


    On Mon 12/26/2011 1:40:02 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\122611-26754-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A
    (0x403, 0xFFFFF68000117040, 0xB3F000005FA9486F, 0xFFFFF680001FE3FA)
    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 which cannot be identified at this
    time.


    On Fri 12/23/2011 9:54:47 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\122411-29328-01.dmp
    This
    was probably caused by the following module: win32k.sys (win32k+0xCB3A9)
    Bugcheck code: 0x3B
    (0xC0000005, 0xFFFFF9600019B3A9, 0xFFFFF8800724B140, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 an exception happened while
    executing a routine that transitions from non-privileged code to privileged
    code.
    This appears to be a typical software driver bug and is not likely to
    be caused by a hardware problem.
    The crash took place in a standard
    Microsoft module. Your system configuration may be incorrect. Possibly this
    problem is caused by another driver on your system which cannot be identified at
    this time.


    On Fri 12/16/2011 3:42:48 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\121611-29530-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50
    (0xFFFFFFFFFFFFFFA0, 0x0, 0xFFFFF8800421D2E8, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.


    On Wed 12/14/2011 2:02:27 PM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\121411-25786-01.dmp
    This
    was probably caused by the following module: iastor.sys (iaStor+0x72046)
    Bugcheck code: 0xD1
    (0xF, 0x2, 0x1, 0xFFFFF880010B3046)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path:
    C:\windows\system32\drivers\iastor.sys
    product: Intel Rapid Storage Technology
    company: Intel
    Corporation

    description: Intel Rapid Storage Technology -
    x64
    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: iastor.sys (Intel Rapid Storage Technology - x64, Intel Corporation).

    Google query: iastor.sys Intel Corporation
    DRIVER_IRQL_NOT_LESS_OR_EQUAL





    On Tue 12/13/2011 1:02:16 PM GMT
    your computer crashed

    crash dump file:
    C:\windows\Minidump\121311-30139-01.dmp
    This was probably caused by the
    following module: igdkmd64.sys (igdkmd64+0xC916E)
    Bugcheck code:
    0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880050E616E, 0xFFFFF88006335138,
    0xFFFFF88006334990)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path:
    C:\windows\system32\drivers\igdkmd64.sys
    product: Intel Graphics Accelerator Drivers for Windows
    XP(R)

    company: Intel
    Corporation

    description: Intel Graphics Kernel Mode Driver
    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.
    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: igdkmd64.sys
    (Intel Graphics Kernel Mode Driver, Intel Corporation).
    Google query: igdkmd64.sys Intel Corporation
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M





    On Sat 12/10/2011 7:09:44 PM GMT
    your computer crashed

    crash dump file:
    C:\windows\Minidump\121011-29577-01.dmp
    This was probably caused by the
    following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A
    (0x8886, 0xFFFFFA800385AF10, 0xFFFFFA800385B840, 0x305)
    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 which cannot be identified at this
    time.


    On Fri 12/9/2011 10:49:31 AM GMT your computer
    crashed

    crash dump file: C:\windows\Minidump\120911-38438-01.dmp
    This
    was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x50
    (0x28EC000, 0x1, 0x7537A05B, 0x
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path:
    C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel &
    System
    Bug check description: This indicates that invalid system memory has
    been referenced.
    This appears to be a typical software driver bug and is not
    likely to be caused by a hardware problem.
    The crash took place in the
    Windows kernel. Possibly this problem is caused by another driver which cannot
    be identified at this time.


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

    وأعتذر لك لأنو صراحه أحس اني طفشتك من كثر مواضيعي الي ماتنتهي ..

صفحة 3 من 4 الأولىالأولى 1 2 3 4 الأخيرةالأخيرة

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

  1. مشكله فى لاب توب HP وعدم تشغيله
    بواسطة megoelmeligy في المنتدى مشاكل الحاسب وحلولها
    مشاركات: 2
    آخر مشاركة: 02-10-2013, 21:19
  2. الجهاز لا يعمل عند تشغيله
    بواسطة العربي77 في المنتدى مشاكل الحاسب وحلولها
    مشاركات: 3
    آخر مشاركة: 21-02-2012, 21:45
  3. صوت بالجهاز عند تشغيله
    بواسطة Gorno في المنتدى مشاكل الحاسب وحلولها
    مشاركات: 50
    آخر مشاركة: 07-01-2012, 09:53
  4. الجهاز بطئ عند تشغيله
    بواسطة عبدالله راشد في المنتدى مشاكل الحاسب وحلولها
    مشاركات: 10
    آخر مشاركة: 14-08-2011, 13:45
  5. 8800GT=متطلبات تشغيله
    بواسطة Sority في المنتدى الأرشيف
    مشاركات: 4
    آخر مشاركة: 26-03-2008, 23:19

المفضلات

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

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