رد مع اقتباسساعدونيبليز
مشكله الشاشه الزرقاء , جميع البيانات موجوده ان شاء الله
السلام عليكم ورحمه الله
عندي مشكلة شاشه الموت الزرقاء في اللاب توب وهذه بيانات الجهاز أولاً :
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4255502336 total
VM: 2147352576, free: 1969004544
dell inspiron 1440
وهنا ريبورت من برنامج whocrashed عن مشكله الشاشه الزرقاء :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 12/13/2012 9:56:48 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFC0000005)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000337E63A, 0x1, 0x1
Error: KMODE_EXCEPTION_NOT_HANDLED
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: KMODE_EXCEPTION_NOT_HANDLED
On Thu 12/13/2012 6:40:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121312-37986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF800030BE16A, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Sat 12/8/2012 6:57:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120812-38173-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x600DD, 0x2, 0x1, 0xFFFFF800031040C5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 12/8/2012 6:53:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120812-30076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x76E5A, 0x2, 0x1, 0xFFFFF800030C80C5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 12/8/2012 6:49:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120812-30342-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003207740, 0xFFFFF80003207740, 0xFFFFF80003207B40)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 12/8/2012 6:46:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120812-33384-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8004B2FBB0, 0x0, 0x7EFA8000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Sat 12/8/2012 6:40:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120812-22027-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x7399)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030DC39B, 0xFFFFF88002FF5978, 0xFFFFF88002FF51D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 12/7/2012 5:31:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120612-35568-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC5 (0x0, 0x2, 0x0, 0xFFFFF800032106FB)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 12/7/2012 4:44:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120612-35989-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x88641)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF88006ADEA28, 0xFFFFF88006ADE280)
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 Fri 12/7/2012 4:01:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120612-30919-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x20EB, 0x2, 0x1, 0xFFFFF800030BB0C5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 12/5/2012 4:11:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120412-23805-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xDC, 0x2, 0x1, 0xFFFFF800030C20C5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 12/3/2012 2:04:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-23961-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1B7D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000338463A, 0x1, 0x1
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard 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 Mon 12/3/2012 1:03:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-20732-01.dmp
This was probably caused by the following module: msahci.sys (msahci+0x1B7D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000258463A, 0x1, 0x1
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\msahci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MS AHCI 1.0 Standard 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 Mon 12/3/2012 12:57:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-25178-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xC095)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000338163A, 0x1, 0x1
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Mon 12/3/2012 8:59:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120312-19312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xDC, 0x2, 0x1, 0xFFFFF8000310D0C5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
أرجو منكم مساعدتي , وجزاكم الله خيراً
ساعدوني
وعليكم السلام
أخي الكريم
متى بالضبط تظهر لك الشاشة الزرقاء ؟؟ ..
هل عندما تقوم باللعب على احدى الالعاب ؟؟
الرجاء ذكر السبب مع رفع صور لدرجات حرارة الجهاز ببرنامج HW Monitor من هنا وذلك طبعاً بعد ضغط الجهاز لمدة لا تقل عن 10 دقائق.
السلام عليكم
الشاشه الزرقاء تظهر في كل مره اقوم بتشغيل اللابتوب واحيانا (قليلاً جداً) تتأخر في الظهور لمده نص ساعه او ربع ساعه ع الأقل , مثل الان
والطريقه التي تجعلني اؤخر ظهورها بإذن الله هي اني اشغل اللابتوب ثم قبل ان تظهر جميع الايقونات في سطح المكتب اقوم بإغلاق اللاب توب من إبدأ
[IMG][/IMG]
ضوابط المشاركة
المفضلات