رد مع اقتباسsh22 @
قم بفحص الرام لأطول فترة ممكنة كما هو مشروح بأول الموضوع وأفحص الهارد أيضاً للتأكد من سلامته.
a.shata @
قم بحذف البرنامج المتسبب فى هذه المشكلة هو برنامج Folder Security Personal
sh22 @
قم بفحص الرام لأطول فترة ممكنة كما هو مشروح بأول الموضوع وأفحص الهارد أيضاً للتأكد من سلامته.
ممتاز موضوع رائع استفدنا مناا
السلام عليكم ورحمة الله وبركاته:ah8::mad:
انا لابتوبي نوعه اسوس
مشكلتي غريبه جدا وانا لما الان مني قادره استوعب اللي صار
كنت جالسه على اللابتوب وعادي اتصفح الانترنت وشغال زي الحلاوه وقمت اصلي طبعا ماقفلت اللابتوب خليته على صفحتي في النت علشان باارجع لها
ولما رجعت لقيت الخلفيه لونها ازرق وكلام كثير بالانجليزي بس قريت الكلمه الاول problem مشكله في الحاسوب قفلت اللابتوب وطلعت البطاريه ورجعتها
بعدها يشتغل ويطلع شعار اسوس بعدين شعار ويندز وبعدو يقفل ويرجع يعيد يطلع اسوس وبعدين ويندز وزي كذا يعيد ويعيد
ومايطفي الا لما اطلع البطاريه
ارجوكم ابغى حل فجأه صار كذا وفي اللابتوب صور وذكريات ماابغاها تروح من سنين ابغى الحل بتجنن
جربى أولاً الدخول فى الوضع الآمن Safe Mode عن طريق الضغط على F5 قبل إقلاع الويندوز أو الضغط على F8 ثم إختيار Safe Modeالمشاركة الأصلية كتبت بواسطة نهلص
وإذا أستطعت الدخول على ال Safe Mode قومى بإلغاء Auto Restart عن طريق إتباع الخطوات المذكورة فى هذه المشاركة >>> https://arabhardware.net/forum/showt...=1#post2026784
ثم قومى بتحميل برنامج WhoCrashed وإعطائى التقرير الخاص به
وإذا لم تستطيعى الدخول على وضع ال Safe Mode فجربى تحميل ويندوز جديد وإذا لم يقبل فهناك مشكلة فى الهاردوير وتستدعى تدخل مهندس صيانة.
السلام عليكم
انا كان عندى مشكلة فى جهاز كمبيوتر
تقرير من who crashed
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 5/21/2014 11:47:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052114-19359-01.dmp
uptime: 01:04:08
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Wed 5/21/2014 11:47:08 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 01:04:08
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Tue 5/20/2014 9:08:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-18236-01.dmp
uptime: 00:56:58
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Mon 5/19/2014 9:04:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-20186-01.dmp
uptime: 00:06:03
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Sun 5/18/2014 11:34:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-30981-01.dmp
uptime: 00:10:35
This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Sun 5/18/2014 10:01:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-25552-01.dmp
uptime: 01:10:10
This was probably caused by the following module: atikmdag.sys (atikmdag+0x277CE)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
Conclusion
6 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
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.
ملف minidump
https://www.mediafire.com/?4vr23ltznv3zwzw
1- نظام التشغيل ونوعه 64bit windows 7 ultimate
2- مضاد الفيروسات الذى تستخدمه و إصداره norton internet security
3- حجم الرامات التى تستخدمها و أسم الشركة المنتجة 8 رامات kingston 4096X2
4- موديل المازربورد و أسم الشركة المنتجة Gigabyte p75_D3
وال Rev (ستجده مكتوب على الأستيكر الموجود على العلبة أو على الطرف السفلى الأيسر للمازربورد) 1.1
5- أسم كارت الشاشة الذى تستخدمه إذا كان خارجى و أسم الشركة المنتجة AMD Radeon R9 200 series
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات seasonic 600 w
عملت اسكان على MemTest وتمام مفهاش اى حاجة رام
عملت اسكان على HD Tune وتمام مفيش اى حاجة
ارجو الحل اخى فى اقرب وقت
معظم الالعاب 15 او 25 دقيقة وشاشة زرقاء
شكرا
السلام عليكم التقرير من البرنامج
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 05/22/2014 03:57:03 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\052214-33321-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
Bugcheck code: 0x7A (0xFFFFFFFFC05F3318, 0xFFFFFFFFC0000185, 0xFFFFFFFFA1A5C8C0, 0xFFFFFFFFBE663524)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 05/20/2014 10:56:34 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\052114-37487-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x189CE)
Bugcheck code: 0x7A (0xFFFFFFFFC0456DF0, 0xFFFFFFFFC0000185, 0x738CE860, 0xFFFFFFFF8ADBE9CE)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 05/17/2014 02:29:17 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-37518-01.dmp
This was probably caused by the following module: discache.sys (discache+0x3867)
Bugcheck code: 0x7A (0xFFFFFFFFC0680508, 0xFFFFFFFFC0000185, 0x7766A820, 0xFFFFFFFFD00A17B6)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\discache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Indexer/Cache Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 05/14/2014 11:56:39 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\051514-35318-01.dmp
This was probably caused by the following module: bhbase.sys (Bhbase+0x1204)
Bugcheck code: 0x7A (0xFFFFFFFFC06A8510, 0xFFFFFFFFC0000185, 0x6FF9820, 0xFFFFFFFFD50A2004)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\bhbase.sys
product: Baidu Antivirus
company: Baidu, Inc.
description: Baidu Antivirus Hook Base
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bhbase.sys (Baidu Antivirus Hook Base, Baidu, Inc.).
Google query: Baidu, Inc. KERNEL_DATA_INPAGE_ERROR
On Wed 05/14/2014 12:34:27 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\051414-33930-01.dmp
This was probably caused by the following module: discache.sys (discache+0x3867)
Bugcheck code: 0x7A (0xFFFFFFFFC04513A0, 0xFFFFFFFFC0000185, 0x6922A820, 0xFFFFFFFF8A274B66)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\discache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Indexer/Cache Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 05/11/2014 01:03:12 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\051114-34195-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE0A09)
Bugcheck code: 0x7A (0xFFFFFFFFC07F1748, 0xFFFFFFFFC0000185, 0x723FD8C0, 0xFFFFFFFFFE2E9BF0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 05/06/2014 12:15:49 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\050614-32417-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
Bugcheck code: 0x7A (0xFFFFFFFFC0600128, 0xFFFFFFFFC0000185, 0x2DE2B884, 0xFFFFFFFFC00258E
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 04/22/2014 02:37:12 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-29390-01.dmp
This was probably caused by the following module: bhbase.sys (Bhbase+0xF44)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF87BDE648, 0xFFFFFFFF87BDE7B4, 0xFFFFFFFF8386BEB0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\bhbase.sys
product: Baidu Antivirus
company: Baidu, Inc.
description: Baidu Antivirus Hook Base
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.
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: bhbase.sys (Baidu Antivirus Hook Base, Baidu, Inc.).
Google query: Baidu, Inc. CRITICAL_OBJECT_TERMINATION
On Sat 04/19/2014 10:38:44 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-31168-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xACDA7)
Bugcheck code: 0x7A (0xFFFFFFFFC0726688, 0xFFFFFFFFC0000185, 0x2F1EA8C0, 0xFFFFFFFFE4CD1000)
Error: KERNEL_DATA_INPAGE_ERROR
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 bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 04/19/2014 02:04:33 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\041914-31652-01.dmp
This was probably caused by the following module: discache.sys (discache+0x3867)
Bugcheck code: 0x7A (0xFFFFFFFFC063E638, 0xFFFFFFFFC0000185, 0x1A3D3820, 0xFFFFFFFFC7CC7796)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\discache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: System Indexer/Cache Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
19 crash dumps have been found and analyzed. Only 10 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:
bhbase.sys (Baidu Antivirus Hook Base, Baidu, Inc.)
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.
نظام التشغيل ويندوز 7 32 بت انتى فايرس افيرا
https://www.mediafire.com/download/s...New+folder.rar الملفات الى ع السي مضغوطة
Crash dumps are enabled on your computer.
On Mon 26/05/2014 08:25:47 م GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cfosspeed6.sys (cfosspeed6+0x1372E9)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880047572E9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed 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: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cFos Software GmbH DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 25/05/2014 07:34:53 م GMT your computer crashed
crash dump file: C:\Windows\minidump\052514-18314-01.dmp
This was probably caused by the following module: cfosspeed6.sys (0xFFFFF8800476F2E9)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800476F2E9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed 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: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cFos Software GmbH DRIVER_IRQL_NOT_LESS_OR_EQUAL
Conclusion
2 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:
cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH)
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.
دوة بيظهر معاية ممكن اعرف معناة للضرورة
مشكور بارك الله فيك اخي
firstnamebasa @
قم بالدخول فى وضع ال Safe Mode ثم أحذف تعريف كارت الشاشة وأحذف بقاياه ببرنامج Driver Sweeper ثم قم بعمل ريستارت لجهازك وقم بتحميل آخر تعريف لكارت الشاشة من الموقع الرسمى.
samaa hegazy @
قم بحذف برنامج Baidu Antivirus وقم بإتباع الخطوات المذكورة فى هذه المشاركة >>> https://arabhardware.net/forum/showt...07#post2072607
وأفحص الهارد ببرنامج HD Tune للتأكد من سلامته
البسة @
قم بحذف برنامج cFosSpeed وأخبرنى إذا تكررت المشكلة مرة أخرى.
مجهود جبار تسلم ايدك
1- نظام التشغيل Windows 7 Ultimate 32-bit(6.1, Build 7600)
2- مضاد الفيروسات الذى تستخدمه و إصداره(لا يوجد)
3- حجم الرامات التى تستخدمها (2g)
4- المازربورد و أسم الشركة جيجابايت
5- أسم كارت الشاشة(AMD 6670 HD)
6- أسم الشركة المنتجة للباورسبلاى و قدرته بالوات 405 وات
------------------------------------------------------------------------------------
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 08/06/2014 02:27:11 ص GMT your computer crashed
crash dump file: C:\Windows\Minidump\060814-13400-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD9E4B)
Bugcheck code: 0x19 (0x21, 0xFFFFFFFFFDCFC000, 0x2018, 0x5A000)
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.
On Sun 08/06/2014 02:27:11 ص GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLpkInstalled+0x18722)
Bugcheck code: 0x19 (0x21, 0xFFFFFFFFFDCFC000, 0x2018, 0x5A000)
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.
On Sat 07/06/2014 04:26:56 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\060714-13650-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD9E4B)
Bugcheck code: 0x19 (0x21, 0xFFFFFFFFFE7F0000, 0x2018, 0x5A000)
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.
On Sat 07/06/2014 12:15:49 م GMT your computer crashed
crash dump file: C:\Windows\Minidump\060714-13806-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD9E4B)
Bugcheck code: 0x19 (0x21, 0xFFFFFFFFFE845000, 0x2018, 0x5A000)
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
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider 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.
المف المطلوب :
https://
Ahmed9 @
قم أولاً بتحميل برنامج أنتى فيرس مثل Avast أو AVG وقم بفحص جهازك بالكامل للتأكد من خلوه من الفيروسات
ثم قم بفحص الرام فترة طويلة كما هو مشروح فى أول الموضوع للتأكد من سلامتها
التعديل الأخير تم بواسطة Ahmed.Elsayed ; 20-06-2014 الساعة 15:57
ضوابط المشاركة
المفضلات